Pattern MCP forces coding agents to reuse components and follow your design system
DonR954 · reddit · 2026-09-24
A developer built Pattern MCP to stop agents from hand-building components that already exist or defaulting to generic ones.
How it works: the agent calls recommendcomponent before picking a UI component. Pattern turns the need into a requirements checklist, fetches real component docs, evaluates each requirement, and returns one verdict: use an existing component or build custom from a grounded reference. Not keyword matching; simple primitives are handled locally.
Three differentiators:
- Works with your own design system — point it at a component directory, manifest, Storybook export, or Figma file (with optional vision step), scoring decisions against your real components;
- Enforceable, not advisory — an opt-in local hook blocks new component writes until Pattern decides, plus a CI check;
- Every decision leaves a receipt — pinned to the commit it was judged against, exportable to a PR.
Extras: close calls get re-checked, reference links verified, per-call time/token/cost shown.
Install: npx pattern-mcp init --yes. Supports Claude Code, Cursor, Codex CLI.
More from coding & agent
- Hot take: a 22-year-old fluent in coding agents beats a lazy senior dev — but watch out for 'slop grenades' — jobergum · 2026-09-24
- Blender MCP hits 29k stars as Opus 5.5 builds cities on medium effort — sidahuj · 2026-09-24
- AI Agent Swarm Reverse-Engineers 2001 GBA Game Snood Byte-for-Byte in Two Weeks — Aizkmusic · 2026-09-24
- AI sped up game development, but shipping a game people want to play is still a grind — AIandDesign · 2026-09-24
- Texting an agent to fix streetlights: Instinct automates civic ticket filing end to end — vaibhavbetter · 2026-09-24
- Cursor launches Rollouts: AI writes monitoring plans and verifies deployments before users see regressions — belce_dogru · 2026-09-24