spirewise 1.7.1 → 1.8.0

package/skills/website-design-skills/07-appcues/SKILL.md

@@ -1,271 +0,0 @@
----
-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

@@ -1,42 +0,0 @@
-# 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.

package/skills/website-design-skills/08-memberstack/SKILL.md

@@ -1,271 +0,0 @@
----
-name: 08-memberstack-designer
-description: >-
-  Memberstack 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 Memberstack
-  (https://www.memberstack.com/): SaaS membership, authentication, Stripe payments, gated content, Webflow/WordPress/custom-code platform. Use when the user asks to "build a site like Memberstack",
-  "use the Memberstack design system", or wants a full design system (tokens,
-  components, pages) in vanilla HTML/CSS/JS that matches Memberstack's live look
-  and feel. Always builds the design system first, then components, then pages —
-  never random designs. Writes output to `websites/08-memberstack/`.
----
-
-# Memberstack 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 **Memberstack** website (https://www.memberstack.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 Memberstack's builder-friendly membership infrastructure 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 Memberstack actually implements (study before building)
-
-This skill is grounded in the live Memberstack site. Recreate these signature patterns:
-
-- **Builder hero** uses the scraped H1 "Launch your membership site this weekend." with subhead about authentication, payments, and gated content dropping into the site you already have.
-- **Social proof badges sit above the hero**: `$200M+ processed` and G2 rating `4.7` on G2.
-- **Nav and CTAs** include Product, Customers, Pricing, Resources, API, Login, "Build for free", "Start building free", and secondary "See pricing."
-- **Conversion reassurance** appears under the hero: "Free until launch", "No credit card required", and "Setup in 5 minutes."
-- **Logo and proof strip** includes customer logos in a marquee-style strip and a builder-money section "Builders are making real money 💰."
-- **Section order and copy** include "The hard way, or the weekend way", "Everything a membership needs. Nothing it doesn't.", "Got questions? We've got answers", and "Build something extraordinary."
-- **Visual system** uses a light grid hero background, white rounded nav shell, indigo CTAs, dark navy text, Tailwind utility-driven rounded cards, DM Sans + Caveat + JetBrains Mono, and small code/builder accents.
-
-## Design system (Memberstack 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 indigo CTA (scraped): `#4353FF`; hover `#3444DD`
-- text navy (scraped): `#1A1A2E`; dark surface `#0F0F17`; elevated dark `#2A2A3E`
-- body gray (scraped): `#6B7280`; muted gray `#9CA3AF`; border `#E5E7EB`
-- background / grid surface (scraped): `#F8F9FC`; white `#FFFFFF`; soft indigo `#EEF2FF`
-- success green (scraped): `#10B981`; warning amber `#F59E0B`; error red `#B91C1C`
-- accent purple (scraped): `#8B5CF6`; secondary indigo `#6366F1`; pink `#EC4899`; coral `#D97757`
-- shadow / overlay values (scraped): `#0000001A`, `#00000014`, `#FFFFFF33`
-
-**Typography**
-- font_family: primary **DM Sans** (scraped Next.js font variables/classes); accent handwritten **Caveat** and code **JetBrains Mono** are also loaded; 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, 500, 600, 700, 800.
-- line_heights: tight 1.1 (display), 1.3 (headings), 1.55–1.65 (body).
-
-**Iconography**
-- style: Lucide line icons, checkmarks, arrows, product/platform logos, and compact builder badges.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: membership UI cards, logo marquees, builder/customer proof, Stripe/G2 badges, and code/integration visuals.
-- 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 marquee logo movement, card hover lift, arrow nudge, and light grid/background reveals.
-
-### 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 Memberstack's nav labels: Product, Customers, Pricing, Resources, API, Login, Build for free.
-- **buttons**: primary (indigo rounded-2xl button with arrow icon and soft indigo shadow), 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 proof badges, logo marquee, hard-way/weekend-way comparison, membership feature grid, FAQ, and final build CTA.
-
-### 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 membership, authentication, Stripe payments, gated content, Webflow/WordPress/custom-code 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/08-memberstack/
-├── 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 Memberstack's scraped design tokens.
-
-## Output — write to `websites/08-memberstack/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/08-memberstack/
-├── index.html                 # full Memberstack-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 Memberstack's
-   live look (grid hero, rounded white nav, indigo CTAs, DM Sans/Caveat/JetBrains Mono, builder badges).
-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 Memberstack's section order: fixed rounded nav → hero proof badges → hero H1/subhead/CTAs → reassurance checklist → logo marquee → hard-way/weekend-way → builder revenue proof → feature grid → FAQ → final CTA → footer.
-- Output written to `websites/08-memberstack/` 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/09-flank/README.md

@@ -1,42 +0,0 @@
-# Flank Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Flank](https://flank.ai/) website — AI startup — enterprise legal AI 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 Flank's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/09-flank/`:
-
-- `index.html` — full Flank-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 Flank patterns it recreates
-
-- Dark black editorial hero with left flower panel and right legal-agent message.
-- "AI agents for enterprise legal" messaging plus intake, drafting, review, and Q&A use cases.
-- White solid CTA, outline secondary CTA, and purple `#8F87FF` news banner.
-- Scrolling inverted customer-logo marquee and restrained enterprise trust cues.
-- Solina + Antarctica variable type, atmospheric grain, radial wash, and subtle motion.
-
-## How to use
-
-Ask the agent to "build a site using the Flank design system" or "make a
-Flank-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.