[New1Direction]

Purpose

Establish a reusable design discipline without restyling production UI. Repo Taste preserves repo.ing's charcoal/emerald palette, approved cat assets, deliberate mono/retro identity and working data/trading flows.

Contents

• Local Repo Taste skill entry points for Codex and Claude Code
• Portable taste principles, repo.ing profile and optional CSS alias reference
• Repeatable QA gate with screenshot widths, real data truth, accessibility and explicit protected-flow requirements
• Agent invocation brief and focused root guidance (UI tasks only)

Why not blindly apply upstream Taste Skill

The upstream anti-slop rules are valuable for composition and browser review, but reject several approved repo.ing design choices (monospace, outlines, grids and tasteful glows). Repo Taste keeps useful checks while documenting deliberate exceptions.

Safety / scope

• Docs/agent instructions/reference CSS only: no runtime imports, UI code, business logic, transactions, settings or contracts changed.
• No live buy, sell, signing, key, database, deploy or main merge.
• No screenshots or browser tests claimed for this documentation-only foundation.

Next proposed pass

Audit /explore in an actual browser and propose an isolated UI-only change with before/after screenshots at 1440/768/390 and both themes.