Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/plugin87/full-stack-design-skills/design-to-code-workflownpx skills add plugin87/full-stack-design-skills --skill design-to-code-workflowgit clone --depth 1 https://github.com/plugin87/full-stack-design-skillsWhat 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 | $0.00123 | $0.02587 |
| Opus 5 | $0.00062 | $0.01293 |
| Sonnet 5 | $0.00025 | $0.00517 |
| Haiku 4.5 | $0.00012 | $0.00259 |
Grade A, and why
design-to-code-workflow 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 2d 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design to Code Workflow
Bridging design systems and development: from Figma specifications to production React components.
The gap between design and code is where friction happens. A smooth design-to-code workflow means designers can specify components once, developers implement them accurately, and updates propagate automatically. This skill focuses on processes, tools, and patterns that eliminate this friction.
Core Principle: Single Source of Truth
The Design-to-Code Pipeline
Figma Design System
↓
Design Tokens (colors, spacing, typography)
↓
Component Specifications (props, states, variants)
↓
Code Generation (or manual implementation)
↓
Component Library (Storybook)
↓
Production Applications
Goal: Changes in Figma automatically propagate to:
- Design tokens in code
- Component props and defaults
- Component documentation
- Type definitions (TypeScript)
Stage 1: Design Specification
What Developers Need
Before writing code, developers need:
-
Component Purpose
- What problem does this component solve?
- When should it be used?
-
Component Specifications
- Visual design (colors, sizes, spacing)
- Interaction states (hover, focus, active, disabled)
- Responsive behavior
- Accessibility requirements
-
Props & Variants
- What props does component accept?
- What values for each prop?
- Default values?
- Type definitions (TypeScript)?
-
Content & Copy
- Labels, helper text, error messages
- Placeholder text
- Call-to-action buttons
-
Examples
- Primary use cases
- Edge cases
- Common variations
Figma as Single Source
Figma should contain:
- Components with variants (primary/secondary, size variants, states)
- Design tokens in Figma Variables (colors, spacing, typography)
- Component documentation (description in component properties)
- Interaction examples (prototypes showing states)
Example: Button Component in Figma
Button (component)
├── Variants
│ ├── Variant: type (primary, secondary, ghost)
│ ├── Variant: size (sm, md, lg)
│ ├── Variant: state (default, hover, focus, active, disabled)
│ └── Variant: icon (with icon, without icon)
├── Properties
│ ├── Label (text)
│ ├── Icon (boolean)
│ └── Loading (boolean)
└── Documentation
└── "Primary action button. Use for main CTAs."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 464 lines · 0 tokens per session scan A f5c1ff5b59f7
design-to-code-workflow is a skill published in the GitHub repository plugin87/full-stack-design-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 2,587 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.