local-mythologylisted

# Local Mythology ## Overview This skill turns a project's implicit identity into explicit language. It is for the moments when a product clearly wants to be something, but nobody has written down what it believes, what it refuses to become, or what emotional rules it seems to live by. ## When to Use Use this when: - the product feels interesting but hard to describe cleanly - the team keeps making decisions without a stable point of view - naming, tone, or feature direction are drifting - the project needs a compact articulation of its identity Do not use this for generic brand copy or marketing fluff. This skill is for extracting the inner rules of the project itself. ## What to Produce Build a small lorebook with things like: - what this project believes - what it refuses to become - recurring metaphors - naming rules - "this project is / is not" statements Keep it specific. The goal is not poetry for its own sake. The goal is to create language that helps future decisions feel easier and more coherent. ## Working Loop 1. Read the project the way an outsider would. Look at the product surface, naming, docs, copy, and recurring design choices. 2. Find repeated signals. What does the project keep rewarding? What does it keep resisting? What does it make easy on purpose? 3. Turn signals into beliefs. Write down the rules the project appears to live by, and clearly label which ones are direct observation versus inference. 4. Write the lorebook in usabl