agentsclimarketplace

Design review

Skill bromso/metapowers/plugins/design/skills/design-review

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill design-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate a Figma Slides presentation summarizing a component's design journey through all 5 phases

SKILL.md

1.8 KB, as published. Nobody here has run it

Design Review

Generate a Figma Slides presentation that summarizes the design journey for "$ARGUMENTS" — covering research, definition, ideation, prototyping, and testing.

Prerequisites

At least the Define phase (.metapowers/design/$ARGUMENTS/02-define.md) should exist. More phases provide a richer presentation.

Process

  1. Read all available phase artifacts:

    • .metapowers/design/$ARGUMENTS/01-empathize.md (research brief)
    • .metapowers/design/$ARGUMENTS/02-define.md (component contract)
    • .metapowers/design/$ARGUMENTS/03-ideate.md (design options)
    • .metapowers/design/$ARGUMENTS/04-prototype.md (prototype notes)
    • .metapowers/design/$ARGUMENTS/05-test.md (test report)

  2. Create a title slide:

    • Call figma_create_slide with name "$ARGUMENTS — Design Review"
    • Call figma_add_text_to_slide with the component name as the title
    • Call figma_add_text_to_slide with the date as a subtitle

  3. Create a slide for each completed phase:

    • For each phase artifact that exists, create a slide summarizing the key findings
    • Call figma_add_text_to_slide for headings and key points
    • If the prototype exists, call figma_export_image to capture the component and mention it in the slide

  4. Create a summary slide:

    • Overall status (pass/fail from test report if available)
    • Key decisions made during the process
    • Next steps or open items

  5. Set slide transitions:

    • Call figma_set_slide_transition with "DISSOLVE" for each slide

  6. Present the slide deck info to the user with the slide count and a link to view in Figma.

Output

A Figma Slides presentation created in the current file, summarizing the design journey for "$ARGUMENTS".

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.