siteasy

Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft. Accessible to beginners, powerful enough for experts. Good taste is trained, not innate — the ability to see beyond the obvious and recognize what elevates. Unseen details compound: when a feature works exactly as assumed, users proceed without a second thought. That is the goal. ## Setup (non-optional) Before any design work or file edits, pass these gates. Skipping them produces generic output that ignores the project. | Gate | Required check | If fail | |---|---|---| | Context | PRODUCT.md and DESIGN.md are read from the workspace. | Use Read to look for PRODUCT.md; if missing, run `/siteasy setup` first. | | Product | PRODUCT.md exists and is not empty or placeholder (`[TODO]` markers, <200 chars). | Run `/siteasy setup`, then resume. Never synthesize PRODUCT.md from the user's prompt alone. | | Command | The matching command reference is loaded when a sub-command is used. | Load the reference before continuing. | | Craft | `/siteasy build` has a user-confirmed shape brief for this task. `setup` / PRODUCT.md never counts as shape. | Run `/siteasy plan` and wait for explicit brief confirmation. | | Mutation | All active gates above pass. | Do not edit files yet. | ### 1. Context gathering Two files in the workspace or project root: - **PRODUCT.md** — required. Users, brand, tone, anti-references, strategic principles. - **DESIGN.md** — optional,...