spirewise 1.7.1 → 1.8.0

package/skills/website-design-skills/17-effortel/SKILL.md

@@ -1,272 +0,0 @@
----
-name: 17-effortel-designer
-description: >-
-  Effortel 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 Effortel
-  (https://www.effortel.com/): telecom SaaS / MVNE, BSS/OSS, eSIM and IoT enablement platform. Use when the user asks to "build a site like
-  Effortel", "use the Effortel design system", or wants a full design
-  system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
-  Effortel's look and feel. Always builds the design system first, then
-  components, then pages — never random designs. Writes output to
-  `websites/17-effortel/`.
----
-
-# Effortel 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 **Effortel** website (https://www.effortel.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 Effortel's premium telecom, operational-growth 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 Effortel actually implements (study before building)
-
-This skill is grounded in the live Effortel site. Recreate these signature patterns:
-
-- **Animated telecom hero** with dark color mode, the exact H1 "Streamline Operations, Skyrocket Revenue, and Delight Customers", and a **Get in touch** CTA.
-- **Navigation** uses lowercase module buttons Products, solutions, resources, services, plus a floating module overlay and animated plus icons.
-- **Section order** moves from hero into product modules, "Unparalleled BSS/OSS Capabilities", "Intuitive Interface and Effortless Self-Management", MVNO launch narrative, recognition, and CTA.
-- **Telecom product language** emphasizes MVNO launchpad, eSIM and IoT enablement, event management, BSS/OSS capabilities, revenue growth, and customer delight.
-- **Design motion** uses GSAP/Lenis, staggered fade-ins, split-word text reveals, clip-in cards, and floating nav modules.
-- **Recognition/social proof** includes "Recognized for Excellence in BSS/OSS and MVNE Solutions" before the conversion CTA "Ready to transform your MVNO?".
-- **Signature visuals**: dark graphite interface, electric cyan accents, pill/arrow buttons, product-dashboard cards, and technical mono/type system.
-
-## Design system (Effortel 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 background (scraped `--swatch--n-800`): `#22282A`; secondary dark (scraped `--swatch--n-700`): `#394247`
-- CTA / accent cyan (scraped `--swatch--a-400`): `#66E8FA`, bright `#9CF0FC`, base `#68D4E3`
-- muted steel (scraped theme color / `--swatch--n-500`): `#92A6B0`; text light `#D5E1E7`
-- deep ink (scraped `--swatch--n-900`): `#171818`; faded panel `#3B4144`
-- support green (scraped): `#B8FD83`, `#A3D190`; purple accent `#C38BFB`
-- success `#22C55E` · warning `#F7B430` (scraped) · error `#D23356` (scraped)
-
-**Typography**
-- font_family: primary **Satoshi Variable** (scraped CSS font-family); supporting
-  **Et Mono / technical mono and Eeeeeet display accent**; 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: 400, 500, 600, 700.
-- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
-
-**Iconography**
-- style: minimal telecom line icons, plus signs in navigation, arrow buttons, and product-module pictograms.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: telecom product screens, MVNO/BSS module cards, recognitions/awards, and dark floating UI modules.
-- usage_guidelines: keep the base dark and premium; use cyan accents for interactive edges, arrows, and active states.
-
-### 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, GSAP stagger, split-word reveal, clip-in cards, Lenis smooth-scroll, and floating module transitions.
-
-### 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 Products / solutions / resources module overlays and a services link.
-- **buttons**: primary, secondary, tertiary, icon-button; match dark/transparent nav buttons, cyan-accent arrows, and Get in touch CTAs.
-- **forms**: input, textarea, select, checkbox, radio, switch.
-- **feedback**: toast, alert, modal, tooltip plus floating module panels and telecom status cards.
-- **content**: cards, tables, lists, accordion, tabs.
-- **marketing**: hero, features, pricing, faq, cta, footer. Add BSS/OSS capability grids, MVNO launch narrative, recognition strip, and Get in touch 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: telecom SaaS / MVNE, BSS/OSS, eSIM and IoT enablement 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/17-effortel/
-├── 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 Effortel's scraped design tokens.
-
-## Output — write to `websites/17-effortel/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/17-effortel/
-├── index.html                 # full Effortel-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 Effortel's
-   look (dark graphite surfaces, steel text, cyan accent, technical motion, MVNE product modules).
-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 Effortel's section order: nav → animated hero → product / solution modules → BSS/OSS capabilities → self-management → MVNO launch → awards/recognition → CTA → footer.
-- Output written to `websites/17-effortel/` 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/18-adopt/README.md

@@ -1,42 +0,0 @@
-# Adopt Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Adopt](https://www.adopt.ai/) website — AI startup / autonomous operations agents for business processes.
-
-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 Adopt's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/18-adopt/`:
-
-- `index.html` — full Adopt-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 Adopt patterns it recreates
-
-- Stacked hero: "Stop Manual Work." / "Start Running" / "Autonomous Operations." with **Request Demo**.
-- Dropdown-heavy nav for Solutions, Product, Resources, About Us.
-- "Powering AI agents across industries" logo strip and product modules for Agent Ready Tooling, Agent Builder, Agentic Automation.
-- Bright scraped palette: blue `#0364FF`, yellow `#FFD422`, pale `#AFE6ED`, orange `#FF5000`, black `#080808`.
-- Satoshi + OpenSauceSans / Trap typography and colorful Lottie/block motifs.
-
-## How to use
-
-Ask the agent to "build a site using the Adopt design system" or "make a
-Adopt-style autonomous operations 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/18-adopt/SKILL.md

@@ -1,273 +0,0 @@
----
-name: 18-adopt-designer
-description: >-
-  Adopt 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 Adopt
-  (https://www.adopt.ai/): AI startup / autonomous operations agents for business processes. Use when the user asks to "build a site like
-  Adopt", "use the Adopt design system", or wants a full design
-  system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
-  Adopt's look and feel. Always builds the design system first, then
-  components, then pages — never random designs. Writes output to
-  `websites/18-adopt/`.
----
-
-# Adopt 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 **Adopt** website (https://www.adopt.ai/).
-
-**Primary goal:** Ensure every generated website follows a scalable design
-system, accessibility standards, responsive principles, clean architecture, and
-modern UI/UX best practices — recreating Adopt's bright agentic-operations 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 Adopt actually implements (study before building)
-
-This skill is grounded in the live Adopt site. Recreate these signature patterns:
-
-- **Hero headline** is split into stacked lines: "Stop Manual Work." / "Start Running" / "Autonomous Operations." with a **Request Demo** CTA.
-- **Subhead** promises agents that run existing software stacks — modern SaaS, legacy apps, and internal tools — 24/7 on the customer infrastructure.
-- **Navigation** includes Solutions, Product, Resources dropdowns, About Us, and Request Demo; dropdowns list industry, use-case, product, blog, events, and security links.
-- **Customer-logo section** states "Powering AI agents across industries" with Automation Anywhere, PriceLabs, Centuri, doola, RallyUp and more.
-- **Product taxonomy** includes Platform Overview, Agent Ready Tooling, Agent Builder, Agentic Automation, 500+ MCP connectors, and no-code agent building.
-- **Outcome proof** includes the scraped H1 "Impact that speaks volumes" and the section "Why winning operations teams start their Agentic AI journey with Adopt AI".
-- **Signature motifs**: bold black type, electric blue CTAs, pale cyan blocks, yellow/orange/pink color chips, Webflow/Lottie hero animation, and rounded dropdown cards.
-
-## Design system (Adopt 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 `--primary-blue`): `#0364FF`
-- accent yellow (scraped `--yellow`): `#FFD422`; orange (scraped `--flame-orange`): `#FF5000`
-- pale cyan (scraped `--pale`): `#AFE6ED`; soft background `#F2FBFC`
-- black / text (scraped `--black`): `#080808`; pure black `#000000`
-- lavender / pink accent (scraped): `#FFB1FC` / `#FFB1F2`; soft lavender `#F4D4F2`
-- neutral: `#FFFFFF`, `#D4E8F4`, `#777777`, `#111111`
-- success `#22C55E` · warning `#FFD422` · error `#EF4444`
-
-**Typography**
-- font_family: primary **Satoshi** (scraped CSS font-family); supporting
-  **OpenSauceSans, Trap, and Ehsmb display/support families**; 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: 400, 500, 600, 700, 800.
-- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
-
-**Iconography**
-- style: colorful small image tiles, dropdown icons, no-code/connector pictograms, and simple arrow CTAs.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: Lottie automation hero, product screenshots, connector cards, industry tiles, and customer logos.
-- usage_guidelines: use bright blue for primary CTAs, black for strong headings, and pale cyan/yellow/orange as modular blocks.
-
-### 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, Lottie hero animation, dropdown transitions, colorful block movement, and fade-up content 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, sidebar, breadcrumbs. Include Solutions/Product/Resources mega-dropdowns with industry and use-case cards.
-- **buttons**: primary, secondary, tertiary, icon-button; match electric-blue Request Demo CTAs with pill/card treatment.
-- **forms**: input, textarea, select, checkbox, radio, switch.
-- **feedback**: toast, alert, modal, tooltip plus agent-run status, approval, and exception-review cards.
-- **content**: cards, tables, lists, accordion, tabs.
-- **marketing**: hero, features, pricing, faq, cta, footer. Add customer-logo strip, product taxonomy, use-case cards, impact metrics, and Request 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: AI startup / autonomous operations agents for business processes.)
-
-## 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/18-adopt/
-├── 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 Adopt's scraped design tokens.
-
-## Output — write to `websites/18-adopt/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/18-adopt/
-├── index.html                 # full Adopt-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 Adopt's
-   look (black display type, blue CTAs, pale cyan surfaces, yellow/orange/pink block motifs, Lottie motion).
-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 Adopt's section order: nav → stacked hero → customer-logo strip → platform/product modules → use-case/industry sections → impact proof → FAQ/resources → demo CTA → footer.
-- Output written to `websites/18-adopt/` 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/19-kraftful/README.md

@@ -1,42 +0,0 @@
-# Kraftful Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Kraftful](https://www.kraftful.com/) website — AI product feedback analysis / product management copilot.
-
-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 Kraftful's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/19-kraftful/`:
-
-- `index.html` — full Kraftful-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 Kraftful patterns it recreates
-
-- Hero H1 "Get insights to build products people love" with Work email → **Start free plan** and Continue with Google.
-- Social proof: Netflix, Dropbox, Meta, Google, five-star badge, "50,000+ product teams analyze feedback".
-- Integration marquee across Zapier, App Store, Google Play, HubSpot, Slack, Trustpilot, G2, Reddit, Salesforce, and more.
-- Product sections for Feedback, Trends, Projects, Surveys, AI-powered user interviews, Kraftful GPT.
-- Scraped tokens: Inter, blue `#5077FF`, purple `#7544FF`, green `#1CBD70`, title `#111219`.
-
-## How to use
-
-Ask the agent to "build a site using the Kraftful design system" or "make a
-Kraftful-style product feedback 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.