--- name: stitchflow-fc712de040a9 slug: stitchflow version: 1.4.0 description: Turn briefs, mockups, and product context into Stitch UI screens, design systems, variants, prototypes, Tailwind-friendly HTML, and screenshots. Use when the user wants to explore a screen, edit an existing Stitch project, compare visual directions, build a multi-screen prototype, or save local design/code-export artifacts from natural-language input. homepage: "https://github.com/yshishenya/stitchflow" category: "design" platforms: "codex, claude-code, openclaw, github-copilot, gemini-cli" install: "bash install.sh --target all" toolkit_root: "${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}" compatibility: "Requires Node.js 22+, a configured STITCH_API_KEY, and either native Stitch MCP tools or the local stitch-starter toolkit installed by this repository." legacy_aliases: "stitch-design-local" --- # StitchFlow Use this skill when the user wants to create a new Stitch screen, refine an existing one, generate design variants, build a multi-screen prototype, run a complete website design process, use `DESIGN.md` / design systems, or export local HTML and screenshots through Stitch. It prefers native Stitch MCP tools when they are available in the current agent session, and falls back to the local toolkit at `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}` when they are not. ## Local setup - Toolkit root: `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}` - API key is expected in `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/.env` - Outputs are saved to `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/runs` - The latest single-screen result is tracked in `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/runs/latest-screen.json` - For final multi-screen work, the Stitch project is the source of truth; local HTML/screenshots are evidence and handoff artifacts. - When code with styles/images is requested, prefer `download-project` over `export-project`. - `download-project` uses `Project.downloadAssets()`: it downloads every project screen's `code.html`, referenced remote images and stylesheet links into per-screen `assets/`, screenshots when available, top-level `DESIGN.md` when exposed, and `download-project.json` with screen metadata and warnings. - If the SDK downloader hits a filesystem path-length error from long Stitch screen titles or image prompts, the CLI automatically falls back to StitchFlow's safe downloader with short screen directories; `--safe-download` forces that path. - Treat `download-project` output as a local code/assets checkpoint for implementation handoff. It can include scratch/design-system screens and may still reference external runtime scripts such as Tailwind CDN, so filter to approved screen ids in handoff notes and vendor/build external dependencies during production implementation. - Use `design-system` when local fallback needs to list, create, update, or apply Stitch design systems exposed by the live MCP schema. ## Native MCP setup If the current client exposes Stitch MCP tools such as `create_project`, `generate_screen_from_text`, `generate_variants`, `upload_design_md`, `create_design_system_from_design_md`, `apply_design_system`, and `get_screen`, use those tools first. Native MCP avoids local SDK transport issues and is the most reliable path in Codex after the client has been restarted with the Stitch MCP server configured. For Codex, a minimal MCP config looks like this: ```toml [mcp_servers.stitch] url = "https://stitch.googleapis.com/mcp" enabled = true [mcp_servers.stitch.http_headers] "X-Goog-Api-Key" = "" ``` Restart the client after changing MCP config so the `stitch` tools are loaded into the session. ## When to use - The user says to use Stitch or StitchFlow - The user wants a screen generated from a brief, spec, or rough idea - The user wants design variants before implementation - The user wants targeted visual edits to a generated screen - The user wants a full multi-screen Stitch project, clickable prototype, or code export - The user wants to import or reuse a `DESIGN.md` design system - The user wants HTML and screenshots exported locally for review ## Workflow routing - Full project prototype, `DESIGN.md`, or final code handoff: Read [project-prototype-export](workflows/project-prototype-export.md) - End-to-end website design delivery from logo and homepage variants to all screens and QA: Read [site-design-delivery](workflows/site-design-delivery.md) - New screen from a prompt or brief: Read [text-to-design](workflows/text-to-design.md) - Targeted changes to an existing Stitch screen: Read [edit-design](workflows/edit-design.md) - Multiple directions from one base screen: Read [variants](workflows/variants.md) ## Core rules 1. Before any Stitch command, rewrite the user request into a stronger design prompt. 2. If the user already has a codebase or UI context, inspect it first and carry that context into the prompt. 3. Prefer `DESKTOP` by default unless the user clearly asks for mobile or tablet. 4. For first-pass exploration, prefer one generated screen plus `3` variants. 5. If a screen is already close, prefer `edit` over full regeneration. 6. For final selected designs, do not replace Stitch with hand-written HTML or locally generated imagery. Keep the Stitch project/prototype as the design source, then export or checkpoint it. 7. When the user asks for an interactive prototype or whole-site app export and the SDK/MCP does not expose the needed endpoint, use the Stitch web UI with Browser/Chrome/Computer Use and record the exact manual/UI handoff step. Still run `download-project` afterward for local code/assets where possible. 8. Always tell the user where the resulting files were saved. 9. Never print or expose `STITCH_API_KEY` or `.env` contents. 10. When native MCP returns `downloadUrl` values, save the HTML and screenshot locally into the normal `runs/` artifact layout before reporting completion. 11. After `download-project`, inspect `download-project.json` and report any warnings or unexpected extra screens before treating the checkpoint as final. 12. For full website design work, do not jump from a single homepage to implementation. Generate logo directions if brand identity is open, create at least five homepage variants, record the selected homepage screen id, then generate every required screen from a screen inventory and audit coverage. ## What good output looks like - the brief is rewritten into a stronger design prompt - the right Stitch workflow is chosen: generate, edit, variants, design system, prototype, or export - the command completes and saves artifacts locally - the response includes project id, screen id(s), output folder, and what to do next - final project handoff identifies whether code came from Stitch UI export, SDK screen export, or a local evidence checkpoint - full website design handoff includes logo decision, homepage selection notes, screen inventory coverage, and product QA status ## Prompt shaping Use [prompt-keywords](references/prompt-keywords.md) to translate vague requests into design language Stitch understands better. Structure prompts like this: ```md [overall vibe, product intent, and audience] Platform: [web/mobile], [desktop/mobile]-first Page goal: - what the screen is for - what primary action matters most Page structure: 1. Header / navigation 2. Main content / hero / dashboard body 3. Secondary content 4. Footer / actions / supporting detail Visual direction: - palette roles - typography tone - spacing density - component style ``` ## After running Stitch Report: - the command used at a high level, not the secret env - the project and screen ids - the output folder under `${STITCH_STARTER_ROOT:-$HOME/.agents/stitch-starter}/runs` - the HTML and image artifact paths if they were downloaded - whether `DESIGN.md` / design system was created or applied - whether prototype/code export was completed in Stitch UI or only a screen-level SDK checkpoint is available - a short design assessment and the best next step ## References - [cli-usage](references/cli-usage.md) - [prompt-keywords](references/prompt-keywords.md) --- Source attribution: yshishenya Original project: https://github.com/yshishenya/stitchflow/blob/643256d66284f868d1588cb8ac45cd1cd8254e2f/skills/stitchflow/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS # Mega AI Hub resource metadata Creator / publisher: yshishenya Original project: https://github.com/yshishenya/stitchflow/blob/643256d66284f868d1588cb8ac45cd1cd8254e2f/skills/stitchflow/SKILL.md Attribution basis: Source repository record Fields of work: Design, Development & Engineering Roles: Frontend Developer, Product Designer, UX Designer Specialties: API, Backend, Design, Word Documents, Frontend, Git, Mobile, Playwright, Testing Tools: Stitch Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b9e467d4f9e5ce5d3e92348215128be391c459924bd1d3eb7de4e6ccd5182728