howarewoo/woostack-visualize
skills/woostack-visualize/SKILL.md
Use when you want an HTML visualization of any source — a spec, plan, file, directory, or concept — tailored to a target audience (engineer, non-technical, investor, or any free-form reader). Reads the real source and writes one self-contained, offline-viewable HTML file; never the source of truth.
development
Updated Jun 4, 2026
$ install --global
skillsauthnpx skillsauth add howarewoo/woo-stack woostack-visualizeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 5:50 AM157.8s2 files scanned
SKILL.md
- name:
- woostack-visualize
- description:
- Use when you want an HTML visualization of any source — a spec, plan, file, directory, or concept — tailored to a target audience (engineer, non-technical, investor, or any free-form reader). Reads the real source and writes one self-contained, offline-viewable HTML file; never the source of truth.
woostack-visualize
Turn any source into one self-contained HTML visualization, tailored to who will read it. The Markdown/code source stays the source of truth; the HTML is a disposable render.
Command
/woostack-visualize <source> [for <audience>]<source>— a spec/plan path, a file, a glob, a directory, or a free-form subject.<audience>— a preset (engineer|non-technical|investor) or any free-form string ("a security auditor", "a designer"). Defaults toengineer.- Examples:
/woostack-visualize .woostack/specs/2026-06-03-auth.md for an investor/woostack-visualize packages/api for a non-technical PM/woostack-visualize the review swarm architecture
Procedure
- Resolve input. Read the actual source. For a file/glob, read the files. For a directory, read enough structure (entry points, key modules, READMEs) to characterize it honestly; state in the visual what you sampled versus read in full. For a free-form subject with no path, build only from what the repo and conversation actually contain. Never invent content. If the source cannot be read, stop and say so — do not render guesses.
- Resolve audience. A preset loads its profile from
references/audiences.md. A free-form audience is interpreted
against the same dimension rubric in that file. Default
engineer. - Compose bespoke HTML. Design the layout, section set, and diagrams to fit this
content and this audience, guided by the audience profile — not a fixed template. Emit a
single self-contained
.htmlfile: inline<style>always; diagrams as inline SVG or pure CSS; JavaScript only when it adds real value and can be inlined. The file MUST render its core content offline, with no network fetch (no CDN-loaded library). For the engineer-audience spec case, woostack-build's spec-template.html is an available starting point. - Write and report. Write to
.woostack/visuals/YYYY-MM-DD-<slug>-<audience>.html(derive<slug>from the source name/subject; kebab-case a free-form audience to a short form). Honor an explicit user-supplied path instead. Print the path and offer to open it — do not open a browser unprompted. If.woostack/does not exist, write next to the source or to a user-supplied path and note thatvisuals/is the default once initialized; do not require/woostack-init.
Hard constraints
- Source of truth is the source. Generated HTML is a disposable render. Re-render anytime.
- Never write into
.woostack/specs/. That holds Markdown source only. Renders go to.woostack/visuals/(gitignored) or a user path. - Self-contained and offline. No CDN, no external fetch to render core content. Inline everything. Prefer inline SVG over a network-loaded diagram runtime.
- No fabrication. Visualize only what the source contains. When a metric, timeline, or benchmark is absent, omit it or mark it unknown — never invent one. This binds hardest for the investor audience.
- Audience is open. The three presets are shortcuts, not an allow-list; any free-form audience is valid, interpreted against the rubric.
- No browser without consent. Report the path; open only if the user agrees.
Related Skills
howarewoo/woostack-dream
testing
VerifiedTrustedCommunity
Use to curate the .woostack/ knowledge store. Reflects over the static memory store + docs (no session mining), then proposes a gated changeset that merges duplicate notes, replaces stale/contradicted ones, drops dead/orphaned notes, resolves conflicts, surfaces consolidated insights, and recommends evidence-guarded documentation edits. Nothing mutates before explicit approval; ends on a summary + iterate loop. Local-only memory (no commit); doc edits land in the working tree. Never commits or merges. Invoke via /woostack-dream [instructions].
SKILL.mdUpdated Jun 10, 2026
howarewoo/woostack-tdd
development
VerifiedTrustedCommunity
woostack's canonical test-driven-development home and on-demand test-adder. The single source for the TDD kernel — Red→Green→Refactor, test-first, cover happy/error/edge/success+failure, framework-aware, no-runner→concrete verification — that woostack-plan, woostack-execute, woostack-debug, and bootstrap patterns.md §7 should link to instead of restating. Also the 14th public command: /woostack-tdd <target> adds appropriate tests to an existing code block, PR, spec, or plan — one verb, target-routed (code→colocated *.test files, PR→tests for the gh pr diff surface, spec→strengthen §7 acceptance criteria, plan→fill failing-test steps) — with a characterization carve-out for existing code (new code is red-first; existing code pins current behavior). Writes tests to the working tree and hands to woostack-commit; never commits, merges, or authors status:/branch:; owns no approval gate.
SKILL.mdUpdated Jun 9, 2026
howarewoo/woostack-fix
development
VerifiedTrustedCommunity
Use to resolve small technical issues (bugs, hotfixes, refactors) through a unified execution loop — diagnose root cause with woostack-debug, author a fix plan under .woostack/fixes/, harden, get explicit user approval, then delegate execution to woostack-execute (TDD per task, task review, commit via woostack-commit, distill).
SKILL.mdUpdated Jun 9, 2026
howarewoo/woostack-execute-overnight
development
VerifiedTrustedCommunity
Use to execute an approved woostack plan UNATTENDED overnight — one autonomous run with no user input after launch that drives every increment to a reviewed stack, swapping woostack-execute's stop-and-ask gates for resolve-or-log-and-continue (woostack-debug on stuck verifications; bounded auto-address on a blocking review; halt-the-track on anything unsafe or ambiguous), honoring optional `## Track:` grouping in the plan (independent, fault-isolated tracks run sequentially), and writing a morning report under .woostack/overnight/ for a human to test in the morning. It is the third choice at woostack-build's execution-handoff gate (Go / Hand off / Run overnight); also usable standalone via /woostack-execute-overnight <plan-path> [--inline|--subagent]. One plan per spec, multiple PRs per plan. Never merges; never relaxes safety for autonomy.
SKILL.mdUpdated Jun 7, 2026