visual-beautiful
The BEAUTIFUL family of the visual-reasoning stack: data visuals that maximize communication plus beauty, the sibling pole to the CLEAR family's communication plus clarity. Use when the user asks for something beautiful, striking, data art, a poster, a wall or lobby display, an exhibition piece, a screensaver, a hero image, a glowing network, a LiDAR city, a wind or flow animation, or "make it gorgeous"; and when the user wants options, to make both poles plus a combined candidate and rate them (the default when a request names neither pole). Keeps the truth floor (real data, disclosed mapping) while relaxing style rules.
Target: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Visual Beautiful
- Purpose
- When to use
- Inputs
- Modes
- The communication floor (always on, every mode)
- Style rules
- Procedure
CLEAR and BEAUTIFUL are two poles of one design space. CLEAR maximizes communication and clarity and tends toward sparsity. BEAUTIFUL maximizes communication and beauty and tends toward aesthetics. Communication is the shared floor and is never traded away. The win is a piece that is high on communication, clarity and beauty at once, so this skill always looks for the front between the poles, not just its own pole. Beauty here is not decoration on top of data. The strongest pieces are beautiful because the data is legible in them: colour breaks where the physics changes, marks that look like samples, motion that is the phenomenon. visual-intent handed off here. That is the default: a request that names neither pole gets a CLEAR version, a BEAUTIFUL version and one combined candidate. A request for beauty, art, display or exhibition narrows to this pole alone. A CLEAR figure exists and the user wants a striking companion of the same data. Not alone when the reader must read exact values or the output feeds a decision. Then CLEAR is required and a BEAUTIFUL piece may be a companion, never the sole output. Say so. Not at all when no renderer can draw the data shape honestly (step 3 fi
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- Lmandrake/MandrakeWorkflows
- Source file
- skills/visual-beautiful/SKILL.md
- Fixed revision
- 1874105936272447e2f9c81ba1dac48dae6ed074
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: Lmandrake/MandrakeWorkflows · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T03:01:44.735Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.