atelier
Skill4 starsChanged 4 days agoMITView on GitHub
Atelier design intelligence (El DT + Impeccable). Use for UI/UX design, craft, critique, audit, polish, anti-slop, tokens, decks, and frontend iteration. Invoke /atelier <command> [target]. Covers landing, dashboard, product UI, components, motion, a11y, and design system alignment.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- Caiollaz/ateliertheir own version, first seen Nov 8, 2026
- ksprashu/agent-skill-forgetheir own version, first seen Nov 1, 2026
- ask-marcel/ask-marcel-office-clitheir own version, first seen Oct 25, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- robingst/skillstheir own version, first seen Oct 20, 2026
- adamramadhn/ateliertheir own version, first seen Oct 20, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- simota/agent-skills★ 99same name
- ask-marcel/ask-marcel-office-cli★ 9same name
- Wondermonger-daydreaming/claude-skills-library★ 7same name
- mhxie/Atelier★ 5same name
- ksprashu/agent-skill-forge★ 3same name
- adamramadhn/atelier★ 2same name
- luminary19/atelier★ 2same name
- anshrajore/atelier-mcp★ 0same name
- Caiollaz/atelier★ 0same name
- remp0x/atelier-claude-plugin★ 0same name
2 more not listed
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 repository169 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/00-orquestador-core.mdcCursor rule
- .cursor/rules/01-protocolos-dt.mdcCursor rule
- .cursor/rules/02-documentacion.mdcCursor rule
- .cursor/rules/03-catalogo-subagentes.mdcCursor rule
- .cursor/rules/05-multi-project-git.mdcCursor rule
- .cursor/rules/06-dt-colaboracion.mdcCursor rule
- .cursor/rules/07-orden-continuo.mdcCursor rule
- .cursor/rules/08-stack-web-default.mdcCursor rule
- .cursor/rules/10-arquitectura-backend.mdcCursor rule
- .cursor/rules/15-engineering-reuse.mdcCursor rule
- .cursor/rules/16-numeric-grounding.mdcCursor rule
- .cursor/rules/17-canvas-first.mdcCursor rule
- .cursor/rules/18-drive-contexto.mdcCursor rule
- .cursor/rules/19-gmail-contexto.mdcCursor rule
- .cursor/rules/20-frontend-ui.mdcCursor rule
- .cursor/rules/21-calendar-contexto.mdcCursor rule
- .cursor/rules/30-testing.mdcCursor rule
- .cursor/rules/31-agent-inbox.mdcCursor rule
- .cursor/rules/40-devops.mdcCursor rule
- .cursor/rules/90-seguridad-secrets.mdcCursor rule
- analisis-propuestaSkill
- arquitectoSkill
- atelier-actualizarSkill
- auditoria-legalSkill
- bragSkill
- brand-guardianSkill
- content-creatorSkill
- data-auditorSkill
- deploySkill
- development-plannerSkill
- devopsSkill
- docSkill
- dt-actualizarSkill
- dt-ayudaSkill
- dt-bootstrapSkill
- dt-calendarSkill
- dt-configSkill
- dt-driveSkill
- dt-gmailSkill
- dt-oficialSkill
- dt-ordenarSkill
- dt-revisar-instalacionSkill
- dt-sessionSkill
- dt-setupSkill
- dt-skillsSkill
- engineering-reuseSkill
- feedback-synthesizerSkill
- frontendSkill
- git-actualizarSkill
- git-guardarSkill
- github-save-releaseSkill
- growth-hackerSkill
- hack-auditSkill
- marketing-strategistSkill
- operations-maintainerSkill
- pitch-specialistSkill
- prd-creatorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 6 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Before writing files in the repo:
- Very specific: line 17
Read vitals/ops/session.yaml.
- Distinctive: line 22
Run once per session (not per sub-command):
- Very specific: line 34
If output reports NO_DESIGN_CONTEXT, stop and follow tools/atelier/generated/references/init.md.
- Distinctive: line 47
Do not create duplicate PRODUCT.md/DESIGN.md.
- Very specific: line 62
When building surfaces, load one tactical skill from .cursor/skills/design/:
- Very specific: line 75
craft / shape+build: write production UI code directly (stack: regla 08-stack-web-default).
- Distinctive: line 98
After resolving analysis and direction, read tools/atelier/generated/references/craft-floor.md immediately before any UI edit, including …
- Distinctive: line 157
No argument: read routing.md and present its context-aware menu.
- Distinctive: line 159
Workflow or command-selection question: read Workflow questions.
- Very specific: line 160
Otherwise: treat the request as general design work.
- Very specific: line 163
After init writes .agents/design-context.md, resume without rerunning context.adapter.mjs.
“Common” is measured: kept by at least 6 in 10 of the 12 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
Atelier — design intelligence (El DT)
Router unificado. Upstream: Impeccable vendoreado vía tools/atelier/.
DT session gate (El DT)
Before writing files in the repo:
- Read
vitals/ops/session.yaml. If missing oroperator.idempty → stop and ask the user to run/yo. - Design context:
.agents/design-context.md— only path, local (gitignored). Criterio:vitals/specs/design-skills-protocol.md§ Contexto de diseño. Fields:.cursor/skills/design/design-context/references/context-schema.md. No separate PRODUCT.md/DESIGN.md unless exporting.
DT context loader
Run once per session (not per sub-command):
node tools/atelier/generated/scripts/context.adapter.mjsOptional target for monorepos:
node tools/atelier/generated/scripts/context.adapter.mjs --target <path>- If output reports
NO_DESIGN_CONTEXT, stop and followtools/atelier/generated/references/init.md. - Imports
.agents/product-marketing.mdwhen present (see design-context skill). UPDATE_AVAILABLE: offer/atelier actualizar(DT maintainer sync), then continue.
Register references (DT paths)
Impeccable 4 names visitor modes. Map register from design-context:
design-context register | Mode | File |
| brand (marketing, landing, portfolio) | Persuade | Modes in this skill + tools/atelier/generated/references/new-work.md |
| product (app, dashboard, tool) | Operate | tools/atelier/generated/references/operate.md |
Do not create duplicate PRODUCT.md/DESIGN.md.
DT-native subcommands
| Command | Action |
/atelier select [brief] | ruby scripts/dt-design-select.rb "brief" + skill design-selector |
/atelier read | skill design-read — V/M/D dials |
/atelier tokens | skill design-tokens |
/atelier template [name] | skill ui-templates or --scaffold → tools/atelier/starters/ |
/atelier deck [brief] | references/deck.md — brand manual gate + slide-deck-html |
/atelier actualizar | skill atelier-actualizar — sync Impeccable upstream |
DT extensions (after Impeccable setup)
When building surfaces, load one tactical skill from .cursor/skills/design/:
| Moment | Skill |
| Post-init | design-selector |
| Pre-craft/shape | design-read |
| Surface layout | system-templates, style-templates, patterns/* |
| Pre-ship | anti-slop + ./scripts/atelier-detect.sh |
Ecosystem lock-in (Shopify, Atlassian) → DT pack wins over generic Impeccable defaults.
Agent routing
- craft / shape+build: write production UI code directly (stack: regla
08-stack-web-default). - critique / audit / polish: may stay spec-only or fix code in place.
- Handoff to frontend when: backend integration, large refactor, E2E tests, or user asks.
Engineering reuse (craft/build)
Apply regla 15-engineering-reuse: discover repo UI before creating new modules.
This skill gives you the tools and permission to create design that earns to be called out-of-distribution craft: Whereas before, your design work would have been safe, timid and measured, you now approach every design task as an award-winning design director with impeccable understanding for what makes exceptional design work: production-grade code, peak creativity, a clear POV, deep understanding of the needs of the client and users, and exceptional craft.
Core principles:
- Go all out. No hedging, no shortcuts. The deliverable must be complete (except assets the user must provide).
- Dream big and bold. Distinct, beautiful, outstanding and highly inspiring work.
- Verify in bounded passes, not a loop, and the ceiling covers the whole cycle: screenshots, defect scans, micro-edits, and rebuilds alike. Build fully, inspect once with a batched round (desktop and mobile together on the web; the shipped device classes on a native platform), fix everything it shows in one batch, confirm with at most one more round, and stop polishing. Open-ended self-QA burns the user's money doing worse what the finish handoffs do better.
Setup
- Run
node tools/atelier/generated/scripts/context.adapter.mjsonce per session, where<skill-base-dir>is the directory that contains this SKILL.md (the skill folder, not a plugin root two levels above it); keep cwd at the user's project. That base directory resolves everytools/atelier/generated/scripts/impeccable <verb>command in this skill and its references, andtools/atelier/generated/scriptsis the fallback only when the runtime reports no base directory. On a Windows shell withoutsh, calltools/atelier/generated/scripts/impeccable.cmdinstead. The launcher runs a self-contained binary that ships next to it or is downloaded once on first run; no Node or other runtime is required. Pass a named source file or route as--target <path>. It loads .agents/design-context.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it. - Load the request's playbook: its Commands-table reference for an explicit/implied sub-command, or tools/atelier/generated/references/new-work.md for a new surface or replacement visual world. Inspect target and incumbent visual truth before editing. When the app cannot run, start with committed visual-regression goldens or screenshot fixtures; verify target and freshness against current tokens, CSS, components, or assets, resolve conflicts, and compare theme/variant captures.
- After resolving analysis and direction, read tools/atelier/generated/references/craft-floor.md immediately before any UI edit, including small refinements. It carries the quality floor, the absolute bans, and the reflexes no detector catches. Do not load it for planning-only work.
Launcher unavailable: On refusal or failure, send a separate message before the next tool call: “Context loading did not run; I’ll read the existing project context directly.” Then read existing .agents/design-context.md and DESIGN.md without inventing missing context, follow applicable steps 2–3, and continue through permitted tools. This applies to planning and editing; launcher failure alone does not block either.
How to design
- The brief wins. Honor pinned aesthetics, eras, materials, fonts, and palettes even when they conflict with a saturated-pattern warning. Redirecting a clear brief toward your taste is failure.
- Refinement preserves; redesign replaces. Refinement keeps the incumbent identity, behavior, copy, and everything outside scope. Ask before replacing factual copy or adding claims. Redesign keeps product truth, content, function, native affordances, and constraints, but treats the old look as evidence and anti-reference; choose a replacement world in new-work and replace DESIGN.md. Never split the difference into polish on the discarded look.
- Visual authority is evidence, not a filename. Missing DESIGN.md alone does not make a project greenfield; new-work decides whether to preserve, expand, or replace the incumbent world.
Modes
The mode names what the visitor's success looks like on this surface.
- Persuade: the visitor decides and acts; design is the product. Landing pages, marketing, campaigns, pricing. Earn attention and action. Ship real imagery when the brief needs it; follow the committed world, not category habit.
- Operate: the visitor completes a task. App UI, dashboards, editors, admin, settings, tools. Scanability, consistency, native expectations, and the real usage scene outrank expression. Brand lives in precise details.
- Read: the visitor understands something. Docs, articles, guides, help, changelogs. Structure for comprehension, then make the reading experience worth staying in.
- Experience: the visitor is inside the work itself. Portfolios, galleries, showcases. Let the artifact lead from the first viewport; the interface recedes.
Choose the mode from the requested surface, not the product, and persist it only in that surface brief. A tool's landing page is still Persuade; a fashion house's documentation is still Read; a docs index is Read, not Persuade. See new-work.md for new surfaces and operate.md for deeper Operate/Read guidance.
Commands
| Command | Category | Description | Reference |
craft [feature] | Build | Deprecated alias for an ordinary new-work request | tools/atelier/generated/references/craft.md |
shape [feature] | Build | Plan UX/UI before writing code | tools/atelier/generated/references/shape.md |
init | Build | Capture durable product context in .agents/design-context.md | tools/atelier/generated/references/init.md |
document | Build | Generate DESIGN.md from existing project code | tools/atelier/generated/references/document.md |
extract [target] | Build | Pull reusable tokens and components into design system | tools/atelier/generated/references/extract.md |
critique [target] | Evaluate | UX design review with heuristic scoring | tools/atelier/generated/references/critique.md |
audit [target] | Evaluate | Technical quality checks (a11y, perf, responsive) | tools/atelier/generated/references/audit.md · native: tools/atelier/generated/references/audit.native.md |
polish [target] | Refine | Final quality pass before shipping | tools/atelier/generated/references/polish.md |
bolder [target] | Refine | Amplify safe or bland designs | tools/atelier/generated/references/bolder.md |
quieter [target] | Refine | Tone down aggressive or overstimulating designs | tools/atelier/generated/references/quieter.md |
distill [target] | Refine | Strip to essence, remove complexity | tools/atelier/generated/references/distill.md |
harden [target] | Refine | Production-ready: errors, i18n, edge cases | tools/atelier/generated/references/harden.md |
onboard [target] | Refine | Design first-run flows, empty states, activation | tools/atelier/generated/references/onboard.md |
animate [target] | Enhance | Add purposeful animations and motion | tools/atelier/generated/references/animate.md |
colorize [target] | Enhance | Add strategic color to monochromatic UIs | tools/atelier/generated/references/colorize.md |
typeset [target] | Enhance | Improve typography hierarchy and fonts | tools/atelier/generated/references/typeset.md |
layout [target] | Enhance | Fix spacing, rhythm, and visual hierarchy | tools/atelier/generated/references/layout.md |
delight [target] | Enhance | Add personality and memorable touches | tools/atelier/generated/references/delight.md |
overdrive [target] | Enhance | Push past conventional limits | tools/atelier/generated/references/overdrive.md |
clarify [target] | Fix | Improve UX copy, labels, and error messages | tools/atelier/generated/references/clarify.md |
adapt [target] | Fix | Adapt for different devices and screen sizes | tools/atelier/generated/references/adapt.md · native: tools/atelier/generated/references/adapt.native.md |
optimize [target] | Fix | Diagnose and fix UI performance | tools/atelier/generated/references/optimize.md |
live | Iterate | Visual variant mode: pick elements in the browser, generate alternatives | tools/atelier/generated/references/live.md |
| select [brief] | DT | Design system recommendation | tools/atelier/generated/references/template.md + design-selector |
| detect [path] | DT | Deterministic anti-slop scan | ./scripts/atelier-detect.sh |
| read | DT | Design Read V/M/D dials | skill design-read |
| tokens | DT | CSS/token expansion | skill design-tokens |
| template [name] | DT | Starters / ui-templates | tools/atelier/generated/references/template.md |
| deck [brief] | DT | Presentation deck | tools/atelier/generated/references/deck.md |
| actualizar | DT | Sync Impeccable vendor | tools/atelier/generated/references/actualizar.md |
Routing:
- No argument: read routing.md and present its context-aware menu; never auto-run a command.
- Explicit or clearly implied request to run a command: load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.
- Workflow or command-selection question: read Workflow questions.
- Otherwise: treat the request as general design work. Missing .agents/design-context.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as
context.adapter.mjsdirects, offering init afterward rather than blocking on it. teachaliasesinit.craftis a deprecated alias for ordinary new-work and adds nothing.shapeowns task discovery, then enters new-work only for visual-world and surface-concept decisions.
After init writes .agents/design-context.md, resume without rerunning context.adapter.mjs; init loads the native platform reference itself when the platform it recorded is ios, android, or adaptive.
Pin / Unpin: tools/atelier/generated/scripts/impeccable pin <pin|unpin> <command> creates or removes a standalone /atelier <command> shortcut. Report the script's result concisely; relay stderr verbatim on error.
Hooks: /atelier hooks <on|off|status|ignore-rule|ignore-file|ignore-value|reset> manages the design detector hook for this project (auto-runs the detector after UI file edits and surfaces findings). Load tools/atelier/generated/references/hooks.md when the user invokes it with any argument.
Doctor: /atelier doctor reports and repairs drift between this project's Impeccable artifacts (.agents/design-context.md, DESIGN.md and its sidecar, config, surface briefs, the hook) and what this version reads. Load tools/atelier/generated/references/doctor.md when the user invokes it, or when they ask what is out of date, stale, or needs refreshing. A CONTEXT_STALE directive in Setup's output is the cheap subset of the same report; act on it there per its own instructions rather than running doctor unasked.
Never repair drift as a side effect of a design task. A CONTEXT_STALE finding is reported, not acted on, unless the user asks. The one exception is a finding marked auto, which the next write to that file performs anyway.
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.

