/arch
ArchitectureModel-invoked

Shared words for deep modules — where the public interface sits, how deep it goes, what leverage it buys. Other skills reach for this when drawing boundaries.

When to use

Automatically when designing module seams or deepening interfaces; invoke explicitly for architecture discussions.

Prerequisites

  • Usually none — the agent discovers `arch` when placing seams. Optional: open a chat about module boundaries.

How to use

  1. Prefer letting /dev or /design pull `arch` in when seams matter.
  2. Or ask explicitly to discuss seam, depth, leverage, locality, or design-it-twice.
  3. Apply the vocabulary to the module you are changing — do not invent a parallel glossary.
  4. For a maintenance scan of deepening debt, use /arch-refactor instead.

Done when

Seam and depth decisions use shared `arch` terms and inform the current /dev or /design work.

Pipeline

Upstream
Implementation or design context
Downstream
Better /dev or /design decisions

Boundaries

Not visual UI design. Not the arch-refactor maintenance scan.

Model-invoked — the agent reaches this when placing seams or deepening a module.

Model-invoked — the agent reaches this when placing seams or deepening a module.

Agent

PRINCIPAL TECH LEAD

Owns: seams, depth, leverage, design-it-twice

Use the techlead to place seams for [module]
techlead
← Skill catalog