Skill Index
Generated from ~/.copilot/skills.
| Name | Description | Source |
|---|---|---|
| adr | The architecture-decision-record system — the single source of truth for binding design, engineering, and platform decisions across projects. Use when writing a new ADR, changing or superseding an existing decision, deprecating one, citing a decision in code review or an agent, or answering “what is our rule for X”. Active records live in references/, tombstoned ones in references/ZZ-deprecated/, and the template in templates/adr-template.md. Storybook and the design-principles skill reference these records; they are not the source. Do NOT use for general prose (technical-writing), product specs (prd-generator), or enforcing visual rules at code time (design-principles cites these records). | ~/.copilot/skills/adr/SKILL.md |
| architecture | Front door for system architecture, tech evaluation, monorepo layout, legacy discovery, tech-debt scoring, and fullstack scaffolding. Trigger on “design system architecture”, “ADR”, “monolith vs microservices”, “choose a database”, “dependency analysis”, “compare frameworks”, “TCO analysis”, “should we adopt X”, “build vs buy”, “monorepo”, “turborepo”, “nx”, “pnpm workspace”, “package boundaries”, “explain this repo”, “onboard me on this codebase”, “AS400”, “COBOL”, “CICS”, “mainframe”, “legacy modernization”, “find tech debt”, “prioritize refactoring”, “code quality audit”, “debt dashboard”, “scaffold a new project”, “what stack should I use”, or “build me a fullstack X”. Does NOT do org strategy (exec), React/CSS (frontend), schema/query tuning (database), CI/CD or Kubernetes (platform), or incident response. Output: an ADR, comparison report, workspace layout, discovery doc, scored debt inventory, or scaffolded project — per the routing table below. | ~/.copilot/skills/architecture/SKILL.md |
| backend | Go backend services: code standards (layering, error handling, concurrency, testing, observability, databases), new Fiber service scaffolding with clean architecture and Helm, and API contract design (REST/OpenAPI/tRPC/GraphQL/gRPC) with RFC 9457 errors and cursor pagination. Triggers: “review this Go handler”, “new Go service”, “design an API”, “scaffold Go”, “fiber api”, “go test”, “wrap this error”, “table-driven test”, “layering”, “concurrency”, “OpenAPI spec”, “tRPC router”, “GraphQL schema”, “Prism mock”, “Go TUI”, “bubbletea”, “terminal UI”, “Postgres transaction”, “profile this”, “golangci-lint”. | ~/.copilot/skills/backend/SKILL.md |
| database | Multi-engine database architect — Postgres-primary schema design (3NF/BCNF normalization, surrogate PKs, named ON DELETE policies, expand-contract migrations) and query tuning (EXPLAIN, indexing, pg_stat_statements). MySQL, Elasticsearch, and Redis references for schema/query/data-structure basics. Use for schema design from feature briefs, refactoring for FK gaps or naming drift, zero-downtime migrations, query performance diagnosis via EXPLAIN ANALYZE, index strategy (B-tree/GIN/BRIN/partial/covering), partitioning at 50M+ rows, bloat/autovacuum tuning, and choosing relational vs document vs columnar vs cache. Postgres is the deepest-covered engine with full DDL/EXPLAIN tooling; MySQL, Elasticsearch, Redis are useful starter references. Triggers: “design a schema”, “normalize”, “ERD”, “slow query”, “explain analyze”, “foreign keys”, “expand-contract”, “index strategy”, “partition”, “mysql schema”, “elasticsearch mapping”, “redis structure”, “database performance”, “denormalize”, “query plan”. | ~/.copilot/skills/database/SKILL.md |
| design | The visual law for any framework — writing/editing CSS, “style this”, “add styles”, Tailwind utility classes, BEM class names, design tokens/CSS custom properties, theming, dark mode, light/dark, multiple themes, print styles/@media print, responsive layout, spacing/padding/margins, motion/transitions, typography/font scale, corner radius, color palette/contrast/WCAG, icon layout (“leading icon”, “trailing icon”, “icon stacking”), border discipline (“nested border”, “borders in borders”), card layout, action button placement, grid layout for icons, content below icon, component APIs/variants/states, design system, developer handoff, 8pt grid, breakpoints. Absorbs css, design-principles, and ui-design-system — CSS mechanics, visual/layout enforcement, and token stewardship all route here. NOT component logic (frontend), prose (technical-writing), or ADR rationale (adr, cited by number). | ~/.copilot/skills/design/SKILL.md |
| exec | Executive advisory front door for CEO/CTO/customer-success leadership. Frames strategic decisions (M&A, pivots, board strategy), tech strategy and org scaling (team topology, DORA health), and customer success analytics (health scoring, churn risk, expansion). Use for board memos, investor updates, OKRs, tech-debt investment cases, team scaling plans, customer health scores, churn-risk analysis, expansion opportunity scoring, executive business reviews, or any “should the leader do X” question. Output: decision memos, board packages, ADRs, scaling plans, QBR decks, success plans — backed by financial_scenario_analyzer.py, strategy_analyzer.py, tech_debt_analyzer.py, team_scaling_calculator.py, health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py. | ~/.copilot/skills/exec/SKILL.md |
| file-organizer | Local-filesystem organization assistant for Downloads, Desktop, Documents, Projects, and Photos — surveys what’s there, proposes a structure that fits how the user actually works, finds duplicates by hash/name/size, and executes a reversible plan only after explicit confirmation (archive over delete). Use when the user says their files are a mess, asks to clean up Downloads/Desktop, restructure a Projects folder, find duplicate files, sort photos by EXIF date, or establish a naming convention they can maintain. Does NOT edit file contents, manage cloud-sync/backup strategy, or touch ~/Library/dotfiles/app bundles without explicit permission. Output: survey report → proposed tree + move/rename/archive plan → confirmed execution log → ongoing maintenance cadence. | ~/.copilot/skills/file-organizer/SKILL.md |
| file-to-markdown | Convert rich documents — PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx/.xls), Outlook (.msg), HTML, CSV, JSON, XML, EPUB, and images — into clean Markdown so their content can be read into context cheaply, using Microsoft’s markitdown. Use this skill WHENEVER you need to read, summarize, extract from, quote, search, or feed the content of a non-Markdown document into the model, especially PDFs and Office files, which are token-expensive or unreadable in raw form. Trigger on things like “read this PDF”, “what does this contract/docx say”, “summarize this deck”, “pull the numbers out of this spreadsheet”, “ingest these files”, “add these files to context”, “convert this to markdown”, or any time a .pdf/.docx/.pptx/.xlsx/.msg/.html/.epub file needs to become text the model can work with. This is the default way to bring document content into a conversation — prefer it over dumping raw file bytes or guessing. It DEFERS to the pdf, docx, xlsx, and pptx skills when the goal is to EDIT or CREATE one of those files rather than read it. | ~/.copilot/skills/file-to-markdown/SKILL.md |
| frontend | Front door for the whole frontend surface — senior React 19 engineering (Server Components, use(), useActionState, Suspense, state location), design-system component authoring for @dmwd-io/design-system (Props JSDoc, CVA, nine UI states), Storybook (CSF3 setup, argTypes/controls, sidebar hierarchy via meta.title), TanStack Router (file routes, Zod search params, loaders, beforeLoad auth), Zod schema architecture (contracts package, branded IDs, discriminated unions, OpenAPI), React performance auditing (Lighthouse, react-scan, bundle budgets), frontend aesthetic direction (named style, type pairing, motion), and Astro (output mode, hydration, content collections, project scaffolding). Trigger on “build a React component”, “new design-system component”, “write a story”, “storybook argTypes”, “move this story”, “tanstack router”, “file-based routes”, “zod schema”, “contracts package”, “app is slow”, “performance audit”, “design a landing page”, “make it look designed”, “astro app”, “client:load”, “scaffold astro”. Does NOT cover CSS mechanics/tokens (design skill), backend/API contracts (backend skill), or test strategy (quality skill). | ~/.copilot/skills/frontend/SKILL.md |
| generators | Generate favicons (16/32/96 + .ico), app icons (180/192/512), Open Graph images (1200×630/675/1200), and company logos via Logo.dev. One entrypoint for all generated artifacts: favicons from logo/emoji/text, OG images from logo/text, logo lookups by domain or batch via Rube MCP. Use for “generate me a favicon”, “create OG images”, “fetch a company logo”, “app icon”, “social sharing image”, “emoji favicon”, “logo.dev lookup”. Validates file sizes, dimensions, format, and WCAG AA contrast. Does NOT design logos from scratch (→ designer), or handle generic image processing beyond social-specific generation. | ~/.copilot/skills/generators/SKILL.md |
| go-task | Author Taskfile.yml files for go-task and Task v3.51. Use when the user asks to create a task, add a task, write or scaffold a Taskfile, convert Makefile or package.json scripts to Task, or design build, test, lint, deploy, dev, setup, reset, kubectl, docker, or monorepo task workflows. Verify with the installed task binary, task —dry, task —list-all, yamllint, and shell syntax checks for referenced scripts. Do not use for GitHub Actions YAML, Makefiles, or application business logic. | ~/.copilot/skills/go-task/SKILL.md |
| legal | Front door for legal document drafting, template selection, and print-ready PDF/court-facing layout design. Absorbs legal-document-drafter, legal-templates, and legal-pdf-layouts. Use for drafting bespoke legal documents (demand letters, cease-and-desists, motions, declarations, NDAs, ToS, privacy policies, DMCA notices, pleadings, contracts), selecting and composing reusable document shells before bespoke work, and designing print-ready court-facing PDFs with deliberate typography and hierarchy. Triggers: “draft a demand letter”, “motion template”, “proposed order”, “declaration”, “NDA”, “MSA”, “certificate of service”, “court-safe PDF”, “legal PDF layout”, “print-ready pleading”, “cease and desist”, “settlement letter”, “privacy policy”, “promissory note”. | ~/.copilot/skills/legal/SKILL.md |
| plan | Turns a fuzzy goal into a parallel-ready execution plan — a smart “planner” model decomposes the work into workstreams so precisely specified (single outcome, exact instructions, binary acceptance criteria, disjoint file ownership) that fast, cheap “executor” models can each complete one in parallel without stepping on each other, then integrate at the end. Use when the user says “make a plan”, “plan this out”, “break this into workstreams”, “parallelize this work”, “spec this out for subagents”, “decompose this”, “create an implementation plan”, “how do we split this across agents”, or wants work laid out so cheaper/faster models can run it. Owns the planner/executor model-routing doctrine (planner = smartest model; executors = Sonnet/Haiku or Codex 5.3 / fastest capable) and the four-parallel-subagents aim. Output is a filled-in plan from references/plan-template.md. Do NOT use for product specs (prd-generator), user stories / sprint planning (agile-product-owner), system-design / ADRs (senior-architect, adr), or general prose (technical-writing). | ~/.copilot/skills/plan/SKILL.md |
| platform | Front door for platform and infrastructure — Helm charts (CRDs out-of-band, Artifact Hub lookup, bjw-s app-template default), raw K8s manifests and custom operators (Kubebuilder/Metacontroller/Crossplane), DevOps (CI/CD, Terraform, Dockerfiles, rollouts), GitHub Actions (reusable workflows, OIDC, signing/scanning), observability (SLOs, burn-rate alerts, dashboards, OTel), and incident command (live response, blameless postmortems, on-call). Absorbs helm, kubernetes-operator, senior-devops, github-actions-architect, observability-designer, incident-commander. Triggers: “helm chart”, “CRDs”, “kubectl apply”, “kubernetes operator”, “CRD”, “kubebuilder”, “dockerfile”, “containerize”, “terraform module”, “ci/cd pipeline”, “github actions workflow”, “OIDC”, “canary”, “blue/green”, “SLO”, “SLI”, “error budget”, “dashboard”, “alerting”, “observability”, “postmortem”, “PIR”, “incident”, “on-call”, “production down”, “SEV1”. NOT app code (frontend/backend), Postgres tuning (database), security review (security). | ~/.copilot/skills/platform/SKILL.md |
| product | Front door for product management — PRDs (full/lean/one-pager/technical), user stories with Given-When-Then AC and sprint planning, product strategy and OKR cascades, and RICE prioritization with customer-interview synthesis. Absorbs prd-generator, agile-product-owner, product-strategist, and product-manager-toolkit; nothing invokes them separately. Trigger on “write a PRD”, “product spec”, “one-pager”, “lean PRD”, “feature brief”, “user story”, “acceptance criteria”, “sprint planning”, “story points”, “INVEST”, “Given-When-Then”, “break down epic”, “velocity”, “product strategy”, “OKR cascade”, “where to play / how to win”, “positioning brief”, “vision statement”, “RICE this”, “prioritize these features”, “synthesize these interviews”, “JTBD”, “opportunity solution tree”, “build the roadmap”. NOT for CEO capital allocation (ceo-advisor), CTO org design (cto-advisor), account health/renewal (customer-success-manager), or sprint-level engineering ticket grooming in a codebase. | ~/.copilot/skills/product/SKILL.md |
| quality | Single front door for testing strategy, test authoring, PR review, and coverage policy. Triggers: “what layer should this test be”, “write tests”, “test coverage”, “Vitest”, “React Testing Library”, “Playwright”, “jest-axe”, “Lost Pixel”, “flaky test”, “open a PR”, “PR description”, “self-review”. Use for: test-layer decisions, naming/structuring tests, coverage policy, test automation (Vitest/RTL/MSW/Playwright/axe/Lost Pixel patterns), flake diagnosis, PR body drafting, reviewer selection. NOT for: writing code (react-engineer/go-backend-engineer), perf audits (react-perf-auditor), security testing (senior-security), API contracts (api-designer). Output: layer rulings, test suites, coverage reports, PR bodies, self-review notes. | ~/.copilot/skills/quality/SKILL.md |
| security | Application-security engineering (STRIDE threat modeling, OWASP review, secure architecture, secret/dependency scanning) and FedRAMP/NIST 800-53 ATO readiness review (impact-level selection, control mapping, Aligned/Partial/Gap verdict). Triggers: threat model, STRIDE, security architecture, OWASP, cryptography, secret scanning, supply chain, SLSA, zero trust, ato, ato ready, fedramp, fedramp high/moderate/low, impact level, nist 800-53, control mapping, conmon, poa&m, ssp, 3pao, authorization to operate, compliance review, or control id (AC-2, SC-7, …). Not for: general CI/CD → platform skill; live incidents → incident-commander; observability → observability-designer; legal prose → legal-document-drafter. | ~/.copilot/skills/security/SKILL.md |
| skill-forge | Create new Agent Skills, validate existing ones, and sync them across Claude Code, Codex, and GitHub Copilot. Use this for authoring or editing a skill from scratch (naming, frontmatter, triggers, references, templates), validating a skill’s format and standards compliance, or syncing and sharing skills across tools and team folders. Triggers: “create a skill”, “new skill”, “edit this skill”, “improve skill triggering”, “skill eval”, “tune skill description”, “validate this skill”, “sync my skills”, “share this skill”, “convert this skill”, “share these skills with”, “install this skill”, “package a skill”, or “share only certain skills”. | ~/.copilot/skills/skill-forge/SKILL.md |
| technical-writing | Single front door for everything written for people — Markdown/MDX, Mermaid diagrams, code comments, commit messages, and teaching MDX pages built from real design-system components. Absorbs the former markdown, mermaid, and docs-that-teach skills; any request for any of them routes here. Use for any .md/.mdx write or edit (docs, guides, READMEs, release notes, runbooks, teaching pages), any diagram, code comments, prose for non-technical readers. Triggers: “write docs”, “format this markdown”, “draw a diagram”, “fix this mermaid”, “write a status update”, “comment this code”, “teaching doc”, “docs that teach”. Validate with scripts/lint.py —git-changed. NOT for PRDs, user stories, PR descriptions, UI microcopy, or legal prose. | ~/.copilot/skills/technical-writing/SKILL.md |
| ux | Single front door for UX — usability, research, information architecture. Use for: Nielsen heuristics, UI copy (labels, errors, empty states), forms, accessibility, user personas, journey maps, usability tests, interview synthesis, IA audits, navigation, taxonomy, sitemaps, card-sort interpretation, OOUX object modeling. Triggers: “usability heuristic”, “user persona”, “journey map”, “usability test”, “research synthesis”, “how should we organize”, “navigation”, “taxonomy”, “sitemap”, “information architecture”, “card sort”, “tree test”, “OOUX”, “form design”, “error message”, “accessibility audit”, “findability”. Does NOT do visual design (use frontend), design tokens (use design), React code (use react-engineer), PRDs (use product), or prose structure (use technical-writing). | ~/.copilot/skills/ux/SKILL.md |