tether-nx

Use when deciding where an Angular file belongs or whether one part may import another - adding a feature or domain, splitting a screen into components, choosing root vs route-level vs component providers, placing shared kit vs feature UI, deciding which layer fetches data and which owns state, or untangling a cross-feature or circular import. Structural placement and dependency direction for Angular 17+ signal-era apps; for per-file API rules (signal syntax, control flow, OnPush) use the Angular team's angular-developer skill.

Use when placing, writing, planning or reviewing code in an Angular Nx workspace - a new library, screen, route, component, service, store, translation key or spec - before the code is written and again before the work is called done. Holds the rule ids agents cite and that a project can override.

Use when a spec, ADR, ARCHITECTURE.md, README or review needs a diagram - a context or container view, a request or data flow, a sequence, or an entity-relationship view of the storage - or when someone asks to visualise how parts of a system talk to each other.

Use when a change, feature, or bug must be understood before it is planned or specced and the touched files, data flow, or constraints are not yet known - before brainstorming a design, before writing-plans, or when a bug report names a symptom but not a location.

Use when building or reviewing anything a user operates — a control, dialog, menu, form, table or route — or when asked for an a11y audit, WCAG 2.2 AA, screen-reader or keyboard support, focus, contrast, reduced motion, or an axe/Lighthouse finding.

Use when a screen loads slowly, janks, re-renders too often or ships too much JavaScript — a long list, a map, a chart, change detection, @defer, bundle size, Core Web Vitals — or when a performance review is asked for.

Use when writing or reviewing TypeScript in an Angular or Nx workspace — a component that loads a list, a value that may be absent, a sort or search over rows, a column config, a class toggle in a template, a helper that already exists once elsewhere — before the code is written and again at review. Also when a static-analysis finding or a strictNullChecks error lands on a file.

Use when a decision spans more than one feature or reverses an earlier choice - a library adopted or refused, a verification or testing policy, a storage or auth model, an API documentation approach - and someone asks to record, document, or justify it. Not for per-feature choices, which belong in the feature's spec or the follow-ups list.

Use when a brainstorm has converged and a ticket or request needs its design written down before planning, or when an existing spec must be amended for a change - after the approach is agreed, before the plan is written.