tp-mcp

Principled MCP (Model Context Protocol) expertise hub — a single skill `mcp-expertise` with five modes covering the full MCP server lifecycle: DESIGN (tool decomposition, output contract, JSON-RPC error discipline, capability negotiation, security checklist, naming, Claude-Optimal validation), SCHEMA (JSON Schema 2020-12 authoring, additionalProperties:false discipline, discriminator enums, constraint discipline, description writing, pitfalls catalog, schemars cheatsheet), IMPLEMENT (Rust with rmcp 0.3 + schemars + tokio, transport choice stdio vs Streamable HTTP, stderr-only logging, error mapping via rmcp::ErrorData, testing with MCP Inspector CLI mode; implementation runs inline in the main agent or forked orchestrator), CLIENT (agent as MCP consumer — the four installation paths, JSON-RPC discovery flow, calling pattern, consumer-side debugging, rmcp client SDK for stdio and Streamable HTTP), and QUALITY (8-dimension Claude-Optimal rubric, forked orchestrator spawns 8 parallel `mcp-quality-judge` subagents in isolated contexts — the single domain exemplar of the lens-prompt pattern). The §3 worked example in `mcp-expertise/references/design-decomposition.md` uses a synthetic `git-cli` decomposition. Hub is a pure router; mechanism lives in `references/`. Includes 1 subagent: `mcp-quality-judge` (QUALITY leaf, background, yellow) — the only marketplace subagent that preloads its domain skill via `skills: [mcp-expertise]`.