feat: homepage v1 with blueprint aesthetic and reusable components

.claude/agent-memory/design-engineer/MEMORY.md

@@ -0,0 +1,4 @@
+# Design Engineer Memory Index
+
+- [Role & Scope](role-and-scope.md) — My responsibilities in apps/web
+- [Tech Stack](project-tech-stack.md) — Current technologies and key files

.claude/agent-memory/design-engineer/project-tech-stack.md

@@ -0,0 +1,29 @@
+---
+name: project-tech-stack
+description: Tech stack of apps/web
+type: reference
+---
+
+## apps/web Tech Stack
+
+| Category | Technology |
+|----------|------------|
+| Framework | Next.js 16.2.6 |
+| UI Library | React 19.2.6 |
+| Styling | Tailwind CSS v4.3.0 |
+| CSS Processor | @tailwindcss/postcss 4.3.0 |
+| Documentation | FumaDocs 16.9.1 (fumadocs-core, fumadocs-mdx, fumadocs-ui) |
+| Icons | lucide-react 1.16.0 |
+| Utility | tailwind-merge 3.6.0 |
+
+## Key Files
+
+- `src/app/global.css` — Global styles + Tailwind imports
+- `src/app/layout.tsx` — Root layout with Inter font + RootProvider
+- `src/lib/source.ts` — FumaDocs content loader
+- `src/lib/shared.ts` — App config (name, routes, GitHub)
+- `src/components/mdx.tsx` — MDX component factory
+
+## Package Manager
+
+pnpm (workspace monorepo)

.claude/agent-memory/design-engineer/role-and-scope.md

@@ -0,0 +1,29 @@
+---
+name: role-and-scope
+description: My role as Senior Design Engineer for apps/web
+type: user
+---
+
+## Role
+
+Senior Design Engineer — responsible for all UI/UX design work in `apps/web`.
+
+## Scope
+
+- **Next.js 16** + React 19
+- **Tailwind CSS v4** (via `@tailwindcss/postcss`)
+- **FumaDocs** for documentation site
+- **shadcn/ui** — to be installed and integrated
+- **lucide-react** for icons
+
+## Responsibilities
+
+- UI component design and implementation
+- Tailwind theme customization
+- Responsive design
+- Design system consistency
+- Integration with FumaDocs layouts
+
+## Working Directory
+
+`C:\Users\dpereira\Documents\github\deessejs-ecosystem\errors\.claude\worktrees\docs\apps\web`

.claude/agent-memory/technical-writer/MEMORY.md

@@ -0,0 +1,9 @@
+# Technical Writer Memory Index
+
+- [Project Analysis](project-analysis.md) — Monorepo structure, tech stack, core library API, documentation status
+- [Fumadocs Docs](fumadocs-docs-reference.md) — fumadocs.dev reference for MDX/UI components
+- [Fumadocs meta.json](fumadocs-meta-json.md) — Navigation tree configuration
+- [Fumadocs Components](fumadocs-components.md) — Complete components reference with Twoslash
+- [Documentation Rules](feedback-documentation-rules.md) — h1/description forbidden, Cards for See Also, explanatory guides
+- [Writing Style](documentation-writing-style.md) — Style from better-auth, Next.js, Fumadocs
+- [Project Notes](project-notes.md) — First PR notes, Vercel config, theme, site config

.claude/agent-memory/technical-writer/documentation-writing-style.md

@@ -0,0 +1,77 @@
+---
+name: documentation-writing-style
+description: Writing style analysis from better-auth, Next.js, and Fumadocs
+type: reference
+---
+
+# Documentation Writing Style Guide
+
+Analyzed from better-auth.com, nextjs.org/docs, and fumadocs.dev
+
+## Recurring Patterns
+
+### Structure
+1. **Intro** — 1-2 contextual sentences before diving in
+2. **Steps** — Numbered or bulleted sequences
+3. **Code blocks** — Always with filename header or context
+4. **Callouts** — Tips, warnings, "Good to know"
+5. **Navigation** — "On this page" sidebar or related links at bottom
+6. **See Also** — Cards at end of page for cross-linking
+
+### Code Blocks
+- Include filename in header or comment above
+- Show language/format
+- Display in tabs when multiple options (npm/pnpm/yarn)
+- Use transformers for highlighting (twoslash for types)
+
+### Callouts
+- `info` (default) — general info
+- `warn`/`warning` — caution
+- `error` — danger
+- `success` — positive outcome
+- `idea` — tip or enhancement
+
+### Prose Style
+- Short, action-oriented sentences ("Let's start by...")
+- Explain WHY before showing HOW
+- Contextual paragraphs between code blocks
+- Tables for options/configuration
+- Numbered steps for procedures
+
+### Navigation
+- "On this page" in-page TOC (Fumadocs auto-generates)
+- Cards at bottom for related pages
+- Never bullet lists for related links
+
+## Template for New Pages
+
+```mdx
+---
+title: Page Title
+description: One-line SEO description
+---
+
+Intro paragraph explaining the concept in 1-2 sentences.
+
+## First Section
+
+Contextual prose...
+
+```ts filename.ts
+// code here
+```
+
+More explanatory text.
+
+## Second Section
+
+...
+
+## See Also
+
+<Cards>
+  <Card title="Related Topic" href="/docs/related">
+    Brief description.
+  </Card>
+</Cards>
+```

.claude/agent-memory/technical-writer/feedback-documentation-rules.md

@@ -0,0 +1,47 @@
+---
+name: documentation-rules
+description: Rules for writing documentation in @deessejs/errors
+type: feedback
+---
+
+# Documentation Writing Rules
+
+## Rule 1: No h1 in MDX content
+**Why:** The page title is set via frontmatter `title` property, not in content.
+**How to apply:** Start content with h2 (`##`) or higher. Never use `#` headings.
+
+## Rule 2: No description in content
+**Why:** Description for SEO is set via frontmatter `description` property.
+**How to apply:** Don't repeat the description in the content body.
+
+## Rule 3: No code in titles
+**Why:** Titles should be readable and descriptive without code.
+**How to apply:** Write titles as concepts, not API names. Exception: if the concept IS the code (e.g., "The `error()` function"), but avoid raw code in titles.
+
+## Rule 4: No code-only blocks
+**Why:** Documentation should be educational guides, not reference dumps.
+**How to apply:** Every code block must be preceded by explanatory paragraphs. Tell WHY, not just WHAT.
+
+## Rule 5: Explain, don't just show
+**Why:** Readers need context to understand when and why to use a feature.
+**How to apply:**
+- Lead with prose explaining the concept
+- Include paragraphs between code blocks
+- Explain the output/what happens
+- Add "why would you use this?" context
+
+## Rule 6: Every file needs a meaningful filename
+**Why:** URLs should be descriptive and SEO-friendly.
+**How to apply:** Use kebab-case descriptive names like `error-factory.mdx`, not `api.mdx` or `guide1.mdx`.
+
+## Rule 7: See Also section uses Cards, not lists
+**Why:** Cards are the Fumadocs standard for cross-linking related pages.
+**How to apply:**
+```mdx
+<Cards>
+  <Card title="Related Topic" href="/docs/related-topic">
+    Brief description of why this is related.
+  </Card>
+</Cards>
+```
+Never use markdown bullet lists for related links.