← ClaudeAtlas

code-printlisted

Draw printed matter in code instead of generating it - single-ink and two-ink posters, covers, zine pages, tickets, invitations, labels, screenprint and risograph looks, halftone and spot-colour work. Vector out, PDF-ready, type that is never wrong, same input same output. Use when asked for a poster, a cover, a print piece, "draw it yourself", "does this have to be image generation", or when the subject is type, geometry, objects, charts or repeated elements rather than skin, hair and photographic light. Ships two drawing engines, a worked example, and a six-question acceptance test.
j912835225-prog/whetstone · ★ 1 · AI & Automation · score 65
Install: claude install-skill j912835225-prog/whetstone
# code-print One sheet, one or two plates, one focus, one area of air. This tool produces **printed matter drawn in code**: vector, exportable to PDF, type that never warps, and the same output from the same input. Its opposite is not "a nice picture" - it is *rolling the dice with an image model*. Image generation draws skin and brushwork; it cannot place a line of type correctly. This draws no skin, but the type is always right and the dimensions are always print-grade. ## What this cuts, and what it does not **Comes here:** pieces whose subject is type, geometry, object silhouettes, diagrams, pattern, or repeated elements. Also pieces that contain a photograph *used as one halftone block of colour*. **Does not come here:** pieces whose subject must be photographic - skin, hair, real light, painted brushwork. Use an image model for that. **Mixed jobs:** get the photographic layer from an image model as one image, then bring it back here and use it **as a plate** - screened to halftone, flattened to one ink, placed in the layout. Type and layout are always drawn in code. ## Work card - eight steps, each with a touchpoint Do not move to the next step without the touchpoint for the current one. 1. **Look at the source, write three columns.** What is there / what is fixed (change it and the thing dies) / what is *unexpected* - each pointing at something specific (who is in front, what is largest, what is loudest). Write them into the build script's docstring. **No unex