Start with words, Mermaid, or code

Describe it.Archify maps it.

No repository is required. Describe a plan, a process, or a system in a normal agent chat and Archify turns it into a checked, interactive diagram. If code exists, the same skill can inspect it for evidence.

Your description is enough to make the first diagram.

Choose how to startRepository optional

Choose the question shape5 typed renderers

01Install the skill

Keep the tool local.

Choose Cursor, Codex, Claude Code, OpenCode, or GitHub Copilot. The switcher gives each one the same checked Skill and zero-dependency renderers—no vendor-specific fork.

Choose your coding agentCodex · same Skill

Global install
npx -y skills add tt-a1i/archify --skill archify --agent codex --global --copy --yes
This repository only
npx -y skills add tt-a1i/archify --skill archify --agent codex --copy --yes

The Start link carries only your agent, language, diagram type, input mode, and a coarse source label. Journey events stay in this browser session and are never sent by Archify. No repository path, title, node, relationship, or source JSON is recorded.

02Ask one bounded question

System overview

What exists, who owns it, and how is it connected?

  • 8–12 core components
  • one primary path
  • external dependencies
  • trust boundaries

Use Archify to turn this plain-language system description into a high-level architecture diagram: [describe the users, core components, primary path, external dependencies, and boundaries]. No repository is required. Ask only for missing facts that would materially change the diagram, mark any remaining unknowns instead of inventing them, and keep one obvious primary path across 8–12 core components.

Open verified proof ↗ Need another recipe?

architecture · classic · static