agentmods.dev

design-framework

design-framework is a command for coding agents from Adityaraj0421/naksha-studio. It costs 54 tokens per session (2,856 once invoked), scanned A, original, MIT.

A command that converts HTML and CSS design output into component code for selected web or mobile frameworks. It supports React with Tailwind, Vue, Svelte, Next.js, Astro, Flutter, React Native, SwiftUI, and Jetpack Compose.

In plain words
What is it for?
Use it to create framework-specific components for web, iOS, Android, or cross-platform mobile projects.
Why use it?
It removes repetitive translation from a visual or HTML design into a framework's component structure. It also accepts an existing file, a component description, or earlier output.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

not rated 316 +4 2mo ago A scan 54 tokens original MIT
View the source file Adityaraj0421/naksha-studio
Install

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.

agentmods
npx agentmods add commands/adityaraj0421/naksha-studio/design-framework
Clone the repo
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

Wrote 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.

agentmods badge for design-framework

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-framework.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-framework)
Your own site
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-framework"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-framework.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,856 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.02856
Opus 5 $0.00027 $0.01428
Sonnet 5 $0.00011 $0.00571
Haiku 4.5 $0.00005 $0.00286

Measured 4d ago against content hash 1ddb37720958, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-framework 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 4d 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.

commands/design-framework.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/design-framework

You are the design studio's Framework Specialist, converting design output into idiomatic, production-ready component code for specific frameworks — web or native mobile.

Input: $ARGUMENTS

Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/framework-specialist.md for framework patterns, conventions, file structure, and QA checklist. Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/design-system-lead.md for token naming conventions.

Process

1. Parse the Request

Extract from $ARGUMENTS:

  • Framework: One of the following —
    • Web: react-tailwind, vue, svelte, nextjs, astro
      • Aliases: react / react-tw → react-tailwind; next / next-app → nextjs; sveltekit → svelte; nuxt / vue3 → vue
    • Native mobile: flutter, react-native, swiftui, jetpack-compose
      • Aliases: rn / expo → react-native; swift / ios → swiftui; compose / android → jetpack-compose
  • Source: Path to existing HTML/design file, component description, or --stdin to read from previous output
  • Component name: Infer from file name or user description (default: DesignOutput)

If no framework is specified, ask the user which framework they're using before proceeding.

2. Load Source Design

If a file path is provided:

  • Read the source HTML/CSS file
  • Extract: component structure, color tokens, typography, spacing, interactive states
  • Identify: which parts are static, which require client-side interactivity

If no file path is provided:

  • Ask the user to paste the HTML/CSS or describe the component
  • Or look for the most recently created HTML file in the current directory

2.5. Fetch Live Framework Documentation

Use Context7 to pull current framework documentation before generating code. This ensures output matches the latest stable APIs rather than training-time snapshots.

Library IDs to resolve (call mcp__plugin_context7_context7__resolve-library-id):

  • react-tailwind → resolve "tailwindcss", then "react"
  • vue → resolve "vue", then "unocss"
  • svelte → resolve "svelte"
  • nextjs → resolve "next"
  • astro → resolve "astro"
  • flutter → resolve "flutter"
  • react-native → resolve "react-native", then "expo" if Expo is in use
  • swiftui → resolve "swiftui" (may fall back to Apple Developer docs)
  • jetpack-compose → resolve "jetpack-compose" or "compose"

Read the full file on GitHub · 236 lines

Changes

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.

  1. 4d ago First seen · 236 lines · 54 tokens per session scan A 1ddb37720958

Subscribe to this mod's changes

design-framework is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 2,856 once invoked, about $0.0003 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-30.

Design and UXFrontendaiclaude-codeclaude-code-plugindesign-systemfigma
Related

Other commands, from other repositories

full-diagnostic

Comprehensive design system health sweep.

murphytrueman/design-system-ops · 6 tokens

describe-component

Generate an AI-optimised component description.

murphytrueman/design-system-ops · 8 tokens

drift-check

Detect where teams are diverging from the system.

murphytrueman/design-system-ops · 9 tokens

governance-review

Quarterly governance review package.

murphytrueman/design-system-ops · 5 tokens

system-health

Score your design system's overall health.

murphytrueman/design-system-ops · 7 tokens

token-audit

Audit your design token architecture.

murphytrueman/design-system-ops · 5 tokens