rcode-frontend-designlisted

@.rcode/references/karpathy-guidelines.md ## Overview Builds **original** frontend interfaces with a committed aesthetic direction. Goal: interfaces someone actually remembers. Different from `rcode-clone-website` (which replicates existing sites pixel-for-pixel). Pairs with `rcode-agent-zahra` for brand alignment. Detailed aesthetic guidelines, type pair recommendations, "what to avoid" list, and rcode-specific RTL guidance live in [`references.md`](references.md). ## Design Thinking — commit before coding Before writing any code, lock these: - **Purpose** — what problem does this UI solve? Who uses it? - **Tone** — pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic, luxury-refined, playful, editorial, brutalist, art-deco, soft pastel, industrial, Omani-modern. **Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.** - **Constraints** — framework, performance, accessibility, Arabic RTL support. - **Differentiation** — what's the one thing someone will remember? Then implement code that is production-grade, visually striking, cohesive, refined in detail, and bilingual-ready (RTL from day one for rcode work). ## Workflow 1. **Understand context** — ask about purpose, audience, constraints, brand alignment. 2. **Commit to a direction** — state the aesthetic in one sentence before writing code. 3. **Check brand alignment** — if rcode branding matters, invoke Zahra (`rcode-agent-zahra`) for brand tokens.