lidge-jun/codexclaw / plugins/codexclaw/skills/dev-visualizer
cxc-dev-visualizer
UnverifiedUse for visual explanations and documents. Triggers: diagrams, charts, interactive models, HTML reports, infographics, 시각화, 그려줘, 문서 만들어줘, 보고서, PDF 생성.
reference/computed-verification.md
View on GitHub# Computed and exported artifact verification
**DIAGRAM-RENDER-VERIFY-01 — for the computed and exported tiers, and for any
artifact you have reason to doubt:** render the final artifact, read the
screenshot/page, fix clipping, collisions, empty charts and runtime errors. Inspect
the longest labels at narrow and wide widths appropriate to the artifact; for
responsive HTML include 320/736px and the intended desktop size. SVG text must remain
legible at its intended display/export sizes, not merely within a valid viewBox.
The paged-report exporter may run a bounded `--dump-dom` SVG crossing diagnostic
on the final filled HTML. It is supplementary P2 review evidence: a crossing is
a review finding, while a timeout, malformed result, or sampling cap is recorded
in `report.notes` and does not change the PDF verdict; the PDF page remains the
authority for print inspection.
For interaction, change the primary input and observe the resulting marks/values;
exercise keyboard access and reset when provided. A static screenshot is not
interaction proof. For PDF, inspect the **actual exported pages**, including
multipage tables, final content, Korean glyphs and selected scenario state.
Print CSS or a PDF filename alone proves nothing. For a delivered PDF/print/paged report, run the
export script's QA (REPORT-QA-01) and the fresh-reader check on the rendered pages
(REPORT-FRESH-01); an orphan line at the top of a page, a heading stranded at the
bottom, a half-empty page or a figure whose text prints under 8.5pt is a defect.
How much of that verification a PDF/print/paged report owes is a **choice stated up front**, not a
fixed tax. Reading every rendered page is expensive, and a draft does not earn it.
Pick a receipt profile — `draft`, `standard` or `publication` — per
[report pipeline](report-pipeline.md) REPORT-ASSURANCE-01, and report the
verdict with the profile and the checks it omitted. A lighter profile is honest; a
draft presented as a verified publication is not.
**DIAGRAM-SYNTAX-01:** use an existing supported parser/checker where available.
XML validation can catch malformed SVG; it cannot catch overlapped labels. Do not
invent a Mermaid CLI parse command or install a runner just for incidental proof.
**DIAGRAM-A11Y-01:** provide names/descriptions, meaningful heading order, data/text
alternatives, visible keyboard focus, non-color meaning, readable contrast and
reduced motion where applicable. These are composition decisions and apply to the
smallest inline visual. The separate inspection pass — reading actual contrast and
reading order in the rendered result — belongs to the tiers that already render;
adding ARIA does not establish accessibility conformance either way.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |