Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

3.6 KB
Raw Blame

Product

Register

product

Users

Anyone who needs to understand, plan, or explain something with steps, parts, relationships, or states, working through an AI agent. The core audience remains software engineers, architects, technical leads, reviewers, and AI coding agents explaining a codebase, system, workflow, request path, data pipeline, or lifecycle in an engineering or review context. The same audience, and people outside engineering, also map everyday subjects: a leave or travel plan, an application or approval process, a back-and-forth exchange, where money or documents go, or where something stands. They need a trustworthy artifact they can inspect, present, and share without adopting a hosted diagram editor.

Product Purpose

Archify turns repository evidence, a bounded system description, or a plain-language account of a plan or process into a polished, interactive map directly in an agent conversation. Success means a reader can understand the primary story quickly, inspect exact authored relationships and evidence when needed, and carry either the complete artifact or one explicitly scoped Route / Reach Share Card into review, documentation, presentation, or everyday use. Archify maps structure (parts, steps, exchanges, flows, and states); numeric charts and dashboards are outside its scope.

Brand Personality

Precise, composed, vivid. Archify should feel like a confident instrument for understanding—technical when the subject is a system, plain-spoken when it is a plan: visually memorable enough to invite exploration, restrained enough to keep topology and evidence authoritative, and explicit about what is generated, verified, optional, or unavailable.

Anti-references

  • Generic Mermaid beautifiers that change themes without improving information architecture.
  • WYSIWYG drawing suites whose editing chrome becomes the product.
  • Motion-first graph demos that imply relationships or activity not present in the authored source.
  • Dense dashboard shells, endless identical card grids, decorative glass, gradient text, and other AI-generated interface clichés.
  • Unbounded icon marketplaces or implicit product-name matching that can change identity without an authored brand fact.

Design Principles

  1. Truth before spectacle: every focus, reachability query, route, story, source link, and receipt must derive from authored or verified evidence.
  2. One spatial narrative first: make the primary path legible before revealing secondary relationships and detail.
  3. Progressive disclosure over permanent chrome: keep the canvas dominant and reuse focused tools instead of adding panels.
  4. Motion has one bounded owner: static meaning must remain complete, motion must be finite and reader-controlled, and exports stay clean.
  5. Portable proof: the default result is a self-contained artifact with deterministic validation and no required hosted runtime; intentional Route and Reach Share Card variants name their scope instead of pretending to be canonical.
  6. Identity without semantic drift: an optional built-in or explicitly captured, digest-pinned brand mark may identify a real product, but it never replaces the portable node type, label, relationship, or evidence contract.

Accessibility & Inclusion

Maintain keyboard access, visible focus, semantic labels, dark and light themes, non-color state cues, readable contrast, and prefers-reduced-motion behavior. Desktop is the primary product surface; narrow screens receive safe containment and usable controls rather than a separate mobile product. Viewer state, animation, and interaction must never be required to understand canonical exports.