Archify
Archify Features and Quickstart: Generate a Verifiable System Map
Run a bounded Archify skill task, inspect typed JSON validation, trace source-backed edges, and export a self-contained architecture diagram.
What you will learn
- Run a bounded Archify task
- Inspect typed IR and validation evidence
- Package a reproducible visual artifact
Before you start
- Basic Git and command-line usage
- Comfort reading a project README
You can explain the project, run its documented first step, and decide what to verify before adopting it.
Key takeaways
- Bounded inputs make Archify's typed IR and validation easy to review.
- Source tracing and structured receipts turn a render into evidence.
- Exported visuals should travel with their input revision and checksum.
Start with one bounded map
Archify is easiest to learn when the input is one request flow, worker pipeline, or lifecycle—not an entire organization. Give the agent named components, known relationships, and the revision or document that supports each fact. The goal is to make the resulting JSON intermediate representation small enough to inspect line by line.
The README advertises architecture, workflow, sequence, data-flow, and lifecycle diagrams, plus presets, themes, finite motion, source tracing, and Before/Delta/After comparisons. Treat each as an independent acceptance test so a polished animation does not hide a missing edge.
Install and validate
The documented install command is `npx skills add tt-a1i/archify -g`. After installation, ask a supported host to produce a small map and save the generated JSON, validation output, and rendered HTML/SVG together. Validation is the gate: if a node, relationship, or layout constraint fails, fix the input instead of asking the model to draw around it.
Inspect at least one source trace and one route or reachability interaction. A reader should be able to open the evidence behind an edge, understand whether it is direct or inferred, and see which revision supplied the fact.
Exercise the export surface
Export one self-contained HTML or SVG artifact, then test a share-card or PNG/WebM path only if your workflow needs it. Check that fonts, media, and links resolve without a development server, and record the Archify release, host, input revision, and output checksum.
If the map will be attached to a pull request, keep the typed JSON and validation receipt beside the image. The image communicates; the structured input and receipt provide the audit trail.
When it is ready for team use
Use Archify for onboarding, design review, incident follow-up, and refactor comparisons where a repeatable visual projection helps discussion. Add a human review step for semantic completeness: deterministic rendering cannot recover facts that were absent from the supplied context.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Install with `npx skills add tt-a1i/archify -g`.
- 2
Describe one bounded flow with named nodes, edges, and source revisions.
- 3
Inspect validation, source traces, and reachability interactions.
- 4
Export a self-contained artifact and archive JSON, receipt, and checksum.
Copy-ready example
npx skills add tt-a1i/archify -g
# Ask for a bounded, source-traceable map in your agent
# Preserve generated JSON, validation receipt, and exported HTML/SVGFrequently asked questions
Do I need to map an entire repository?
No. Start with one bounded flow; smaller inputs make missing or inferred relationships visible.
Is a rendered SVG enough for review?
No. Keep the typed JSON, validation receipt, source revision, and checksum with the visual artifact.
Sources
- Archify README (captured 2026-08-31)Source checked 2026-08-31
- Archify repositorySource checked 2026-08-31