{"id":77628,"plugin_id":"plugins_6ae8cbe5a6708191b99fec2318f2e009","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:25.138Z","digest":"6cc3fa4846209f6bf63d1babeaefc189e8aadb53f483aac4b627c09d0c14f207","against":null,"payload":{"description":"Architect an MCP server or interactive MCP App from a user's idea, API concept, existing workflow, or product brief before writing implementation code.","included_files":[],"name":"plan-mcp-app","skill_md_contents":"---\nname: plan-mcp-app\ndescription: Architect an MCP server or interactive MCP App from a user's idea, API concept, existing workflow, or product brief before writing implementation code.\n---\n\n# Plan an MCP project\n\n1. Determine target users, meaningful actions, target hosts, auth needs, data sensitivity, read/write effects and desired user experience. Use a reasonable default when unspecified and document it.\n2. Decide whether the task needs: (a) tool-only MCP, (b) tool-plus-UI MCP App, (c) both with graceful fallback. Never add UI merely for decoration.\n3. Identify resource boundaries, typed tool operations, schemas, error cases, rate limits, pagination, idempotency and confirmation for consequential writes. Prefer fewer well-named tools over one generic `execute` tool.\n4. Select TypeScript + official MCP SDK as new-project default; Python or existing stack when requested. Verify current SDK API signatures before coding; do not invent unverified imports.\n5. Choose transport based on deployment: Streamable HTTP over HTTPS for remote use; stdio only for local hosts that support it. Identify session, auth, and hosting considerations.\n6. If UI: sketch states (loading, data, empty, error, permission, retry), host capability negotiation and tool-only fallback. Read `../../references/protocol-and-ui.md` and `../../references/design-references.md`.\n7. For substantial projects consider the specialists in `../../references/orchestration.md`. Use real subagents only when tools support them.\n8. Propose smallest vertical slice and verification plan, then implement it when coding tools exist and user intent authorizes it.\n\nOutput: one-paragraph brief; architecture and trust boundaries; tool contract table; UI decision; project layout; milestones; tests and approval gates. Do not overplan a tiny server.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}