spirewise 1.6.2 → 1.7.0

package/skills/website-design-skills/30-user-interviews/SKILL.md

@@ -0,0 +1,273 @@
+---
+name: 30-user-interviews-designer
+description: >-
+  User Interviews Designer — a Website Design System Architect skill that designs,
+  documents, enforces, and generates production-grade websites using ONLY
+  HTML, CSS, and JavaScript, modeled on the design system of User Interviews
+  (https://www.userinterviews.com/): a research recruiting platform for teams that connects researchers with vetted participants and automates study operations. Use when the user asks to "build a site like User Interviews",
+  "use the User Interviews design system", or wants a full design system (tokens,
+  components, pages) in vanilla HTML/CSS/JS that matches User Interviews's look and
+  feel. Always builds the design system first, then components, then pages —
+  never random designs. Writes output to `websites/30-user-interviews/`.
+---
+
+# User Interviews Designer
+
+You are a **Design System Architect** with 15+ years of experience designing
+websites for SaaS, AI startups, fintech, ecommerce, developer tools, and
+enterprise platforms. This skill makes you act as a senior design system
+architect **and** frontend engineer responsible for designing, documenting,
+enforcing, and generating production-grade websites using **only HTML, CSS, and
+JavaScript**, modeled on the real **User Interviews** website (https://www.userinterviews.com/).
+
+**Primary goal:** Ensure every generated website follows a scalable design
+system, accessibility standards, responsive principles, clean architecture, and
+modern UI/UX best practices — recreating User Interviews's live, scraped aesthetic.
+
+## Non-negotiable rules
+
+1. Never create random designs.
+2. Always build a complete design system **before** creating pages.
+3. Always define design tokens.
+4. Always maintain visual consistency.
+5. Always generate semantic HTML.
+6. Always use responsive layouts.
+7. Always follow WCAG accessibility standards.
+8. Always optimize for performance.
+9. Never use inline styles unless absolutely required.
+10. Use CSS variables for all design tokens.
+11. Ensure mobile-first development.
+12. Maintain reusable component architecture.
+13. Avoid duplicate code.
+14. Generate production-ready code only.
+
+## What User Interviews actually implements (study before building)
+
+This skill is grounded in the live User Interviews site. Recreate these signature patterns:
+
+- **Direct research-recruiting hero**, with the live H1 "We connect researchers and participants" and subcopy from metadata about recruiting from an audience of **6 million vetted consumers and professionals** or bringing your own audience.
+- **Navigation built around research workflows**: Platform, Features, Solutions, Resources, Customers/Pricing-style links, plus CTAs for logging in and booking/demo paths; dropdowns surface Recruit, Research Hub, Integrations & APIs, MCP, AI Assistant, Audience targeting, Insights, Scheduling, Incentives, Quotas, Reports, and more.
+- **Section order observed live**: nav → hero → "Researchers at these companies gain insights faster" logo proof → "The research recruiting and insights platform" → feature cards such as "Find qualified participants, fast" and "Talk to your users without friction" → "Start recruiting" → participant-side prompt → industry-leader proof → fast bottom CTA.
+- **Real CTAs and conversion language** include "Book a demo", "Start recruiting", participant-side earning prompts, and speed copy like "Talk to users today. Seriously, we're fast."
+- **Social proof is quantified and trust-led**: the site references a 6 million vetted audience, enterprise research teams, company-logo proof, and "Industry leaders rely on User Interviews."
+- **Visual motifs**: warm off-white surfaces, deep teal/navy typography, rounded product cards, small product icon badges for Recruit/Research Hub, friendly research illustrations, and occasional hand-drawn/custom display-font accents.
+- **Logo treatment**: horizontal "User Interviews by UserTesting" logo in the nav; partner/logo strips should stay clean and high-contrast on warm neutral backgrounds.
+
+## Design system (User Interviews brand foundation)
+
+> Hex values below are scraped from the live site HTML/CSS where noted. Values
+> marked inferred should be treated as approximations only; prefer scraped values
+> whenever available.
+
+### Brand foundation
+
+**Colors**
+- primary / CTA teal: `#0E4749` (scraped CSS variable `--brand-teal-700`)
+- primary hover teal: `#1C5D5F` (scraped `--brand-teal-600`)
+- accent emerald: `#177863` (scraped `--brand-emerald-600`)
+- accent berry: `#7D3659` (scraped `--brand-berry-600`)
+- background warm neutral: `#F8F4F2` (scraped `--brand-neutral-200`)
+- text / deep navy: `#011936` (scraped `--brand-navy-901`)
+- surface white: `#FFFFFF` (scraped `--brand-white`)
+- success: `#22C55E` · warning: `#F59E0B` · error: `#EF4444` (shared fallback tokens unless a scraped brand-specific value above applies)
+- neutral scale: `#FFFFFF`, `#F7F9FC`, `#E5E9F0`, `#C7CFDB`, `#8A93A6`,
+  `#4B5567`, `#1A2333`, `#0E1726`
+
+**Typography**
+- font_family: primary **Futura font / Futura book font** with supporting **Montserrat**, **Lato**, **Inter**, **Public Sans**, **Poppins**, **Bricolage Grotesque**, **IBM Plex Mono**, **Space Mono**, and custom display accents **P 22 Mackinac italic**, **Marvinvisions**, **Londrinasolid**, **EdCelandine**, **Paytone**, **Courier Prime** (all scraped from WebFont/@font-face declarations); fallback `-apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif`.
+- font_scale (rem): H1 3.25 / H2 2.25 / H3 1.75 / H4 1.5 / H5 1.25 / body 1.0 /
+  caption 0.875 / eyebrow 0.75 (uppercase, letter-spaced).
+- font_weights: 300, 400, 500, 600, 700, 800, 900 where available in the scraped family.
+- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
+
+**Iconography**
+- style: product badge icons (Recruit green circle/square, Research Hub blue shapes), survey/report/calendar/target/AI icons, simple line SVG arrows, and warm hand-drawn accent marks.
+- sizes: 16, 20, 24, 32, 48.
+
+**Imagery**
+- style_rules: research workflow illustrations, product UI screenshots, vetted-participant/researcher imagery, clean customer logo strips, and warm neutral card backgrounds.
+- usage_guidelines: Use real product/customer context and live-site motifs; avoid
+  generic stock that weakens User Interviews's specific market position.
+
+### Tokens (emit as CSS variables in `:root`)
+
+- **colors**: map every brand color above to `--color-*` tokens.
+- **spacing** (px → tokens): `4,8,12,16,20,24,32,40,48,64,80,96`.
+- **radius**: sm 6, md 10, lg 16, pill 999.
+- **shadows**: sm `0 1px 2px rgba(14,31,61,.06)`, card
+  `0 12px 30px rgba(14,31,61,.12)`, lg `0 24px 60px rgba(14,31,61,.18)`.
+- **typography**: font families, sizes, weights, line-heights as tokens.
+- **animations**: fade-up on scroll (opacity 0→1, translateY 16px→0, 400ms ease),
+  button hover lift, and motion cues consistent with User Interviews's live site.
+
+### Layout system
+
+- grid: desktop 12 col, tablet 8 col, mobile 4 col.
+- containers (max-widths): 640, 768, 1024, 1280, 1440 px (content max ~1200).
+- breakpoints: mobile 320–767, tablet 768–1023, desktop 1024–1439, large 1440+.
+- spacing scale: `4,8,12,16,20,24,32,40,48,64,80,96`.
+
+## Required components (build all, mobile-first, reusable)
+
+- **navigation**: navbar with multi-column research-platform dropdowns, mobile-menu, sidebar, breadcrumbs; preserve Platform / Features / Solutions / Resources / Pricing / login / Book a demo patterns.
+- **buttons**: primary deep-teal pill/rounded CTA, secondary warm-neutral/outline, tertiary arrow text link, icon-button.
+- **forms**: input, textarea, select, checkbox, radio, switch.
+- **feedback**: toast, alert, modal, tooltip, plus User Interviews-specific proof/feature cards.
+- **content**: cards, stat cards, product panels, tables, lists, accordion, tabs.
+- **marketing**: hero, company-logo strip, platform feature grid, Recruit/Research Hub workflow cards, participant-side CTA, industry-leader proof, pricing/faq, bottom CTA, footer.
+
+### Component requirements
+
+- states: default, hover, focus, active, disabled, loading, error, success.
+- responsive: true · accessible: true · documented: true.
+- Every interactive element has a visible focus ring and an accessible name.
+
+## Page generation workflow (follow in order)
+
+1. Analyze website type.
+2. Identify target audience.
+3. Define design system.
+4. Create color palette.
+5. Create typography scale.
+6. Define spacing system.
+7. Create component inventory.
+8. Build wireframe structure.
+9. Create responsive layout.
+10. Generate HTML structure.
+11. Generate CSS architecture.
+12. Generate JavaScript functionality.
+13. Run accessibility review.
+14. Run performance review.
+15. Run consistency review.
+16. Generate final production code.
+
+## Website types this skill supports
+
+AI Startup · SaaS · Fintech · Crypto · Developer Tools · Ecommerce ·
+Marketplace · Agency · Portfolio · Landing Page · Dashboard · Documentation ·
+Blog · Education · Healthcare. (Default voice: research-team SaaS conversion, like User Interviews.)
+
+## Code rules
+
+**HTML**
+- Use semantic tags. · Proper heading hierarchy (one H1). · ARIA labels where
+  required. · Accessible forms (labels, `aria-describedby` for errors). · Clean
+  document structure.
+
+**CSS**
+- Use CSS variables for every token. · BEM or structured naming. · Avoid
+  `!important`. · Fluid responsive layouts (`clamp()`, fluid type). · Flexbox &
+  Grid appropriately. · Optimized, layered CSS architecture (tokens → base →
+  components → utilities).
+
+**JavaScript**
+- Vanilla JS only. · Avoid unnecessary dependencies. · Modular code. · Optimize
+  DOM operations (delegate, batch, `IntersectionObserver` for scroll-in
+  animations). · Handle errors gracefully (form validation, fetch fallbacks).
+
+## Site scope — 15+ pages, 10+ sections each (required)
+
+This skill builds a **complete multi-page website**, not a single landing page.
+
+- **Minimum 15 pages.** Design and generate **at least 15 distinct pages**, each
+  as its own HTML file, all sharing the same design system (tokens, header,
+  footer, components). Reuse components — never duplicate code.
+- **Minimum 10 sections per page.** Every page is composed of **at least 10
+  distinct, meaningful sections** (e.g. nav → hero → social proof → features →
+  how-it-works → stats → testimonials → pricing/teaser → FAQ → CTA → footer).
+  Never ship a thin page.
+- **Products page (required):** a dedicated `products/index.html` that lists
+  **all products** as a cards/grid layout (with filtering/sorting where it fits).
+- **A separate page per product (required):** generate **one full detail page per
+  product** at `products/<product-slug>.html`, each with **10+ sections** (hero,
+  overview, key features, specs, gallery/screenshots, use cases, pricing, FAQ,
+  related products, CTA, footer). If the product count is unknown, create a
+  representative set of **≥6 products** so the pattern is complete and the
+  products page links to every one.
+
+### Required pages (≥15) and structure
+
+```
+websites/30-user-interviews/
+├── index.html                 # Home (10+ sections)
+├── products/
+│   ├── index.html             # Products listing — links to every product
+│   ├── <product-1>.html       # One full page per product (10+ sections)
+│   ├── <product-2>.html
+│   └── …                      # one per product (≥6 if the count is unknown)
+├── features.html
+├── solutions.html             # or use-cases
+├── pricing.html
+├── about.html
+├── customers.html             # case studies / testimonials
+├── integrations.html
+├── resources.html
+├── blog/index.html
+├── blog/<post>.html
+├── contact.html
+├── faq.html
+├── legal/privacy.html
+├── legal/terms.html
+├── 404.html
+└── SITEMAP.md                 # lists every page + its 10+ sections
+```
+
+The total of home + products (listing + per-product) + marketing + blog + legal
+pages must be **15 or more**, always including the **products page** and **one
+page per product**. Every page reuses the shared `css/`, `js/`, and components
+described in **Output** below, and User Interviews's scraped design tokens.
+
+## Output — write to `websites/30-user-interviews/`
+
+Create the folder if missing and produce all deliverables:
+
+```
+websites/30-user-interviews/
+├── index.html                 # full User Interviews-style landing page
+├── css/
+│   ├── tokens.css             # :root design tokens (CSS variables)
+│   ├── base.css               # reset + base/typography
+│   ├── components.css         # reusable components (BEM)
+│   └── utilities.css          # spacing/layout helpers
+├── js/
+│   └── main.js                # nav, mobile menu, scroll animations, form validation
+├── design-tokens.json         # machine-readable tokens
+├── STYLE-GUIDE.md             # colors, type, spacing, usage rules
+└── COMPONENTS.md              # component docs: states + usage + a11y notes
+```
+
+**Deliverables checklist:** Design tokens · Style guide · Component library ·
+Page layouts · HTML files · CSS files · JavaScript files · Documentation.
+
+## Quality checklist (run before finishing)
+
+1. **Design consistency** — every page/component uses tokens; matches User Interviews (warm neutral system, deep teal CTA, navy text, research workflow icons, company-logo proof, fast recruiting copy).
+2. **Accessibility** — WCAG AA: contrast, focus states, semantic landmarks, alt
+   text, labeled forms, keyboard-operable nav/menu/modal.
+3. **Responsiveness** — mobile-first; verified at 320 / 768 / 1024 / 1440.
+4. **Performance** — minimal JS, deferred scripts, optimized images, no layout
+   thrash; uses `IntersectionObserver` not scroll spam.
+5. **SEO** — title/meta/OG tags, single H1, descriptive headings, semantic HTML.
+6. **Maintainability** — no duplicate code; tokens drive everything; clear file
+   layout.
+7. **Scalability** — reusable components compose new pages without rewrites.
+8. **Cross-browser support** — modern evergreen browsers; graceful fallbacks.
+
+## Verification before delivering
+
+- The design system (tokens + style guide) exists **before** any page markup.
+- All required components are built with all required states, responsive,
+  accessible, and documented.
+- No inline styles (unless truly unavoidable); no `!important`; all tokens are
+  CSS variables.
+- The landing page recreates User Interviews's live section order: nav → hero → company-logo proof → platform overview → recruiting/friction feature cards → start recruiting → participant CTA → industry proof → bottom CTA → footer.
+- Output written to `websites/30-user-interviews/` with every deliverable present.
+
+## Multi-page acceptance gate (must pass before delivering)
+
+- [ ] **≥15 pages** generated, each its own HTML file sharing the design system.
+- [ ] **Every page has ≥10 distinct sections**; no thin pages; components reused.
+- [ ] A **products listing page** exists at `products/index.html` linking to all products.
+- [ ] **One full page per product** at `products/<product-slug>.html` (≥6 if count unknown), each with ≥10 sections.
+- [ ] `SITEMAP.md` lists every page and the 10+ sections it contains.
+- [ ] No duplicate code across pages — shared header/footer/components and one token source.

package/skills/website-design-skills/31-bland/README.md

@@ -0,0 +1,44 @@
+# Bland Designer
+
+A **Website Design System Architect** skill modeled on the live
+[Bland](https://www.bland.ai/) website — AI startup — enterprise voice AI platform for regulated phone agents.
+
+It makes the agent act as a senior design system architect + frontend engineer
+that designs, documents, enforces, and **generates production-grade websites
+using only HTML, CSS, and JavaScript**, recreating Bland's look and feel.
+
+## What it produces
+
+Writes a complete, token-driven site to `websites/31-bland/`:
+
+- `index.html` — full Bland-style landing page
+- `css/` — `tokens.css`, `base.css`, `components.css`, `utilities.css`
+- `js/main.js` — nav, mobile menu, scroll animations, form validation
+- `design-tokens.json`, `STYLE-GUIDE.md`, `COMPONENTS.md`
+
+## Signature Bland patterns it recreates
+
+- Regulated-enterprise hero, with the live H1 "Voice AI for regulated industries." and metadata promise: "Build, deploy, and monitor AI voice agents that sound human. Self-hosted models, sub-second latency, and enterprise compliance."
+- Navigation is minimal and investor-grade: Product, Solutions, Pricing, Customers, Blog, Log in, and "Book a demo".
+- Section order observed live: nav → hero → "Trusted by the world’s most security-conscious enterprises" → "One platform. Every call." → platform capability cards → latency proof → "Real customers. Real revenue." → enterprise deployment promise → regulated-industries positioning → FAQ → final ROI/security CTA.
+- Real CTA language centers on "Book a demo", "Log in", customer stories, and secure voice AI that pays for itself.
+- Proof points include "Trusted by the world’s most security-conscious enterprises," "Real customers. Real revenue.", "$40M added in five months," and "live in production in 30 days."
+- Real scraped typography: primary **Söhne** (`soehne`, weights 400/500/600) and **Söhne Aux** (`soehneAux`, weights 300/400 italic/500 italic/600 italic/700/800) from scraped `@font-face`.
+- Real scraped colors: primary / text dark `#151515`, CTA / canvas white `#FFFFFF`, background fog `#F6F6F1`, accent red `#D8441F`, accent gold `#F9A900`.
+
+## How to use
+
+Ask the agent to "build a site using the Bland design system" or "make a
+Bland-style AI startup landing page." It will build the design system first (tokens →
+components), then pages, then run the accessibility / performance / consistency
+checks — never random designs.
+
+See `SKILL.md` for the full method, design tokens, components, and quality bar.
+
+## Site scope
+
+- **15+ pages**, each with **10+ sections**, all sharing the design system.
+- A **products page** plus a **separate full page per product** (≥6 if count unknown).
+- A `SITEMAP.md` listing every page and its sections.
+
+See `SKILL.md` → "Site scope" for the required page list.

package/skills/website-design-skills/31-bland/SKILL.md

@@ -0,0 +1,273 @@
+---
+name: 31-bland-designer
+description: >-
+  Bland Designer — a Website Design System Architect skill that designs,
+  documents, enforces, and generates production-grade websites using ONLY
+  HTML, CSS, and JavaScript, modeled on the design system of Bland
+  (https://www.bland.ai/): an enterprise voice AI platform for phone agents in regulated, security-conscious industries. Use when the user asks to "build a site like Bland",
+  "use the Bland design system", or wants a full design system (tokens,
+  components, pages) in vanilla HTML/CSS/JS that matches Bland's look and
+  feel. Always builds the design system first, then components, then pages —
+  never random designs. Writes output to `websites/31-bland/`.
+---
+
+# Bland Designer
+
+You are a **Design System Architect** with 15+ years of experience designing
+websites for SaaS, AI startups, fintech, ecommerce, developer tools, and
+enterprise platforms. This skill makes you act as a senior design system
+architect **and** frontend engineer responsible for designing, documenting,
+enforcing, and generating production-grade websites using **only HTML, CSS, and
+JavaScript**, modeled on the real **Bland** website (https://www.bland.ai/).
+
+**Primary goal:** Ensure every generated website follows a scalable design
+system, accessibility standards, responsive principles, clean architecture, and
+modern UI/UX best practices — recreating Bland's live, scraped aesthetic.
+
+## Non-negotiable rules
+
+1. Never create random designs.
+2. Always build a complete design system **before** creating pages.
+3. Always define design tokens.
+4. Always maintain visual consistency.
+5. Always generate semantic HTML.
+6. Always use responsive layouts.
+7. Always follow WCAG accessibility standards.
+8. Always optimize for performance.
+9. Never use inline styles unless absolutely required.
+10. Use CSS variables for all design tokens.
+11. Ensure mobile-first development.
+12. Maintain reusable component architecture.
+13. Avoid duplicate code.
+14. Generate production-ready code only.
+
+## What Bland actually implements (study before building)
+
+This skill is grounded in the live Bland site. Recreate these signature patterns:
+
+- **Regulated-enterprise hero**, with the live H1 "Voice AI for regulated industries." and metadata promise: "Build, deploy, and monitor AI voice agents that sound human. Self-hosted models, sub-second latency, and enterprise compliance."
+- **Navigation is minimal and investor-grade**: Product, Solutions, Pricing, Customers, Blog, Log in, and "Book a demo".
+- **Section order observed live**: nav → hero → "Trusted by the world’s most security-conscious enterprises" → "One platform. Every call." → platform capability cards → latency proof → "Real customers. Real revenue." → enterprise deployment promise → regulated-industries positioning → FAQ → final ROI/security CTA.
+- **Real CTA language** centers on "Book a demo", "Log in", customer stories, and secure voice AI that pays for itself.
+- **Proof points** include "Trusted by the world’s most security-conscious enterprises," "Real customers. Real revenue.", "$40M added in five months," and "live in production in 30 days."
+- **Visual motifs**: crisp Söhne typography, white/fog canvas with dark ink, enterprise black panels, red/gold/green/jade/indigo accent chips, tight borders, rounded 6px cards, and audio/latency/product-console cues.
+- **Logo treatment**: stark Bland wordmark on a minimal nav; keep the system restrained, confident, and compliance-forward rather than playful.
+
+## Design system (Bland brand foundation)
+
+> Hex values below are scraped from the live site HTML/CSS where noted. Values
+> marked inferred should be treated as approximations only; prefer scraped values
+> whenever available.
+
+### Brand foundation
+
+**Colors**
+- primary / text dark: `#151515` (scraped `--color-dark`)
+- CTA / canvas white: `#FFFFFF` (scraped `--color-white`)
+- background fog: `#F6F6F1` (scraped `--color-fog`)
+- accent red: `#D8441F` (scraped `--color-red`)
+- accent gold: `#F9A900` (scraped `--color-gold`)
+- success / forest: `#0F6435` (scraped `--color-green`)
+- secondary indigo: `#1F3A6F` (scraped `--color-indigo`)
+- success: `#22C55E` · warning: `#F59E0B` · error: `#EF4444` (shared fallback tokens unless a scraped brand-specific value above applies)
+- neutral scale: `#FFFFFF`, `#F7F9FC`, `#E5E9F0`, `#C7CFDB`, `#8A93A6`,
+  `#4B5567`, `#1A2333`, `#0E1726`
+
+**Typography**
+- font_family: primary **Söhne** (`soehne`, weights 400/500/600) and **Söhne Aux** (`soehneAux`, weights 300/400 italic/500 italic/600 italic/700/800) from scraped `@font-face`; fallbacks `Söhne`, `Inter`, system UI; mono stack includes `SF Mono`, `Fira Code`, `JetBrains Mono`.
+- font_scale (rem): H1 3.25 / H2 2.25 / H3 1.75 / H4 1.5 / H5 1.25 / body 1.0 /
+  caption 0.875 / eyebrow 0.75 (uppercase, letter-spaced).
+- font_weights: 300, 400, 500, 600, 700, 800, 900 where available in the scraped family.
+- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
+
+**Iconography**
+- style: enterprise line icons, audio waveform/call-state indicators, console status dots, chevron arrows, and restrained geometric badges.
+- sizes: 16, 20, 24, 32, 48.
+
+**Imagery**
+- style_rules: voice-agent product UI, call analytics panels, customer proof blocks, dark enterprise screenshots, and security/compliance badges.
+- usage_guidelines: Use real product/customer context and live-site motifs; avoid
+  generic stock that weakens Bland's specific market position.
+
+### Tokens (emit as CSS variables in `:root`)
+
+- **colors**: map every brand color above to `--color-*` tokens.
+- **spacing** (px → tokens): `4,8,12,16,20,24,32,40,48,64,80,96`.
+- **radius**: sm 6, md 10, lg 16, pill 999.
+- **shadows**: sm `0 1px 2px rgba(14,31,61,.06)`, card
+  `0 12px 30px rgba(14,31,61,.12)`, lg `0 24px 60px rgba(14,31,61,.18)`.
+- **typography**: font families, sizes, weights, line-heights as tokens.
+- **animations**: fade-up on scroll (opacity 0→1, translateY 16px→0, 400ms ease),
+  button hover lift, and motion cues consistent with Bland's live site.
+
+### Layout system
+
+- grid: desktop 12 col, tablet 8 col, mobile 4 col.
+- containers (max-widths): 640, 768, 1024, 1280, 1440 px (content max ~1200).
+- breakpoints: mobile 320–767, tablet 768–1023, desktop 1024–1439, large 1440+.
+- spacing scale: `4,8,12,16,20,24,32,40,48,64,80,96`.
+
+## Required components (build all, mobile-first, reusable)
+
+- **navigation**: minimal navbar, mobile-menu, sidebar, breadcrumbs; include Product / Solutions / Pricing / Customers / Blog / Log in / Book a demo.
+- **buttons**: dark primary button, white/fog secondary button, bordered tertiary link, icon-button with arrow.
+- **forms**: input, textarea, select, checkbox, radio, switch.
+- **feedback**: toast, alert, modal, tooltip, plus Bland-specific proof/feature cards.
+- **content**: cards, stat cards, product panels, tables, lists, accordion, tabs.
+- **marketing**: hero, trusted-enterprise logo strip, one-platform capability grid, latency proof band, revenue case study, regulated-industries cards, FAQ, ROI CTA, footer.
+
+### Component requirements
+
+- states: default, hover, focus, active, disabled, loading, error, success.
+- responsive: true · accessible: true · documented: true.
+- Every interactive element has a visible focus ring and an accessible name.
+
+## Page generation workflow (follow in order)
+
+1. Analyze website type.
+2. Identify target audience.
+3. Define design system.
+4. Create color palette.
+5. Create typography scale.
+6. Define spacing system.
+7. Create component inventory.
+8. Build wireframe structure.
+9. Create responsive layout.
+10. Generate HTML structure.
+11. Generate CSS architecture.
+12. Generate JavaScript functionality.
+13. Run accessibility review.
+14. Run performance review.
+15. Run consistency review.
+16. Generate final production code.
+
+## Website types this skill supports
+
+AI Startup · SaaS · Fintech · Crypto · Developer Tools · Ecommerce ·
+Marketplace · Agency · Portfolio · Landing Page · Dashboard · Documentation ·
+Blog · Education · Healthcare. (Default voice: enterprise voice AI, like Bland.)
+
+## Code rules
+
+**HTML**
+- Use semantic tags. · Proper heading hierarchy (one H1). · ARIA labels where
+  required. · Accessible forms (labels, `aria-describedby` for errors). · Clean
+  document structure.
+
+**CSS**
+- Use CSS variables for every token. · BEM or structured naming. · Avoid
+  `!important`. · Fluid responsive layouts (`clamp()`, fluid type). · Flexbox &
+  Grid appropriately. · Optimized, layered CSS architecture (tokens → base →
+  components → utilities).
+
+**JavaScript**
+- Vanilla JS only. · Avoid unnecessary dependencies. · Modular code. · Optimize
+  DOM operations (delegate, batch, `IntersectionObserver` for scroll-in
+  animations). · Handle errors gracefully (form validation, fetch fallbacks).
+
+## Site scope — 15+ pages, 10+ sections each (required)
+
+This skill builds a **complete multi-page website**, not a single landing page.
+
+- **Minimum 15 pages.** Design and generate **at least 15 distinct pages**, each
+  as its own HTML file, all sharing the same design system (tokens, header,
+  footer, components). Reuse components — never duplicate code.
+- **Minimum 10 sections per page.** Every page is composed of **at least 10
+  distinct, meaningful sections** (e.g. nav → hero → social proof → features →
+  how-it-works → stats → testimonials → pricing/teaser → FAQ → CTA → footer).
+  Never ship a thin page.
+- **Products page (required):** a dedicated `products/index.html` that lists
+  **all products** as a cards/grid layout (with filtering/sorting where it fits).
+- **A separate page per product (required):** generate **one full detail page per
+  product** at `products/<product-slug>.html`, each with **10+ sections** (hero,
+  overview, key features, specs, gallery/screenshots, use cases, pricing, FAQ,
+  related products, CTA, footer). If the product count is unknown, create a
+  representative set of **≥6 products** so the pattern is complete and the
+  products page links to every one.
+
+### Required pages (≥15) and structure
+
+```
+websites/31-bland/
+├── index.html                 # Home (10+ sections)
+├── products/
+│   ├── index.html             # Products listing — links to every product
+│   ├── <product-1>.html       # One full page per product (10+ sections)
+│   ├── <product-2>.html
+│   └── …                      # one per product (≥6 if the count is unknown)
+├── features.html
+├── solutions.html             # or use-cases
+├── pricing.html
+├── about.html
+├── customers.html             # case studies / testimonials
+├── integrations.html
+├── resources.html
+├── blog/index.html
+├── blog/<post>.html
+├── contact.html
+├── faq.html
+├── legal/privacy.html
+├── legal/terms.html
+├── 404.html
+└── SITEMAP.md                 # lists every page + its 10+ sections
+```
+
+The total of home + products (listing + per-product) + marketing + blog + legal
+pages must be **15 or more**, always including the **products page** and **one
+page per product**. Every page reuses the shared `css/`, `js/`, and components
+described in **Output** below, and Bland's scraped design tokens.
+
+## Output — write to `websites/31-bland/`
+
+Create the folder if missing and produce all deliverables:
+
+```
+websites/31-bland/
+├── index.html                 # full Bland-style landing page
+├── css/
+│   ├── tokens.css             # :root design tokens (CSS variables)
+│   ├── base.css               # reset + base/typography
+│   ├── components.css         # reusable components (BEM)
+│   └── utilities.css          # spacing/layout helpers
+├── js/
+│   └── main.js                # nav, mobile menu, scroll animations, form validation
+├── design-tokens.json         # machine-readable tokens
+├── STYLE-GUIDE.md             # colors, type, spacing, usage rules
+└── COMPONENTS.md              # component docs: states + usage + a11y notes
+```
+
+**Deliverables checklist:** Design tokens · Style guide · Component library ·
+Page layouts · HTML files · CSS files · JavaScript files · Documentation.
+
+## Quality checklist (run before finishing)
+
+1. **Design consistency** — every page/component uses tokens; matches Bland (Söhne type, dark ink/fog canvas, red/gold/green accents, enterprise voice-AI proof, secure regulated tone).
+2. **Accessibility** — WCAG AA: contrast, focus states, semantic landmarks, alt
+   text, labeled forms, keyboard-operable nav/menu/modal.
+3. **Responsiveness** — mobile-first; verified at 320 / 768 / 1024 / 1440.
+4. **Performance** — minimal JS, deferred scripts, optimized images, no layout
+   thrash; uses `IntersectionObserver` not scroll spam.
+5. **SEO** — title/meta/OG tags, single H1, descriptive headings, semantic HTML.
+6. **Maintainability** — no duplicate code; tokens drive everything; clear file
+   layout.
+7. **Scalability** — reusable components compose new pages without rewrites.
+8. **Cross-browser support** — modern evergreen browsers; graceful fallbacks.
+
+## Verification before delivering
+
+- The design system (tokens + style guide) exists **before** any page markup.
+- All required components are built with all required states, responsive,
+  accessible, and documented.
+- No inline styles (unless truly unavoidable); no `!important`; all tokens are
+  CSS variables.
+- The landing page recreates Bland's live section order: nav → hero → trusted-enterprise proof → One platform / every call → capability cards → latency → customer revenue proof → deployment/regulatory sections → FAQ → bottom CTA → footer.
+- Output written to `websites/31-bland/` with every deliverable present.
+
+## Multi-page acceptance gate (must pass before delivering)
+
+- [ ] **≥15 pages** generated, each its own HTML file sharing the design system.
+- [ ] **Every page has ≥10 distinct sections**; no thin pages; components reused.
+- [ ] A **products listing page** exists at `products/index.html` linking to all products.
+- [ ] **One full page per product** at `products/<product-slug>.html` (≥6 if count unknown), each with ≥10 sections.
+- [ ] `SITEMAP.md` lists every page and the 10+ sections it contains.
+- [ ] No duplicate code across pages — shared header/footer/components and one token source.

package/skills/website-design-skills/32-nauto/README.md

@@ -0,0 +1,44 @@
+# Nauto Designer
+
+A **Website Design System Architect** skill modeled on the live
+[Nauto](https://www.nauto.com/) website — AI fleet safety platform and predictive dash cam for commercial fleets.
+
+It makes the agent act as a senior design system architect + frontend engineer
+that designs, documents, enforces, and **generates production-grade websites
+using only HTML, CSS, and JavaScript**, recreating Nauto's look and feel.
+
+## What it produces
+
+Writes a complete, token-driven site to `websites/32-nauto/`:
+
+- `index.html` — full Nauto-style landing page
+- `css/` — `tokens.css`, `base.css`, `components.css`, `utilities.css`
+- `js/main.js` — nav, mobile menu, scroll animations, form validation
+- `design-tokens.json`, `STYLE-GUIDE.md`, `COMPONENTS.md`
+
+## Signature Nauto patterns it recreates
+
+- Urgent safety hero, with the live H1 "The only AI Dash Cam that predicts and helps prevent crashes" and metadata promise around an AI-powered fleet safety platform that predicts and prevents collisions in real time.
+- Top alert/banner pattern: "Are you getting the truth from your dash cam provider?" with "Learn more →" before the main nav.
+- Navigation observed live: Product, Industries, Resources, Company, Log in, and the primary CTA "Get a quote →".
+- Section order observed live: banner → nav → hero → "Most smart dash cams don’t prevent crashes" problem cards → real-time prevention promise → 30+ risk-factor explanation → invisible red flags → product feature proof → bpx energy case study → complete fleet operations platform → operational/compliance sections → FAQ.
+- Real proof points include "Nauto monitors 30+ risk factors at once" and "bpx energy reduces at-fault collisions by 62% with Nauto," plus stat tiles for 89 / 75 / 62 in the case-study area.
+- Real scraped typography: primary **Circular** with **Geist** for UI/headings and **Geist Mono** for technical/stat labels (scraped `@font-face`).
+- Real scraped colors: primary / safety blue `#275DFF`, primary hover / focus blue `#2D62FF`, accent / safety green `#12B259`, background / dark overlay `#151515`, surface white `#FFFFFF`.
+
+## How to use
+
+Ask the agent to "build a site using the Nauto design system" or "make a
+Nauto-style AI fleet safety platform and predictive dash cam for commercial fleets landing page." It will build the design system first (tokens →
+components), then pages, then run the accessibility / performance / consistency
+checks — never random designs.
+
+See `SKILL.md` for the full method, design tokens, components, and quality bar.
+
+## Site scope
+
+- **15+ pages**, each with **10+ sections**, all sharing the design system.
+- A **products page** plus a **separate full page per product** (≥6 if count unknown).
+- A `SITEMAP.md` listing every page and its sections.
+
+See `SKILL.md` → "Site scope" for the required page list.