Pattern MCP - Showcases

162 Patterns

30 Deep cards

132 Index rows

26 Categories

31 Dependency edges

126 Invariants

architecture · 13app-shell · 13ui · 14forms · 7i18n · 4docs-ax · 3databases · 9db-ops · 3identity · 6anti-abuse · 5admin-privacy · 8ai · 16toolkits · 1analytics · 7notifications · 5jobs · 3pwa · 4viz · 63d · 3content · 5desk · 6velocity-interaction · 4velocity-data · 6velocity-runtime · 7velocity-measurement · 3integrations · 1

Every number on this page is computed live from pattern-library/registry.json — the same file the MCP server reads.

Pattern-Abhängigkeitsgraph

The registry's depends_on graph — arrows point dependency → dependent; node color marks DAG layer, not category.

Registry Dependency DAG

Live projection of pattern-library/registry.json. Emulating a pattern means building its ancestors first.

6 of 30 deep patterns (ui-explosive-discovery, optimistic-mutation, intent-preloading, no-waterfall-loading, main-thread-budget, latency-tracing) have no dependency edges and are not drawn above. The 132 light index rows are not graphed — the Data tab lists every pattern of both tiers.

Ephemere Container-Architektur

One tool call's journey through the ephemeral, read-only server container.

Spawn-per-session Architecture

Kernel-enforced isolation: the server can read the repo and nothing else — no network, no writes, no persistence.

Tools & Protokoll

The six read-only tools the server advertises, and the JSON-RPC handshake every session starts with.

search_patterns

Search the pattern library by capability, feature, or concept — the entry point; follow up with get_pattern.

query natural-language or keyword query (required)

limit max results, 1–20, default 5

category optional exact filter: architecture, ai, ui, docs, jobs

get_pattern

Fetch the full curated card for one pattern: docs, code entry points, tests, showcase proof, invariants, emulation notes.

id exact pattern id, e.g. "layered-rag" (required)

get_file_excerpt

Read a bounded, line-numbered excerpt of a referenced repo file. Secret paths and traversal are rejected.

path repo-relative path (required)

start_line 1-based start line, default 1

line_count 1–250 lines, default 100

trace_capability

Trace a capability end-to-end: concept → docs → code → tests → showcase proof, with invariants attached.

capability capability or concept to trace (required)

recommend_emulation_plan

Assemble a dependency-ordered emulation plan — deterministic registry assembly with prerequisites, no inference.

capabilities list of desired capabilities (required)

include_dependencies expand prerequisites via depends_on, default true

validate_snippet

Check a Svelte/TS snippet against v10r conventions (runes, component-first, tokens, Valibot) — loop until clean.

snippet code to validate, at most 20000 chars (required)

language 'svelte' or 'ts', default 'svelte'

MCP Handshake

The client → server sequence mcp/smoke.ts exercises. Notifications get no reply; tools/call repeats per invocation.

← Back to Showcases

Geht dieses Pattern noch besser? Sag uns, wie.

Feedback geben