GitHub
flow-curator
Manage backlog and archive completed work. Use for backlog operations, archiving phases, or keeping active plan focused. Curates plan organization.
☆ 38View skill
Browse skills
Explore AI skills for development, content, data and productivity. Compare the description and repository popularity before opening a skill.
Categories
Browse skills
GitHub
flow-architect
Guide architectural decisions and PLAN.md updates using Flow framework. Use when user discusses "architecture", "how should we architect", "design patterns", "how should we structure", "how do we structure", "t...
☆ 38View skill
GitHub
flow-navigator
Navigate Flow projects with dashboard-first pattern. Use when user asks about status, current work, what's next, or project progress. Read-only skill.
☆ 38View skill
GitHub
flow-verifier
Verify plan consistency, generate summaries, maintain plan health. Use for review, verification, summaries, or plan maintenance. Mostly read-only with maintenance operations.
☆ 38View skill
GitHub
flow-documenter
Document findings and maintain task notes using Flow framework. Use when user says "document", "document this", "document finding", "add notes", "add this to notes", "write this down", "summarize", "summarize t...
☆ 38View skill
GitHub
dispatching-parallel-agents
Use multiple Claude agents to investigate and fix independent problems concurrently
☆ 38View skill
GitHub
getting-started-with-skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
☆ 38View skill
GitHub
localizing-variables
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
☆ 38View skill
GitHub
root-cause-tracing
Systematically trace bugs backward through call stack to find original trigger
☆ 38View skill
GitHub
simplifying-control-flow
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
☆ 38View skill
GitHub
systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
☆ 38View skill
GitHub
verification-before-completion
Run verification commands and confirm output before claiming success
☆ 38View skill
GitHub
installing-skills-system
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
☆ 38View skill
GitHub
domain-focused-naming
Name code by what it does in the domain, not how it's implemented or its history
☆ 38View skill
GitHub
flow-designer
Design features through brainstorming and make architectural decisions. Use when user wants to brainstorm, design approach, make architecture choices, or update PLAN.md.
☆ 38View skill
GitHub
flow-initializer
Initialize Flow projects from scratch, migrate existing docs, or update old structures. Use when user says "start flow", "initialize", "migrate to flow", "set up flow project".
☆ 38View skill
GitHub
keeping-routines-focused
Each routine does one thing and does it well - extract when routines have multiple responsibilities
☆ 38View skill
GitHub
maintaining-consistent-abstractions
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
☆ 38View skill
GitHub
exploring-alternatives
Try 2-3 different approaches before implementing - don't settle for first design you think of
☆ 38View skill
GitHub
encapsulating-complexity
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
☆ 38View skill
GitHub
writing-plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
☆ 38View skill
GitHub
testing-skills-with-subagents
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
☆ 38View skill
GitHub
single-purpose-variables
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
☆ 38View skill
GitHub
commenting-intent
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
☆ 38View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.