p2p-dev
About
The p2p-dev skill helps developers implement custom P2P networking for DETR in Ëtrid using Rust. It provides scaffolding for peer discovery, messaging protocols, and replacing libp2p with custom logic. Use this skill when you need to build or modify decentralized peer-to-peer networking layers.
Documentation
Quick Install
/plugin add https://github.com/EojEdred/Etrid/tree/main/p2p-devCopy and paste this command in Claude Code to install this skill
GitHub 仓库
Related Skills
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
Remembering Conversations
DevelopmentThis skill enables semantic and text-based search through previous Claude Code conversations to retrieve facts, patterns, and decisions. Developers should use it when a partner references past discussions or when debugging familiar issues to avoid reinventing solutions. It operates on a "search before reinventing" principle and requires using subagents for efficient context management.
huggingface-accelerate
DevelopmentHuggingFace Accelerate provides the simplest API for adding distributed training to PyTorch scripts with just 4 lines of code. It offers a unified interface for multiple distributed training frameworks like DeepSpeed, FSDP, and DDP while handling automatic device placement and mixed precision. This makes it ideal for developers who want to quickly scale their PyTorch training across multiple GPUs or nodes without complex configuration.
nextjs
DevelopmentThis skill provides Next.js architectural standards and enforces the BFF pattern for App Router-based projects. It implements server/client component separation, data fetching strategies, and performance optimizations while ensuring SEO best practices. Use it when designing Next.js applications, implementing Server Actions, route handlers, or establishing clean architecture boundaries between frontend and backend services.
