cover
Skill0 starsChanged 59 days agoMITView on GitHub
Create or update a project-specific DESIGN.md with a distinctive art direction and visual tokens for pages, images, and video. Trigger on "DESIGN.md", "视觉设计", "设计规范", "design spec", or "参考 XX 风格做设计". Not for a one-off mockup or video production.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- grooownow/qa-pilottheir own version, first seen Oct 28, 2026
- osteel/agent-skillstheir own version, first seen Oct 13, 2026
- howells/fictiontheir own version, first seen May 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- howells/fiction★ 23same name
- grooownow/qa-pilot★ 6same name
- osteel/agent-skills★ 3same 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.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acquisitionSkill
- after-actionSkill
- breachSkill
- cartographic-reconSkill
- chartSkill
- codifySkill
- conopsSkill
- dossierSkill
- executeSkill
- go-nogoSkill
- herdrSkill
- netease-mailSkill
- neutralizeSkill
- paperworkSkill
- passdownSkill
- repairSkill
- sanitizeSkill
- taskingSkill
- tracebackSkill
- warroomSkill
- x-likes-digestSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create or update a project-owned DESIGN.md: art direction, visual tokens, and medium-specific expression rules.
- Distinctive: line 35
Before combining references or handing a direction to a renderer, read Cross-media design, including reference collaboration, conflict …
- Distinctive: line 58
Ask the user (or infer from context):
- Distinctive: line 64
If the user gives a short description without these details, make reasonable assumptions based on the product type and state them before …
- Very specific: line 69
When a request names a style, supplies new visual references, or needs a direction chosen, read Style routing.
- Distinctive: line 72
Do not route from brand names or palette keywords alone.
- Distinctive: line 77
Add references only when they answer a specific unresolved question.
- Distinctive: line 88
Read selected specifications in full.
- Distinctive: line 156
After the DESIGN.md, list which references were studied and what was adapted from each.
- Very specific: line 158
Write evidence to .design/evidence.json:
- Distinctive: line 186
Don't represent another product's DESIGN.md or brand assets as your own.
- Distinctive: line 187
Don't add or combine references merely to satisfy a count or appear original.
- Distinctive: line 188
Don't include implementation code (CSS, JSX, etc.) — DESIGN.md is a spec, not code.
- Distinctive: line 189
Don't prescribe exact component markup — describe the visual properties (border radius, shadow, padding) not the HTML structure.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Visual Design
Create or update a project-owned DESIGN.md: art direction, visual tokens, and medium-specific expression rules. Renderers consume this contract; Cover does not make pages, images, or films. Preserve existing project choices unless the user requests a redesign.
Core Rule
Study one strong, concrete reference as a whole before pursuing originality. Carry its composition, hierarchy, typography, color relationships and rhythm into a coherent product visual language. Strong resemblance is a valid learning goal; adapt only where real content, use, or project constraints require it. Identify the source and material departures. Do not pass off another project's DESIGN.md or protected brand assets as the product's own.
Art direction before tokens
State the project's visual idea and the concrete choices that make it recognizable:
composition, shape, color relationships, typography, material, and, when relevant,
motion and sound. Select a dominant direction rather than averaging references.
For image generation, follow the user's prompt; catalog style routing is not
mandatory unless requested. Serious data charts using lieflat-charts follow
its data, template and visual rules, not the surrounding artistic direction.
Warm paper, muted colors, rounded cards, and glossy gradients are choices, never
a universal safe default. Cold, monochrome, saturated, rough, or austere work can
be equally coherent. Legibility constrains use, not personality.
Before combining references or handing a direction to a renderer, read Cross-media design, including reference collaboration, conflict resolution and ownership. These rules also apply to HTML alone. For artist, artwork, or launch-film references, read Reference selection. A palette swap alone does not establish a new art direction. Each new HTML work or film needs its own subject-led composition and signature choices, even when its style family or project tokens are shared. Read the artifact-identity section of the cross-media contract before handing a direction to a renderer.
Reference Library
~/.agents/repos/awesome-design-md/design-md/For product UI references, read the repo README first for the current index. Artist portfolios, specific artworks, and official films can also supply reference vocabulary; use actual inspected material and its provenance.
Workflow
Step 1: Understand the project
Ask the user (or infer from context):
- What is the product? (SaaS dashboard, CLI tool, developer platform, consumer app, etc.)
- Who is the audience? (developers, enterprise, consumers, designers, etc.)
- What is the desired visual tone? (warm/human, cold/technical, premium/luxury, playful, minimal, etc.)
- Any existing brand constraints? (logo, existing colors, company design system)
If the user gives a short description without these details, make reasonable assumptions based on the product type and state them before generating.
Step 2: Find reference matches
When a request names a style, supplies new visual references, or needs a direction chosen, read Style routing. Use its catalog and structured route to resolve explicit/project/evidence selection before synthesis. Do not route from brand names or palette keywords alone. Preserve uncertainty when observations are insufficient; adding references does not require a new skill.
Study one primary reference selected for the project's task and artistic direction. Add references only when they answer a specific unresolved question; preserve the primary reference's overall visual coherence rather than mixing for novelty. For UI references use the awesome-design-md index; for artworks/films use the reference-selection guide. A style catalog is a discovery pool, not 29 inputs to blend. Existing project DESIGN.md can be one reference during an update.
Select by the decision that needs evidence: expressive choices must fit the work's thesis; structure and controls must fit the reader task. Industry similarity can help find functional patterns but does not select the aesthetic. Use only the relevant reference layers; do not force one source from each library.
Read selected specifications in full; inspect artworks directly and films at the level needed for the claim. Record frame-only, sequence, audio, and creator-credit evidence separately. Do not infer motion timing or sound from stills.
Step 3: Form the product language
Produce a DESIGN.md around the resolved visual thesis. Derive tokens and medium rules from it, learning the primary reference's choices together and adapting them to actual product needs. Preserve project constraints outside the requested change; record which defaults are replaced and why. Do not average reference styles or let website tokens overrule the selected art direction.
The synthesis should feel like a coherent design system, not a patchwork. A single artifact should have a clear visual thesis. A project may define named directions with explicit selection rules; resolve one direction per artifact. Shared identity can survive different palettes and media through recurring shape, composition, typography, material, or motion choices.
Step 4: Output
Record the art direction (thesis, signature choices, scope, and avoided defaults) before deriving tokens. Use the token structure below as a base; add medium rules only for requested media, following the cross-media reference:
---
version: alpha
name: <Project Name>
description: <One paragraph capturing the visual thesis — palette, type voice, spatial character>
---
colors:
primary: "#hex"
primary-active: "#hex"
ink: "#hex"
body: "#hex"
muted: "#hex"
hairline: "#hex"
canvas: "#hex"
surface-card: "#hex"
surface-dark: "#hex"
on-primary: "#hex"
on-dark: "#hex"
success: "#hex"
warning: "#hex"
error: "#hex"
typography:
display-lg:
fontFamily: "..."
fontSize: 48px
fontWeight: 400
lineHeight: 1.1
# ... through body-sm
spacing:
unit: 4px
# semantic spacing tokens
components:
# key component patternsAdapt the token set to what matters for the project. Don't include every possible token — include what the AI agent needs to render the product's core screens consistently.
After the DESIGN.md, list which references were studied and what was adapted from each.
Write evidence to .design/evidence.json:
{
"references_studied": ["vercel-DESIGN.md", "linear-DESIGN.md"],
"adaptations": {"vercel-DESIGN.md": "dark color palette", "linear-DESIGN.md": "keyboard-first interaction"},
"wholesale_copy": false
}Run gate:
python3 <skill-dir>/scripts/synthesis_gate.py --design <path> --evidence .design/evidence.jsonpass means structural checks passed, not that the style is distinctive or
visually accepted. Report structural validation and artistic review separately.
Inspect requested samples for recognizable choices, content fit, and fidelity
to the chosen direction; absent samples remain not-run. Do not generate
additional deliverables merely to satisfy a visual check.
Optional Implementation Checks
Generating DESIGN.md does not require UI implementation advice. Only when the
user also asks to build or review the UI, read
Implementation checks. It checks
functional correctness and fidelity, without adding aesthetic defaults.
What Not To Do
- Don't represent another product's DESIGN.md or brand assets as your own.
- Don't add or combine references merely to satisfy a count or appear original.
- Don't include implementation code (CSS, JSX, etc.) — DESIGN.md is a spec, not code.
- Don't prescribe exact component markup — describe the visual properties (border radius, shadow, padding) not the HTML structure.
Canon 输出边界
读取共享契约:/home/yhr/.agents/repos/agent-skills/references/canon-output-contract.md。
- Generated DESIGN.md files are project artifacts. If a visual/design decision should persist across projects, record it in Canon
decisions/orpatterns/and reference the DESIGN.md path. - Canon update-card path, when needed:
/media/yhr/2T/Canon/raw/update-cards/<date>-cover-<topic>.md.
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.

