Source record updated
Use for navigation, controls, tables, labels, help text, and anything a person must operate.
LEARN SILVER SIGNAL / PUBLIC BRAND KIT / REVISION 1.0
A practical visual system for lessons, research tools, community spaces, and small AI-assisted workflows. It borrows the legibility and visible structure of late-1990s software without treating the past as decoration.
HANDOFF FILES
Use the full package for implementation, or take the brief and tokens separately for an AI or engineering handoff.
silver-signal-brand-kit.zip↓Claude design briefProduct and visual instructionsclaude-design-brief.md↓Design tokensColors, type, spacing, bordersdesign-tokens.json↓Stable public paths are reserved above. A file may be temporarily unavailable while the downloadable package is being published.
FOUNDATION / PRINCIPLES
The interface should feel dependable before it feels impressive. Favor clear labels, visible structure, and familiar controls.
Name what is ready, pending, local, or unavailable. Color may reinforce a state, but text must always explain it.
Show sources, dates, limits, and confidence. Avoid decorative certainty, synthetic urgency, and intelligence cosplay.
Review steps and privacy reminders are product features. Do not optimize careful work into one unexplained click.
FOUNDATION / COLOR
Blue establishes application structure. Silver and paper carry most content. Semantic colors communicate state only when paired with a written label.
#245EDBActive chrome, primary markers#0B3D91Frames, selected states#D4D0C8Classic controls, dividers#ECE9D8Menus, toolbars, panels#FFFFFFReading and data areas#111111Primary text and outlines#67B94AReady and online states#FFD83DCaution and review states#C83B24Blocked and destructive statesFOUNDATION / TYPOGRAPHY
Source record updated
Use for navigation, controls, tables, labels, help text, and anything a person must operate.
Start with one clear question.
Use selectively for page titles and learning headlines. Keep body copy in the interface face.
CONFIDENCE: MODERATE
Use for file names, identifiers, timestamps, tokens, compact metadata, and machine-readable values.
FOUNDATION / GEOMETRY
Start from a 4-pixel unit. Prefer borders, alignment, and spacing over shadows. When a shadow is useful, make it short and visibly mechanical.
--space-14px--space-28px--space-312px--space-416px--space-624px--space-832px--space-1248px2px solid #143C8C1px solid #BCBCBC2px outset #FFFFFF2px inset #FFFFFFCOMPONENTS / CORE UI
Use for major tools and contained workspaces.
Modified today · review pending
Use sentence case and concrete verbs. Reserve the strongest outline for one preferred action per view.
Pair shape, color, and plain language.
PATTERNS / INFORMATION
Put source information beside interpretation. A person should be able to see what entered the system, what happened to it, and what remains uncertain.
| Claim | Service resumes Monday |
|---|---|
| Observed | 14 Aug 2026, 09:20 |
| Source | Public bulletin / direct copy |
| Confidence | Review |
| Missing | Official schedule confirmation |
Use rows for facts and provenance. Do not hide important qualifiers inside a tooltip.
A useful prompt names the task, evidence, limits, and output. It does not rely on a role-play persona to create authority.
GUIDANCE / APPLICATION
SPECIMEN / AI WORKSPACE
This static specimen demonstrates how an AI-assisted tool can show context, process, limits, and output without pretending the system is a person or an oracle.
“I found two posts saying the town water notice was lifted. How should I check this before sharing it?”
Treat the posts as leads, not confirmation. Check the town or utility's official notice page and confirm that the update names your service area and is newer than the original advisory. If no official update is available, share that the claim is unconfirmed and link to the latest dated notice instead.