feature-orchestrator
Generate the required feature plan file skeleton and enforce section outputs + Touched YES/NO gates.
Essential command-line tools and system utilities.
Generate the required feature plan file skeleton and enforce section outputs + Touched YES/NO gates.
Maintains project context through progressive disclosure and enforced documentation. This skill should be used when starting work on a new project to initialize context documentation, or continuously during development to maintain up-to-date project structure and coding conventions. Triggers on project initialization, file modifications, or when the agent needs to understand project architecture.
Write self-documenting code that explains itself through clear structure and naming, add minimal helpful comments to explain large sections of code logic, and avoid comments about changes or fixes that won't be relevant in the future. Use this skill when deciding whether to add comments to code, writing comments for complex logic sections, ensuring code is self-explanatory through good naming, refactoring code to reduce the need for comments, or reviewing existing comments for relevance and clarity. This skill applies when working on any code files where you need to balance code clarity with appropriate documentation.
Use when monitoring code quality over time, measuring refactoring impact, tracking if complexity is improving or worsening, or validating technical debt work - tracks complexity metrics across git history identifying improving, stable, or deteriorating files
ไปฃ็ ้ๆๆๅๆ่ฝใๅฝ็จๆท้่ฆไผๅไปฃ็ ็ปๆใๆถ้คไปฃ็ ๅผๅณใๆน่ฟ่ฎพ่ฎกๆจกๅผใๆๅไปฃ็ ๅฏ็ปดๆคๆงๆ่ฟ่กๆถๆๆน่ฟๆถไฝฟ็จๆญคๆ่ฝใ
Enforce ownership boundaries between coverage-nextjs and template-coverage-creatives. Never mix responsibilities.
CodeRabbitใฎใฌใใฅใผใณใกใณใใ่ชๅไฟฎๆญฃใใใใใฎใฏใผใฏใใญใผๆ้ ใงใใใฌใใฅใผไฟฎๆญฃใฎไพ้ ผใใใฃใๅ ดๅใซไฝฟ็จใใฆใใ ใใใ
Open source license compliance including compatibility analysis, obligations tracking, and compliance workflows
Makefile patterns for development workflows. Use when creating or understanding Makefiles for build automation, release workflows, and development iteration.
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
Blob storage patterns for file persistence. Use when implementing storage operations or file management. Triggers: storage.System, Store, Retrieve, Delete, Validate, Path, atomic writes, path traversal protection, storage keys, filesystem, base_path, temp file. File patterns: pkg/storage/*.go
Ensure all asset filenames are lowercase and hyphenated
Use when implementing any feature or bugfix, before writing implementation code
Checks if docs need updates. MUST use proactively after adding new public APIs, breaking changes, or significant architectural changes. Also triggers on "ใใญใฅใกใณใ", "docs".
Analyze files in a codebase to understand structure, find patterns, extract metadata, and generate summaries. Use when exploring unfamiliar codebases, documenting project structure, or when users ask about file contents, organization, or relationships.
Before modifying shared code (types, APIs, utilities), find all consumers. Prevents partial migrations and broken integrations. Trigger before changing any exported symbol.
ๆๅฎใใใใใฉใซใๅ ใฎMDใใกใคใซใ่ชญใฟๅใใๅ่ณชใใงใใฏใชในใใซๅบใฅใใฆ่ฉไพกใฌใใผใใ็ๆใๅ่ณชใใงใใฏใๅฎไบ็ขบ่ชใๅบๆบๅคๅฎใงๅฟ ใไฝฟ็จใMUST BE USED for quality gates.
Refactors for readability after verification is green, re-running checks and updating 20_verification.md.
้กน็ฎไธไธๆ่ชๅจๆดๆฐๅจใๅฝๆฐๅขๅ่ฝใ้ๆไปฃ็ ใไฟฎๆนๆถๆๆถ่งฆๅ๏ผ็กฎไฟ project_context.md ไฟๆๆๆฐใ่งฆๅ่ฏ๏ผๆฐๅ่ฝ, ้ๆ, ๆถๆๅๆด, ๆฐๆจกๅ, ๆฐ็ณป็ป, ๅฎๆๅฎ็ฐใ
Safe cleanup + de-bloat operator for SYSopGPTWSL. Inventories candidates, proposes an action plan, and only deletes after explicit user confirmation. Defaults to repo-scoped, reversible moves into `sysop/out/janitor_trash/`. Use when the user says โclean upโ, โcleanupโ, โdeleteโ, โremove duplicatesโ, โfree disk spaceโ, โdeclutterโ, or โbloatโ.
Use when implementing any feature or bugfix, before writing implementation code