spirewise 1.7.1 → 1.9.0

package/skills/website-design-skills/15-draftbit/SKILL.md

@@ -1,275 +0,0 @@
----
-name: 15-draftbit-designer
-description: >-
-  Draftbit 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 Draftbit
-  (https://draftbit.com/): Developer tools — AI and visual builder for native mobile and web apps. Use when the user asks to "build a site like Draftbit",
-  "use the Draftbit design system", or wants a full design system (tokens,
-  components, pages) in vanilla HTML/CSS/JS that matches Draftbit's look and
-  feel. Always builds the design system first, then components, then pages —
-  never random designs. Writes output to `websites/15-draftbit/`.
----
-
-# Draftbit 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 **Draftbit** website (https://draftbit.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 Draftbit's live-scraped aesthetic.
-
-## Non-negotiable rules
-
-1. Never create random designs.
-2. Always build a complete design system **before** creating pages.
-3. Always define design tokens.
-4. Always maintain visual consistency.
-5. Always generate semantic HTML.
-6. Always use responsive layouts.
-7. Always follow WCAG accessibility standards.
-8. Always optimize for performance.
-9. Never use inline styles unless absolutely required.
-10. Use CSS variables for all design tokens.
-11. Ensure mobile-first development.
-12. Maintain reusable component architecture.
-13. Avoid duplicate code.
-14. Generate production-ready code only.
-
-## What Draftbit actually implements (study before building)
-
-This skill is grounded in the live Draftbit site. Recreate these signature patterns:
-
-- **Hero headline:** "Start building your app today".
-- **Feature grid in hero:** "Claude Code & OpenAI Codex", "Full visual editing", "Websites or mobile apps", "Source code and GitHub", "100+ integrations", "Experts standing by".
-- **Primary CTAs:** "Start building for free", "Work with experts", nav buttons "Login" and "Get started free".
-- **Social proof:** "4.8 Avg Rating" and "Trusted by 200k+ builders"; later stats show "200k+ Builders", "50k+ Apps created", "4.8 Average customer rating".
-- **Navigation:** Platform, Services, Pricing, Customers; mobile menu repeats those plus auth CTAs and theme toggle.
-- **Design language:** modern Astro/Tailwind UI with translucent floating nav, rounded 4xl panels, gradient border, violet/pink/sky/amber radial hero wash, light/dark mode.
-- **Typography:** locally preloaded DM Sans weights Regular, Medium, SemiBold, Bold.
-
-## Design system (Draftbit brand foundation)
-
-> Hex values and typefaces below are from the live rendered page, raw HTML, and
-> linked/inline CSS inspected during rebuild. Values marked **inferred** were not
-> exposed as named CSS tokens but were selected from visible live-site cues.
-
-### Brand foundation
-
-**Colors**
-- primary violet (scraped inline): `#5A45FF`; secondary violet (scraped): `#8B5CF6`
-- accent pink (scraped): `#EC4899`; sky (scraped): `#38BDF8`; amber (scraped): `#F59E0B`
-- light backgrounds (scraped): `#FCFCFD`, `#F8FAFC`, `#EEF2FF`
-- dark backgrounds (scraped): `#020617`, `#1E293B`
-- card/nav surfaces (inferred from Tailwind classes): `rgba(255,255,255,.70)`, `rgba(255,255,255,.80)`
-- success: `#22C55E` · warning: `#F59E0B` · error: `#EF4444`
-- neutral scale: `#FFFFFF`, `#F7F9FC`, `#E5E9F0`, `#C7CFDB`, `#8A93A6`,
-  `#4B5567`, `#1A2333`, `#0E1726`
-
-**Typography**
-- font_family: primary **"DM Sans"** (local preloaded woff2: Regular, Medium, SemiBold, Bold); 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: Lucide line icons for bot, brush, monitor, git branch, plug, life buoy, star ratings, arrows.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: app-template screenshots, platform screenshots, founder avatar, gradient/radial abstract backdrops.
-- usage_guidelines: use real product UI, customer/logo proof, and brand-specific
-  hero imagery before generic stock.
-
-### Tokens (emit as CSS variables in `:root`)
-
-- **colors**: map every brand color above to `--color-*` tokens, including
-  `--color-primary`, `--color-primary-hover`, `--color-accent`,
-  `--color-background`, `--color-surface`, and `--color-text`.
-- **spacing** (px → tokens): `4,8,12,16,20,24,32,40,48,64,80,96`.
-- **radius**: sm 4, md 8, 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, and Astro island hydration, theme toggle, menu details animation, gradient hover/focus rings.
-
-### 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**: floating translucent navbar, mobile details menu, theme toggle, auth CTAs, sidebar, breadcrumbs.
-- **buttons**: violet primary, translucent outline/secondary, tertiary link, icon-button.
-- **forms**: signup prompts, textarea, select, checkbox, radio, switch.
-- **feedback**: toast, alert, modal, tooltip.
-- **content**: rating badge, news cards, template screenshot rails, stats cards, tables, lists, accordion, tabs.
-- **marketing**: gradient hero, feature grid, whats-new cards, founder letter, app-template gallery, expert services, stats, cta, footer.
-
-### Component requirements
-
-- states: default, hover, focus, active, disabled, loading, error, success.
-- responsive: true · accessible: true · documented: true.
-- Every interactive element has a visible focus ring and an accessible name.
-
-## Page generation workflow (follow in order)
-
-1. Analyze website type.
-2. Identify target audience.
-3. Define design system.
-4. Create color palette.
-5. Create typography scale.
-6. Define spacing system.
-7. Create component inventory.
-8. Build wireframe structure.
-9. Create responsive layout.
-10. Generate HTML structure.
-11. Generate CSS architecture.
-12. Generate JavaScript functionality.
-13. Run accessibility review.
-14. Run performance review.
-15. Run consistency review.
-16. Generate final production code.
-
-## Website types this skill supports
-
-AI Startup · SaaS · Fintech · Crypto · Developer Tools · Ecommerce ·
-Marketplace · Agency · Portfolio · Landing Page · Dashboard · Documentation ·
-Blog · Education · Healthcare. (Default voice: Developer tools — AI and visual builder for native mobile and web apps.)
-
-## 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/15-draftbit/
-├── 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 Draftbit's scraped design tokens.
-
-## Output — write to `websites/15-draftbit/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/15-draftbit/
-├── index.html                 # full Draftbit-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 Draftbit's
-   live look (rounded gradient panels, violet primary, pink/sky/amber accents, DM Sans, light/dark mode support).
-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 Draftbit's section order: floating nav → gradient hero/feature grid → CTA/rating badge → What’s new cards → founder letter → Build Anything gallery → AI/platform sections → Expert Services → stats → footer.
-- Output written to `websites/15-draftbit/` 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/16-payman/README.md

@@ -1,42 +0,0 @@
-# Payman Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Payman](https://paymanai.com/) website — fintech / agentic banking platform for regulated financial institutions.
-
-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 Payman's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/16-payman/`:
-
-- `index.html` — full Payman-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 Payman patterns it recreates
-
-- Cream hero with SOC 2 Certified badge, exact H1 "Agentic AI That Does the Banking. Under Your Control.", and **Schedule Demo** CTA.
-- Resources dropdown, Agentic Banking nav, and featured resource card.
-- Partner-logo marquee: "Backed by the leaders in money movement" with Visa, Coinbase, Circle.
-- Middlesex Federal Savings quote and "Read the announcement" link.
-- Teal `#0A3B44`, cream `#F5F3EB`, yellow `#FFFC4F`, Ubuntu + DM Sans + IBM Plex Mono typography.
-
-## How to use
-
-Ask the agent to "build a site using the Payman design system" or "make a
-Payman-style agentic banking 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/16-payman/SKILL.md

@@ -1,273 +0,0 @@
----
-name: 16-payman-designer
-description: >-
-  Payman 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 Payman
-  (https://paymanai.com/): fintech / agentic banking platform for regulated financial institutions. Use when the user asks to "build a site like
-  Payman", "use the Payman design system", or wants a full design
-  system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
-  Payman's look and feel. Always builds the design system first, then
-  components, then pages — never random designs. Writes output to
-  `websites/16-payman/`.
----
-
-# Payman 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 **Payman** website (https://paymanai.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 Payman's regulated-banking, conversational-AI 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 Payman actually implements (study before building)
-
-This skill is grounded in the live Payman site. Recreate these signature patterns:
-
-- **Regulated banking hero** on cream with a SOC 2 Certified pill, the exact H1 "Agentic AI That Does the Banking. Under Your Control.", subhead "We deploy AI that executes real banking transactions...", and a rounded **Schedule Demo** CTA.
-- **Navigation** includes Home, Agentic Banking, Resources dropdown (Blog, Events, Press, Reports & Guides, AI Banking Safety, Media), About, and a hidden-on-load Schedule Demo CTA.
-- **Partner-logo marquee** states "Backed by the leaders in money movement" and repeats Visa, Coinbase, and Circle logos at low opacity.
-- **Partner quote section** labeled "From Our Partners" quotes Middlesex Federal Savings CEO John Wiseman and links "Read the announcement".
-- **Comparison table section** titled "The AI that does the banking, not just talks about it." with columns Customer Says / Today / With Payman and examples like "Pay my electric bill".
-- **Regulated-trust sections** include "Built for regulated institutions", SOC 2 Certified, GCP or Azure, Compliance Ready, and core-banking connectivity.
-- **Signature motifs**: teal-on-cream palette, yellow highlights, rounded cards, serif quote/headline moments, banking demo imagery, and conversational transaction traces.
-
-## Design system (Payman 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 / text teal (scraped `--teal`): `#0A3B44`, hover `#053139`
-- CTA surface teal (scraped `--teal`): `#0A3B44` with cream text
-- accent yellow (scraped `--yellow`): `#FFFC4F`
-- background / cream (scraped `--cream`): `#F5F3EB`; light blue surface (scraped `--light-blue`): `#EBF4F5`
-- ink / primary neutral (scraped): `#171717`, `#0A0A0A`, `#262626`
-- muted text (scraped): `#737373`, `#A1A1A1`
-- success `#22C55E` · warning `#F59E0B` · error (scraped red utility): `#FB2C36`
-
-**Typography**
-- font_family: primary **Ubuntu** (scraped @font-face, weights 400/500/700); supporting
-  **DM Sans for UI/body and IBM Plex Mono for technical labels**; 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, 700.
-- line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
-
-**Iconography**
-- style: simple SVG line icons, arrow-right CTAs, chevrons, checkmarks, and banking-status glyphs.
-- sizes: 16, 20, 24, 32, 48.
-
-**Imagery**
-- style_rules: banking AI demo imagery, partner logos, transaction tables, trust badges, and quote cards.
-- usage_guidelines: pair cream surfaces with teal text/CTAs; use yellow sparingly for “with Payman” wins and compliance confirmations.
-
-### 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, marquee logo motion and subtle table/card 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 a Resources dropdown with a featured event card, like Payman.
-- **buttons**: primary, secondary, tertiary, icon-button; match rounded-full teal CTAs with arrow icons and cream text.
-- **forms**: input, textarea, select, checkbox, radio, switch.
-- **feedback**: toast, alert, modal, tooltip plus transaction trace / approval-state cards.
-- **content**: cards, tables, lists, accordion, tabs.
-- **marketing**: hero, features, pricing, faq, cta, footer. Add partner-logo marquee, Middlesex quote, comparison table, regulated-trust proof, and bottom 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: fintech / agentic banking platform for regulated financial institutions.)
-
-## 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/16-payman/
-├── 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 Payman's scraped design tokens.
-
-## Output — write to `websites/16-payman/`
-
-Create the folder if missing and produce all deliverables:
-
-```
-websites/16-payman/
-├── index.html                 # full Payman-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 Payman's
-   look (cream surfaces, teal CTAs/text, yellow confirmation highlights, rounded regulated-fintech cards).
-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 Payman's section order: nav → hero → money-movement logo marquee → partner quote → comparison table → intent-data/features → regulated-trust → core integration → FAQ → CTA → footer.
-- Output written to `websites/16-payman/` 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/17-effortel/README.md

@@ -1,42 +0,0 @@
-# Effortel Designer
-
-A **Website Design System Architect** skill modeled on the live
-[Effortel](https://www.effortel.com/) website — telecom SaaS / MVNE, BSS/OSS, eSIM and IoT enablement 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 Effortel's look and feel.
-
-## What it produces
-
-Writes a complete, token-driven site to `websites/17-effortel/`:
-
-- `index.html` — full Effortel-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 Effortel patterns it recreates
-
-- Dark animated hero with exact H1 "Streamline Operations, Skyrocket Revenue, and Delight Customers".
-- Floating nav modules for Products, solutions, resources, and services with plus/arrow controls.
-- BSS/OSS, MVNO launch, eSIM, IoT and event-management product storytelling.
-- Recognition section: "Recognized for Excellence in BSS/OSS and MVNE Solutions".
-- Scraped palette: `#22282A`, `#394247`, cyan `#66E8FA`/`#68D4E3`; Satoshi Variable + Et Mono.
-
-## How to use
-
-Ask the agent to "build a site using the Effortel design system" or "make a
-Effortel-style telecom SaaS 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.