agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/design-lab/SKILL.md

design-lab

Skill32 starsChanged 6 months agoMITView on GitHub

Interactive design exploration environment: conducts design interviews, generates multiple UI variants in a temporary design lab, collects feedback, and refines the design until the direction is confirmed.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    License: no LICENSE file in the upstream repo <!-- das:install:end -->

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

design-lab

Catalogue stub — full skill: 0xdesign/design-plugin

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/design-lab/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/design-lab/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as design-lab, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/design-lab ] && echo "global" || echo "project"

    Global:

    npx skills add 0xdesign/design-plugin --skill design-lab -g -y

    Project:

    npx skills add 0xdesign/design-plugin --skill design-lab -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add 0xdesign/design-plugin
/plugin install design-and-refine@design-plugins

Heads-up

  • Requires: A web project with a running dev server (the variations are previewed in the browser)
  • License: no LICENSE file in the upstream repo
<!-- das:install:end -->

Invoke after install

  • Skill name: design-lab
  • Trigger phrases: "design lab", "design exploration", "design variants", "iterative design"
  • Plugin route only: the /design-and-refine:start command (optionally with a component name)

What it does

Runs an interactive design exploration session in the user's own codebase. It first conducts a brief design interview and infers the existing design system, then generates several distinct UI variations as real working components in a temporary design-lab route. You compare them side by side in the browser, leave element-level feedback through an overlay, and the skill synthesizes a refined version, repeating until a direction is confirmed. It ends with an implementation plan and removes its temporary files.

The skill's text relies on a FeedbackOverlay template that lives outside the skill directory, in the plugin's templates folder. The npx install copies only the skill, so the agent recreates the overlay from the skill's description; for the complete, upstream-intended setup use the Claude Code plugin route above.

When NOT to use

  • A single design pass with no comparison loop → use design-consultation or plan-design-review
  • Polishing or cleaning up an existing interface → use baseline-ui
  • Generating and iterating visuals outside a codebase → use design-catalogue to pick a design-generation skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free