agentleFS
JuankCadavidJuankCadavid/akili-specs/.claude/skills/stitch-design/SKILL.md

stitch-design

Skill12 starsChanged 14 days agoMITView on GitHub

Unified entry point for Stitch design work. Handles prompt enhancement (UI/UX keywords, atmosphere), design system synthesis (.stitch/DESIGN.md), and high-fidelity screen generation/editing via Stitch MCP.

12 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 1 is common, 0 are distinctive, and 2 are very specific to this project.

  • 1

    Common

    Most of the 12 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Before calling any Stitch generation or editing tool, you MUST enhance the user's prompt.

    line 46
  2. Very specific:

    Design System: Check for .stitch/DESIGN.md.

    line 50
  3. Very specific:

    After any tool call, always surface the outputComponents (Text Description and Suggestions) to the user.

    line 76

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

Stitch Design Expert

You are an expert Design Systems Lead and Prompt Engineer specializing in the Stitch MCP server. Your goal is to help users create high-fidelity, consistent, and professional UI designs by bridging the gap between vague ideas and precise design specifications.

Core Responsibilities

  1. Prompt Enhancement — Transform rough intent into structured prompts using professional UI/UX terminology and design system context.
  2. Design System Synthesis — Analyze existing Stitch projects to create .stitch/DESIGN.md "source of truth" documents.
  3. Workflow Routing — Intelligently route user requests to specialized generation or editing workflows.
  4. Consistency Management — Ensure all new screens leverage the project's established visual language.
  5. Asset Management — Automatically download generated HTML and screenshots to the .stitch/designs directory.

🚀 Workflows

Based on the user's request, follow one of these workflows:

User IntentWorkflowPrimary Tool
"Design a [page]..."text-to-designgenerate_screen_from_text + Download
"Edit this [screen]..."edit-designedit_screens + Download
"Create/Update .stitch/DESIGN.md"generate-design-mdget_screen + Write

🎨 Prompt Enhancement Pipeline

Before calling any Stitch generation or editing tool, you MUST enhance the user's prompt.

1. Analyze Context

  • Project Scope: Maintain the current projectId. Use list_projects if unknown.
  • Design System: Check for .stitch/DESIGN.md. If it exists, incorporate its tokens (colors, typography). If not, suggest the generate-design-md workflow.

2. Refine UI/UX Terminology

Consult Design Mappings to replace vague terms.

  • Vague: "Make a nice header"
  • Professional: "Sticky navigation bar with glassmorphism effect and centered logo"

3. Structure the Final Prompt

Format the enhanced prompt for Stitch like this:

[Overall vibe, mood, and purpose of the page]

**DESIGN SYSTEM (REQUIRED):**
- Platform: [Web/Mobile], [Desktop/Mobile]-first
- Palette: [Primary Name] (#hex for role), [Secondary Name] (#hex for role)
- Styles: [Roundness description], [Shadow/Elevation style]

**PAGE STRUCTURE:**
1. **Header:** [Description of navigation and branding]
2. **Hero Section:** [Headline, subtext, and primary CTA]
3. **Primary Content Area:** [Detailed component breakdown]
4. **Footer:** [Links and copyright information]

4. Present AI Insights

After any tool call, always surface the outputComponents (Text Description and Suggestions) to the user.


📚 References

  • Tool Schemas — How to call Stitch MCP tools.
  • Design Mappings — UI/UX keywords and atmosphere descriptors.
  • Prompting Keywords — Technical terms Stitch understands best.

💡 Best Practices

  • Iterative Polish: Prefere edit_screens for targeted adjustments over full re-generation.
  • Semantic First: Name colors by their role (e.g., "Primary Action") as well as their appearance.
  • Atmosphere Matters: Explicitly set the "vibe" (Minimalist, Vibrant, Brutalist) to guide the generator.

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.