ln-72-current-architecture-documenter
Documents implemented current-state architecture from repository evidence. Use for onboarding or migration baselines; not for target design, audit verdicts, or code changes.
npx skills add levnikolaevich/claude-code-skills --skill ln-72-current-architecture-documenter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Current Architecture Documenter **Goal:** Produce a trustworthy snapshot of the architecture implemented in the checked-out repository. Document what exists and how it behaves; do not score it, prescribe a target architecture, repair code, or turn intended diagrams into facts. **Execution contract:** Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete only when its action and required evidence are complete. `N/A`, skipped, unavailable, or delegated items remain incomplete. Before returning, apply this skill's verdict and approval rules to every incomplete item and prepend **Checklist: X/Y complete**<br>**Incomplete: None | section/item — reason; outcome impact; exact next action**; list every incomplete item. ## Tool Routing | Need | Preferred capability | Fallback | |---|---|---| | Snapshot identity and worktree state | Git status, branch, remote, and HEAD | Record the supplied snapshot as `UNVERIFIED` | | Structure and configuration | Native listing, search, manifests, and direct file reads | Narrow manual inspection | | Symbols, dependencies, and consumers | Language intelligence or resolved depen
- Tool Routing
- Artifact Rules
- Checklist
- 1. Establish the Documentation Contract
- 2. Map the System Breadth
- 3. Trace Critical Behavior
- 4. Write the Current-State Artifact
- 5. Verify and Report
- Output Contract
What does the ln-72-current-architecture-documenter skill do?
Documents implemented current-state architecture from repository evidence. Use for onboarding or migration baselines; not for target design, audit verdicts, or code changes.
How do I install it?
Run `npx skills add levnikolaevich/claude-code-skills --skill ln-72-current-architecture-documenter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From levnikolaevich/claude-code-skills, a repository with 528 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.