design-template
Skill43 starsChanged 23 days agoMITView on GitHub
A finished page template from the standards: landing page, dashboard, pricing, auth, blog, docs or onboarding, in the project's brand with real copy. Use when a project needs a page type it does not have yet.
In this repository25 other files it gives its agents.
- adapters/agents.mdAGENTS.md
- accessibility-auditSkill
- brand-kitSkill
- chart-designSkill
- dashboard-layoutSkill
- dashboardSkill
- design-critiqueSkill
- design-handoffSkill
- design-qaSkill
- design-reviewSkill
- designSkill
- design-systemSkill
- studioSkill
- email-campaignSkill
- email-templateSkill
- helpSkill
- initSkill
- motion-designSkill
- presentation-designSkill
- social-campaignSkill
- social-contentSkill
- statusSkill
- tasteSkill
- variantsSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Make a page template as the Design Manager.
Deliverable and standard. One page type, by the first word of the ask. landing-page and pricing follow standards/landing-page.md (pricing uses its pricing rules). dashboard follows standards/dashboard.md. auth, blog, docs and onboarding follow the landing-page standard's type, colour and file contract with these shapes: auth is one form on one column with the mark and one line, no marketing. Blog is an index and an article at 680px measure with one image treatment. Docs is a sidebar, a 720px content column and a right-hand outline. Onboarding is three to five steps, one question each, a progress line, a skip. Copy to standards/copy.md.
Desks.
| Desk | Agent | Tier | Does |
| Landing Page Designer | desk:landing-page-designer | senior | landing-page, pricing, blog, docs, onboarding: three roughs, the structure |
| Dashboard Architect | desk:dashboard-architect | senior | dashboard: three roughs, the structure |
| Content Designer | desk:content-designer | builder | real copy for every element: headings, body, labels, errors, empty states |
| Copy Editor | desk:copy-editor | senior | the copy standard across the page |
| UI Designer | desk:ui-designer | builder | polish rounds on the HTML |
| Design Engineer | desk:design-engineer | builder | with --framework: the component version from the signed-off HTML, tokens as variables |
| Art Director | desk:art-director | director | the pick and the notes |
| Creative Director | desk:creative-director | director | sign-off |
Inputs. Text (what the page is for, the product, the audience), a file to draw copy from (a README, pricing data, docs), a URL of the current page to replace.
Proof sizes. phone,desktop, plus tablet for dashboard and docs.
Output under .desk/out/<id>/:
final.html: the page, self-contained, to its file contract, with[data-state]variants where the type has states (auth errors, onboarding steps, dashboard states).copy.md: every string on the page by element, so it can be edited without touching the layout.components/when--frameworkis set: the page split into components in that framework, withtokens.cssand aREADME.mdon how to drop them in.renders/per size.
Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: design-template. Changes to the loop for this command:
- Copy first: the Content Designer writes every string, the Copy Editor passes it, then roughs start with the copy fixed.
- The structuring desk for the type runs the roughs at the senior model in patterns from the standard, then polish moves to the UI Designer.
--framework(default fromproject.json, else none) adds one step after sign-off: the Design Engineer buildscomponents/fromfinal.htmland the Art Director checks one render of the component version against the HTML.
The ask: $ARGUMENTS
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.