What problem does it solve? Project instructions often fail because rules are written in the wrong layer: facts pasted into instructions instead of knowledge, one-off tasks frozen as permanent rules, or conversational tone guidance given to an agentic Cowork project that needs deliverables and save paths. This Skill routes every rule to the correct layer (profile, project instruction, knowledge, memory, or skill) before writing, and audits existing instructions that Claude ignores. ## Core Features & Use Cases - Layer routing: Classifies each rule against a durability test (durable, non-obvious, no better home) and assigns it to the right layer for Chat Projects or Cowork Projects, which have opposite mental models. - Three modes: CREATE (interview of max 7 questions, routing table, then drafting within a 1,500-2,500 character budget), AUDIT (named-failure catalog such as instruction-resume, dead rule, encyclopedia, silent conflict, orphaned negative), and PACKAGE (full project setup with folders, connectors, skills, and a versioned source file for teams). - Platform-accurate guidance: Encodes verified facts such as Cowork not reading ~/.claude, Cowork projects being local-only, 50 MB file limits, and the documented organization-over-individual precedence. - Use Case: A user pastes a 9,000-character instruction that Claude ignores; the Skill counts and classifies every fragment, names each failure, moves the pricing table to knowledge, and delivers a full rewrite with concrete test prompts. ## Quick Start Ask the assistant to write or review the instructions for your Claude project, pasting any existing instruction text and mentioning whether it is a Chat Project or a Cowork Project.
