installing-skills-system
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
Découvrez les skills Bases de données, comparez leurs dépôts et consultez leurs instructions.
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
Name code by what it does in the domain, not how it's implemented or its history
Design features through brainstorming and make architectural decisions. Use when user wants to brainstorm, design approach, make architecture choices, or update PLAN.md.
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".
Each routine does one thing and does it well - extract when routines have multiple responsibilities
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Try 2-3 different approaches before implementing - don't settle for first design you think of
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Managing complexity is software's primary technical imperative - all other goals are secondary
Design in pseudocode first, iterate approaches, then translate to code
Brief description of what this Skill does and when to use it. Include specific trigger phrases. Use when user asks "trigger phrase 1", "trigger phrase 2", or wants to [outcome]. Max 1024 characters.
Brief description of what this Skill does and when to use it. Include specific trigger phrases users would say. Use when user asks "trigger phrase 1", "trigger phrase 2", or wants to [outcome]. Max 1024 charact...
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Choose names that fully and accurately describe what the variable represents
Interactive idea refinement using Socratic method to develop fully-formed designs
Execute implementation work with gate checks and verification. Use when user wants to code, build features, implement iterations, or execute action items. Enforces gates, guides workflow, tracks progress.
Mark tasks and phases complete after verification. Use when finishing tasks, closing phases, or marking work done. Ensures all work verified before completion.
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.