memer/SKILLS.md

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 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
• Debugging
• Documentation
• UI/UX
• Marketing
• Brainstorming

Specialized Skills

Software Development

• Architecture and System Design
• Feature Implementation
• Refactoring
• Code Review
• Test Strategy
• API and Backend Work
• Database Migrations and Data Evolution
• Dependency Lifecycle Management
• Performance Optimization
• Security Review and Hardening
• Observability and Operability
• Maintenance and Technical Debt Planning
• Frontend UI Implementation
• Repository Exploration
• Release and Change Summary

Debugging

• Bug Triage
• Debugging Workflow
• Incident Response and Stabilization

Documentation

• Architecture Decision Records
• Technical Documentation
• Onboarding Documentation

UI/UX

• UX Review
• Accessibility Review
• Design System and UI Consistency

Marketing

• Product Copy
• Marketing Content
• Messaging and Positioning
• Content Strategy and SEO

Brainstorming

• Ideation
• Structured Brainstorming
• Roadmap and Opportunity Prioritization

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.