Document and visualise your architecture
You want architecture docs that don't lie and update when code changes. Graphify automatically maps codebase dependencies, diagram-design generates editorial HTML+SVG diagrams in one command without opening Figma, document-skills structures clean Markdown documentation around these visuals.
Why
Docs that don't self-update are dead. You code faster with an agent: docs drift twice as fast. You come back to a project 3 months later. The README mentions a deprecated DB schema. The architecture diagram on Miro was never updated. JSDoc comments date from sprint 0. Nobody knows what userServiceV3.ts does because the decision to create it lives in an archived Slack thread. Onboarding to your own code takes 2 days. This kit flips the problem: you derive docs from code, not the other way. An agent indexes the repo as a queryable graph, skills generate architecture diagrams from code, and…
When
Phase: ≥3-month project, ≥10 code files, onboarding or refactor on the horizon. Audience: tech lead, solo coming back after a break, team welcoming a new member. ✅ You know it's your kit when You forgot how your own code works: userServiceV3.ts, what was that again? Painful onboarding: 2-3 days for a new hire to be productive on the repo map Upcoming multi-file refactor: you're afraid to touch a…
Tools included
- Graphify
- Diagram Design
- Document Skills