What problem does it solve? When a Claude Code session has both the spa-velocity React frontend and api-velocity NestJS backend loaded as working directories, the active doctrine (CLAUDE.md, skills, agents, settings) loads from only one repo, causing the wrong conventions to be applied to the other repo's files. This Skill prevents cross-repo mistakes such as applying React rules to NestJS code, citing ambiguous ADR numbers that collide between repos, and bundling cross-repo work into a single PR. ## Core Features & Use Cases - Path-based lens switching: Determines which repo's conventions apply based on the file being edited, and mandates reading the target repo's repo-conventions skill and subagents before editing non-primary-repo files. - ADR qualification rule: Enforces repo-qualified ADR citations (e.g., "spa-velocity ADR-007") in any cross-repo context, since both repos use overlapping ADR numbers with different meanings. - Coordination-doc pattern: Requires a coordination plan document, per-repo branches and PRs, per-repo test runs, and cross-linked SPECs for features spanning both repositories. - Use Case: A prompt asks to add a new API endpoint plus the React hook that consumes it. The skill triggers a coordination plan, applies NestJS conventions to the api-velocity controller, applies React/TanStack Query conventions to the spa-velocity hook, and requires a lens-switch attestation in the response. ## Quick Start Ask the assistant to implement a feature touching both repos, for example: "both: add a projects endpoint in api-velocity and a useProjects hook in spa-velocity."
