{"id":77620,"plugin_id":"plugins_6ae8cbe5a6708191b99fec2318f2e009","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:24.879Z","digest":"3c51bc1de2e09d8a5757f6d510f96a0ac5b1e6e6cba88c5d1651011e7f3cefcd","against":null,"payload":{"description":"Build a complete MCP server or interactive MCP App from a natural-language idea or API brief, including source, real tests, and a runnable handoff where tools permit.","included_files":[],"name":"build-from-idea","skill_md_contents":"---\nname: build-from-idea\ndescription: Build a complete MCP server or interactive MCP App from a natural-language idea or API brief, including source, real tests, and a runnable handoff where tools permit.\n---\n# Full build: idea to MCP App\n\nUse when the user says 'build', 'create', 'make', 'implement', 'ship a prototype', or wants an actual MCP application. Do not stop after architecture when code execution is available.\n\n## Phase A — understand and choose\n1. Identify the primary workflow, target MCP hosts, data source, read/write effects and need for an interactive UI. Prefer the smallest complete vertical slice.\n2. Check available filesystem/terminal/browser/subagent tools; read `../../references/execution-model.md`. If no code tools exist, provide a complete handoff package or implementable code in the available output medium, without claiming running results.\n3. Consult `../plan-mcp-app/SKILL.md`, `../design-mcp-tools/SKILL.md`; define tools with schema, auth, output and explicit failure cases. Avoid a generic `execute` tool.\n4. For new TypeScript projects, check the **v2** MCP TypeScript SDK documentation first (`@modelcontextprotocol/server`, v2 is current as of late 2026). For MCP Apps, check the current `@modelcontextprotocol/ext-apps` docs and registration helpers. Use Python or existing project tech if more appropriate.\n\n## Phase B — build\n5. Create real source files, dependency manifest, README, sample environment file without secrets, test fixtures and scripts. Implement a real underlying operation; don't create inert demos pretending to be integrated.\n6. Include tool-only textual/structured outputs first. Add an MCP Apps `ui://` resource and host bridge **only if it materially improves user interaction**. Reference `../build-mcp-ui/SKILL.md` for binding and accessible states.\n7. Consult `../../references/design-references.md` for product-specific visual direction. Use references for patterns; do not paste copyrighted code/assets without rights.\n8. Apply auth/authorization and failure handling before finalizing. Read `../secure-mcp-server/SKILL.md` when connecting real user data, external actions or any privileged write.\n9. Use `../orchestrate-agents/SKILL.md` only when genuine subagent facilities are present and useful. Otherwise complete the same steps sequentially, without imaginary roles or reports.\n\n## Phase C — verify and deliver\n10. Run real typecheck/build, unit/integration tests and MCP protocol calls with an actual client/Inspector where possible; render UI in a real compatible host/harness if possible. Do not mark unavailable tests as PASS.\n11. Independently inspect security and design quality, fix bounded findings and rerun tests; see `../test-mcp-project/SKILL.md` and `../review-mcp-design/SKILL.md`.\n12. Deliver source/files, how to run, tool contract table, test evidence, known limitations and any approvals needed. Do not auto-push/publish/deploy.\n\n**Completion:** at least one useful tool behaves as specified in a real test, or explicitly disclose why environment prevented this. Never describe a skeleton as a deployed working integration.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}