|
| 1 | +# Canvas Taste |
| 2 | + |
| 3 | +This file owns portable Canvas artifact design judgment inside distributed `agent-html`. |
| 4 | + |
| 5 | +It is not a hard-rule file, API surface, primitive catalog, or host architecture guide. `AGENTS.md` owns executable rules. Component and style routes own source selection. `TASTE.md` owns the visual and compositional judgment agents need when an artifact must feel like a coherent work surface instead of a component inventory. |
| 6 | + |
| 7 | +## Artifact Judgment |
| 8 | + |
| 9 | +- Treat artifact content as a scene before treating it as a component list. |
| 10 | +- Let the primary media, object, or workflow establish the stage before adding UI containers. |
| 11 | +- Make one visual or object lead each major block. |
| 12 | +- Use UI as annotation, orientation, and control around the work; do not let UI containers become the work. |
| 13 | +- Prefer existing Canvas primitives and public content classes before inventing new component families. |
| 14 | + |
| 15 | +## Layout Judgment |
| 16 | + |
| 17 | +- Prefer spacing, alignment, type, captions, and state markers before adding another bordered surface. |
| 18 | +- Use panels only for real objects, control groups, placeholders, disclosures, or data scopes. |
| 19 | +- Do not wrap every image, caption, source link, and note in separate bordered surfaces. |
| 20 | +- Avoid card-inside-card depth unless each layer has a distinct object identity. |
| 21 | +- Let image-heavy artifacts use images as layout structure, not only as content inside cards. |
| 22 | + |
| 23 | +## Media Judgment |
| 24 | + |
| 25 | +- Media should carry semantic work, not just decoration. |
| 26 | +- Repeated images in one scene should have distinct jobs: context, scale, detail, sequence, evidence, or closure. |
| 27 | +- Replace visually similar supporting images when they repeat the same idea. |
| 28 | +- Keep credits and sources traceable without interrupting the narrative rhythm. |
| 29 | +- Use inline image credits near media and collect long source lists in a final source area when repeated links would break the story. |
| 30 | + |
| 31 | +## Component Judgment |
| 32 | + |
| 33 | +- Use `components/ui` primitives for ordinary actions, labels, display, disclosure, overlays, and navigation. |
| 34 | +- Use existing rich components only when their behavior matches the task. |
| 35 | +- Reuse `Timeline` for chronological or route structure before making a custom route component. |
| 36 | +- Do not create a new rich component for a one-off artifact arrangement. |
| 37 | +- Promote a local pattern only when repeated behavior or a reusable arrangement appears. |
| 38 | + |
| 39 | +## Review Checklist |
| 40 | + |
| 41 | +- The first viewport identifies the artifact subject without reading the file name. |
| 42 | +- Each major block has one leading visual, object, or workflow. |
| 43 | +- Borders are not the default hierarchy mechanism. |
| 44 | +- Panels mark meaningful boundaries instead of routine spacing. |
| 45 | +- Source links and credits are traceable without dominating the page. |
| 46 | +- Repeated images in the same block say different things. |
| 47 | +- Existing primitives are composed before new components are invented. |
| 48 | +- The artifact reads as a coherent scene or workflow, not a pile of containers. |
0 commit comments