Skip to content

docs(brand): lock pillar CRT styling system + per-screen palettes - #152

Closed
cmFrameShift wants to merge 1 commit into
mainfrom
docs/pillar-crt-styling-system
Closed

cmFrameShift wants to merge 1 commit into
mainfrom
docs/pillar-crt-styling-system

Conversation

@cmFrameShift

@cmFrameShift cmFrameShift commented Jun 12, 2026 •

Copy link
Copy Markdown
Collaborator

Title

Lock pillar CRT styling system and per-screen palettes (#161)

Description

This PR documents the confirmed CRT/terminal treatment for all pillar apps as a locked design decision. Christoph signed off against a visual mockup. This spec becomes the reference for all future pillar work so agents and contributors start from a shared baseline rather than re-deriving it.

Changes Included

  • Added/updated documentation

Specifically:

  • Palette-agnostic CRT treatment: immersive frame, grunge overlay, CRT bloom + chromatic fringe, rounded corners, hover glow, locked button system, colour hierarchy, dynamic fill meter
  • Per-screen palette assignments: User/Admin (mustard), Rally Point (rust), Fleet Command (radar green, already shipped in feat(fleet): Fleet Command rebrand + radar-green identity + four-role model (#106) #148), S.P.O.I.L.S. (oxblood), Proving Ground (blue), Terminal (purple/cyan -- v1 proposal, not yet locked)
  • Sub-decisions: grunge 50% on pillar screens, 20% on utility screens; destructive actions use muted red
  • Landing page and Muster Hub explicitly excluded from CRT treatment
  • Visual reference HTML and PDF added to 02_DESIGN & WORKING FILES/

Purpose

This PR aims to lock the CRT styling system as a confirmed decision so all future pillar PRs have a single authoritative spec to reference, preventing design drift across agents and contributors.

Related Issues / Epics

Testing

  1. Open docs/brand/ and confirm the CRT spec document is present and readable
  2. Cross-reference the per-screen palette table against the approved visual mockup
  3. Confirm Landing page and Muster Hub are explicitly listed as exclusions

Developer Notes

Confirmed design decision: one shared CRT/terminal treatment across all
pillar apps + User/Admin screens, palette swaps per screen. Landing + Muster
Hub excluded. Records the treatment, per-screen palettes, sub-decisions
(grunge levels, destructive=muted red, Terminal dual-accent v1 proposal),
and the per-screen PR split. Visual reference + PDF in the Drive design files.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cmFrameShift
cmFrameShift requested a review from blairg23 as a code owner June 12, 2026 13:15
@netlify

netlify Bot commented Jun 12, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for musterdeck ready!

Name Link
🔨 Latest commit 07a2afe
🔍 Latest deploy log https://app.netlify.com/projects/musterdeck/deploys/6a2c065fccd45c000832acf1
😎 Deploy Preview https://deploy-preview-152--musterdeck.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@blairg23

Copy link
Copy Markdown
Member

Closing in favor of #169.

The branch docs/pillar-crt-styling-system did not follow the type/NNN-short-description naming convention we have standardized. All commits are identical -- only the branch name changed to docs/161-pillar-crt-styling. Please continue review on #169.

@blairg23 blairg23 closed this Jun 12, 2026
@blairg23
blairg23 deleted the docs/pillar-crt-styling-system branch June 12, 2026 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs(brand): lock pillar CRT styling system and per-screen palettes

2 participants