Loading...
Loading...
Found 653 Skills
Orchestration workflow for orchestrator role ONLY. Use when: - Agent's role name (tmux pane title) is "orchestrator"
Project documentation that stays alive. Read before starting work, update after finishing. Covers project setup, specs, architecture diagrams, and execution plans. Use when starting a project, writing a spec, checking existing docs, updating docs after changes, or when someone says "set up docs", "create a plan", "audit docs", or "init project".
Define a new task with structured requirements before implementation. Use when the user says "define task", "new task", "spec this", or wants to formalize a feature/bug/refactor before planning.
A 10-step methodology for building software with AI collaboration - from north star through automated Ralph loop execution with zero human-in-the-loop code writing
Provides active execution protocols to rigorously audit how code, directory structures, and agent actions comply with the authoritative ecosystem specs. Trigger when validating new skills, plugins, or workflows.
Use when storing project artifacts in basic memory storage.
REST and GraphQL API architect for designing robust, scalable APIs. Use when designing new APIs or improving existing ones.
Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.
Transform feature descriptions into well-structured project plans following conventions
Design distributed systems using Leslie Lamport's rigorous approach. Emphasizes formal reasoning, logical time, consensus protocols, and state machine replication. Use when building systems where correctness under concurrency and partial failure is critical.
Prototype Design Skill
Convert between Skill (SKILL.md) and Prompt (chat box instruction) formats. Supports two-way conversion between Skill→Prompt and Prompt→Skill with zero loss of core information. Use this when users mention Skill to Prompt conversion, Prompt to Skill conversion, format mutual conversion, or SKILL.md conversion.