92 lines
4.2 KiB
Markdown
92 lines
4.2 KiB
Markdown
|
# Skill Index
|
||
|
|
|
||
|
|
This file is the canonical registry for the instruction suite. Read this index after `AGENTS.md` and the deployment profile, then open only the hub and skill files needed for the current task.
|
||
|
|
|
||
|
|
## Skill Contract
|
||
|
|
|
||
|
|
Every skill file follows the same structure:
|
||
|
|
- `Purpose`
|
||
|
|
- `When to use`
|
||
|
|
- `Inputs to gather`
|
||
|
|
- `How to work`
|
||
|
|
- `Output expectations`
|
||
|
|
- `Quality checklist`
|
||
|
|
- `Handoff notes`
|
||
|
|
|
||
|
|
## Loading Guidance
|
||
|
|
|
||
|
|
- If [DEPLOYMENT-PROFILE.md](./DEPLOYMENT-PROFILE.md) is filled in, treat it as the default preference layer before applying generic skill guidance.
|
||
|
|
- Start narrow: one hub plus the smallest set of specialized skills that covers the task.
|
||
|
|
- Typical task size: two to four skills.
|
||
|
|
- Larger, cross-functional tasks may need four to six skills, but only when each one adds a distinct concern.
|
||
|
|
- Prefer high-leverage skills that shape implementation quality over collecting adjacent but redundant guidance.
|
||
|
|
- When in doubt, prioritize repository exploration, implementation/debugging, testing, and one domain-specific skill.
|
||
|
|
|
||
|
|
## Category Hubs
|
||
|
|
|
||
|
|
- [Software Development](./hubs/software-development.md)
|
||
|
|
- [Debugging](./hubs/debugging.md)
|
||
|
|
- [Documentation](./hubs/documentation.md)
|
||
|
|
- [UI/UX](./hubs/ui-ux.md)
|
||
|
|
- [Marketing](./hubs/marketing.md)
|
||
|
|
- [Brainstorming](./hubs/brainstorming.md)
|
||
|
|
|
||
|
|
## Specialized Skills
|
||
|
|
|
||
|
|
### Software Development
|
||
|
|
|
||
|
|
- [Architecture and System Design](./skills/software/architecture-system-design.md)
|
||
|
|
- [Feature Implementation](./skills/software/feature-implementation.md)
|
||
|
|
- [Refactoring](./skills/software/refactoring.md)
|
||
|
|
- [Code Review](./skills/software/code-review.md)
|
||
|
|
- [Test Strategy](./skills/software/test-strategy.md)
|
||
|
|
- [API and Backend Work](./skills/software/api-backend.md)
|
||
|
|
- [Database Migrations and Data Evolution](./skills/software/database-migrations.md)
|
||
|
|
- [Dependency Lifecycle Management](./skills/software/dependency-lifecycle.md)
|
||
|
|
- [Performance Optimization](./skills/software/performance-optimization.md)
|
||
|
|
- [Security Review and Hardening](./skills/software/security-review-hardening.md)
|
||
|
|
- [Observability and Operability](./skills/software/observability-operability.md)
|
||
|
|
- [Maintenance and Technical Debt Planning](./skills/software/maintenance-technical-debt.md)
|
||
|
|
- [Frontend UI Implementation](./skills/software/frontend-ui-implementation.md)
|
||
|
|
- [Repository Exploration](./skills/software/repo-exploration.md)
|
||
|
|
- [Release and Change Summary](./skills/software/release-change-summary.md)
|
||
|
|
|
||
|
|
### Debugging
|
||
|
|
|
||
|
|
- [Bug Triage](./skills/debugging/bug-triage.md)
|
||
|
|
- [Debugging Workflow](./skills/debugging/debugging-workflow.md)
|
||
|
|
- [Incident Response and Stabilization](./skills/debugging/incident-response-stabilization.md)
|
||
|
|
|
||
|
|
### Documentation
|
||
|
|
|
||
|
|
- [Architecture Decision Records](./skills/documentation/architecture-decision-records.md)
|
||
|
|
- [Technical Documentation](./skills/documentation/technical-docs.md)
|
||
|
|
- [Onboarding Documentation](./skills/documentation/onboarding-docs.md)
|
||
|
|
|
||
|
|
### UI/UX
|
||
|
|
|
||
|
|
- [UX Review](./skills/ui-ux/ux-review.md)
|
||
|
|
- [Accessibility Review](./skills/ui-ux/accessibility-review.md)
|
||
|
|
- [Design System and UI Consistency](./skills/ui-ux/design-system-consistency.md)
|
||
|
|
|
||
|
|
### Marketing
|
||
|
|
|
||
|
|
- [Product Copy](./skills/marketing/product-copy.md)
|
||
|
|
- [Marketing Content](./skills/marketing/marketing-content.md)
|
||
|
|
- [Messaging and Positioning](./skills/marketing/messaging-positioning.md)
|
||
|
|
- [Content Strategy and SEO](./skills/marketing/content-strategy-seo.md)
|
||
|
|
|
||
|
|
### Brainstorming
|
||
|
|
|
||
|
|
- [Ideation](./skills/brainstorming/ideation.md)
|
||
|
|
- [Structured Brainstorming](./skills/brainstorming/structured-brainstorming.md)
|
||
|
|
- [Roadmap and Opportunity Prioritization](./skills/brainstorming/roadmap-opportunity-prioritization.md)
|
||
|
|
|
||
|
|
## Quick Routing Hints
|
||
|
|
|
||
|
|
- If the task changes code, start with the software development hub.
|
||
|
|
- If the task starts from a defect, regression, failing test, or unclear breakage, add debugging skills.
|
||
|
|
- If the task changes how people use, adopt, or understand the product, add documentation and possibly UX or marketing skills.
|
||
|
|
- If the task asks for options, concepts, or strategic directions before execution, use brainstorming skills.
|
||
|
|
- If the task affects long-term system health, look for architecture, security, performance, observability, dependency, or maintenance skills before loading more tactical ones.
|