# Visualize

Visualizes anything at all and never declines, a codebase, a physical setup, a...

- Repository: https://github.com/danielmiessler/LifeOS (19669 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add danielmiessler/LifeOS --skill Visualize -g -a claude-code -y`
Codex: `npx skills add danielmiessler/LifeOS --skill Visualize -g -a codex -y`
Cursor: `npx skills add danielmiessler/LifeOS --skill Visualize -g -a cursor -y`
Gemini CLI: `npx skills add danielmiessler/LifeOS --skill Visualize -g -a gemini-cli -y`

## Description

Visualizes anything at all and never declines, a codebase, a physical setup, a timeline, a process, finances, a comparison, a concept, a URL, a dataset, as a short console summary plus a designed HTML page, every fact labelled with where it came from (a file quote, a URL, the principal's words, or general knowledge). USE WHEN visualize, visualize this, visualize my <anything>, visualize <project>, show me this visually, draw it, map it, lay it out, how does X work, explain this architecture, map this system, system map, architecture map, what are the moving parts, draw my setup, show me my plan, walk me through this codebase, diagram this project or ISA. NOT FOR a standalone generated illustration or header image with no visualize ask (Art), rendering an ISA page (ISA), turning session output into an artifact (HTML), or hand-drawn sketches (Excalidraw).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Visualize

**Contents:** Ideal State · Intent Routing · Data & Config · Split of work · Gotchas · Examples

Points at a project, repo, directory or ISA and leaves the principal understanding how it works: a concise ASCII map in the console and a designed HTML explanation saved next to the code. The purpose is that nothing runs in production that nobody understands.

Points at a physical plan (a gear setup, a rig, a room, a purchase list) and leaves the principal seeing it: a to-scale top-down drawing with the cost split, the full order and the open decisions, every fact quoted from the plan document.

Anything else (an idea, a comparison, a dataset, a timeline, a process) becomes one hand-built concept page with a short console summary. The skill never declines.

## Ideal State

- Whatever is named gets visualized through the route that fits it (system map, physical plan or concept page), never declined and never squeezed into the wrong route.
- Every fact on a page says where it came from (a `file` or `file:line`, a verbatim plan quote, a URL, `computed`, the principal's words or `general knowledge`), and anything unconfirmed is labelled as such rather than stated.
- The console summary alone tells the principal what the thing is and the one thing worth acting on, and the page holds the full picture, looked at in a real renderer before delivery.
- The subject is only read: the page (and a plan's model under USER) are the only writes, and no secret value lands on any page.

## Intent Routing

The rest: https://github.com/danielmiessler/LifeOS/blob/HEAD/LifeOS/install/skills/Visualize/SKILL.md