Update to Build MCP Apps & Agents

{
  "description": "Review, refactor or upgrade an existing MCP server or MCP App without breaking its API, user workflows or security boundaries.",
  "included_files": [],
  "name": "modernize-mcp-project",
  "skill_md_contents": "---\nname: modernize-mcp-project\ndescription: Review, refactor or upgrade an existing MCP server or MCP App without breaking its API, user workflows or security boundaries.\n---\n\n# Existing-project upgrade\n\n1. Inspect repository state, uncommitted changes, transport, tool names/schemas, UI resources, current dependencies, tests and deployment assumptions. Do not overwrite the user's work.\n2. Agree internally on scope from the user request; prefer the smallest compatible diff. Identify externally consumed tool names and schemas as contracts.\n3. For legacy UI link metadata or transports, confirm current MCP/MCP Apps documentation, then migrate conservatively with backward compatibility where necessary.\n4. Reproduce bugs first. Preserve read/write authorization and any approval semantics.\n5. Delegate independent review only when real subagents are supported; avoid overlapping file changes.\n6. Run baseline and post-change tests; compare failures, runtime behavior, tool discovery and UI rendering.\n7. Deliver a readable change summary, compatibility/migration notes, results and limitations. Ask before disruptive operations such as publishing or pushing.\n\nRead `../../references/protocol-and-ui.md`, `../../references/orchestration.md`, and `../../references/testing.md`.\n"
}