gabelul/stitch-kit / skills/stitch-mcp-delete-project
stitch-mcp-delete-project
VerifiedPermanently deletes a Stitch project and all its screens. Destructive — requires explicit user confirmation before calling.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
SKILL.md
View on GitHub---
name: stitch-mcp-delete-project
description: Permanently deletes a Stitch project and all its screens. Destructive — requires explicit user confirmation before calling.
allowed-tools:
- "stitch*:*"
---
# Stitch MCP — Delete Project
Permanently deletes a Stitch project and all its screens, designs, and history. This action is irreversible.
## Critical prerequisite
**Only use this skill when the user explicitly mentions "Stitch".**
**This is a destructive action.** You MUST ask the user to confirm before calling `delete_project`. Never auto-delete.
## When to use
- User explicitly asks to delete a Stitch project
- Cleaning up test/scratch projects after confirming with the user
- The orchestrator offers project cleanup and the user accepts
## Step 1: Confirm the project
Show the user what they're about to delete:
1. Call `stitch-mcp-get-project` with `projects/[ID]` to get the project title and screen count
2. Present: "You're about to permanently delete **[title]** ([N] screens). This cannot be undone. Proceed?"
3. Only continue if the user explicitly confirms
## Step 2: Call the MCP tool
```json
{
"name": "delete_project",
"arguments": {
"name": "projects/3780309359108792857"
}
}
```
### `name` — full path with `projects/` prefix
```
✅ "projects/3780309359108792857"
❌ "3780309359108792857"
```
This follows the same format as `get_project` — both use `projects/ID`.
## After deleting
- Confirm: "Project **[title]** has been deleted."
- Offer: "Want to see your remaining projects?" → `stitch-mcp-list-projects`
- Do NOT attempt to access the deleted project's screens or data
## Anti-patterns
- **Never delete without explicit user confirmation** — even if the orchestrator suggests cleanup
- **Never delete multiple projects in a batch** without confirming each one
- **Never use numeric ID** — `delete_project` requires the full `projects/ID` path
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |