Conceptual Digital Patina showcase for the fictional KEPT long-life personal archive service: a digital archive interface and printed memory object showing subtle traces of age, annotations, revisions, and careful maintenance.
All styles

Design direction / assertive

Digital Patina

Make software history, accumulated use, and technical personality feel valuable rather than obsolete.

Choose this style

01 / Overview

Feels technical, nostalgic, expert, with a deliberate rather than generic personality.

Signature move

A current interface exposes one persistent trace of prior states, commands, or user-made customization.

Intensity
assertive
Versatility
4 / 5
ID
digital-patina

02 / Example art

Digital Patina

Original artwork establishes the direction's visual language before it is translated into an interface.

Conceptual Digital Patina showcase for the fictional KEPT long-life personal archive service: a digital archive interface and printed memory object showing subtle traces of age, annotations, revisions, and careful maintenance.
Make software history, accumulated use, and technical personality feel valuable rather than obsolete.

03 / Website example

Try the page as a working experience

Explore this responsive page directly inside the catalog. Its primary navigation, controls, and interactions are live; open it full screen to experience the original composition.

Examples are in production

The direction is available now. Its brand websites are being built as independent sites and will appear here during local production.

04 / Fit

Suitable for

Suitable for

developer tools / ai / gaming / music / creative tools / technology

Business goals

control / customize / remember / explore

A strong choice when

Strong when developer tools, ai, gaming, music need to control, customize, remember through a memorable but repeatable visual system.

Avoid when

Avoid when the brief needs complete visual neutrality or when this direction would compete with essential information and actions.

05 / Design system

Design system

Rules that should remain coherent as content, devices, and business needs change.

01Composition
Command history, nested workspaces, visible state, and current interaction conventions within an older visual cadence.
02Hierarchy
Make the signature move the first organizing decision, then reveal supporting information through stable scale, alignment, and sequence.
03Typography
Characterful mono plus a highly legible interface sans; pixel or bitmap faces only at suitable sizes.
04Color
Phosphor, system gray, ink, and one bright status color with current contrast standards.
05Imagery
Screens, artifacts, waveforms, code, or user-made output rather than fake hacker imagery.
06Material
CRT bloom, scan lines, window chrome, and worn controls used selectively and honestly.
07Motion
Typing, state trails, window choreography, and immediate keyboard feedback with modern performance.

Adaptation

Keep the signature move invariant. Adapt imagery, material, language, and interaction to the actual developer tools, ai, gaming context rather than copying a finished reference.

Accessibility

Use progressive disclosure, stable alignment, and generous line spacing for dense information. Provide an equivalent reduced-motion state. Meet WCAG AA contrast, visible focus, 44px targets, and never encode meaning through color or style alone.

06 / Background

Background

These lineages are source-linked research doors, not permission to copy a particular work or brand.

  • 01web one
  • 02terminal ui
  • 03hypercard
  • 04net art

Guardrail

Preserve current usability and accessibility; nostalgia is a product voice, not permission to recreate old limitations.

07 / Agent recipe

digital-patina

Use the stable ID and recipe to give design agents the same context. Always adapt the output to the real business.

Prompt recipe

Use case: stylized-concept
Asset type: Aesthetic Directions Encyclopedia showcase, 3:2 landscape master
Primary request: Create one polished freeform showcase for Digital Patina, applied to KEPT, a clearly fictional long-life personal archive service.
Scene/backdrop: a digital archive interface and printed memory object showing subtle traces of age, annotations, revisions, and careful maintenance.
Style/medium: A coherent contemporary design world, not a collage of references. Make software history, accumulated use, and technical personality feel valuable rather than obsolete.
Composition/framing: Command history, nested workspaces, visible state, and current interaction conventions within an older visual cadence. Keep all important content inside an 8 percent safe margin.
Typography: Characterful mono plus a highly legible interface sans; pixel or bitmap faces only at suitable sizes.
Color palette: Phosphor, system gray, ink, and one bright status color with current contrast standards.
Imagery: Screens, artifacts, waveforms, code, or user-made output rather than fake hacker imagery.
Materials/textures: CRT bloom, scan lines, window chrome, and worn controls used selectively and honestly.
Text (verbatim): "KEPT". No other readable words.
Constraints: Original fictional concept; visibly applied to ui, website, editorial; realistic production detail; no real company, client, result, claim, signature, or watermark; no imitation of a living artist or proprietary campaign.
Avoid: retro skin over generic SaaS, fake terminal text, low contrast justified as nostalgia, real logos, watermarks, artist imitation, generic mood board, illegible filler text.
Pilot refinement: Make one dominant integrated real-world application readable at thumbnail scale. Secondary views may support it but must remain subordinate. Do not create an equal-weight tiled mood board or generic presentation collage unless sequencing is essential to the direction. Render the exact requested text correctly and do not invent other readable copy.

Working constraints

  • Use one coherent direction grammar, not a collage of style references.
  • Use only a fictional business and minimal exact text.
  • Do not imitate a living artist, real brand, client project, or proprietary campaign.
  • Preserve essential hierarchy, legibility, contrast, and reduced-motion equivalence.
  • Avoid: retro skin over generic SaaS.
  • Avoid: fake terminal text.
  • Avoid: low contrast justified as nostalgia.

08 / Sources & rights

Sources & rights

Work ownerSol

Example licenseAll rights reserved

  1. 01

    Olia Lialina — A Vernacular Web: Indigenous and Barbarians

    Role: lineage · Linked source retains its own rights; IndexStyle structured description is CC BY 4.0.

  2. 02

    Computer History Museum

    Role: lineage · Linked source retains its own rights; IndexStyle structured description is CC BY 4.0.

  3. 03

    Museums Victoria Collections「Hypercard Overview」

    Role: lineage · Linked source retains its own rights; IndexStyle structured description is CC BY 4.0.

  4. 04

    Rhizome ArtBase

    Role: lineage · Linked source retains its own rights; IndexStyle structured description is CC BY 4.0.

The choice will be carried into the Quick Brief and can still be removed before sending.

Choose this style