Loading...
Loading...
Found 2,889 Skills
Use when a Beat change is implemented and ready to archive — not for verifying implementation
Use when starting a Beat change to create spec artifacts — not for task breakdown, implementation, or exploration
This skill should be used when the user says "interview me about", "help me clarify", "stress-test my idea", "let's explore this concept", "challenge my assumptions about", "grill me on", "drill into my plan", or needs structured questioning to refine and articulate their thinking.
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Generate or update CLAUDE.md from blueprint artifacts. Use when adding team instructions, converting inline content to @imports, or setting up CLAUDE.local.md.
Research an Elixir/Phoenix topic on the web. Searches ElixirForum, HexDocs, blogs, and GitHub. Uses efficient markdown conversion.
Maintain project brain with architectural decisions in memory file.
2. Create Feature Design Document
Execute Solana token trades - market orders, limit/pending orders, copy trading, and order management. Use when user wants to "buy tokens", "sell tokens", "place order", "cancel order", "check order status", "copy trade", "follow wallet", or execute any trading operation.
Document a recently solved problem to compound your team's knowledge
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when creating new skills, editing existing skills, or verifying skills work before deployment