Loading...
Loading...
Found 2,038 Skills
Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions.
Format, numbering, and when-to-write criteria for Architecture Decision Records in docs/adr/. Use when recording an architectural decision, when another skill flags a decision as ADR-worthy, or when the user asks to write or review an ADR.
Documentation pipeline automation and docs-as-code workflows
Scans directory structure, detects projects, maps dependencies, and documents code organization into a repo.md file. Use when the user needs a codebase overview, project structure map, or repository context before security analysis.
Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/
Create release notes that summarize features, fixes, and migration guidance for software releases.
Use when the user wants to brainstorm an idea or design a feature/spec. Explores intent and requirements through dialogue, then writes a spec document to docs/spark/ and STOPS. Does not auto-chain to implementation planning or any other skill.
AGENTS.md 거버넌스 시스템을 분석·생성하는 마스터 프롬프트. 현재 프로젝트를 분석하여 루트 AGENTS.md와 하위 AGENTS.md를 즉시 생성하고, CLAUDE.md에 @AGENTS.md 링크를 추가한다. "AGENTS.md 만들어줘", "에이전트 규칙 만들어줘", "/agents-md" 호출 시 반드시 실행하라.
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
Generate a comprehensive repository summary and narrative story from commit history
Generate a GROOVE.md onboarding guide for contributors to a groove-enabled project. Explains the compound loop, commands, and conventions.
Automated retrospectives — captures learnings at EPIC completion and on manual invocation. EPIC-scoped retros embed a Retrospective section in the EPIC artifact. Cross-epic and time-based retros produce standalone retro docs. Triggers on: 'retro', 'retrospective', 'post-mortem', 'lessons learned', 'debrief', 'what worked', 'what didn't work', 'what did we learn', 'reflect', or automatically after EPIC terminal transitions.