readme-stylelisted

# README Style — Swiss Grid Brutalism Samuhlo's READMEs: strict order on the grid, controlled vandalism in the margins. Load when generating or refreshing a project README — not for generic doc tasks. ## Philosophy _"Arquitecturas sólidas como el hormigón, fluidas como el agua. Código limpio + caos controlado."_ A README is an architect presenting a blueprint, not a tool describing a project. Technical, self-assured, direct, with an edgy sci-fi undercurrent and terminal/bash vocabulary where it fits naturally. Every word should sound like Samuel wrote it at 2am after shipping something he's proud of. ## Before writing Read the code — never ask for a description. 1. **Read the vibe** — immersive (WebGL/GSAP-heavy) vs clean SaaS architecture. Calibrate the tagline and where `_note:` lands. 2. **Extract the DNA** — stack table only with tech actually found in the code. No filler, no invented rows. 3. **Find the magic** — the file with the heaviest logic or best animation is the snippet. No boilerplate. 4. **Don't invent** — no database section without a DB, no motion section without motion. Omit cleanly. 5. **Resolve URLs** from `package.json`, git remotes, deploy config (`vercel.json`, `nuxt.config`, `netlify.toml`). ## Signature marks These are what make it a Samuhlo README. Everything else is flexible: - **H1 as a script run** — `# <code>./[PROJECT_NAME].sh</code>`, uppercase. - **Numbered section headers** — `## // 00_ SECTION_NAME`, uppercase, doubl