Render a diagram in Adobe Illustrator via ExtendScript automation. Given a design specification from diagram-graphic-design (grid, type, color, elements) and a visual encoding plan from diagram-visual-encoding (composition, channels, layout), produce a complete JSX script that creates the diagram in Illustrator, exports it as PNG for review, and iterates until the visual output matches the specification. Handles the JSX file execution pattern, coordinate system translation, MRAP error recovery, and the render-evaluate-fix loop. Use this skill after design decisions are complete and you need to produce the actual Illustrator file. Also use when iterating on an existing diagram — fixing rendering bugs, adjusting positions, or re-exporting. Triggers on: render, Illustrator, ExtendScript, JSX, execute, export, .ai file, draw, implement, create the diagram, make it in Illustrator.
Render a diagram as SVG markup without requiring Adobe Illustrator. Given a design specification from diagram-graphic-design (grid, type, color, elements) and a visual encoding plan from diagram-visual-encoding (composition, channels, layout), produce a complete SVG file that can be viewed in any browser, embedded in HTML, or converted to PNG. This is the portable alternative to diagram-illustrator-render — use it when Illustrator is not available, when SVG output is preferred, or when the diagram needs to be web-embeddable. Triggers on: SVG, render as SVG, no Illustrator, web diagram, browser diagram, portable, HTML diagram, vector, scalable, embed, without Illustrator.
Orchestrate the diagram pipeline: content analysis → visual encoding → graphic design → rendering (Illustrator or SVG). Routes user requests to the appropriate skill, manages the handoff of specifications between skills, and provides re-entry points when the user identifies problems at any layer. Use this skill as the primary entry point when asked to create a diagram, chart, or visual explanation. Also use when the user wants to modify an existing diagram and you need to determine which layer the change belongs to. Triggers on: create a diagram, make a diagram, visualize this, diagram this, Illustrator diagram, SVG diagram, information design, one-pager, visual explanation, render as SVG, no Illustrator, web diagram, portable diagram.
Analyze source material and determine what a diagram should show. Given a document, dataset, or concept description, extract the key dimensions, find the story, prioritize what earns visual encoding vs. annotation vs. being cut entirely, and write the content that will appear on the diagram. Produces a structured specification that the information design skill (diagram-visual-encoding) consumes. Use this skill whenever someone asks to create a diagram, visual explanation, infographic, or information graphic from source material — this is always the first step before any visual decisions. Also use when the user says a diagram "doesn't tell the right story" or "is missing the point" — those are content analysis problems, not design problems. Triggers on: diagram, visual explanation, infographic, information design, visualize this, explain this visually, one-pager, concept map, educational diagram, framework diagram.
Apply graphic design principles to make a diagram look right. Given a visual design plan from diagram-visual-encoding (composition type, channel assignments, spatial layout), produce a complete design specification: grid system, type scale, color palette, spacing constants, and stroke hierarchy. Grounded in Gestalt perception principles, Lupton's typographic systems (Thinking with Type), Müller-Brockmann's grid theory, and Albers/Itten color theory. Use this skill after visual encoding decisions are made and before rendering begins. Also use when a diagram "looks unprofessional" or "feels off" — those are graphic design problems, not information design problems. Triggers on: graphic design, make it look better, polish, refine the design, typography, spacing, colors, grid, layout, alignment, visual hierarchy, professional, clean up.
Decide how information should be visually encoded in a diagram. Given a content specification from the diagram-content-analysis skill (dimensions, priorities, story, relationships), select the visual channels, composition pattern, and spatial layout that most effectively communicate the data. Grounded in Tufte's information design principles, Cleveland & McGill's perceptual effectiveness research, and Bertin's visual variable taxonomy. Use this skill after content analysis is complete and before graphic design begins. Also use when a diagram "looks fine but doesn't communicate" or when the viewer can't find the pattern — those are encoding problems, not graphic design problems. Triggers on: visual encoding, chart type, diagram type, composition selection, information design, how should I show this, what kind of chart, Tufte, data-ink ratio.