stitch-mcp-list-screens

List all screens within a specific Stitch project, returning screen names, titles, thumbnails, and device types. Use when the user wants to browse generated designs, find a specific screen to iterate on, or select a screenId for export via get_screen. Requires projectId in projects/{id} format.

261 stars

Best use case

stitch-mcp-list-screens is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. List all screens within a specific Stitch project, returning screen names, titles, thumbnails, and device types. Use when the user wants to browse generated designs, find a specific screen to iterate on, or select a screenId for export via get_screen. Requires projectId in projects/{id} format.

List all screens within a specific Stitch project, returning screen names, titles, thumbnails, and device types. Use when the user wants to browse generated designs, find a specific screen to iterate on, or select a screenId for export via get_screen. Requires projectId in projects/{id} format.

Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.

Practical example

Example input

Use the "stitch-mcp-list-screens" skill to help with this workflow task. Context: List all screens within a specific Stitch project, returning screen names, titles, thumbnails, and device types. Use when the user wants to browse generated designs, find a specific screen to iterate on, or select a screenId for export via get_screen. Requires projectId in projects/{id} format.

Example output

A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.

When to use this skill

  • Use this skill when you want a reusable workflow rather than writing the same prompt again and again.

When not to use this skill

  • Do not use this when you only need a one-off answer and do not need a reusable workflow.
  • Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/stitch-mcp-list-screens/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/stitch-skills/stitch-mcp-list-screens/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/stitch-mcp-list-screens/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How stitch-mcp-list-screens Compares

Feature / Agentstitch-mcp-list-screensStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

List all screens within a specific Stitch project, returning screen names, titles, thumbnails, and device types. Use when the user wants to browse generated designs, find a specific screen to iterate on, or select a screenId for export via get_screen. Requires projectId in projects/{id} format.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# List Screens

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

Lists all screens contained within a specific project.

## Use Case
Invoke this skill to browse the history of generated designs in a project or to find a specific screen to reference or iterate upon.

## Input Parameters

The skill expects you to extract the following information from the user request:
*   `projectId` (required): The ID of the project. **Format**: `projects/{project_id}`.

## Output Schema

Returns an object with `screens` array:
*   **`screens`**:
    *   `name`: Resource identifier (e.g., `projects/123/screens/abc`).
    *   `title`: Auto-generated title.
    *   `screenshot`: Thumbnail URL.
    *   `deviceType`: The device type of the screen.

## Usage Example

User Input: "Show me all screens in this project."

Agent Action:
1.  Extract project ID.
2.  Call `list_screens` tool with arguments `{"projectId": "projects/123456"}`.

## References

- [Examples](examples/usage.md)

Related Skills

tui-index-list

261
from partme-ai/full-stack-skills

Generate and render a pixel-precise ASCII TUI Index List component with complete output blocks (TUI_RENDER, COMPONENT_SPEC, PENCIL_SPEC, PENCIL_BATCH_DESIGN) for Pencil MCP drawing workflows. Use when the user asks to create an index list in a terminal UI, text-based interface, or Pencil MCP project.

stitch-vue-vant-components

261
from partme-ai/full-stack-skills

Convert Stitch designs into modular Vite + Vue 3 + Vant 4 mobile components. Use when the user mentions Vant or Vue Mobile conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Vant tokens (mobile-first 375px, safe area), enforces Vue SFC structure with Vant 4 components (van-button, van-field, van-nav-bar, van-tabbar).

stitch-vue-layui-components

261
from partme-ai/full-stack-skills

Convert Stitch designs into modular Vite + Vue 3 + Layui-Vue components. Use when the user mentions Layui conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Layui tokens (2px/4px radius), enforces Vue SFC structure with Layui-Vue components (layui-btn, layui-input, lay-card, lay-page-header).

stitch-vue-element-components

261
from partme-ai/full-stack-skills

Convert Stitch designs into modular Vite + Vue 3 + Element Plus components. Use when the user mentions Element Plus, element-ui, or Vue Desktop conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Element Plus tokens, enforces Vue SFC structure with el-* components (el-button, el-form, el-table, el-card, el-menu).

stitch-vue-bootstrap-components

261
from partme-ai/full-stack-skills

Convert Stitch designs into modular Vite + Vue 3 + BootstrapVue/BootstrapVueNext components. Use when the user mentions Bootstrap or BootstrapVue conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to Bootstrap utilities, enforces Vue SFC structure with Bootstrap components (b-container, b-row, b-col, b-button, b-card).

stitch-uviewpro-components

261
from partme-ai/full-stack-skills

Convert Stitch designs into uni-app + Vue 3 + uView Pro pages and components. Use when the user mentions uView Pro, uviewpro, or uni-app Vue 3 conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to rpx/theme, enforces u-* component contracts (u-tabs, u-form, u-picker, u-card) with script setup.

stitch-uview-components

261
from partme-ai/full-stack-skills

Convert Stitch designs into uni-app + Vue 2 + uView 2.0 pages and components. Use when the user mentions uView, uView 2, or uni-app Vue 2 conversion from Stitch. Retrieves screen HTML via Stitch MCP get_screen, maps Tailwind to rpx/theme, enforces uni-app page structure with uView 2 u-* components (u-navbar, u-form, u-button, u-cell-group).

stitch-ui-prompt-architect

261
from partme-ai/full-stack-skills

Build Stitch-ready prompts from vague UI ideas (Path A) or from a Design Spec plus user request (Path B). Use when polishing a UI prompt before Stitch generation, improving a prompt that produced poor results, or merging a Design Spec with framework contracts (uView, Element Plus, Layui, Bootstrap, Vant) into a sectioned Context/Layout/Components prompt.

stitch-ui-designer

261
from partme-ai/full-stack-skills

Master orchestrator for end-to-end Stitch UI design and generation. Use when the user asks to design, create, or make a UI screen using Stitch. Coordinates design spec generation, framework contract injection, prompt assembly, and MCP execution (create_project, generate_screen_from_text, get_screen) in a single workflow.

stitch-ui-design-variants

261
from partme-ai/full-stack-skills

Generate alternative Stitch design variant prompts for A/B testing and creative exploration. Use when the user wants multiple style, layout, or content options for a Stitch screen. Takes a base Design Spec or prompt and produces 3 distinct variants (layout, style, or content variations).

stitch-ui-design-spec-vant

261
from partme-ai/full-stack-skills

Vant 4 (Vue 3/Mobile) design spec for Stitch screen generation. Use when the user mentions Vant, vant4, or vant-ui in a Stitch design request. Outputs a hard-constraints prefix with Vant tokens (Primary #1989fa, van-button/van-field/van-nav-bar components, mobile-first 375px) or a CONTRACT_SELECTION_JSON_V1 selector.

stitch-ui-design-spec-uviewpro

261
from partme-ai/full-stack-skills

uView Pro (uni-app/Vue 3) design spec for Stitch screen generation. Use when the user mentions uview-pro, uviewpro, or uview 3.0 in a Stitch design request. Outputs a hard-constraints prefix with uView Pro tokens (Primary #3c9cff, rpx units, u-button/u-form/u-navbar components, script setup) or a CONTRACT_SELECTION_JSON_V1 selector.