Skip to content
Back to skills

Ideate

ASecurity

Explore multiple design approaches for a component before committing to an implementation

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agents

Works with

  • mcp

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add bromso/metapowers --skill ideate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ideate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ideate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bromso-ideate/badge)](https://www.skillsdirectory.com/skills/bromso-ideate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Explore multiple design approaches for a component before committing to an implementation
---

# Ideate

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

## Prerequisites

Read `.metapowers/design/$ARGUMENTS/02-define.md`. If this file does not exist, tell the user:

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

If `--skip-checks` is present in $ARGUMENTS, skip this check and log to `.metapowers/design/$ARGUMENTS/skip-log.md`.

## Process

1. **Read context files:**
   - Read `.metapowers/design/$ARGUMENTS/01-empathize.md` for research findings (if exists)
   - Read `.metapowers/design/$ARGUMENTS/02-define.md` for the component contract
   - Read `plugins/design/shared/wcag-criteria.md` for accessibility constraints

2. **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

3. **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)

4. **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

5. **Recommend one approach** with clear rationale explaining why it best satisfies the component contract.

6. **Write the artifact** to `.metapowers/design/$ARGUMENTS/03-ideate.md`

## Output

The ideation document written to `.metapowers/design/$ARGUMENTS/03-ideate.md`. Present a summary to the user highlighting:
- Number of options explored
- Recommended approach and rationale
- Key trade-offs between options
- Any contract constraints that were difficult to satisfy

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.