Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ZachArticulateV/designer-pro-and-seo/plugin install designer-pro-and-seoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-build)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-build"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-build"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00085 | $0.01636 |
| Opus 5 | $0.00043 | $0.00818 |
| Sonnet 5 | $0.00017 | $0.00327 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
design-build scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-build
Family: design Status: Stable
Purpose
The frontend code generator — and the payoff of the whole design loop. It takes a
design system (from design-system-gen) and renders a real, on-brand starting
page via render_page.py (semantic HTML5, the system's actual palette/type/
effects as CSS variables, prefers-reduced-motion fallback, :focus-visible
states, contrast-safe buttons), then elaborates it with taste. The differentiator
is the anti-slop discipline: distinctive type, color, and interaction instead of
the default gradient-purple, rounded-corner look — grounded in the chosen style's
characteristics from data/ui-styles.csv.
Triggers
- "build the site" / "make the UI" / "design and code"
- "create a landing page" / "build a component"
- "make this beautiful" / "production-grade frontend"
Inputs
- Design system (from
design-system-gen, or "generate one") - Page/component spec (from
blast-prompt, or free-text) - Stack (HTML+CSS+JS | React | Next.js | Vue | Svelte | Astro)
- Variants (1 = single build; 2+ = invokes
parallel-build)
Steps
- Get the design system. Run
design-system-genif none exists; save JSON. - Render the on-brand scaffold — a real, accessible starting point, not a blank
page:
(orpython3 "${CLAUDE_PLUGIN_ROOT}/scripts/design/render_page.py" --design-json ds.json --out page.html # use `py` on Windows if python3 is absent ($env:CLAUDE_PLUGIN_ROOT in PowerShell)--product-type/--industry/--keywordsto run the engine inline). - Elaborate with taste (anti-slop pass). Replace placeholder copy (use
copywriting), shape the sections to the brief, and add distinctive details that match the style'scharacteristicsfromdata/ui-styles.csv— reject the generic AI look. Honordata/ux-rules.csv(one primary CTA, contrast, etc.). Apply the tell→build-move mapping and the chart-handling guidance inreferences/design-build/anti-slop.md(it applies the sharedreferences/shared/anti-slop-principles.mdrubric at build time). When a section needs a chart, let the data shape pick it deterministically rather than defaulting to a bar or pie:
It returns a chart type, an A/B/C accessibility grade + fallback, apython3 "${CLAUDE_PLUGIN_ROOT}/scripts/design/gen_charts.py" --shape time-series-multi --series 4 --colors "#1f77b4,#ff7f0e" # use `py` on Windowsvolume_warningwhen the series/point count overflows the chart's readable band, and (with--colors) a series-color contrast check reusing the engine's WCAG luminance. The reasoning behind the shape→chart table is inreferences/design-build/chart-selection.md. - Target the stack. For HTML+CSS+JS, build straight from the scaffold. For
React/Vue/etc., translate the scaffold's structure + tokens into components
(use
design-tokens-emitfor the token file). - Variants. If the user wants 2+, hand the brief + design system to
parallel-build. - Pre-delivery. Run
design-accessibilityandqa-gatebefore handoff.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 109 lines · 85 tokens per session scan A 4b2efd636a1e
design-build is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 1,636 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
web-design
A web design workflow for turning a brief, reference website, screenshot, or keywords into a design specification and then web code. It covers visual style, page structure, interaction, responsive layouts, and motion.
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
Component Variants / States Documentation コンポーネント状態の文書化
A code review check for new reusable interface components and the variations and states they support, such as hover, focus, disabled, loading, and error states.
Design Source-of-Truth Conformance デザイン定義準拠
A code review check that compares new interface values—such as colors, spacing, font sizes, rounded corners, and shadows—with the project's documented design rules or token files. It only runs when those design definitions exist.