atlas-skinlisted

# Atlas Skin Render an Atlas vault markdown note into a frozen MDX **digest** under `{vaultDir}/visuals/` (or `config.visuals.dir` if set in `atlas.config.json`), mirroring the source folder. The markdown stays the single source of truth; the `.mdx` is a human-facing, regenerable render. Never edit the source note. **Product:** [memory-atlas-visuals](https://www.npmjs.com/package/memory-atlas-visuals) (Atlas Visuals). CLI: `pnpm exec atlas-visuals …` or `npx atlas-visuals …`. Resolve paths from the consuming repo: | Token | Source | |-------|--------| | `{vaultDir}` | `atlas.config.json` → vault dir (e.g. `atlas/`, `my-project-atlas/`) | | `{visualsDir}` | `config.visuals.dir` if set, else `{vaultDir}/visuals` | | `{appDir}` | `{visualsDir}/app` (Vite gallery app) | ## When to use The user wants to *read* a dense note (tech-debt, idea, program, spec) with real UI — status/severity at a glance, scannable sections, ledger/callout structure — through the Atlas Visuals live gallery (`{appDir}/`). ## Procedure Given a source path like `{vaultDir}/tech-debt/<slug>.md`: 1. **Compute provenance** (run from the repo root): ```bash VAULT=$(node -e "const c=require('./atlas.config.json'); console.log(c.vaultDir||c.vault||'atlas')") # or read vaultDir from atlas.config.json however the repo documents it SRC={vaultDir}/tech-debt/<slug>.md # the source note REL=${SRC#${VAULT}/} # e.g. tech-debt/<slug>.md SKIN=default