Declaudify

Create a custom slash command called declaudify for this project.

First, check the current Claude Code docs for how custom slash commands work (file location, frontmatter format, argument syntax like $ARGUMENTS). Don't assume — the format changes. Look it up, then build accordingly.

PURPOSE The command strips the generic "AI-generated" house aesthetic out of UI that I (or you) have produced, and regenerates it with intentional design choices. It should work whether I point it at a specific component/file ($ARGUMENTS) or ask it to audit the current frontend.

THE AESTHETIC TO KILL This is the convergent look every AI design tool defaults to. Treat each of these as a code smell to find and remove:

• High-contrast display serifs (Canela/Sectra-like, thin hairline + fat stem) used for headlines by default
• Cream/off-white (#f5f0e8-ish) backgrounds OR near-black, paired with a single rust/terracotta-orange accent
• One word per headline italicized in the accent color (the #1 tell)
• Letter-spaced uppercase monospace/grotesque kickers and labels
• Thin horizontal rules and middot (·) separators flanking section labels
• Oversized italic numerals (01, 02) for list items
• Icons inside rounded-square tiles inside cards
• Pseudo-editorial "magazine" framing applied to things that aren't editorial
• Excessive monospace with decorative lines beside it

WHAT THE COMMAND SHOULD DO

1. Scan the target (file in $ARGUMENTS, or the frontend if no arg) for the tells above — fonts, the cream+orange palette, italicized accent words, monospace labels, rounded-square icon tiles.
2. Report what it found and why each reads as templated.
3. Rewrite using design choices justified by THIS project's actual context — read any existing design tokens, theme files, brand/style guides, or CLAUDE.md design notes in the repo and build from those. If none exist, ask me for a direction before inventing one. Do NOT swap one default aesthetic for a different default aesthetic.
4. Keep all functionality, props, and behavior identical. This is a visual pass only.

Before writing the command file, restate in one line how you'll handle the "no design system exists yet" case, then create it.