Define relationships before rules
A useful visual language explains relationships: which shapes belong together, how materials respond to light and what makes an important object stand apart. A list of approved colours is not enough. Two artists can use the same palette and produce scenes with entirely different priorities. Begin with a few representative images and annotate the decisions they demonstrate. Show why a doorway uses a particular silhouette or why a creature carries brighter accents than the surrounding foliage. The explanation helps the rule travel beyond the original example.
Give materials a consistent behaviour
Wood, stone and metal should remain recognisable across locations, even when lighting changes. Establish a small range of edge treatments, surface patterns and highlight behaviours that can be adapted without becoming arbitrary. A carved wooden mechanism may share the same broad proportions as a stone gate while retaining a different weight and finish. Consistency does not require identical textures everywhere. It gives artists a dependable starting point, so local variations feel like changes within a world rather than evidence of several incompatible worlds joined together.
Reserve contrast for decisions
When everything receives the strongest colour, sharpest edge and brightest highlight, nothing communicates priority. Decide where contrast is needed for a player's action and where quieter treatment supports atmosphere. An interactable handle can borrow a familiar warm accent without turning the whole room into a collection of instructions. Test that relationship against several backgrounds, not just the reference scene where it was first approved. The visual language should survive new circumstances and still direct attention when several elements compete for the same small area.
Make exceptions explain themselves
An unusual object can become more convincing when it deliberately breaks an established pattern. A cold blue relic in a warm timber workshop might signal an unfamiliar origin. The exception works because the surrounding rules remain visible. Record the reason for the difference and identify which characteristics should still connect it to the game: scale, rendering style or readable silhouette, for example. Without that boundary, an exception can quietly become a new default. A world loses its visual identity through unexplained variation more often than through a single bold choice.
Keep the guide usable
A guide should answer the questions artists encounter during production. Include examples of common mistakes, a few comparisons at actual gameplay size and clear ownership for decisions that need review. A beautiful document that nobody can search will do little to keep a project coherent. Update it when a solved problem reveals a better principle, and retire guidance that no longer matches the game. The strongest shared language is a living reference: specific enough to protect identity, but open enough to allow the next artist to contribute something distinctive.
Explore Shadow & Ember
