← ClaudeAtlas

shapelisted

Run a time-boxed system design session with the user for something new (a project, a feature, a tool, a take-home), from a rough idea to a design doc that a fresh session can build from. Five clocked steps in system-design order — requirements, entities and scale, approaches, interfaces and decisions, scope and the doc. The user decides; the agent widens the options, then narrows the scope. Use when the user asks for a design session, with words such as "let's design", "design this", "system design approach", "scope this", "interview me", "brainstorm this with me", or a time for design ("design in 2h"). Not for a question or a thought said out loud (assess and stop), not for one decision that needs a page (brief-artifact), not for the task plan after the design (the plan genre of writing-markdown-docs, or the visual-artifacts Plan page), and not for explaining a system that already exists.
SeanoChang/seanock · ★ 0 · Data & Documents · score 70
Install: claude install-skill SeanoChang/seanock
# shape In a design session the agent widens: it shows approaches and cases the user did not think of. The user narrows: one scope, small enough to build in the time there is. Without a clock the widening wins. So the time is fixed and the scope varies. The session ends on time with a design doc, and the doc lists what was not decided. ## Which rule applies Other files cover some of the same cases. For each, one rule applies: - **The time box in CLAUDE.md.** This skill is how that rule runs for a design session. Its must-haves and its cut list are in "The clock". The cut list of the build is made in step 5. - **A question, or a thought said out loud,** gets an assessment and a stop, as CLAUDE.md says. Start a session only when the user asks for one. - **Pages.** In a session, "Pages" below replaces the `brief-artifact` skill's own rule for when to make a page. - **The doc.** The design genre of `writing-markdown-docs` sets its outline, tables, word budget and path. Step 5 says only what goes into each section. - **Task order and tiers.** The plan genre and CLAUDE.md set them, in the next session. Step 5 names milestones and deep dives, and orders no tasks. - **Agents.** Step 5 starts one `verifier` in its refute mode. This skill starts no other agent. ## Before the first step 1. **Get the time box.** If the user gave none, ask once: 120 minutes for a project, 30 for a feature. A box of 60 minutes or less is a feature. 2. **Note the start** (`date`). Sho