spirewise 1.6.0 → 1.6.3

package/skills/website-design-skills/06-distributional/SKILL.md

@@ -0,0 +1,271 @@
+---
+name: 06-distributional-designer
+description: >-
+  Distributional 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 real design system of Distributional
+  (https://www.distributional.com/): AI reliability / testing company site currently presenting a coming-soon landing page. Use when the user asks to "build a site like Distributional",
+  "use the Distributional design system", or wants a full design system (tokens,
+  components, pages) in vanilla HTML/CSS/JS that matches Distributional's live look
+  and feel. Always builds the design system first, then components, then pages —
+  never random designs. Writes output to `websites/06-distributional/`.
+---
+
+# Distributional 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 **Distributional** website (https://www.distributional.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 Distributional's minimal, anticipation-focused AI startup holding-page 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 Distributional actually implements (study before building)
+
+This skill is grounded in the live Distributional site. Recreate these signature patterns:
+
+- **Current live site is a coming-soon page**, not a full product site: the scraped `<title>` is "Coming Soon."
+- **Hero content is minimal**: eyebrow "Coming Soon", H1 "Something new is coming", and subhead "Check back soon for updates."
+- **No visible nav, footer, CTA buttons, testimonials, or product sections** were present in the live scrape; generated work must not invent them unless the user explicitly asks for expansion.
+- **Design language is light and spacious** with a centered single-column layout and a max-width content block (`min(100%, 54rem)`).
+- **Color tokens are inline and real**: black `#202124`, white `#FFFFFF`, purple `#6464FA`, pink `#ED77F8`, and gray text `#495057`.
+- **Visual motif** uses two large radial gradients: purple glow at the upper-left and pink glow at the lower-right over a white background.
+- **Typography is system-first Inter** with an oversized, tightly kerned display H1 using `clamp(4rem, 12vw, 8.5rem)`, line-height `.86`, and letter-spacing `-.075em`.
+
+## Design system (Distributional brand foundation)
+
+> Hex values below are scraped from the live HTML/CSS when available. Values marked
+> **(inferred)** were inferred from visible motifs or non-inline CSS references when
+> exact inline tokens were not exposed by the live scrape.
+
+### Brand foundation
+
+**Colors**
+- primary purple (scraped): `#6464FA`
+- accent pink (scraped): `#ED77F8`
+- text black (scraped): `#202124`
+- body gray (scraped): `#495057`
+- background / surface (scraped): `#FFFFFF`
+- purple radial glow (scraped rgba): `rgba(100, 100, 250, 0.16)`
+- pink radial glow (scraped rgba): `rgba(237, 119, 248, 0.13)`
+
+**Typography**
+- font_family: primary **Inter** (scraped inline `font-family: Inter, ui-sans-serif, system-ui...`); system UI fallback is part of the live declaration; system fallback
+  `-apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif`.
+- font_scale (rem): H1 3.75 / H2 2.5 / H3 2.0 / H4 1.5 / H5 1.25 / body 1.0 /
+  caption 0.875 / eyebrow 0.75 (uppercase, letter-spaced).
+- font_weights: 400, 700, 800.
+- line_heights: tight 1.1 (display), 1.3 (headings), 1.55–1.65 (body).
+
+**Iconography**
+- style: none visible on the current live site; if needed, use minimal geometric line icons only.
+- sizes: 16, 20, 24, 32, 48.
+
+**Imagery**
+- style_rules: no imagery visible; use abstract radial gradients and quiet whitespace rather than stock photography.
+- usage_guidelines: Pair real scraped content patterns with purposeful product,
+  customer, or abstract visuals; avoid generic stock that weakens the brand voice.
+
+### 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, xl 24, pill 999.
+- **shadows**: sm `0 1px 2px rgba(14,23,38,.06)`, card
+  `0 12px 30px rgba(14,23,38,.12)`, lg `0 24px 60px rgba(14,23,38,.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 subtle opacity fade and gentle radial-gradient drift only if motion is requested.
+
+### 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, mobile-menu (hamburger → full-screen or drawer), sidebar,
+  breadcrumbs. Match Distributional's nav labels: none on the current live site (optional future nav only if user requests a fuller site).
+- **buttons**: primary (no CTA button on the current live site; if added, use purple `#6464FA` with white text), secondary, tertiary/text link, icon-button.
+- **forms**: input, textarea, select, checkbox, radio, switch.
+- **feedback**: toast, alert, modal, tooltip.
+- **content**: cards, stat cards, quote/testimonial cards, tables, lists, accordion, tabs.
+- **marketing**: hero, features, pricing, faq, cta, footer. Include coming-soon hero, optional email capture only when requested, and radial gradient atmosphere.
+
+### 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: AI reliability / testing company site currently presenting a coming-soon landing page.)
+
+## 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/06-distributional/
+├── 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 Distributional's scraped design tokens.
+
+## Output — write to `websites/06-distributional/`
+
+Create the folder if missing and produce all deliverables:
+
+```
+websites/06-distributional/
+├── index.html                 # full Distributional-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 Distributional's
+   live look (minimal coming-soon page, huge Inter display type, purple/pink glows, no invented social proof).
+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 Distributional's section order: centered coming-soon hero only (eyebrow → H1 → message); add expansion sections only on explicit user request.
+- Output written to `websites/06-distributional/` 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/07-appcues/README.md

@@ -0,0 +1,42 @@
+# Appcues Designer
+
+A **Website Design System Architect** skill modeled on the live
+[Appcues](https://www.appcues.com/) website — SaaS customer engagement, onboarding, product adoption, web/mobile experiences, and AI platform.
+
+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 Appcues's look and feel.
+
+## What it produces
+
+Writes a complete, token-driven site to `websites/07-appcues/`:
+
+- `index.html` — full Appcues-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 Appcues patterns it recreates
+
+- Hero messaging: "Personalized for every user. Easy for every team" and "Experiences that get smarter with every interaction."
+- Blurple `#5C45FF`, dark navy `#020C1C`, header `#121627`, body `#20222E`, yellow `#F0FC5B`.
+- Product menu for Web and Mobile, banner for Appcues AI, and CTAs like Book a demo / Interactive tour.
+- Animated wavy underline, logo marquee, rounded UI cards, and icon-rich dropdowns.
+- Outcome-led sections for attention, first wins, retention, and growth.
+
+## How to use
+
+Ask the agent to "build a site using the Appcues design system" or "make a
+Appcues-style 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/07-appcues/SKILL.md

@@ -0,0 +1,271 @@
+---
+name: 07-appcues-designer
+description: >-
+  Appcues 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 real design system of Appcues
+  (https://www.appcues.com/): SaaS customer engagement, onboarding, product adoption, web/mobile experiences, and AI platform. Use when the user asks to "build a site like Appcues",
+  "use the Appcues design system", or wants a full design system (tokens,
+  components, pages) in vanilla HTML/CSS/JS that matches Appcues's live look
+  and feel. Always builds the design system first, then components, then pages —
+  never random designs. Writes output to `websites/07-appcues/`.
+---
+
+# Appcues 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 **Appcues** website (https://www.appcues.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 Appcues's playful yet sophisticated product-adoption SaaS 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 Appcues actually implements (study before building)
+
+This skill is grounded in the live Appcues site. Recreate these signature patterns:
+
+- **AI engagement hero** uses scraped copy "Experiences that get smarter with every interaction" and explains an AI-powered engine that reaches users across every channel.
+- **Primary H1 in the page markup** is "Personalized for every user. Easy for every team." with the supporting promise of web, email, and mobile experiences at the right moment.
+- **Top banner** promotes "Introducing Appcues AI: a system of agents that help build better experiences" with a "Learn more" link.
+- **Nav and CTAs** include Product dropdown, Web, Mobile, Interactive tour, Login (hidden on some breakpoints), "Book a demo", and demo/tour-oriented actions.
+- **Section flow** includes "Make the most out of your product investment", "Start with the outcome you want", "Built for non-technical teams with a need for speed", and lifecycle outcome sections.
+- **Outcome cards** use scraped headings "Turn attention into excitement", "Guide users to their first win", "Keep customers coming back", and "Create experiences that drive growth."
+- **Signature motifs**: blurple primary, dark navy surfaces, tan/light backgrounds, animated wavy underline CSS, logo marquee, rounded interface cards, icon-heavy product menus, and Navattic interactive demo embeds.
+
+## Design system (Appcues brand foundation)
+
+> Hex values below are scraped from the live HTML/CSS when available. Values marked
+> **(inferred)** were inferred from visible motifs or non-inline CSS references when
+> exact inline tokens were not exposed by the live scrape.
+
+### Brand foundation
+
+**Colors**
+- primary / blurple (scraped): `#5C45FF`; alternate `#5C5CFF`
+- primary hover/dark (scraped): `#4534BF`
+- light blurple (scraped): `#8B8BFF`; soft lavender `#DCE1FF`
+- dark background (scraped): `#020C1C`; darker `#0B0D16`; navy `#121627`
+- text body/header (scraped): `#20222E`, `#1D2033`, `#373C54`; on-dark body `#DADDE7`
+- surface / light (scraped): `#FFFFFF`, `#F5F8FB`, `#F5F7FA`, tan `#F4F2EF`
+- accent yellow (scraped): `#F0FC5B`; green `#7CEECD`; blue `#81B3FF`
+
+**Typography**
+- font_family: primary **DM Sans** (scraped Google/Webflow families include DM Sans and the live CSS uses it alongside **DM Mono**, **Anton**, **Mulish**, **Poppins**, **Work Sans**, and decorative **Justmeagaindownhere** / **Naturaly**); system fallback
+  `-apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif`.
+- font_scale (rem): H1 3.75 / H2 2.5 / H3 2.0 / 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.
+- line_heights: tight 1.1 (display), 1.3 (headings), 1.55–1.65 (body).
+
+**Iconography**
+- style: Phosphor/Iconify-style product icons, arrow glyphs, sparkle AI icons, and soft colored icon tiles.
+- sizes: 16, 20, 24, 32, 48.
+
+**Imagery**
+- style_rules: in-app, email, mobile, and notification UI screenshots; demo embeds; logo marquee; product-adoption outcome cards.
+- usage_guidelines: Pair real scraped content patterns with purposeful product,
+  customer, or abstract visuals; avoid generic stock that weakens the brand voice.
+
+### 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, xl 24, pill 999.
+- **shadows**: sm `0 1px 2px rgba(14,23,38,.06)`, card
+  `0 12px 30px rgba(14,23,38,.12)`, lg `0 24px 60px rgba(14,23,38,.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 wavy underline movement, logo marquee, rounded card hover lifts, and demo reveal animations.
+
+### 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, mobile-menu (hamburger → full-screen or drawer), sidebar,
+  breadcrumbs. Match Appcues's nav labels: Product, Web, Mobile, Interactive tour, Login, Book a demo.
+- **buttons**: primary (blurple filled rounded button with white text; secondary demo/tour links), secondary, tertiary/text link, icon-button.
+- **forms**: input, textarea, select, checkbox, radio, switch.
+- **feedback**: toast, alert, modal, tooltip.
+- **content**: cards, stat cards, quote/testimonial cards, tables, lists, accordion, tabs.
+- **marketing**: hero, features, pricing, faq, cta, footer. Include AI banner, multi-channel product hero, outcome cards, speed/non-technical-team sections, logo marquee, demo CTA, and 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: SaaS customer engagement, onboarding, product adoption, web/mobile experiences, and AI platform.)
+
+## 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/07-appcues/
+├── 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 Appcues's scraped design tokens.
+
+## Output — write to `websites/07-appcues/`
+
+Create the folder if missing and produce all deliverables:
+
+```
+websites/07-appcues/
+├── index.html                 # full Appcues-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 Appcues's
+   live look (blurple/dark navy contrast, wavy underline, marquee logos, friendly product icons).
+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 Appcues's section order: AI banner → nav → hero → product investment proof → smarter interactions/AI → outcome cards → speed/non-technical team section → lifecycle use cases → growth CTA → footer.
+- Output written to `websites/07-appcues/` 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/08-memberstack/README.md

@@ -0,0 +1,42 @@
+# Memberstack Designer
+
+A **Website Design System Architect** skill modeled on the live
+[Memberstack](https://www.memberstack.com/) website — SaaS membership, authentication, Stripe payments, gated content, Webflow/WordPress/custom-code platform.
+
+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 Memberstack's look and feel.
+
+## What it produces
+
+Writes a complete, token-driven site to `websites/08-memberstack/`:
+
+- `index.html` — full Memberstack-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 Memberstack patterns it recreates
+
+- Hero: "Launch your membership site this weekend."
+- Proof badges: `$200M+ processed`, `4.7` on G2, free until launch, no credit card, setup in 5 minutes.
+- Nav labels Product, Customers, Pricing, Resources, API, Login, Build for free.
+- Light grid background, rounded white nav, indigo `#4353FF`, dark `#1A1A2E`, gray `#6B7280`.
+- DM Sans, Caveat, and JetBrains Mono with builder-friendly cards and membership feature sections.
+
+## How to use
+
+Ask the agent to "build a site using the Memberstack design system" or "make a
+Memberstack-style 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.