le-sensvisual

LeSensVisual (By THNg)

Help people recognise a subject, understand its message and experience a coherent visual world. TYY joins topic, visual meaning and readable composition. Apply it through the best supported medium for this audience. Honour the user's specified output; otherwise choose a useful format. Editability is a requirement when requested.

Design authority

User intent and required facts govern the work. TYY governs the visual benefits. A resolved artifact design guides production. Specialist recipes, templates and helpers implement that design through supported host operations. Preserve the intended visual benefits when adapting implementation; follow the host's tool contracts and report actual limits honestly.

Design the visual experience, then realise it. Bring the subject to life through meaningful illustrations, photographs, objects, actions and relationships. Extend this world into supporting content, with calm reading fields and a shared identity. Select and coordinate tools to deliver the intended expression at its useful scale and detail. Adapt the richness to the audience and task; keep explicit plain-material requests and narrow edits within scope.

• World: setting, people, objects, materials and atmosphere make this subject recognisable.
• Meaning: images and visual treatments add recognition, explanation, memory or experience.
• Relationships: show useful connections, transformations, sequences, comparisons and groupings.
• Composition: let the message organise the canvas; protect calm reading areas and a clear hierarchy.
• Harmony: coordinate imagery, supporting symbols, colour, type and the identity across a set.

An opportunity is a useful chance to establish that world, create atmosphere, embody an idea, illustrate an action, expose a relationship, protect reading space or unite the composition. Look in supporting content as well as the opening. A tidy text layout that bypasses strong opportunities fails the design goal. Atmosphere is valuable without proving a mechanism; factual diagrams still need truthful connections. Use the eleven TYY lenses for deeper calibration, not an asset quota.

Start in the actual host

Resolve the design and production method through this core, then read the relevant recipe and host instructions for its operations. Attachments supply guidance, not tools or a shared filesystem. Portable text uses RESOURCE: path sections. Ask only for missing input or capability that materially blocks the task.

Create as one coordinated task

1. Set the job. Resolve the audience, message, required facts and requested output. Otherwise choose a useful supported medium. Establish editing operations when requested.
2. Resolve the visual experience. Turn important messages into concrete visible subjects, actions and relationships, including useful supporting content. Compose them with the subject's setting, atmosphere, calm reading fields and shared identity. Specify what the viewer sees and understands in each selected expression; headings, containers and a hero alone leave supporting meaning unresolved. Use the worked decisions and one relevant selected reference to resolve valuable opportunities before selecting production tools. Transfer its visual functions into this subject, not its layout or historical facts. Adapt richness to the audience and task.

Carry one map through production: message/region → concrete visible expression and audience benefit → responsible tool → actual result → placement. Resolve the expression and its relationship to the information before assigning its tool. For example: human assistance → librarian receiving a reader's question beside the handoff explanation. Working context or an existing record suffices; small work needs only a few settled sentences.

1. Choose tools to realise that design. Honour a specified method; otherwise choose by the complete visual experience and actual delivery, precision, interaction or editing needs. PNG can be generated whole or assembled; readable copy belongs to either. Choose assembly for a useful contribution to this design, rather than renderer availability alone. For whole-image generation, brief the world, main/supporting expressions, relationships and copy together. For assembly, produce/source the selected contributions at their planned dimensions, crop and layers; actually call the available image-generation tool for planned new illustrations. Retain and inspect actual results and obtain usable files/asset IDs through supported transfer. See production.
2. Assemble and harmonise where required. Place the actual contributions with readable information and truthful relationships. Carry the same map through artwork and assembly in this task. Coordinate scale, crop, layers, colour and detail across the whole canvas. Continue dependent placement once its asset is available; independent work can proceed meanwhile. If a contribution fails, resolve that operation while preserving its intended benefit. A different deliverable needs agreement.
3. Inspect and correct the result. Open/render the delivered artifact and inspect each page and its supporting regions. Establish what intended meaning is visible, where it is visible, and which important benefit is still missing. Review world, atmosphere, relationships, composition, reading fields, harmony, evidence and closure. Revisit opportunities omitted from the plan. Restore missing visual meaning before cosmetic polish, then check facts, readability, geometry, requested editing and delivery. Refine and inspect again. Disclose unavailable visual verification. See review.
4. Deliver. Attach/show the finished artifact and required companions. State material shortfalls and checks actually performed. If the host requires user continuation, identify that specific limit and next action; intermediate artwork leaves required assembly unfinished.

Requested visual PPTX: execute the illustrated plan

Read presentations before construction. The writer consumes the same design, actual artwork and placements, including supporting regions. Use its consumed layout/asset structure or the optional checked execution helpers. Verify actual embedded media and required editable information. The AI coordinates these operations; the user need not request each stage. Explicit plain-material requests and narrow edits retain their scope.

Choose practical depth

Load the recipe for the active route; keep unrelated specialist material unloaded. Helpers and presets implement TYY and the resolved design. Replacing a helper preserves the required production operations and requested output.

For sets, assign complementary page jobs and use the intended proportions. Teaching makes the worked situation or mechanism tangible, with copyable code/data companions when needed. Existing-artifact conversion is a user-requested branch. Scoped refinements preserve useful identity; redesign may replace it.