designlisted

# /mneme:design — Design UI pages as reviewed HTML etalons, before any code An ENTRY skill of the plan family: multi-turn, gated by HARD STOPS, and NOT an engine run — every design gate is HUMAN, at the skill level (the two-hard-stop precedent of `/mneme:plan`). The engine and the mneme MCP tools are untouched. Its place in the pipeline: задача/спека → `/mneme:design` (эталоны) → `/mneme:plan` «реализовать страницу по эталону `design/pages/<slug>/<slug>.html`» → migrate → `/mneme:dev`. design NEVER launches plan — the finale hands over the READY phrase as a fenced block (the grill precedent); running it is the user's move. The skill drives ONE UI task through FOUR stages; each stage ends in a HARD STOP — the turn ends, and continuation happens only on the user's explicit confirmation. Whether a stage's outcome is "obviously fine" is the USER's judgement, never the agent's. ## Arguments `/mneme:design "<UI task in words>"` — the feature or page(s) to design, in plain language. No argument → ask for the task in one line (numbered prompt). Never invent a task. ## Artifacts — in the TARGET project's repo, never in the corpus - **A page is a FOLDER** `design/pages/<slug>/` — the etalon `design/pages/<slug>/<slug>.html` (ONE file per page: all states and fixtures INSIDE, deliberate decisions annotated via HTML comments / data-attributes) plus THAT page's composition drafts (`<slug>-draft-*.html`) and future iterations. The slug `index` is RESERVED for the pages index