When should I use this skill?

Only when the user explicitly mentions Stitch, to create a project and obtain a projectId for screen generation.

What IDs are produced and how are they used?

The tool returns a full path like projects/3780309359108792857 and a numeric ID 3780309359108792857. Use the full path for list/get operations and the numeric ID for generate_screen_from_text or get_screen.

What comes after creating the project?

Use stitch-mcp-generate-screen-from-text to generate the first screen within the newly created project.

stitch-mcp-create-project

Scanned

npx machina-cli add skill gabelul/stitch-kit/stitch-mcp-create-project --openclaw

Files (1)

SKILL.md

2.6 KB

Stitch MCP — Create Project

Creates a new Stitch project. A project is a container that holds one or more generated screens. You need a projectId before you can call generate_screen_from_text.

Critical prerequisite

Only use this skill when the user explicitly mentions "Stitch" in their request. Never trigger Stitch operations silently during regular conversation.

When to use

Starting a new design task or app concept
The user says "create a Stitch project", "start a new project in Stitch", "design X using Stitch"
You need a projectId before calling generate_screen_from_text
Starting work in a new domain (keep related screens in one project)

Step 1: Extract a meaningful title

Infer a descriptive project title from the user's request:

User says	→ title
"Design a pet adoption app"	`"PawPals"` or `"Pet Adoption App"`
"Make a login page"	`"Login Page"`
"SaaS dashboard for analytics"	`"Analytics Dashboard"`
"E-commerce product listing"	`"Product Listing"`

If no clear name is evident, use a descriptive label: "Design Project [date]".

Step 2: Call the MCP tool

{
  "name": "create_project",
  "arguments": {
    "title": "[Descriptive project title]"
  }
}

Step 3: Extract and store the project ID — CRITICAL

The tool returns a name field in the format projects/NUMERIC_ID. You must extract the numeric portion:

Tool response:

{
  "name": "projects/3780309359108792857",
  "title": "Analytics Dashboard"
}

Extract:

Full name: projects/3780309359108792857 → use for list_screens, get_project
Numeric ID: 3780309359108792857 → use for generate_screen_from_text, get_screen

Store both values. Announce to the user:

"Created project 'Analytics Dashboard' (ID: 3780309359108792857). Ready to generate screens."

ID format rules (critical — different tools need different formats)

Tool	ID format required
`generate_screen_from_text`	Numeric only: `3780309359108792857`
`get_screen`	Numeric only: `3780309359108792857`
`list_screens`	Full path: `projects/3780309359108792857`
`get_project`	Full path: `projects/3780309359108792857`

Integration

After creating a project, the next step is always stitch-mcp-generate-screen-from-text to generate the first screen.

Source

git clone https://github.com/gabelul/stitch-kit/blob/main/skills/stitch-mcp-create-project/SKILL.mdView on GitHub

Overview

This skill creates a new Stitch project container that holds generated screens. You need a projectId before generating screens, and you’ll reference both the full project path and numeric ID depending on the API call.

How This Skill Works

From the user request, infer a descriptive project title, call the MCP tool with that title to create the project, then extract the numeric ID from the response (projects/NUM) and store both the full path and the numeric ID. After creation, proceed to generate the first screen with stitch-mcp-generate-screen-from-text.

When to Use It

Starting a new design task or app concept in Stitch
The user explicitly asks to create a Stitch project
You need a projectId before calling generate_screen_from_text
Starting work in a new domain and want to keep related screens in one project
Preparing to generate the first screen after project creation

Quick Start

Step 1: Infer a descriptive project title from the user request.
Step 2: Call the MCP tool with {"name": "create_project", "arguments": {"title": "<Your Title>"}}.
Step 3: Extract the numeric ID from the response (projects/NUM) and announce: 'Created project "<Title>" (ID: NUM). Ready to generate screens.'

Best Practices

Only trigger Stitch MCP when the user explicitly mentions Stitch
Infer a descriptive project title from the user request
If the title isn’t clear, fall back to a label like 'Design Project [date]'
Extract and store both the full path (projects/NUM) and the numeric ID
Announce the created project to the user and proceed to generate the first screen

Example Use Cases

User: 'Design a pet adoption app' → creates project titled 'PawPals' (or 'Pet Adoption App') and a numeric ID, ready to generate screens
User: 'Make a login page' → creates project titled 'Login Page' with an ID, ready to generate the first screen
User: 'SaaS dashboard for analytics' → creates project titled 'Analytics Dashboard' with an ID, ready to generate the first screen
User: 'E-commerce product listing' → creates project titled 'Product Listing' with an ID, ready to generate the first screen
User: 'Start a new Stitch project for Finance app onboarding' → creates project titled 'Finance App Onboarding' with an ID, ready to generate the first screen

Frequently Asked Questions

Add this skill to your agents