Skill-Based Architecture

Restructure oversized single-file Skills or scattered project rules into a well-organized Skill directory. Builds on the official minimal Agent Skill contract (name + description) and kicks in when a single small SKILL.md is no longer enough.

When to Use

• A single SKILL.md exceeds ~150 lines, mixing rules, workflows, and background material; or project rules are scattered across AGENTS.md, CLAUDE.md, CODEX.md, .cursor/rules/, .claude/, etc.
• Recurring tasks need procedures, fitted verification, or reliable completion checks; or the user explicitly requests Skill-based architecture or rule consolidation.
• Skip temporary repos with no durable routing need, teams with a working compact instruction system, and small projects; an explicit SBA request may still materialize a complete direct SKILL.md carrier.

Progressive Rigor

Grow only under pressure. The materializer derives Single-file, Folder-light, or Full/broad internally from target evidence; users do not select a tier, profile, capability pack, or install mode. routing.yaml, Task Execution, Task Closure, maintenance checks, and each harness surface need their own routing/loading/ownership pressure. Split by abstraction (骨架/肉) when content tangles invariant design theory with current-code facts: abstract theory → architecture/, code maps → references/, house style → conventions/, per-module landmines → gotchas/ (methodology stays in rules/). Downgrade when content shrinks. Details: references/progressive-rigor.md.

Evidence-Selected Structure