ik

Generates a self-contained interactive HTML diagram mapping repository architecture and subsystem interactions.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/inayayousfi/myconfig --skill ik-inayayousfi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ik
Source: https://github.com/inayayousfi/myconfig/tree/main/dotfiles/ai/.agents/skills/ik
Command: npx skills add https://github.com/inayayousfi/myconfig --skill ik-inayayousfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding how a large or unfamiliar repository is structured takes hours of reading code, and written documentation often goes stale or misses how components actually interact. This Skill explores a codebase and produces a single visual HTML map showing systems, their roles, and how they call or depend on each other. ## Core Features & Use Cases - Architecture Exploration: Reads entry points, manifests, configs, directory structure, and source code to build a mental model of what each system is and how it interacts. - Focused Subsystem Mode: Accepts an optional argument (e.g. a subsystem name) to explore that area in depth while still diagramming its direct neighbors so boundaries stay visible. - Self-Contained Visual Output: Produces one HTML file with inline CSS, SVG diagrams, and JavaScript that opens directly from disk with no server, network, or external dependencies. - Use Case: After cloning an unfamiliar monorepo, run the Skill to get a clickable diagram where each node shows a generic role plus its real name, with full explanations revealed on click. ## Quick Start Ask the AI to map this repository's architecture, or pass a subsystem name like payments to focus the diagram on that area.

Frequently Asked Questions about ik

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize a repository's architecture automatically?▼

Run the Skill with no argument to explore the whole repo, or pass a subsystem name to focus on it. It reads entry points, configs, and source code, then writes a single self-contained HTML file with an interactive diagram to /tmp/ik/.

How to generate a diagram of one subsystem in a monorepo?▼

Pass the subsystem name as an argument, for example /ik payments. The Skill explores that subsystem in depth plus a shallow pass on whatever it directly interacts with, so the diagram shows boundaries instead of an isolated island.

Does the generated HTML diagram need a server or internet?▼

No. The output is one fully self-contained HTML file with inline styles, scripts, and SVG. It renders correctly when opened straight from disk via file:// with no server and no network access.

Why does the diagram use generic names alongside real component names?▼

Each component is described by its generic role first, with the real name in parentheses immediately after, so readers understand the system's shape on its own terms while still mapping concepts directly to concrete code.

Can I open the diagram from WSL on Windows?▼

Yes. The Skill detects WSL and converts the output path with wslpath -w, producing a Windows-style path like \\wsl.localhost\distro\tmp\ik\file.html that pastes directly into a Windows browser address bar.