spirewise 1.7.1 → 1.9.0

package/skills/website-design-skills/19-kraftful/SKILL.md

@@ -1,273 +0,0 @@
----
-name: 19-kraftful-designer
-description: >-
-  Kraftful 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 Kraftful
-  (https://www.kraftful.com/): AI product feedback analysis / product management copilot. Use when the user asks to "build a site like
-  Kraftful", "use the Kraftful design system", or wants a full design
-  system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
-  Kraftful's look and feel. Always builds the design system first, then
-  components, then pages — never random designs. Writes output to
-  `websites/19-kraftful/`.
----
-
-# Kraftful 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 **Kraftful** website (https://www.kraftful.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 Kraftful's friendly product-insights 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 Kraftful actually implements (study before building)
-
-This skill is grounded in the live Kraftful site. Recreate these signature patterns:
-
-- **Announcement bars** lead the page: "🎁 December Deal..." and "Kraftful has been acquired by Amplitude! Read the story".
-- **Hero** uses the exact H1 "Get insights to build products people love" and subhead "Reviews, surveys, calls, support tickets — analyzed in minutes, no hallucinations".
-- **Conversion form** combines Work email → **Start free plan**, divider "or", and **Continue with Google**.
-- **Social proof** shows Netflix, Dropbox, Meta, Google logos plus a five-star badge and "50,000+ product teams analyze feedback".
-- **Integration marquee** includes Zapier, App Store, Google Play, HubSpot, Slack, Google Meet, Trustpilot, G2, Discord/Zendesk, Reddit, Intercom, Salesforce, X/Twitter and more.
-- **Feature sections** cover Feedback, Trends, Projects, Surveys, AI-powered user interviews, Kraftful GPT, customer stories, and blog stories with repeated **Try for free** links.
-- **Signature motifs**: crisp white SaaS layout, blue/purple buttons, green success accents, rounded pill fields, star ratings, and playful product screenshots.
-
-## Design system (Kraftful brand foundation)
-
-> Hex values below are scraped from the live HTML/CSS where available. Values
-> labeled **inferred** are chosen from repeated visible brand motifs when exact
-> CSS tokens were not exposed in the initial scrape.
-
-### Brand foundation
-
-**Colors**
-- primary blue (scraped): `#5077FF`; hover blue `#4C72F5`
-- brand purple (scraped `--new-k-purple`): `#7544FF`; soft primary `#C4C7FA`
-- accent green (scraped `--new-green`): `#1CBD70`; soft green `#B6EEBD`, `#EBF4EB`
-- text / title (scraped `--title`): `#111219`; new black `#1E2027`; gray `#6D707A`
-- warm accent red/coral (scraped): `#FE6155`; yellow accent `#FFEF63`
-- background / surface: `#FFFFFF`, `#F5F5F5`, `#F4FAF4`, `#DEEFFD`
-- success `#1CBD70` · warning `#FFEF63` · error `#FE6155`
-
-**Typography**
-- font_family: primary **Inter** (scraped WebFont.load Google family 300–900); supporting
-  **GeneralSans and Satoshi for brand/display surfaces**; system 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.
-- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
-
-**Iconography**
-- style: integration logos, star ratings, Google sign-in icon, tooltip marker, and small product UI pictograms.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: product feedback screenshots, integration logo marquees, customer portraits, stars, and UI cards.
-- usage_guidelines: make the UI white and crisp; use blue for CTAs, green for positive insight states, purple for brand accents.
-
-### 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,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, integration marquee, product-card reveals, testimonial carousel, and button hover lift.
-
-### 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, sidebar, breadcrumbs. Include Team, Blog, Case Studies links plus Sign up and Login actions.
-- **buttons**: primary, secondary, tertiary, icon-button; match Start free plan, Continue with Google, Try for free, and Login button styles.
-- **forms**: input, textarea, select, checkbox, radio, switch.
-- **feedback**: toast, alert, modal, tooltip plus feedback-volume, hallucination-detection, and roadmap/user-story cards.
-- **content**: cards, tables, lists, accordion, tabs.
-- **marketing**: hero, features, pricing, faq, cta, footer. Add email capture, logo/social proof, integrations marquee, feedback/trends/projects/surveys sections, customer quotes.
-
-### 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 product feedback analysis / product management copilot.)
-
-## 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/19-kraftful/
-├── 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 Kraftful's scraped design tokens.
-
-## Output — write to `websites/19-kraftful/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/19-kraftful/
-├── index.html                 # full Kraftful-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 Kraftful's
-   look (white surfaces, blue CTAs, purple/green accents, rating badges, integration logos).
-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 Kraftful's section order: announcement bars → nav → hero/email capture → customer logos + 50,000+ proof → integration marquee → feedback analysis → trends → projects → surveys → AI interviews → customer stories → blog → CTA/footer.
-- Output written to `websites/19-kraftful/` 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/20-greenhouse/README.md

@@ -1,42 +0,0 @@
-# Greenhouse Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Greenhouse](https://www.greenhouse.com/) website — SaaS / applicant tracking, hiring platform, AI recruiting tools.
-
-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 Greenhouse's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/20-greenhouse/`:
-
-- `index.html` — full Greenhouse-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 Greenhouse patterns it recreates
-
-- Split hero H1: "The only hiring platform you’ll" / "ever need".
-- AI promo: interview notes, candidate answers, MCP, Notetaker, Candidate Question Agent.
-- Social proof: "See who’s hiring with Greenhouse" and "Great companies hire with Greenhouse".
-- Ocado quote: simplified recruitment and cut time-to-hire by nearly 30%.
-- Scraped palette: `#15372C`, `#008561`, `#4CB398`, `#E6FFF8`; Untitled Sans + Untitled Serif.
-
-## How to use
-
-Ask the agent to "build a site using the Greenhouse design system" or "make a
-Greenhouse-style hiring platform 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/20-greenhouse/SKILL.md

@@ -1,273 +0,0 @@
----
-name: 20-greenhouse-designer
-description: >-
-  Greenhouse 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 Greenhouse
-  (https://www.greenhouse.com/): SaaS / applicant tracking, hiring platform, AI recruiting tools. Use when the user asks to "build a site like
-  Greenhouse", "use the Greenhouse design system", or wants a full design
-  system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
-  Greenhouse's look and feel. Always builds the design system first, then
-  components, then pages — never random designs. Writes output to
-  `websites/20-greenhouse/`.
----
-
-# Greenhouse 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 **Greenhouse** website (https://www.greenhouse.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 Greenhouse's enterprise hiring, structured-recruiting 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 Greenhouse actually implements (study before building)
-
-This skill is grounded in the live Greenhouse site. Recreate these signature patterns:
-
-- **Hero headline** is the exact split H1 "The only hiring platform you’ll" / "ever need".
-- **AI promo copy** says "Automatically capture interview notes, get instant answers about your candidates and connect the AI tools you already use directly to Greenhouse."
-- **Navigation** uses a deep green header/drawer with search, product/company/resources links, sign-in handling, and localized variants.
-- **Social proof sections** include "See who’s hiring with Greenhouse" and "Great companies hire with Greenhouse".
-- **Customer quote** from Ocado Group says Greenhouse simplified recruitment and cut time-to-hire by nearly 30%.
-- **Content flow** includes "What’s next for Greenhouse AI", "The best teams start with hiring – and the best hiring starts with Greenhouse", and "Everything you need to get better at hiring".
-- **Signature motifs**: dark greenhouse-green nav, mint/teal accents, editorial serif moments, people + UI clusters, AI capability cards, and smooth load-in animations.
-
-## Design system (Greenhouse brand foundation)
-
-> Hex values below are scraped from the live HTML/CSS where available. Values
-> labeled **inferred** are chosen from repeated visible brand motifs when exact
-> CSS tokens were not exposed in the initial scrape.
-
-### Brand foundation
-
-**Colors**
-- primary dark green (scraped `--green-950`): `#15372C`; deeper `#031C17`, `#133026`
-- primary CTA green (scraped `--green-700`): `#008561`; hover `#006147`, `#006B4A`
-- accent mint/teal (scraped): `#4CB398`, `#73C2B0`, `#ADE1D4`
-- light mint surfaces (scraped): `#E6FFF8`, `#F3FFFB`, `#C9F0E6`
-- secondary blue link/accent (scraped): `#3574D6`, `#0050BD`; warm accent `#FFA52E`
-- neutral: `#FFFFFF`, `#F8F8F8`, `#000000`, `#333333`
-- success `#008561` · warning `#FFA52E` · error `#EF4444`
-
-**Typography**
-- font_family: primary **Untitled Sans** (scraped CSS font-family; Google Inter also loaded); supporting
-  **Untitled Serif / Untitled Serif Italic for editorial quote/headline moments**; system 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.
-- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
-
-**Iconography**
-- style: thin arrows, search/hamburger icons, AI/recruiting product icons, and customer logo marks.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: people-working photos, candidate/workflow UI clusters, AI product cards, customer logos, and quote panels.
-- usage_guidelines: lead with deep green navigation and CTAs; use mint surfaces for product cards and serif type for quotes.
-
-### 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,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, load-in fade/translate, drawer/search transitions, and subtle card reveal motion.
-
-### 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, sidebar, breadcrumbs. Include Greenhouse-style dark green drawer/search header with sign-in and product/resource links.
-- **buttons**: primary, secondary, tertiary, icon-button; match green filled CTAs, white/outline secondary buttons, and arrow text links.
-- **forms**: input, textarea, select, checkbox, radio, switch.
-- **feedback**: toast, alert, modal, tooltip plus candidate notes, AI answer cards, and hiring workflow status panels.
-- **content**: cards, tables, lists, accordion, tabs.
-- **marketing**: hero, features, pricing, faq, cta, footer. Add AI capability promo, hiring-company logo strips, customer quote, product/workflow cards, resources, and demo 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 / applicant tracking, hiring platform, AI recruiting tools.)
-
-## 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/20-greenhouse/
-├── 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 Greenhouse's scraped design tokens.
-
-## Output — write to `websites/20-greenhouse/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/20-greenhouse/
-├── index.html                 # full Greenhouse-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 Greenhouse's
-   look (deep green header, green CTAs, mint accents, serif quotes, people + recruiting UI clusters).
-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 Greenhouse's section order: nav → split H1 hero → AI capability promo → hiring-company proof → Greenhouse AI section → team/hiring value sections → Ocado quote → platform/resources → CTA → footer.
-- Output written to `websites/20-greenhouse/` 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/21-weavy/README.md

@@ -1,42 +0,0 @@
-# Weavy Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Weavy](https://www.weavy.ai/) website — AI creative workflow platform, now Figma Weave.
-
-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 Weavy's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/21-weavy/`:
-
-- `index.html` — full Weavy-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 Weavy patterns it recreates
-
-- `www.weavy.ai` redirects to Figma Weave at `weave.figma.com`; banner says Weavy is now Figma Weave.
-- Hero identity: "Figma Weave", "Artistic Intelligence", "Use all AI models, together at last".
-- Node-based workflow platform with AI models + professional editing tools.
-- GSAP/ScrollTrigger/Draggable, leader-line connectors, Splide sliders, creative workflow motion.
-- Scraped palette: rich black `#252525`, lemon `#F7FF9E`, eggshell `#EAEADA`; Figma Sans Regular + DM Sans.
-
-## How to use
-
-Ask the agent to "build a site using the Weavy design system" or "make a
-Weavy-style AI creative workflow 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.