skills/stitch-skills/stitch-mcp-get-project/SKILL.md
Retrieve detailed metadata of a specific Stitch project including design theme, fonts, device type, and screen instances. Use when you need project context before generating new screens or to verify project existence. Requires the project resource name in projects/{id} format.
npx skillsauth add partme-ai/full-stack-skills stitch-mcp-get-projectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Stitch".
Do NOT use this skill if:
projectId and screenId and your goal is to get screen details or code. Use stitch-mcp-get-screen directly instead.This skill retrieves the detailed metadata of a specific Stitch project.
Invoke this skill when you need to know the context of a project (e.g., its default theme, device type) before generating new screens, or to verify project existence.
The skill expects you to extract the following information from the user request:
name (required): The resource name of the project. Format: projects/{project_id}.If the user provides a resource path or URL, use the following rules to extract the project name:
Format: web application/stitch/projects/{projectId}
projectId and construct the name as projects/{projectId}.Format: projects/{projectId}
Format: https://stitch.withgoogle.com/projects/{projectId}
projectId and construct the name as projects/{projectId}.Example: Input "Describe web application/stitch/projects/12345", Call get_project(name="projects/12345").
Returns a Project object including:
name, title, createTime, updateTimedesignTheme: Detailed theme settings.screenInstances: List of screen instances currently in the project.User Input: "What is the theme of project 'projects/123'?"
Agent Action:
get_project tool with arguments {"name": "projects/123"}.development
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.