Loading...
Loading...
Found 95 Skills
Universal context management and planning system. PROACTIVELY activate for: (1) ANY complex task requiring planning, (2) Multi-file projects/websites/apps, (3) Architecture decisions, (4) Research tasks, (5) Refactoring, (6) Long coding sessions, (7) Tasks with 3+ sequential steps. Provides: optimal file creation order, context-efficient workflows, extended thinking delegation (23x context efficiency), passive deep analysis architecture, progressive task decomposition, and prevents redundant work. Saves 62% context on average. Essential for maintaining session performance and analytical depth.
Claude Code AI-assisted development workflow. Activate when discussing Claude Code usage, AI-assisted coding, prompting strategies, or Claude Code-specific patterns.
Use when users say "create a skill", "make a new skill", "build a skill", "skill for X", "package this as a skill", or when refactoring/updating/auditing existing skills that extend agent capabilities with specialized knowledge, workflows, or tool integrations.
[Tooling & Meta] Save memory checkpoint to preserve analysis context
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.
Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
GitHub Actions CI/CD workflows for automating build, test, and deployment
Use when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across domain flows. Use when adding new features that share mechanics with existing ones.
Use when you need to quickly log work activities and maintain consistent tags without duplicates or gaps
Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.