house-stylelisted

# House Style Every other skill in this OS produces a generic-but-solid format by default. This skill captures *your company's* format once — voice, structure, terminology, templates, branding — into `memory/house-style.md`, so from then on every spec, update, and plan comes out looking like it was written inside your company, not by a tool. **Grounded in:** style-guide practice (e.g. *The Elements of Style*; Mailchimp / Atlassian content design systems): codify voice + structure once, apply it everywhere. ## When to use this - First-time setup: you want all outputs to match your company's format. - You have an existing doc (a real PRD, a brand guide, a great stakeholder update) and want Claude to write like that. - Your outputs keep coming out in a style you have to re-edit every time. - Onboarding the OS for a new team with its own conventions. ## Before you start (gather these) Format is learned from an example, never asked cold. Get one of these in hand: - **A real document the company published** — a shipped PRD, a launch update, a board memo. The more recent and the more "normal" it is, the better; a showpiece teaches you the exception. - **The audience it was written for** — an exec memo and a team update follow different rules, and merging them produces a style that fits neither. - **Anything already written down** — a style guide, a brand doc, a template someone maintains. Even a stale one tells you what they *think* the rules are. - **The terminology that matte