Claude Style Illustration

Provide the topic/idea, with an optional object, action, metaphor, count or ratio. Default to one 1:1 image and no text/logo/date/caption/UI/frame/watermark. Choose among the five supported ratios and agree a concise anchor/action metaphor; do not add a questionnaire for noncritical details.

Plan two to four meaningful elements, one focal cluster and enough margin. Use a compact centered square, stacked portrait action, horizontal object relationship or one continuous vertical gesture as appropriate. Select two to four reference crops for linework/shapes/hands/simple objects, inspecting them before generation; use their grammar without duplicating subjects or gallery layout.

Write a full prompt distinguishing use case, topic/action, style-reference role, exact ratio, flat background/palette, subject placement and exclusions. Use hard flat boundaries, rounded marker terminals and hand wobble, without blur, gradient, grain, shading or literal scene-building. Default to no words/logos; a specifically requested functional integration mark is a separate explicit exception.

The package documents a portable FAL route using Node.js 20+, server-side FAL_KEY and one WebP request per concept; an explicitly requested available native image tool can use the same brief without that key. Obtain authorization for a new paid request. Save the prompt and task path, use selected local references and pass the correct size preset explicitly—the helper’s own default is landscape, unlike the Skill’s square default.

Resume a recorded FAL task with the same prompt, output, ratio/quality and reference-byte hashes, polling/fetching its saved request ID rather than submitting replacements. The helper writes its task record only after submission returns; if the response/record is lost or concurrent runs occur, do not assume exactly-once charging. Check provider history before authorizing another submission. Preserve failed records and approved images.

Keep the raw generation and normalize a separate final with Python 3/Pillow using the chosen background and ratio. The script center-crops and maps pixels to ink/paper/background; inspect for cropped gestures or lost lines. Use lossless WebP for the strict palette, and avoid applying this step when a deliberate user request requires texture, gradients or extra colors.

Run the file/ratio checker and, for a batch, the manifest suite report. The basic checker allows a ratio tolerance and reports palette diagnostics; the suite enforces near-exact ratio and at most three colors for runtime outputs, with catalog-montage exceptions. Neither does visual semantics/OCR or proves the background region is uniformly filled.

Inspect every final at full size and thumbnail scale for one idea, two to four elements, clean silhouette, margins, flat color, loose lines and no unwanted words/UI/branding. State a targeted correction if needed and authorize any new paid task separately. Deliver actual individual files, raw/final paths, exact prompt, FAL task/request details when used and a concise QA note; a contact index is an extra, not the output itself.