git:20260418.efa2006 to git:20260421.e268813

1 added, 80 removed. Audit A to B.

- # CLAUDE.md

- This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

- ## Repository Purpose

- A Claude Code plugin marketplace for linked-intent development (LID). Contains installable plugins for structured design-before-code workflows. There is no build system, test suite, or application code.

- ## Structure

- - **`plugins/`**: Claude Code plugin marketplace — three installable plugins

- - **`linked-intent-dev/`**: Core LID workflow + `/lid-setup` command

- - **`arrow-maintenance/`**: Arrow tracking overlay + `/map-codebase` command for brownfield bootstrap

- - **`.claude-plugin/marketplace.json`**: Marketplace manifest listing all plugins

- ## Plugin Architecture

- This repo is a **Claude Code plugin marketplace**. Users install via:

- ```

- /plugin marketplace add jszmajda/lid

- /plugin install linked-intent-dev@jszmajda-lid

- /plugin install arrow-maintenance@jszmajda-lid

- ```

- The plugins form a layered system:

- 1. **linked-intent-dev** is the core workflow — consult for ALL code changes. New features get full 4-phase design (HLD → LLD → EARS specs → Plan). Bug fixes skip doc creation but still verify intent coherence. Includes `/lid-setup` for project bootstrapping.

- 2. **arrow-maintenance** overlays on top — adds navigation (`index.yaml`) and tracking (arrow docs) for projects too large to hold in one context window. Includes `/map-codebase` for brownfield codebase mapping.

- Both LID plugins use EARS (Easy Approach to Requirements Syntax) for specifications with semantic IDs (`{FEATURE}-{TYPE}-{NNN}`), `@spec` code annotations, and status markers (`[x]` implemented, `[ ]` gap, `[D]` deferred).

- ## Editing Guidelines

- - Each plugin lives in `plugins/<name>/` with `.claude-plugin/plugin.json` manifest

- - Skills follow the SKILL.md frontmatter format (`name`, `description` in YAML front matter)

- - The skill `description` field is critical — it determines when Claude auto-invokes the skill. Use specific trigger words, not vague descriptions

- - Reference templates live in `references/` subdirectories within each skill

- ## LID Mode: Full

- ## Linked-Intent Development (MANDATORY)

- **Consult the `linked-intent-dev` skill for ALL code changes.** All changes start with intent:

- ```

- HLD → LLDs → EARS → Tests → Code

- ```

- - **New features**: Full workflow (HLD → LLD → EARS → Tests → Code)

- - **Bug fixes**: Walk the arrow like any other change — find where intent diverged, cascade from there. No short-circuit.

- - **If unsure**: Use the full workflow.

- Mutation, not accumulation — docs reflect current intent, not history.

- ### Navigation

- | What you need | Where to look |

- |---|---|

- | High-level design | `docs/high-level-design.md` |

- | Low-level designs | `docs/llds/` |

- | EARS specs | `docs/specs/` |

- ### Terminology

- - **LLD**: Low-level design — detailed component design docs in `docs/llds/`

- - **EARS**: Easy Approach to Requirements Syntax — structured requirements in `docs/specs/`. Markers: `[x]` implemented, `[ ]` active gap, `[D]` deferred

- - **Arrow**: A traced dependency from HLD through code, tracked in `docs/arrows/`

- ### Code Annotations

- Annotate code with `@spec` comments linking to EARS IDs:

- ```

- // @spec AUTH-UI-001, AUTH-UI-002

- ```

- Test files also reference specs for traceability.

+ AGENTS.md