Apply Ruben's established visual system consistently without copying the subjects or compositions of earlier images.
Before proposing concepts, writing a production prompt, generating an image, or judging an output, read references/style-spec.md in full.
Canonical references
Use these packaged images as style references when the image tool supports reference inputs:
assets/anchor-stone-linen.png— canonical anchor for tactile realism, matter-of-fact physical impossibility, and material detail.assets/anchor-glass-switch.png— canonical anchor for palette, restraint, object simplicity, patina, and unlikely material substitution.assets/stress-test-linen-light-door.png— validated range test for a more spatial or narrative subject. It proves the style can scale beyond tabletop objects, but it is not a third canonical anchor.
Treat every packaged image as a style reference, never as an edit target. Preserve the files unchanged. Do not reuse their stone, switch, door, rippling linen, or tangible-light concepts unless the user explicitly asks for them.
Workflow
- Understand what the image must communicate. If the request points to a document, page, or other source, inspect it before selecting a metaphor.
- Reduce the concept to one familiar subject or interaction plus one quiet anomaly. The concept should fit in one sentence.
- If the user requests options, offer three directions that use genuinely different visual mechanisms. Otherwise choose the clearest direction and generate directly.
- Use the environment's raster image-generation capability. When an image generation skill is available, follow it as the execution layer and use this skill as the authoritative style layer.
- Supply the two canonical anchors as reference images whenever supported. Add the stress-test image only when the brief benefits from architectural, spatial, or more narrative range.
- Inspect the output against the quality gate in the style specification. If one targeted change would fix a clear failure, make that single change and re-check. Do not drift into a wholesale redesign without the user's direction.
- Report or upload the final asset as requested. Generation does not imply permission to modify an external page; upload only when explicitly asked.
Notion covers
For a Notion page cover:
- read the page before choosing the concept;
- generate a panoramic image at least 1,500 pixels wide when possible;
- keep every essential subject detail within the central 60% of the canvas, both horizontally and vertically;
- leave expendable dark texture above, below, and at both sides for responsive cropping;
- omit text because the page title appears below the cover;
- visually verify the installed crop after upload.
Prefer a native authenticated upload. Do not expose a private image through an unrelated public hosting service merely to obtain a cover URL.
Boundaries
- Do not treat a palette match alone as success. The conceptual anomaly, material credibility, restraint, and negative space are equally defining.
- Do not copy a canonical subject or mechanism to manufacture consistency.
- Do not add multiple surreal events, symbolic clutter, or explanatory text.
- Do not make the anomaly magical or spectacular when it can be physical and matter-of-fact.
- Preserve the user's requested subject, destination, and number of outputs.