GitHub
installing-skills-system
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
☆ 38View skill
Databases AI Skills
Discover Databases skills, compare source repositories and read the instructions for each workflow.
Categories: Databases
Databases Clear filters
Browse skills
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
GitHub
reducing-complexity
Managing complexity is software's primary technical imperative - all other goals are secondary
☆ 38View skill
GitHub
designing-before-coding
Design in pseudocode first, iterate approaches, then translate to code
☆ 38View skill
GitHub
your-skill-name
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.
☆ 38View skill
GitHub
your-skill-name
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...
☆ 38View skill
GitHub
remembering-conversations
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
☆ 38View skill
GitHub
flow-planner
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
☆ 38View skill
GitHub
naming-variables
Choose names that fully and accurately describe what the variable represents
☆ 38View skill
GitHub
brainstorming-ideas-into-designs
Interactive idea refinement using Socratic method to develop fully-formed designs
☆ 38View skill
GitHub
flow-builder
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.
☆ 38View skill
GitHub
flow-completer
Mark tasks and phases complete after verification. Use when finishing tasks, closing phases, or marking work done. Ensures all work verified before completion.
☆ 38View skill
GitHub
subagent-driven-development
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
☆ 38View skill
GitHub
requesting-code-review
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
☆ 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.