Skip to content

lidge-jun/codexclaw / plugins/codexclaw/skills/dev-visualizer

cxc-dev-visualizer

Verified

Use for visual explanations and documents. Triggers: diagrams, charts, interactive models, HTML reports, infographics, 시각화, 그려줘, 문서 만들어줘, 보고서, PDF 생성.

FileKindSize
SKILL.mdskill md3.7 KB
agents/openai.yamlconfig179 B
assets/editorial-report.htmlother17.4 KB
assets/exhibit-recipes.jsonconfig26.7 KB
assets/paged-report.htmlother24.5 KB
assets/report-examples/decision-en.jsonconfig5.2 KB
assets/report-examples/decision-ko.jsonconfig5.0 KB
assets/report-examples/reference-en.jsonconfig4.8 KB
assets/report-examples/reference-ko.jsonconfig4.8 KB
assets/report-examples/research-en.jsonconfig4.2 KB
assets/report-examples/research-ko.jsonconfig4.1 KB
assets/report-model.example.jsonconfig1.6 KB
assets/research-handoff.example.jsonconfig1.6 KB
reference/artifact-composition.mdmarkdown4.8 KB
reference/authoring-routes.mdmarkdown3.5 KB
reference/computed-verification.mdmarkdown2.7 KB
reference/delivery-and-provenance.mdmarkdown762 B
reference/document-pdf.mdmarkdown17.3 KB
reference/english-authoring.mdmarkdown3.6 KB
reference/environment-detection.mdmarkdown3.3 KB
reference/exhibit-recipes.mdmarkdown12.8 KB
reference/html-templates.mdmarkdown18.0 KB
reference/page-role-catalog.mdmarkdown2.5 KB
reference/port-maintenance.mdmarkdown3.0 KB
reference/print-provenance.mdmarkdown2.9 KB
reference/reader-documents.mdmarkdown3.9 KB
reference/report-pipeline.mdmarkdown12.7 KB
reference/report-writing.mdmarkdown15.2 KB
reference/scope-and-maintenance.mdmarkdown957 B
reference/source-patterns.mdmarkdown10.3 KB
reference/svg-and-interaction.mdmarkdown9.3 KB
reference/visual-design.mdmarkdown11.3 KB
reference/visualize-contract.mdmarkdown1.1 KB
scripts/diagram-to-html.shexecutablescript8.2 KB
scripts/exhibit-contract.mjsscript24.9 KB
scripts/export-paged-report.mjsexecutablescript40.4 KB
scripts/quality-gate.mjsscript5.0 KB
scripts/report-contract.mjsscript18.1 KB
scripts/report-intake.mjsscript2.8 KB
scripts/report-locale.mjsscript27.0 KB
scripts/research-adapter.mjsscript8.7 KB
upstream/sync-check.shexecutablescript3.6 KB
upstream/visualize-upstream.mdmarkdown1.0 KB

reference/port-maintenance.md

View on GitHub
# Visualizer maintenance: codexclaw first, Aside follows

Shared behavior is maintained in
[codexclaw's dev-visualizer](https://github.com/lidge-jun/codexclaw/tree/dev/plugins/codexclaw/skills/dev-visualizer).
[aside-visualizer](https://github.com/lidge-jun/aside-visualizer) consumes selected,
verified changes and owns its Aside adapters. This is the maintenance direction,
not a claim about which project historically originated every part of the skill.

## Fix, port, verify, close

1. Map the Aside issue's acceptance criteria to shared behavior and host-specific
   adaptations. Reuse the existing report model, exporter and checks; do not build
   a second evidence or quality-gate engine.
2. Fix shared behavior in codexclaw and verify the exact changed revision. Record
   the upstream commit/PR and check results. Distinguish a work branch, merged
   `dev`, merged `main`, a published release, and the actually loaded consumer version.
3. Port the verified changes into Aside. Preserve its bundled reader references,
   source-only authoring and no-system-Chrome PDF path. Adapt host-specific work
   there instead of adding an Aside runtime dependency to codexclaw.
4. Verify the downstream revision against every applicable acceptance criterion,
   using isolated fixtures. Record the upstream SHA, downstream SHA, consumer
   version (or unknown), intentional differences, and completed/skipped checks.
5. Close the Aside issue only after the port is merged into its delivery branch
   and downstream evidence satisfies the full issue. Verify installation too when
   the issue promises installed behavior. Keep partial ports open. An upstream
   issue closing, a green unrelated suite, or a document describing a fix is not
   downstream completion. In upstream PRs use a reference, not a cross-repository
   auto-closing directive for the Aside issue.

Track four states separately: implemented, documented-only, intentionally
different, and pending. The downstream README owns the issue-to-port ledger;
codexclaw records shared changes and their proof rather than maintaining a second
Aside backlog. A checksum or version receipt records provenance, not semantic
correctness. Unexecuted required checks never count as passed checks.

This workflow applies when maintenance is requested. It grants no implicit
cross-repository push, publication, installation, issue closure or independent
loop. Artifact requests retain VIZ-SCOPE-01 and proportionate assurance profiles.

## Historical boundary before the 2026-09-22 fixes

At codexclaw `main` 1914fb679b2f625989be5af2322eec8a749663d4 and `dev`
d9d8a086a1da586008d88c8c9328b781f43e4ca0, the visualizer sources were identical.
The report model, research handoff and standalone receipt gate existed, but the
exporter still ignored NOT RUN. The pipeline described an unshipped Playwright/font
migration. This is the pre-fix baseline, not current capability documentation.
Current commands and limitations belong in report-pipeline.md; downstream acceptance
and the exact ported revision belong in the Aside README and provenance manifest.
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: 197kUpdated Claude CodeCodexVerifiedInstall
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: 197kUpdated Claude CodeCodexVerifiedInstall
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: 197kUpdated Claude CodeCodexVerifiedInstall
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: 197kUpdated Claude CodeCodexVerifiedInstall