design-present

design-present is a command for Claude Code from Adityaraj0421/naksha-studio. It costs 22 tokens per session (1,806 once invoked), scanned A, original, MIT.

A command that turns screens from Figma, a collaborative interface-design tool, into an interactive HTML presentation. The presentation can include annotations, transitions, speaker notes, and keyboard navigation.

In plain words
What is it for?
Use it for stakeholder reviews, design critiques, and case-study presentations based on Figma files.
Why use it?
It removes the need to build a slide deck by hand from design screens. It provides a self-contained presentation that can be deployed for reviews or walkthroughs.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

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

Install

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.

Claude Code
/plugin marketplace add Adityaraj0421/naksha-studio
Claude Code
/plugin install naksha-studio

Made for: Claude Code.

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-present

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-present.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-present)
Your own site
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-present"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-present.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,806 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.1 $0.00022 $0.01806
Opus 5 $0.00011 $0.00903
Sonnet 5 $0.00004 $0.00361
Haiku 4.5 $0.00002 $0.00181

Measured 6d ago against content hash f9856c89119e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

design-present 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 6d 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-present.md · 250 lines

How it starts

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

/design-present

You are generating an interactive HTML presentation from Figma designs. This creates a self-contained, deployable presentation for stakeholder reviews, design critiques, or case study walkthroughs.

Input: $ARGUMENTS

Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ui-designer.md for visual design principles and ${CLAUDE_PLUGIN_ROOT}/skills/design/references/motion-designer.md for animation guidance.

Process

1. Connect & Extract Screens

figma_get_status → verify connection

Get the file structure to identify presentable screens:

figma_execute: `
  await figma.loadAllPagesAsync();
  const pages = figma.root.children.map(p => ({
    name: p.name,
    frames: p.children
      .filter(c => c.type === 'FRAME' || c.type === 'SECTION')
      .map(f => ({
        id: f.id,
        name: f.name,
        width: Math.round(f.width),
        height: Math.round(f.height),
        childCount: f.children?.length || 0
      }))
  }));
  return pages;
`

2. Determine Presentation Structure

Based on the Figma file structure and user intent, plan the slide deck:

Presentation Types:

Type Structure Best For
Walkthrough Screen-by-screen with annotations, flow arrows Design review, team feedback
Pitch Problem → Solution → Features → Impact Stakeholder buy-in, client presentations
Case Study Challenge → Process → Solution → Results Portfolio, design challenges

Default to walkthrough if not specified.

3. Capture Screenshots

For each screen to present:

figma_capture_screenshot(frameId) → save as slide image

Or use REST API for cloud-state images:

figma_get_component_image(nodeId, format='png', scale=2)

4. Extract Design Metadata

For each screen, extract contextual information:

figma_execute: `
  const frame = await figma.getNodeByIdAsync('FRAME_ID');
  const texts = frame.findAllWithCriteria({ types: ['TEXT'] });
  const headings = texts
    .filter(t => t.fontSize >= 20)
    .map(t => ({ text: t.characters, size: t.fontSize }))
    .sort((a, b) => b.size - a.size);

  const colors = new Set();
  function collectColors(node) {
    if (node.fills?.length && node.fills[0]?.type === 'SOLID') {
      const c = node.fills[0].color;
      colors.add('#' + [c.r, c.g, c.b].map(v => Math.round(v * 255).toString(16).padStart(2, '0')).join(''));
    }
    if ('children' in node) node.children.forEach(collectColors);
  }
  collectColors(frame);

  return {
    name: frame.name,
    dimensions: { w: Math.round(frame.width), h: Math.round(frame.height) },
    headings: headings.slice(0, 3),
    colorPalette: [...colors].slice(0, 8),
    componentCount: frame.findAllWithCriteria({ types: ['INSTANCE'] }).length,
    textNodeCount: texts.length
  };
`

Read the full file on GitHub · 250 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. 6d ago First seen · 250 lines · 22 tokens per session scan A f9856c89119e

Subscribe to this mod's changes

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

Related

Other commands, from other repositories