Loading...
Loading...
Found 1,951 Skills
Initializes or refreshes the Domain Registry in CLAUDE.md by scanning the project for library directories. Run this once per project, or after adding new libraries. Creates the registry table that domain-context skill uses for auto-loading.
Identify underspecified areas in the current feature spec by asking up
Deprecated: this skill has moved to building-blocks.
Checks hierarchy & links, SSOT, proactive compression, requirements compliance, freshness indicators, legacy cleanup, stack adaptation. Returns findings with severity, location, and recommendations.
Generate a custom checklist for the current feature based on user requirements.
Update existing app design document based on codebase changes and project evolution
Generate a project-specific CLAUDE.md by analyzing the current repository's code, build system, and architecture. 4-phase pipeline: SCAN, DETECT, GENERATE, VALIDATE. Auto-detects language/framework and enriches output with domain-specific conventions (e.g., go-sapcc-conventions for sapcc Go repos). Use for "generate claude.md", "create claude.md", "init claude.md", "bootstrap claude.md", "make claude.md". Do NOT use for improving an existing CLAUDE.md (use claude-md-improver instead).
UPDATE-DOCS phase. Refresh README.md, CLAUDE.md, and docs/index.html to reflect changes made this session. Commits and pushes doc updates. Terminal phase — declares COMPLETE.
Save an archival summary of an AI conversation to Nathan's Obsidian vault, using Nathan's Thinking note template and vault folder conventions to capture intellectual journeys, key insights, and technical logs. Use when archiving a chat session to Nathan's Obsidian vault.
Validates SKILL.md files against Claude Code skill best practices. Checks conciseness, description quality, progressive disclosure, workflow structure, and common anti-patterns. Use when reviewing or auditing skills before shipping.
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. For exploratory or ambiguous requests where the user is unsure what to do, prefer ce-brainstorm first.