\r \r

Role\r

\r This skill owns skill catalogs, routing indexes, migration catalogs, and repository knowledge structure for AI-facing documentation. It keeps discoverability clean after refactors and ensures future agents can route work without loading unnecessary material.\r \r

When To Use\r

\r

• Use for skill indexes, routing references, migration reports, knowledge catalogs, and AI-facing repository guidance.\r
• Use for keywords such as skill index, routing map, knowledge base, migration report, and AI docs structure.\r
• Use when a skill system, AI workflow, or repository knowledge layout is being reorganized.\r \r

Source Material\r

\r

• AI-ENTRY.md\r
• AI-README.md\r
• CLAUDE.md\r
• dev/ai/skills/_index.md\r
• dev/ai/skills/weline-framework-skill-router/SKILL.md\r
• dev/ai/skills/documentation-standards/SKILL.md\r \r

Responsibilities\r

\r

• Keep skill indexes and routing references current after structural changes.\r
• Preserve repository reading order and discovery guidance for future agents.\r
• Record migration mappings and missing-source status when skills are reorganized.\r
• Keep AI-facing knowledge concise, navigable, and self-consistent.\r \r

Workflow\r

\r

1. Read the current AI entry documents and routing indexes before restructuring knowledge files.\r
2. Identify outdated paths, renamed skills, and role-based routing needs.\r
3. Rewrite indexes and mapping documents to match the new structure.\r
4. Preserve mandatory reading order and critical repository guardrails in the knowledge surface.\r
5. Record migration scope, source usage, and missing-source status in a dedicated report.\r
6. Validate that each referenced path exists and matches the intended role.\r
7. Report the new navigation model and any remaining follow-up needs.\r \r

Weline Rules\r

\r

• Read AI-ENTRY.md first.\r
• Prefer diagrams and module docs before reading source code.\r
• Keep AI-facing routing material concise and discoverable.\r
• Do not require legacy source files at runtime for the new skill system.\r \r

Inputs Required\r

\r

• The old and new skill structures.\r
• Required role model and routing expectations.\r
• Any mandatory source list or migration constraints.\r
• The target directory and naming scheme.\r \r

Expected Output\r

\r

• Updated knowledge-base files, indexes, and migration mappings.\r
• A self-consistent route from entry docs to the new skill system.\r
• A report that records whether any required source material was missing.\r \r

Validation\r

\r

• Check that all referenced skill paths exist.\r
• Check that role names, folder names, and index labels align.\r
• Check that the new knowledge files preserve critical repository rules.\r
• Check that migration reporting accurately reflects source availability.\r \r

Constraints\r

\r

• Do not leave stale routing references to the old structure without explanation.\r
• Do not depend on runtime loading of legacy skill files.\r
• Do not omit migration notes when the structure changed materially.\r
• Do not bloat the index with redundant narrative when a routing table is enough.\r \r