A design-exploration step that creates at least three visual and layout approaches for a component, compares their trade-offs, and recommends one. A component is a reusable interface element such as a button, form field, or dialog.

Use it to explore component layouts and visual directions after the component’s requirements have been defined.

It helps teams compare alternatives before committing to one design, rather than building the first idea without considering its drawbacks.

ideate — Skill for Claude Code by bromso/metapowers

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 bromso/metapowers

Claude Code

/plugin install design

Made for: Claude Code.

Or install design, the plugin that ships this one along with the rest of its 8 skills, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bromso/metapowers/ideate/github.svg)](https://agentmods.dev/skills/bromso/metapowers/ideate)

Your own site

<a href="https://agentmods.dev/skills/bromso/metapowers/ideate"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/ideate/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bromso/metapowers/ideate"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/ideate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 651 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.00651
Opus 5.5	$0.00026	$0.00260
Sonnet 5.5	$0.00013	$0.00130
Haiku 4.5	$0.00006	$0.00065

Measured 3d ago against content hash d3bc020d0618, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ideate 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 3d 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.

plugins/design/skills/ideate/SKILL.md · 52 lines

How it starts

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

Ideate

Generate multiple design options for "$ARGUMENTS" before committing to a single approach. Encourage creative exploration by producing at least 3 distinct options.

Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/design/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.

Prerequisites

Read .metapowers/design/<project>/02-define.md. If this file does not exist, tell the user:

Phase 2 (Define) has not been completed for "". Run /design:define-component <project> first, or use --skip-checks to bypass.

Process

Read context files:
- Read .metapowers/design/<project>/01-empathize.md for research findings (if exists)
- Read .metapowers/design/<project>/02-define.md for the component contract
- Read ${CLAUDE_PLUGIN_ROOT}/shared/wcag-criteria.md for accessibility constraints
Read the design system via MCP tools:
- Call figma_get_design_system to understand available tokens and patterns
- Call figma_get_variables with exportFormat: "json" to get token values
Generate 3+ design options. For each option:
- Describe the visual approach and layout strategy
- Map which tokens from the design system would be used
- Evaluate against the component contract's constraints
- Assess accessibility compliance
- Note trade-offs (complexity, flexibility, consistency)
Create a FigJam brainstorming board (if FigJam is available):
- Call figjam_create_stickies with each option as a sticky note
- Call figjam_create_table with a comparison matrix
Recommend one approach with clear rationale explaining why it best satisfies the component contract.

Read the full file on GitHub · 52 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.

3d ago First seen · 52 lines · 64 tokens per session scan A d3bc020d0618

Subscribe to this mod's changes

ideate is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 651 once invoked, about $0.0003 per session on Opus 5.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-10-21.

Claude Code Design and UX claude-agent claude-code-plugin claude-skills context-design context-engineering

design-method

Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.

fusengine/agents · 35 tokens

design-webapp

Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.

fusengine/agents · 31 tokens

design-web

Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.

fusengine/agents · 36 tokens

motion-art-direction

Use when a film needs a look before any scene code — ads, launch teasers, brand films, type-led films with no screenshots, or whenever a draft looks flat (white ground, small tiles, centered text, fades, slow camera drift, logo opener). Locks .motion/look.md at Gate 0 (3 text sketches → challenger locks the tone blind…

fusengine/agents · 172 tokens

motion-craft

Use when deciding how a film beat looks and moves — motion density (a gesture in progress at every moment: 0.75 s gesture-free max, CTA still ≤ 1.2 s, beats every 0.5-1 s, ≥ 1 onset/s) with read time ≥ 0.25 s/word, one primary gesture with subordinate details, the two film types (cut-based edit, one continuous…

fusengine/agents · 164 tokens

design-review

Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup.

fusengine/agents · 29 tokens