All authors
Claude Skills by felipemelendez
github.com/felipemelendez19 skills0 installs45 views
- BrainstormingUse when starting a new feature or design with open choices, before code is written. Not for small fixes, chores, or work with an approved spec.Votes: 0GitHub stars: 3
- Dispatching Parallel AgentsUse when 3+ tasks share no files and no order, so they can run at once. Review happens after all return.Votes: 0GitHub stars: 3
- Dispatching SubagentsUse when running plan tasks one at a time with a review after each — for tasks with dependencies, sensitive code, or shared files.Votes: 0GitHub stars: 3
- Executing PlansUse when driving a written plan to completion, task by task. Routes each task to sequential or parallel dispatch.Votes: 0GitHub stars: 3
- Finishing A BranchUse when a branch's work is done and tests pass, to choose merge, PR, keep or discard. Nothing destructive without confirmation.Votes: 0GitHub stars: 3
- Handing Off To Fresh ContextUse when context is filling on a long task, to leave a short note so work resumes cleanly after compaction.Votes: 0GitHub stars: 3
- Managing MemoryUse when the user says "remember", "save this", "I told you before", or "forget that".Votes: 0GitHub stars: 3
- Receiving Code ReviewUse when responding to code review feedback from a person or an agent. Check each point before changing code; no performative agreement.Votes: 0GitHub stars: 3
- Requesting Code ReviewUse when a finished change needs its Standard or Full review before it merges, becomes a PR, or is called done. Not for work in progress.Votes: 0GitHub stars: 3
- Research ClassifierUse when a spec or plan about to be written depends on a library, vendor API or version. Decides whether to check current docs first.Votes: 0GitHub stars: 3
- Systematic DebuggingUse when a bug, test failure or unexpected behavior needs its cause found before a fix. Not for the expected red phase of TDD. Runs before test-driven-development.Votes: 0GitHub stars: 3
- Test Driven DevelopmentUse when implementing a feature or bugfix where a test is practical, before writing the code. Not for docs or config with no testable behavior.Votes: 0GitHub stars: 3
- Using Git WorktreesUse when work needs its own branch and checkout — a long feature, a risky refactor, or a parallel attempt.Votes: 0GitHub stars: 3
- Using OrchestratorUse when deciding which orchestrator skill fits a task, or which reply format a cadence-enabled project uses.Votes: 0GitHub stars: 3
- Verification Before CompletionUse when about to claim a code change (feature, fix, refactor, upgrade, migration) is done, fixed or passing — run the command that proves it first. Not for a small edit the user spelled out. Runs last, after any review.Votes: 0GitHub stars: 3
- Writing PlansUse when a spec is approved and implementation has not started, to write a checklist plan file. Not when a plan already covers the work.Votes: 0GitHub stars: 3
- Writing SkillsUse when adding a new skill or editing an existing one. Not for commands (commands/*.md) or agent definitions.Votes: 0GitHub stars: 3
- TemplatesUse when <trigger>. Not for <adjacent non-trigger>.Votes: 0GitHub stars: 3
- CadenceUse when changing production code or tests in projects with enabled docs/llm-orchestrator/cadence.json. Not for ordinary documentation or questions.Votes: 0GitHub stars: 3