# Build brief: Rebus

Resource base: https://mejohnc.org (or the preview host used to obtain this file).

Use this direction within the user’s requested project and existing design constraints.

## Illustrative use case, not project requirements
A puzzle page with a picture sequence, a labeled answer field, and an optional explanation.

A visual word puzzle that substitutes pictures for words or syllables. Because its meaning depends on language and context, it is not a universal replacement for written labels.

## Essential cues
- Image-word substitution
- Sequenced symbols
- Wordplay

## Recipe
- Use the puzzle as optional content.
- Provide a text equivalent or reveal.
- Keep navigation outside the puzzle.

## Optional decoration
Create a coherent image-word puzzle and a text equivalent.

## Avoid
Replacing essential labels with ambiguous icons or assuming the same solution works across languages.

## Values and validation
Read [tokens](/territories/rebus/tokens.json) and [acceptance checklist](/territories/rebus/checklist.md). Use [the working example](/territories/rebus/example/) to inspect color roles, spacing, hierarchy, and interaction states. It is a UI translation, not a reproduction of historical art. Tokens describe the base UI; [example CSS](/territories/assets/example.css) contains the style-specific composition and decorative layer. Preview navigation with `?navigation=top`, `?navigation=sidebar`, or `?navigation=tabs`; combine with `project`. Use [Compare](/territories/compare/) for mobile (390 px), tablet (820 px), and desktop (1440 px) viewports.

## Delivery
Preserve real content and existing working behavior. Check keyboard, narrow layout, error, empty, and success states. Report any departures from this recipe with a reason. Do not claim to have inspected a preview or run checks that you could not access.

Schema 1.0.0; revision f5fd78058ba2.