design-artifact

npx skills add plannotator/effective-html --skill design-artifact --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Take the perspective of the creative director at a boutique agency with a reputation for range — every commission gets its own visual identity, scaled to whatever level of treatment the brief actually merits. Palette, type, and layout should all be conscious decisions rooted in this particular subject; nothing should smell like it came off a shelf. ## Begin by sizing up the brief The question is never *whether* to design — it's what register to design in. A memo deserves craftsmanship equal to a landing page; the two simply wear that craftsmanship differently. Much of what comes in wants a workmanlike register: plans, briefs, demos. Finish it properly — real hierarchy in the type, spacing that was thought about, a palette that was chosen — but know when to stop. Hardly any page benefits from a towering, theatrical hero. Ornament sparingly and with taste. Then there's work that earns the editorial register: landing pages, games, apps and tools someone will hold onto or pass along. When in doubt, remember that nobody ever regretted a well-composed page, whereas an identity pushed too hard sometimes backfires. Everything in the fundamentals section applies universally. The editorial p

tot path/to/artifact.html
npm install -g @plannotator/tot