# Skyzai illustration brief

[D] Reusable commission template. Not a delivered or licensed artwork pack.
Normative rules and performance budgets live in the current brand guide,
Illustration & Diagrams and Ship the visual sections; do not freeze a second scale here.

## 1. Name the job

- Product, owning surface and state:
- Audience and the one question to answer:
- Adjacent heading, explanation and real action:
- Intended display size and compact crop:
- What remains understandable with the image removed:
- Interface spot / editorial scene / factual diagram / photography:
- App-specific setting and why it suits the customer's job:
- Subject and the particular action or relationship:
- Viewpoint, scale and focal crop:
- Composition: intimate/expansive, quiet/active, symmetrical/off-centre:
- How these four choices differ from neighbouring illustrations:
- How this setting differs from sibling apps (not just colour or camera angle):
- Original scene ID and its single assigned content placement:
- Logical slot (not a new placement for each responsive export or DOM variant):
- Existing scene register reviewed to avoid visual repetition:
- For Skyzai: whose agency is visible, and what can they understand, choose or change?

Choose among three complementary layers: moving atmosphere sets the scene,
original editorial artwork tells the story, and Material illustrations with
official Google Material Symbols explain the mechanism. They share a language;
they are not three mandatory decorations for every section.

## 2. Pin a reference and a family

Skyzai has its own cyberpunk visual world: agency before scenery. Its selected
interpretation draws on Timothy Leary's individual as a reality pilot, using
knowledge and technology for self-direction. Bruce Bethke coined the term;
Leary developed this interpretation. This is not a definition of the entire
genre or an adoption of all Leary's views. The linked source accounts and
interface requirements live in the guide's `#skyzai-cyberpunk` section.

Start with “your keys, your network, your agency”. Show a meaningful choice,
discovery or freely chosen connection. Future cities, metal and glass, luminous
colour and lived-in technology are optional means, not requirements. Daylight,
domestic, natural or abstract settings can express technological self-direction.
Neon and dystopia are not acceptance criteria. The Me / We / They entrances
share this direction through distinct scenes for personal agency, shared purpose
and useful machine connections. Do not use APU's illustrations or settings on
Skyzai surfaces. Use the shared Material Bridge rendering language instead of
switching to cinematic game art or a default violet neon palette.

This does not reskin APU, Circle, ReFu or other sibling products as cyberpunk.
Every app needs a distinct setting chosen for its purpose. Share Google Sans,
Material behaviour and official Symbols, accessible semantic colours, the
contained moving glow and the standard of meaningful original composition.
Cyberpunk art does not force dark mode, neon controls or recoloured artwork.

Material Bridge is the rendering style, not the recurring subject. Preserve
geometric painterly forms, simplified silhouettes, sculptural forms, softly
painted shading, tactile matte surfaces, deliberate colour and soft light.
APU's Mediterranean coast is not the Skyzai default. The six references
in `apu/manifest.json` document provenance and rendering craft, not stock
artwork for reuse. “Material Bridge” names this selected illustration direction,
not a Google component library, certification or third-party artwork licence.
Start from one customer outcome and keep the metaphor legible at card size.

Vary four axes without changing the rendering craft:

- Settings: interiors, wilderness, workshops and everyday spaces; not always futuristic cities.
- Subjects: people, tools, objects, natural systems and interactions; not always buildings.
- Viewpoints: close-ups, overhead views, eye-level scenes, wide landscapes and unusual crops.
- Composition: intimate or expansive, quiet or active, symmetrical or off-centre.

No default repetition of bridges, arches, terraces or golden sunsets. Give any
such motif a specific conceptual reason. A different camera angle or palette on
the same coast does not create a distinct app setting; nor must one app stay in
one location. Use an app-specific representative for craft and product meaning,
not as a fixed camera or staging template. A quiet Material spot illustration
need not depict an entire setting. Compare planned scenes side by side; variety
must clarify their particular ideas, not introduce arbitrary novelty.

For Material illustrations, assemble one principal object and at most two
supporting objects: note cards, conversation fragments, source sheets or
connected tiles. Use existing shape, spacing, surface and elevation tokens in
HTML/CSS or reviewed SVG. Place unchanged, registered Google Material Symbols
inside the composition, with the approved axes and semantic currentColor.
Do not generate, redraw or roughen the official glyphs. Keep the specimen still
and non-interactive, with its complete meaning in adjacent text—not a fake
button, recording state or proof of an integration.

Original rounded linework is a separate optional spot-illustration treatment,
not a replacement icon family. Review actual size, not only a magnified
artboard. State the family decisions explicitly:

- Stable stroke/end treatment, tactile finish and shape vocabulary:
- Variable perspective, scene scale, focal placement and composition:
- Detail threshold at smallest approved size:
- Linework and accent roles; system light/dark and explicit warmth treatment:
- Focal object, supporting objects and crop safe area:
- Motion, if necessary; still and reduced-motion treatment:

Use one approved app-specific representative as the setting/campaign reference,
alongside the shared interface and delivery rules. Do not independently regenerate the style
for every screen. Do not generate logos or imitate controls.
Material Symbols serve both control/navigation icons and the explanatory
objects above. Their role must stay clear: decorative symbols do not become
controls, and actual icon-only controls still need accessible names and targets.

### Moving atmosphere

Choose two reviewed hues that relate to the artwork; keep semantic action,
text, error and focus roles unchanged. Reuse the existing contained-glow policy,
not a new animation engine. Colour peaks roam to bounded fresh destinations,
including centre, edges and corners; neighbouring light pools mix rather than
cover one another. Verify green/blue overlap contributes cyan, visible movement,
pause/resume, reduced motion, hidden/offscreen stopping and useful stills.
Retain padding inside the invisible rounded container and an external gap to
the next surface. Keep Material objects legible above the glow; ordinary task
states may omit atmosphere entirely. Exact motion acceptance lives in the guide.

### Reusable editorial prompt skeleton

Original still concept illustration for [product / surface / customer question].
Show [one useful change] through [one readable metaphor]. Set it in [app-specific
environment], chosen because [connection to this app's job], distinct from
[sibling app's setting]. Compose [focal subject, scale and negative space] in
[the shared Material Bridge geometric painterly language]. View it from
[close-up / overhead / eye-level / wide / unusual crop], with [intimate or
expansive, quiet or active, symmetrical or off-centre composition]. Keep the
craft consistent, not the camera or subject. Compared with [neighbouring scene],
this illustration expresses [different idea] through [distinct staging].
For Skyzai, show [whose agency] through [a meaningful choice or discovery];
do not equate cyberpunk with a compulsory neon city or dystopia.
Use clear silhouettes, sculptural planes, softly painted shading, matte grain
and deliberate light; share rendering craft without copying APU's scenes.
Choose [soft lighting and tactile materials appropriate to this world]. No
default repetition of bridges, arches, terraces or golden sunsets. Do not default
to a Mediterranean coast or add architecture/landscape unless the idea calls for it.
Use [reviewed scene colours] with [small accent]. Keep
important content inside [placement-specific safe area] of [required aspect
ratio; 3:2 card, 16:9 chapter or another reviewed format]. Do not copy an
existing poster or reuse any existing scene, including one from the same topic.
Create original artwork for this placement; a new crop, recolour, mirror or minor
prop change is not a new illustration. No lettering, logos,
watermarks, embedded UI, fake screenshots, glossy generic 3D objects or
decorative robot, brain or circuit-board filler. A machine may be a subject when
its specific role is the idea, not decoration. Keep labels and actions outside the artwork.

Attach this app's approved rendering and setting representative,
when available; name what to retain from each. For a new app, review a first
representative before expanding the set, rather than borrowing another app's world.
Review the generated image for meaning, anatomy, accidental text, crop and
misleading product claims. A successful generation call is not acceptance.

## 3. Historical optional commission: a bridge to understanding

This named example is provenance, not a default prompt or the meaning of Material
Bridge. Use the four-axis brief above for each new idea; do not repeat this scene.

Audience: a first-time visitor learning how sources support an answer.
Question: how do the pieces come together without losing their origin?
Scene: packet-shaped stepping stones connect a question to a readable answer;
the source side stays visible. Use the Building a Bridge reference selectively
for warmth and metaphor, never as a blanket interface skin.

No simulated customer, return, working installation, product screenshot or
logo redraw. Natural subject colours are allowed in reviewed editorial art;
they do not become interface colour roles. Label a plausible product scene as
concept artwork. An accessible Community file is not itself a reuse licence.

## 4. Deliver source, exports and evidence together

- Stable scene ID, single assigned placement, export IDs and revision; owner
  and acceptance status. Responsive/appearance exports and an approved silent
  hover derivative are variants of that same placement, not new placements.
- Editable master, creator/model/version when available, date and edit history.
  Record unavailable generator metadata explicitly; never invent a model ID.
- Reference provenance, rights or licence record and usage restrictions.
- For generated work: prompt hash and private prompt/source custody.
- Approved dimensions, focal point, crop and smallest tested size.
- SVG for reviewed vectors; responsive AVIF/WebP plus fallback for raster work.
- Remove SVG scripts, handlers, foreign objects and external references.
- External SVGs: explicit approved ground variants. Inline SVGs: role-bound
  fills/strokes; CSS inheritance is not available through an external img.
- Alt-text decision and text equivalent; meaningful labels remain HTML.
- Motion source plus complete still; never require a runtime generator to read.
- SHA-256 per export, family revision and review receipt in the asset manifest.

## 5. Accept in context

- The picture helps this state; heading and action work without it.
- Skyzai: the useful choice or discovery remains legible without neon scenery.
  The picture supports human agency, not compulsory automation or surveillance.
  Concept artwork does not prove key custody, sharing controls or live integrations.
- All four appearances and forced colours preserve the task.
- No clipping at compact width or 200% text; RTL composition is reviewed.
- Decorative images are hidden from assistive technology; meaningful images
  have useful alternative text. A diagram has a complete text equivalent.
- Media failure, offline reading and reduced motion do not block action.
- Source and exports agree; approved logo geometry remains separate.
- Performance follows the guide's shared budgets, or a measured exception.
- Rounded inset frame and external spacing after every glow-bearing surface;
  internal padding alone does not create a gap to the next card.
- Never use the same illustration twice. Audit every placement across pages,
  sections and apps, including a card and its destination. Use distinct original
  artwork or omit the second picture; preserve continuity through title, colour
  and Material motion instead. Compare scene IDs and hashes, then visually review
  for crops, recolours, mirrors and minor edits that disguise a repeated scene.
- Official logos, functional icons and Material building blocks may repeat;
  assembled Material illustrations follow the same one-placement rule.
- Review the full collection side by side for repeated settings, subjects,
  viewpoints and compositions—not only duplicate files. Each illustration must
  express its particular idea and feel distinct beside the others. Keep strong
  scenes; regenerate or omit weak ones rather than churning the whole collection.
- Skyzai's agency-led scenes use the shared Material Bridge rendering language,
  not APU's existing illustrations or scenery. Sibling products keep their own
  visual worlds. Audit both rendering consistency and original settings;
  new colours, props or a crop do not make a reused scene original.
- Supporting art stays still. Any approved hero hover derivative is small,
  silent, optional, cancellable and unnecessary for touch/keyboard use.
- Archive superseded drafts with provenance outside the active family.

For the optional bridge scene, informative alt text can be: “A bridge of source
packets connects a question to an answer.” If the adjacent paragraph already
supplies that meaning, use empty alt text instead.