gabriel-tutor

Seams — Design skill for Claude Code

Design community

Seams: design at the seams, build in slices.

How to install Seams

This entry records only its repository, not the path inside it, so there is no exact command to give. Open gabriel-tutor/seams and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Seams does

Seams: design at the seams, build in slices. A Claude Code plugin that makes Matt Pocock's engineering skills lead every session: a routing bootstrap, a one-question-at-a-time design grill with a 10-axis design lens, gated spec → tickets → implement, a definition of done and handover, and a repo foundations survey. One-command install.

Alternatives in Design

  • Interface Design — Design engineering for Claude Code 4.3k ★
  • Extract — Design System & Product Reverse-Engineering - Extract tokens, components, architecture, and PRDs from codebase 2.8k ★
  • Companion — 2,200+ Web & mobile UI for Claude Code & Codex 2.2k ★

README

Seams

**Design at the seams. Build in slices.**

Seams is a Claude Code plugin (plugin id `matt-pocock-workflow`) that makes [Matt Pocock's engineering skills](https://github.com/mattpocock/skills) lead every session, the way Superpowers does for its own skills: a session bootstrap that routes each development task, a grill that asks one clickable question at a time, gated spec, tickets and implement steps, and a senior-engineer layer around them (design lens, definition of done, handover, repo foundations).

The workflow

Every session starts with the routing policy in context. From there, a request goes through three stages: **route**, **design**, **build**. Every diamond is a question Claude asks you, one at a time with the recommended answer first, and waits on. Nothing is built, published or merged without a yes.

1. Route: ceremony scales with the change

flowchart LR
    S([Session starts]) --> B[/"Bootstrap injected:
routing policy in context"/] B --> R{Classify
the request} R -->|typo, copy, config| T["Edit"] --> V R -->|broken, failing, slow| D["diagnosing-bugs
reproduce → hypotheses
→ regression test → fix"] --> V R -->|bounded change| G["grill"] --> TDD["tdd at the
agreed seams"] --> V R -->|new behavior| G2["grill"] --> I["implement"] --> V R -->|multi-session build| G3["grill"] --> SPEC["to-spec → to-tickets
→ implement per ticket"] --> V R -->|too foggy to see the way| W[/"suggests /wayfinder"/] V["verification-before-completion
+ handover"] B -.repo not set up.-> FO["foundations
(once per repo)"]

2. Design: the grill, one question at a time

flowchart TD
    G["Facts from the code
+ one decision, clickable"] --> Q{frontier
empty?} Q -->|no| G Q -->|yes| L["Design lens, 10 axes
data · seams · failure modes · scale · security
observability · rollout · testing · operability · cost"] L -->|an axis applies
and is uns