design-lock
Skill2 starsChanged 3 months agoMITView on GitHub
Freezes the design constitution. Walks through the 9 sections of DESIGN-LOCK.md, previews each choice, locks it. After LOCK, /build works only with these values. Also appends approved elements from §7 imagery and §8 section vocabulary to references/approved-manifest.md.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sander217/sanstudiotheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sander217/sanstudio★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Pivotal moment of the workflow: Before this: research and decisions.
- Very specific: line 14
After /refs (there is a proposal with reasons).
- Very specific: line 16
Before /tokens and /build (they refuse to work without LOCK).
- Distinctive: line 28
If anything is missing — offer to run what's missing first.
- Distinctive: line 44
Ask: accept / change / show alternatives.
- Distinctive: line 45
If "change" — offer 3 variants, let user pick.
- Very specific: line 46
Write the final value to DESIGN-LOCK.md, mark STATUS: LOCKED.
- Very specific: line 64
If yes — every section gets STATUS: LOCKED.
- Very specific: line 69
After the freeze, walk two more passes to update references/approved-manifest.md:
- Distinctive: line 82
Every approved section type becomes a "must appear on the landing" contract:
- Very specific: line 97
After LOCK, any edit to DESIGN-LOCK.md:
- Distinctive: line 104
One section — one screen: Do not dump the whole thing.
- Distinctive: line 108
Do not accept "just do whatever": If unsure, show real-site examples.
- Distinctive: line 113
Do not fill sections on autopilot without per-section confirmation.
- Distinctive: line 114
Do not allow LOCK if any field is still TBD.
- Distinctive: line 115
Do not change already-LOCKED sections in the same session ("oh let's try again") — explicit override only.
- Distinctive: line 116
Do not skip previews — they save "looked fine on paper, bad in the eye".
- Very specific: line 117
Do not overwrite references/approved-manifest.md — always append.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/design-lock
Pivotal moment of the workflow. Before this: research and decisions. After this: build only.
Fills DESIGN-LOCK.md — the design constitution that gets frozen and does not change without explicit override.
When to use
- After
/refs(there is a proposal with reasons). - OR after
/brief+/copy-analyzeif there are no references. - Before
/tokensand/build(they refuse to work without LOCK).
Requirements
Verify readiness:
brief/00-priority.md— LOCKED (desktop-first / mobile-first).brief/01-business.md— filled (niche, competitors).brief/05-design.md— filled (mood, associations).brief/copy-analysis.md— exists (affects length, tone, section structure).references/proposal.md— exists (if/refsalready ran).references/approved-manifest.md— exists (created by/refs; empty is fine).
If anything is missing — offer to run what's missing first.
Process
Walk the 9 DESIGN-LOCK.md sections strictly in order. Each is a separate dialog.
For every section:
- Show the current proposed values (from
references/proposal.mdif present, else frombrief/05-design.md). - Explain briefly why these values (one sentence).
- Show a preview — generate a mini-HTML example right in the message:
- For type — a block with H1, H2, body using the actual fonts.
- For color — palette tiles with HEX values.
- For radius — 3 squares with different radii for comparison.
- For spacing — a visual scale.
- For motion — describe (ease + duration) + offer a URL of a site with the example.
- Ask: accept / change / show alternatives.
- If "change" — offer 3 variants, let user pick.
- Write the final value to
DESIGN-LOCK.md, markSTATUS: LOCKED.
Section order (by dependency):
- Spacing — base of everything.
- Type scale — depends on spacing.
- Color — independent.
- Radius — independent (but should match density).
- Motion — independent, but should match mood.
- Density — affects spacing multipliers.
- Photography — independent.
- Section vocabulary — depends on structure from
/copy-analyze. - Anti-patterns — all on by default; only disable with a reason.
Final step:
- Show the full
DESIGN-LOCK.mdto the user. - Explicit confirmation: "freeze? After this, changes require override with an entry in the decision log."
- If yes — every section gets
STATUS: LOCKED. - Record the first entry in
DESIGN.md→ Decisions log about the LOCK.
Appending to the approved manifest
After the freeze, walk two more passes to update references/approved-manifest.md:
Pass 1. §7 Photography / Imagery items.
Any concrete visual element the user committed to becomes a manifest entry:
[ ] imagery: full-bleed hero photograph, aspect 16:9 ← DESIGN-LOCK §7
[ ] imagery: documentary style, high contrast ← DESIGN-LOCK §7Pass 2. §8 Section vocabulary items.
Every approved section type becomes a "must appear on the landing" contract:
[ ] section: hero (large visual + headline) ← DESIGN-LOCK §8
[ ] section: proof (numbers or logos) ← DESIGN-LOCK §8
[ ] section: offer (product + benefits) ← DESIGN-LOCK §8
[ ] section: cta-form (request form) ← DESIGN-LOCK §8If a section type is defined in §8 but never actually needed on this landing (e.g. proof was locked in the vocabulary but the client has no numbers yet) — user must explicitly remove it from the manifest here, with a note in DESIGN.md decision log. Never silently drop.
Append, do not overwrite. /refs populated the file first; subsequent skills (/animation, /icons) will append more.
Enforcement rules
After LOCK, any edit to DESIGN-LOCK.md:
- Requires explicit
overridefrom the user. - Is recorded in
DESIGN.md→ Decisions log with a reason. - Triggers reevaluation of dependent sections (e.g. changing base spacing → recompute the whole rhythm).
Rules of behavior
- One section — one screen. Do not dump the whole thing.
- Always show a preview. Abstract numbers are meaningless without a visual.
- Offer 3 alternatives when the user asks — not 10, not 2.
- Do not push fashion. Serif is trendy right now — but if the brand is tech SaaS, sans is better.
- Do not accept "just do whatever". If unsure, show real-site examples.
- Never skip the manifest append. Silent drops of approved elements is the failure mode.
What NOT to do
- Do not fill sections on autopilot without per-section confirmation.
- Do not allow LOCK if any field is still TBD.
- Do not change already-LOCKED sections in the same session ("oh let's try again") — explicit override only.
- Do not skip previews — they save "looked fine on paper, bad in the eye".
- Do not overwrite
references/approved-manifest.md— always append.
Next
After LOCK:
/blocks— ifbrief/blocks/interactive block configs aren't filled yet./animation— dedicated motion brief; appends animation items to the manifest./tokens— generatessite/css/tokens.cssfrom DESIGN-LOCK./mediaand/icons— assets./build— section assembly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

