<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/claude-rules/ui-prototyping.md, branch main</title>
<subtitle>Claude Code skills, rules, and language bundles
</subtitle>
<id>https://git.cjennings.net/rulesets/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/rulesets/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/'/>
<updated>2026-07-11T07:02:45+00:00</updated>
<entry>
<title>docs(spec): add UI-prototyping process for non-trivial-UI specs</title>
<updated>2026-07-11T07:02:45+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-11T07:02:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=53f6ce69cab812b57985b992709d894c5077ffb3'/>
<id>urn:sha1:53f6ce69cab812b57985b992709d894c5077ffb3</id>
<content type='text'>
For a spec whose deliverable is a real UI, a design argued on paper is a guess. New claude-rules/ui-prototyping.md: research the category first, brainstorm the UX in the spec, build ~5 distinct working prototypes over one engine, iterate one to a final, and record a UI decision only once it's been seen working in a prototype. spec-create gains the step for non-trivial-UI specs. spec-review gates on it: research cited, final prototype linked, iterations in history, decisions backed by a prototype. Prototypes live at docs/prototypes/&lt;spec-name&gt;-prototype-&lt;N&gt;.html.

Worked example: archsetup's timer-panel spec and its three prototypes.
</content>
</entry>
</feed>
