Use for visual explanations and documents. Triggers: diagrams, charts, interactive models, HTML reports, infographics, 시각화, 그려줘, 문서 만들어줘, 보고서, PDF 생성.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Turn the reader's question and supplied facts into a useful visual artifact.
Use dev
for scope, work class and verification; a document request does not automatically
require a development loop. This skill owns artifact composition and delivery.
dev-uiux-design owns broader design judgment, dev-frontend owns frontend
implementation, and available format-specific skills own document mechanics.
| Condition | Reference |
|---|---|
| Every artifact: caller scope and requested outcome | Scope, authoring routes |
| Choosing HTML, SVG, inline output, PDF, document format or scientific plotting | Authoring routes |
| Before composing/styling/building any visual | Artifact composition |
| Human-readable reports and documents | Reader documents, report writing |
| Research reports, analytical exhibits or English/bilingual output | Research/language/exhibit routes |
| Computed/exported tiers, or any artifact in doubt | Computed verification |
| PDF/print/paged report assurance profile | Report pipeline |
| Delivery, borrowing sources or refreshing the skill | Delivery and provenance |
VIZ-VERIFY-SCALE-01 — the proof matches the failure it would catch. Rendering an artifact and reading the result costs a round trip, and much of what this skill produces cannot fail out of sight: the reader sees an inline visual before a screenshot could reach you, and a static page in normal flow shows its own text. Spend the round trip where the visible result is computed rather than written.
| Delivering | Before delivery |
|---|---|
| An inline visual in this conversation, or a fenced diagram the host renders | Reread the source once and send it. The reader's screen is the render. |
| A small static HTML/SVG page in ordinary flow — prose, tables, hand-placed shapes, no runtime data, no library, no export | Reread the source, save it, return the link. |
| Anything whose visible result is computed — marks drawn from data, connector geometry derived from rendered bounds, a runtime library or webfont, an input that changes the output | DIAGRAM-RENDER-VERIFY-01 in full. |
| PDF, print output, or a multi-page paged report | DIAGRAM-RENDER-VERIFY-01 with a stated assurance profile. Merely saving or sharing a simple static HTML/SVG file does not promote it to this tier. |
Two rules hold in every tier. An unrun check is never written up as a passed one: "not rendered — static HTML in normal flow" is honest, "verified" is not. And a defect promotes the artifact: once the reader reports something wrong, or a first render shows it, render each further fix before sending it. Nothing here is enforced by a hook, and the calling task's own verification gate still governs its work.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
The English summary is being prepared. Showing the original description.
Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.
The English summary is being prepared. Showing the original description.
Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.
The English summary is being prepared. Showing the original description.
Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.
The English summary is being prepared. Showing the original description.
Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.
The English summary is being prepared. Showing the original description.
Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.
The English summary is being prepared. Showing the original description.