What is the numeric ID used for?

The numeric ID is used for screen generation operations like generate_screen_from_text and get_screen.

What happens after the project is created?

The full project name (projects/123456) and numeric ID (123456) are stored; use the numeric ID for screens and the full name for project-level queries. You should also confirm the creation to the user.

When should I use this skill?

Only when the user explicitly mentions Stitch and you need to start a new Stitch project, start a new app, or initialize a fresh workspace with a clean slate.

stitch-mcp-create-project

npx machina-cli add skill partme-ai/stitch-skills/stitch-mcp-create-project --openclaw

Files (1)

SKILL.md

2.6 KB

When to use this skill

CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Stitch".

ALWAYS use this skill when:

The user wants to start a new design task or app idea using Stitch.
The user asks to "create a Stitch project", "start a new app in Stitch".
The user switches context to a completely different domain (e.g., from "Medical App" to "Gaming App") and needs a clean slate.
You need to obtain a projectId before generating screens.

Trigger phrases include:

"Create a new Stitch project" (创建新 Stitch 项目)
"Start a new Stitch app" (开始一个新 Stitch 应用)
"Initialize Stitch workspace" (初始化 Stitch 工作区)

How to use this skill

Analyze the User Request: Extract a meaningful title for the project.
- User: "Design a cyberpunk blog." -> Title: "Cyberpunk Blog"
- User: "Make a login page." -> Title: "Login Page Project" (Generic)
Call the MCP Tool: Invoke create_project with the title.
- If your client namespaces MCP tools, call mcp__<serverName>__create_project.
Handle the Output (CRITICAL):
- The tool returns a name field (e.g., projects/123456).
- YOU MUST EXTRACT THE NUMERIC ID.
- Example: projects/123456 -> 123456.
- Store BOTH the full name (projects/123...) and the numeric ID (123...) in your context.
- Usage Rule:
- Use Numeric ID (123...) for generate_screen_from_text and get_screen.
- Use Full Name (projects/123...) for list_screens and get_project.

Best Practices

Meaningful Titles: Always try to infer a descriptive title. Avoid "Untitled Project".
One Project per Domain: Encourage users to keep related screens (Login, Home, Settings) in the same project. Only create a new project if the domain changes.
Context Persistency: Explicitly tell the user: "I've created project 'X' (ID: 123). I will use this for our design session."

Keywords

English keywords: create project, new project, start app, initialize, setup, workspace, container, new design, project id, stitch project

Chinese keywords (中文关键词): 创建项目, 新建项目, 开始设计, 初始化, 建立工程, 新应用, 项目ID, 启动项目

References

Examples

Source

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

Overview

Creates a new Stitch project container to start a design task, app idea, or fresh workspace. It assigns a dedicated project ID and a full project path for subsequent work.

How This Skill Works

Analyze the user request to derive a meaningful project title, call the MCP tool create_project with that title, then parse the output to extract the numeric ID from the full name (e.g., projects/123456). Store both the full name (projects/123456) and the numeric ID (123456) for different operations, using the numeric ID for screen generation and the full name for list/get operations.

When to Use It

When the user explicitly mentions Stitch and wants to start a new design task or app idea using Stitch.
When the user asks to 'create a Stitch project' or 'start a new Stitch app' and a fresh workspace is required.
When switching contexts to a completely different domain and a clean slate is needed in Stitch.
When you need to obtain a projectId before generating screens.
When beginning a design session that requires a dedicated Stitch project container.

Quick Start

Step 1: Analyze the user request to derive a descriptive project title (e.g., 'Cyberpunk Blog').
Step 2: Call MCP tool create_project with the derived title (e.g., create_project('Cyberpunk Blog')).
Step 3: From the response, extract numeric ID (e.g., 123456) and full name ('projects/123456'); confirm creation to the user and store both identifiers.

Best Practices

Infer a descriptive, meaningful title for the new project; avoid 'Untitled Project'.
Keep one project per domain; relate related screens (Login, Home, Settings) to the same project unless the domain changes.
Explicitly tell the user: 'I've created project 'X' (ID: 123). I will use this for our design session.'
Use the numeric ID for generate_screen_from_text and get_screen operations, and use the full project name for list_screens and get_project.
Validate the title and confirm creation before proceeding with screen generation or design tasks.

Example Use Cases

User requests: 'Create a new Stitch project for Cyberpunk Blog' -> title 'Cyberpunk Blog', project created with ID 123456.
User says: 'Start a new Stitch app in Stitch' -> a fresh project container is created for the new app idea.
User switches from Medical App to Gaming App -> a new project is created to keep domains separated.
User needs to generate screens and asks for IDs first -> extract numeric ID (123456) from 'projects/123456' for screen ops.
User asks to list or fetch screens -> use the full name 'projects/123456' with list_screens or get_project.

Frequently Asked Questions

Add this skill to your agents