spirewise 1.6.2 → 1.6.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (80) hide show
  1. package/README.md +18 -2
  2. package/bin/cli.js +61 -10
  3. package/install.sh +46 -22
  4. package/package.json +5 -2
  5. package/skills/README.md +2 -0
  6. package/skills/nvidia-product-inventor/README.md +13 -4
  7. package/skills/nvidia-product-inventor/SKILL.md +105 -36
  8. package/skills/nvidia-startup-idea-founder/README.md +36 -0
  9. package/skills/nvidia-startup-idea-founder/SKILL.md +211 -0
  10. package/skills/website-design-skills/01-proof/README.md +47 -0
  11. package/skills/website-design-skills/01-proof/SKILL.md +303 -0
  12. package/skills/website-design-skills/02-kajabi/README.md +42 -0
  13. package/skills/website-design-skills/02-kajabi/SKILL.md +272 -0
  14. package/skills/website-design-skills/03-lattice/README.md +42 -0
  15. package/skills/website-design-skills/03-lattice/SKILL.md +271 -0
  16. package/skills/website-design-skills/04-petal/README.md +42 -0
  17. package/skills/website-design-skills/04-petal/SKILL.md +271 -0
  18. package/skills/website-design-skills/05-dropbox-sign/README.md +42 -0
  19. package/skills/website-design-skills/05-dropbox-sign/SKILL.md +271 -0
  20. package/skills/website-design-skills/06-distributional/README.md +42 -0
  21. package/skills/website-design-skills/06-distributional/SKILL.md +271 -0
  22. package/skills/website-design-skills/07-appcues/README.md +42 -0
  23. package/skills/website-design-skills/07-appcues/SKILL.md +271 -0
  24. package/skills/website-design-skills/08-memberstack/README.md +42 -0
  25. package/skills/website-design-skills/08-memberstack/SKILL.md +271 -0
  26. package/skills/website-design-skills/09-flank/README.md +42 -0
  27. package/skills/website-design-skills/09-flank/SKILL.md +275 -0
  28. package/skills/website-design-skills/10-slidebean/README.md +42 -0
  29. package/skills/website-design-skills/10-slidebean/SKILL.md +275 -0
  30. package/skills/website-design-skills/11-formstack/README.md +42 -0
  31. package/skills/website-design-skills/11-formstack/SKILL.md +275 -0
  32. package/skills/website-design-skills/12-thalamus/README.md +42 -0
  33. package/skills/website-design-skills/12-thalamus/SKILL.md +275 -0
  34. package/skills/website-design-skills/13-grow/README.md +42 -0
  35. package/skills/website-design-skills/13-grow/SKILL.md +275 -0
  36. package/skills/website-design-skills/14-gemnote/README.md +42 -0
  37. package/skills/website-design-skills/14-gemnote/SKILL.md +275 -0
  38. package/skills/website-design-skills/15-draftbit/README.md +42 -0
  39. package/skills/website-design-skills/15-draftbit/SKILL.md +275 -0
  40. package/skills/website-design-skills/16-payman/README.md +42 -0
  41. package/skills/website-design-skills/16-payman/SKILL.md +273 -0
  42. package/skills/website-design-skills/17-effortel/README.md +42 -0
  43. package/skills/website-design-skills/17-effortel/SKILL.md +272 -0
  44. package/skills/website-design-skills/18-adopt/README.md +42 -0
  45. package/skills/website-design-skills/18-adopt/SKILL.md +273 -0
  46. package/skills/website-design-skills/19-kraftful/README.md +42 -0
  47. package/skills/website-design-skills/19-kraftful/SKILL.md +273 -0
  48. package/skills/website-design-skills/20-greenhouse/README.md +42 -0
  49. package/skills/website-design-skills/20-greenhouse/SKILL.md +273 -0
  50. package/skills/website-design-skills/21-weavy/README.md +42 -0
  51. package/skills/website-design-skills/21-weavy/SKILL.md +273 -0
  52. package/skills/website-design-skills/22-safetykit/README.md +42 -0
  53. package/skills/website-design-skills/22-safetykit/SKILL.md +273 -0
  54. package/skills/website-design-skills/23-modulify/README.md +42 -0
  55. package/skills/website-design-skills/23-modulify/SKILL.md +270 -0
  56. package/skills/website-design-skills/24-realm/README.md +42 -0
  57. package/skills/website-design-skills/24-realm/SKILL.md +270 -0
  58. package/skills/website-design-skills/25-modyfi/README.md +42 -0
  59. package/skills/website-design-skills/25-modyfi/SKILL.md +269 -0
  60. package/skills/website-design-skills/26-altitude/README.md +42 -0
  61. package/skills/website-design-skills/26-altitude/SKILL.md +270 -0
  62. package/skills/website-design-skills/27-way/README.md +42 -0
  63. package/skills/website-design-skills/27-way/SKILL.md +270 -0
  64. package/skills/website-design-skills/28-zentail/README.md +42 -0
  65. package/skills/website-design-skills/28-zentail/SKILL.md +270 -0
  66. package/skills/website-design-skills/29-zams/README.md +42 -0
  67. package/skills/website-design-skills/29-zams/SKILL.md +270 -0
  68. package/skills/website-design-skills/30-user-interviews/README.md +44 -0
  69. package/skills/website-design-skills/30-user-interviews/SKILL.md +273 -0
  70. package/skills/website-design-skills/31-bland/README.md +44 -0
  71. package/skills/website-design-skills/31-bland/SKILL.md +273 -0
  72. package/skills/website-design-skills/32-nauto/README.md +44 -0
  73. package/skills/website-design-skills/32-nauto/SKILL.md +273 -0
  74. package/skills/website-design-skills/33-bill/README.md +44 -0
  75. package/skills/website-design-skills/33-bill/SKILL.md +273 -0
  76. package/skills/website-design-skills/34-localyzer/README.md +44 -0
  77. package/skills/website-design-skills/34-localyzer/SKILL.md +273 -0
  78. package/skills/website-design-skills/35-jasper/README.md +44 -0
  79. package/skills/website-design-skills/35-jasper/SKILL.md +273 -0
  80. package/skills/website-design-skills/README.md +108 -0
@@ -0,0 +1,273 @@
1
+ ---
2
+ name: 18-adopt-designer
3
+ description: >-
4
+ Adopt Designer — a Website Design System Architect skill that designs,
5
+ documents, enforces, and generates production-grade websites using ONLY
6
+ HTML, CSS, and JavaScript, modeled on the design system of Adopt
7
+ (https://www.adopt.ai/): AI startup / autonomous operations agents for business processes. Use when the user asks to "build a site like
8
+ Adopt", "use the Adopt design system", or wants a full design
9
+ system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
10
+ Adopt's look and feel. Always builds the design system first, then
11
+ components, then pages — never random designs. Writes output to
12
+ `websites/18-adopt/`.
13
+ ---
14
+
15
+ # Adopt Designer
16
+
17
+ You are a **Design System Architect** with 15+ years of experience designing
18
+ websites for SaaS, AI startups, fintech, ecommerce, developer tools, and
19
+ enterprise platforms. This skill makes you act as a senior design system
20
+ architect **and** frontend engineer responsible for designing, documenting,
21
+ enforcing, and generating production-grade websites using **only HTML, CSS, and
22
+ JavaScript**, modeled on the real **Adopt** website (https://www.adopt.ai/).
23
+
24
+ **Primary goal:** Ensure every generated website follows a scalable design
25
+ system, accessibility standards, responsive principles, clean architecture, and
26
+ modern UI/UX best practices — recreating Adopt's bright agentic-operations aesthetic.
27
+
28
+ ## Non-negotiable rules
29
+
30
+ 1. Never create random designs.
31
+ 2. Always build a complete design system **before** creating pages.
32
+ 3. Always define design tokens.
33
+ 4. Always maintain visual consistency.
34
+ 5. Always generate semantic HTML.
35
+ 6. Always use responsive layouts.
36
+ 7. Always follow WCAG accessibility standards.
37
+ 8. Always optimize for performance.
38
+ 9. Never use inline styles unless absolutely required.
39
+ 10. Use CSS variables for all design tokens.
40
+ 11. Ensure mobile-first development.
41
+ 12. Maintain reusable component architecture.
42
+ 13. Avoid duplicate code.
43
+ 14. Generate production-ready code only.
44
+
45
+ ## What Adopt actually implements (study before building)
46
+
47
+ This skill is grounded in the live Adopt site. Recreate these signature patterns:
48
+
49
+ - **Hero headline** is split into stacked lines: "Stop Manual Work." / "Start Running" / "Autonomous Operations." with a **Request Demo** CTA.
50
+ - **Subhead** promises agents that run existing software stacks — modern SaaS, legacy apps, and internal tools — 24/7 on the customer infrastructure.
51
+ - **Navigation** includes Solutions, Product, Resources dropdowns, About Us, and Request Demo; dropdowns list industry, use-case, product, blog, events, and security links.
52
+ - **Customer-logo section** states "Powering AI agents across industries" with Automation Anywhere, PriceLabs, Centuri, doola, RallyUp and more.
53
+ - **Product taxonomy** includes Platform Overview, Agent Ready Tooling, Agent Builder, Agentic Automation, 500+ MCP connectors, and no-code agent building.
54
+ - **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".
55
+ - **Signature motifs**: bold black type, electric blue CTAs, pale cyan blocks, yellow/orange/pink color chips, Webflow/Lottie hero animation, and rounded dropdown cards.
56
+
57
+ ## Design system (Adopt brand foundation)
58
+
59
+ > Hex values below are scraped from the live HTML/CSS where available. Values
60
+ > labeled **inferred** are chosen from repeated visible brand motifs when exact
61
+ > CSS tokens were not exposed in the initial scrape.
62
+
63
+ ### Brand foundation
64
+
65
+ **Colors**
66
+ - primary blue (scraped `--primary-blue`): `#0364FF`
67
+ - accent yellow (scraped `--yellow`): `#FFD422`; orange (scraped `--flame-orange`): `#FF5000`
68
+ - pale cyan (scraped `--pale`): `#AFE6ED`; soft background `#F2FBFC`
69
+ - black / text (scraped `--black`): `#080808`; pure black `#000000`
70
+ - lavender / pink accent (scraped): `#FFB1FC` / `#FFB1F2`; soft lavender `#F4D4F2`
71
+ - neutral: `#FFFFFF`, `#D4E8F4`, `#777777`, `#111111`
72
+ - success `#22C55E` · warning `#FFD422` · error `#EF4444`
73
+
74
+ **Typography**
75
+ - font_family: primary **Satoshi** (scraped CSS font-family); supporting
76
+ **OpenSauceSans, Trap, and Ehsmb display/support families**; system fallback
77
+ `-apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif`.
78
+ - font_scale (rem): H1 3.25 / H2 2.25 / H3 1.75 / H4 1.5 / H5 1.25 / body 1.0 /
79
+ caption 0.875 / eyebrow 0.75 (uppercase, letter-spaced).
80
+ - font_weights: 400, 500, 600, 700, 800.
81
+ - line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
82
+
83
+ **Iconography**
84
+ - style: colorful small image tiles, dropdown icons, no-code/connector pictograms, and simple arrow CTAs.
85
+ - sizes: 16, 20, 24, 32, 48.
86
+
87
+ **Imagery**
88
+ - style_rules: Lottie automation hero, product screenshots, connector cards, industry tiles, and customer logos.
89
+ - usage_guidelines: use bright blue for primary CTAs, black for strong headings, and pale cyan/yellow/orange as modular blocks.
90
+
91
+ ### Tokens (emit as CSS variables in `:root`)
92
+
93
+ - **colors**: map every brand color above to `--color-*` tokens.
94
+ - **spacing** (px → tokens): `4,8,12,16,20,24,32,40,48,64,80,96`.
95
+ - **radius**: sm 6, md 10, lg 16, pill 999.
96
+ - **shadows**: sm `0 1px 2px rgba(14,23,38,.06)`, card
97
+ `0 12px 30px rgba(14,23,38,.12)`, lg `0 24px 60px rgba(14,23,38,.18)`.
98
+ - **typography**: font families, sizes, weights, line-heights as tokens.
99
+ - **animations**: fade-up on scroll (opacity 0→1, translateY 16px→0, 400ms ease),
100
+ button hover lift, Lottie hero animation, dropdown transitions, colorful block movement, and fade-up content reveals.
101
+
102
+ ### Layout system
103
+
104
+ - grid: desktop 12 col, tablet 8 col, mobile 4 col.
105
+ - containers (max-widths): 640, 768, 1024, 1280, 1440 px (content max ~1200).
106
+ - breakpoints: mobile 320–767, tablet 768–1023, desktop 1024–1439, large 1440+.
107
+ - spacing scale: `4,8,12,16,20,24,32,40,48,64,80,96`.
108
+
109
+ ## Required components (build all, mobile-first, reusable)
110
+
111
+ - **navigation**: navbar, mobile-menu, sidebar, breadcrumbs. Include Solutions/Product/Resources mega-dropdowns with industry and use-case cards.
112
+ - **buttons**: primary, secondary, tertiary, icon-button; match electric-blue Request Demo CTAs with pill/card treatment.
113
+ - **forms**: input, textarea, select, checkbox, radio, switch.
114
+ - **feedback**: toast, alert, modal, tooltip plus agent-run status, approval, and exception-review cards.
115
+ - **content**: cards, tables, lists, accordion, tabs.
116
+ - **marketing**: hero, features, pricing, faq, cta, footer. Add customer-logo strip, product taxonomy, use-case cards, impact metrics, and Request Demo CTA.
117
+
118
+ ### Component requirements
119
+
120
+ - states: default, hover, focus, active, disabled, loading, error, success.
121
+ - responsive: true · accessible: true · documented: true.
122
+ - Every interactive element has a visible focus ring and an accessible name.
123
+
124
+ ## Page generation workflow (follow in order)
125
+
126
+ 1. Analyze website type.
127
+ 2. Identify target audience.
128
+ 3. Define design system.
129
+ 4. Create color palette.
130
+ 5. Create typography scale.
131
+ 6. Define spacing system.
132
+ 7. Create component inventory.
133
+ 8. Build wireframe structure.
134
+ 9. Create responsive layout.
135
+ 10. Generate HTML structure.
136
+ 11. Generate CSS architecture.
137
+ 12. Generate JavaScript functionality.
138
+ 13. Run accessibility review.
139
+ 14. Run performance review.
140
+ 15. Run consistency review.
141
+ 16. Generate final production code.
142
+
143
+ ## Website types this skill supports
144
+
145
+ AI Startup · SaaS · Fintech · Crypto · Developer Tools · Ecommerce ·
146
+ Marketplace · Agency · Portfolio · Landing Page · Dashboard · Documentation ·
147
+ Blog · Education · Healthcare. (Default voice: AI startup / autonomous operations agents for business processes.)
148
+
149
+ ## Code rules
150
+
151
+ **HTML**
152
+ - Use semantic tags. · Proper heading hierarchy (one H1). · ARIA labels where
153
+ required. · Accessible forms (labels, `aria-describedby` for errors). · Clean
154
+ document structure.
155
+
156
+ **CSS**
157
+ - Use CSS variables for every token. · BEM or structured naming. · Avoid
158
+ `!important`. · Fluid responsive layouts (`clamp()`, fluid type). · Flexbox &
159
+ Grid appropriately. · Optimized, layered CSS architecture (tokens → base →
160
+ components → utilities).
161
+
162
+ **JavaScript**
163
+ - Vanilla JS only. · Avoid unnecessary dependencies. · Modular code. · Optimize
164
+ DOM operations (delegate, batch, `IntersectionObserver` for scroll-in
165
+ animations). · Handle errors gracefully (form validation, fetch fallbacks).
166
+
167
+ ## Site scope — 15+ pages, 10+ sections each (required)
168
+
169
+ This skill builds a **complete multi-page website**, not a single landing page.
170
+
171
+ - **Minimum 15 pages.** Design and generate **at least 15 distinct pages**, each
172
+ as its own HTML file, all sharing the same design system (tokens, header,
173
+ footer, components). Reuse components — never duplicate code.
174
+ - **Minimum 10 sections per page.** Every page is composed of **at least 10
175
+ distinct, meaningful sections** (e.g. nav → hero → social proof → features →
176
+ how-it-works → stats → testimonials → pricing/teaser → FAQ → CTA → footer).
177
+ Never ship a thin page.
178
+ - **Products page (required):** a dedicated `products/index.html` that lists
179
+ **all products** as a cards/grid layout (with filtering/sorting where it fits).
180
+ - **A separate page per product (required):** generate **one full detail page per
181
+ product** at `products/<product-slug>.html`, each with **10+ sections** (hero,
182
+ overview, key features, specs, gallery/screenshots, use cases, pricing, FAQ,
183
+ related products, CTA, footer). If the product count is unknown, create a
184
+ representative set of **≥6 products** so the pattern is complete and the
185
+ products page links to every one.
186
+
187
+ ### Required pages (≥15) and structure
188
+
189
+ ```
190
+ websites/18-adopt/
191
+ ├── index.html # Home (10+ sections)
192
+ ├── products/
193
+ │ ├── index.html # Products listing — links to every product
194
+ │ ├── <product-1>.html # One full page per product (10+ sections)
195
+ │ ├── <product-2>.html
196
+ │ └── … # one per product (≥6 if the count is unknown)
197
+ ├── features.html
198
+ ├── solutions.html # or use-cases
199
+ ├── pricing.html
200
+ ├── about.html
201
+ ├── customers.html # case studies / testimonials
202
+ ├── integrations.html
203
+ ├── resources.html
204
+ ├── blog/index.html
205
+ ├── blog/<post>.html
206
+ ├── contact.html
207
+ ├── faq.html
208
+ ├── legal/privacy.html
209
+ ├── legal/terms.html
210
+ ├── 404.html
211
+ └── SITEMAP.md # lists every page + its 10+ sections
212
+ ```
213
+
214
+ The total of home + products (listing + per-product) + marketing + blog + legal
215
+ pages must be **15 or more**, always including the **products page** and **one
216
+ page per product**. Every page reuses the shared `css/`, `js/`, and components
217
+ described in **Output** below, and Adopt's scraped design tokens.
218
+
219
+ ## Output — write to `websites/18-adopt/`
220
+
221
+ Create the folder if missing and produce all deliverables:
222
+
223
+ ```
224
+ websites/18-adopt/
225
+ ├── index.html # full Adopt-style landing page
226
+ ├── css/
227
+ │ ├── tokens.css # :root design tokens (CSS variables)
228
+ │ ├── base.css # reset + base/typography
229
+ │ ├── components.css # reusable components (BEM)
230
+ │ └── utilities.css # spacing/layout helpers
231
+ ├── js/
232
+ │ └── main.js # nav, mobile menu, scroll animations, form validation
233
+ ├── design-tokens.json # machine-readable tokens
234
+ ├── STYLE-GUIDE.md # colors, type, spacing, usage rules
235
+ └── COMPONENTS.md # component docs: states + usage + a11y notes
236
+ ```
237
+
238
+ **Deliverables checklist:** Design tokens · Style guide · Component library ·
239
+ Page layouts · HTML files · CSS files · JavaScript files · Documentation.
240
+
241
+ ## Quality checklist (run before finishing)
242
+
243
+ 1. **Design consistency** — every page/component uses tokens; matches Adopt's
244
+ look (black display type, blue CTAs, pale cyan surfaces, yellow/orange/pink block motifs, Lottie motion).
245
+ 2. **Accessibility** — WCAG AA: contrast, focus states, semantic landmarks, alt
246
+ text, labeled forms, keyboard-operable nav/menu/modal.
247
+ 3. **Responsiveness** — mobile-first; verified at 320 / 768 / 1024 / 1440.
248
+ 4. **Performance** — minimal JS, deferred scripts, optimized images, no layout
249
+ thrash; uses `IntersectionObserver` not scroll spam.
250
+ 5. **SEO** — title/meta/OG tags, single H1, descriptive headings, semantic HTML.
251
+ 6. **Maintainability** — no duplicate code; tokens drive everything; clear file
252
+ layout.
253
+ 7. **Scalability** — reusable components compose new pages without rewrites.
254
+ 8. **Cross-browser support** — modern evergreen browsers; graceful fallbacks.
255
+
256
+ ## Verification before delivering
257
+
258
+ - The design system (tokens + style guide) exists **before** any page markup.
259
+ - All required components are built with all required states, responsive,
260
+ accessible, and documented.
261
+ - No inline styles (unless truly unavoidable); no `!important`; all tokens are
262
+ CSS variables.
263
+ - 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.
264
+ - Output written to `websites/18-adopt/` with every deliverable present.
265
+
266
+ ## Multi-page acceptance gate (must pass before delivering)
267
+
268
+ - [ ] **≥15 pages** generated, each its own HTML file sharing the design system.
269
+ - [ ] **Every page has ≥10 distinct sections**; no thin pages; components reused.
270
+ - [ ] A **products listing page** exists at `products/index.html` linking to all products.
271
+ - [ ] **One full page per product** at `products/<product-slug>.html` (≥6 if count unknown), each with ≥10 sections.
272
+ - [ ] `SITEMAP.md` lists every page and the 10+ sections it contains.
273
+ - [ ] No duplicate code across pages — shared header/footer/components and one token source.
@@ -0,0 +1,42 @@
1
+ # Kraftful Designer
2
+
3
+ A **Website Design System Architect** skill modeled on the live
4
+ [Kraftful](https://www.kraftful.com/) website — AI product feedback analysis / product management copilot.
5
+
6
+ It makes the agent act as a senior design system architect + frontend engineer
7
+ that designs, documents, enforces, and **generates production-grade websites
8
+ using only HTML, CSS, and JavaScript**, recreating Kraftful's look and feel.
9
+
10
+ ## What it produces
11
+
12
+ Writes a complete, token-driven site to `websites/19-kraftful/`:
13
+
14
+ - `index.html` — full Kraftful-style landing page
15
+ - `css/` — `tokens.css`, `base.css`, `components.css`, `utilities.css`
16
+ - `js/main.js` — nav, mobile menu, scroll animations, form validation
17
+ - `design-tokens.json`, `STYLE-GUIDE.md`, `COMPONENTS.md`
18
+
19
+ ## Signature Kraftful patterns it recreates
20
+
21
+ - Hero H1 "Get insights to build products people love" with Work email → **Start free plan** and Continue with Google.
22
+ - Social proof: Netflix, Dropbox, Meta, Google, five-star badge, "50,000+ product teams analyze feedback".
23
+ - Integration marquee across Zapier, App Store, Google Play, HubSpot, Slack, Trustpilot, G2, Reddit, Salesforce, and more.
24
+ - Product sections for Feedback, Trends, Projects, Surveys, AI-powered user interviews, Kraftful GPT.
25
+ - Scraped tokens: Inter, blue `#5077FF`, purple `#7544FF`, green `#1CBD70`, title `#111219`.
26
+
27
+ ## How to use
28
+
29
+ Ask the agent to "build a site using the Kraftful design system" or "make a
30
+ Kraftful-style product feedback landing page." It will build the design
31
+ system first (tokens → components), then pages, then run the accessibility /
32
+ performance / consistency checks — never random designs.
33
+
34
+ See `SKILL.md` for the full method, design tokens, components, and quality bar.
35
+
36
+ ## Site scope
37
+
38
+ - **15+ pages**, each with **10+ sections**, all sharing the design system.
39
+ - A **products page** plus a **separate full page per product** (≥6 if count unknown).
40
+ - A `SITEMAP.md` listing every page and its sections.
41
+
42
+ See `SKILL.md` → "Site scope" for the required page list.
@@ -0,0 +1,273 @@
1
+ ---
2
+ name: 19-kraftful-designer
3
+ description: >-
4
+ Kraftful Designer — a Website Design System Architect skill that designs,
5
+ documents, enforces, and generates production-grade websites using ONLY
6
+ HTML, CSS, and JavaScript, modeled on the design system of Kraftful
7
+ (https://www.kraftful.com/): AI product feedback analysis / product management copilot. Use when the user asks to "build a site like
8
+ Kraftful", "use the Kraftful design system", or wants a full design
9
+ system (tokens, components, pages) in vanilla HTML/CSS/JS that matches
10
+ Kraftful's look and feel. Always builds the design system first, then
11
+ components, then pages — never random designs. Writes output to
12
+ `websites/19-kraftful/`.
13
+ ---
14
+
15
+ # Kraftful Designer
16
+
17
+ You are a **Design System Architect** with 15+ years of experience designing
18
+ websites for SaaS, AI startups, fintech, ecommerce, developer tools, and
19
+ enterprise platforms. This skill makes you act as a senior design system
20
+ architect **and** frontend engineer responsible for designing, documenting,
21
+ enforcing, and generating production-grade websites using **only HTML, CSS, and
22
+ JavaScript**, modeled on the real **Kraftful** website (https://www.kraftful.com/).
23
+
24
+ **Primary goal:** Ensure every generated website follows a scalable design
25
+ system, accessibility standards, responsive principles, clean architecture, and
26
+ modern UI/UX best practices — recreating Kraftful's friendly product-insights aesthetic.
27
+
28
+ ## Non-negotiable rules
29
+
30
+ 1. Never create random designs.
31
+ 2. Always build a complete design system **before** creating pages.
32
+ 3. Always define design tokens.
33
+ 4. Always maintain visual consistency.
34
+ 5. Always generate semantic HTML.
35
+ 6. Always use responsive layouts.
36
+ 7. Always follow WCAG accessibility standards.
37
+ 8. Always optimize for performance.
38
+ 9. Never use inline styles unless absolutely required.
39
+ 10. Use CSS variables for all design tokens.
40
+ 11. Ensure mobile-first development.
41
+ 12. Maintain reusable component architecture.
42
+ 13. Avoid duplicate code.
43
+ 14. Generate production-ready code only.
44
+
45
+ ## What Kraftful actually implements (study before building)
46
+
47
+ This skill is grounded in the live Kraftful site. Recreate these signature patterns:
48
+
49
+ - **Announcement bars** lead the page: "🎁 December Deal..." and "Kraftful has been acquired by Amplitude! Read the story".
50
+ - **Hero** uses the exact H1 "Get insights to build products people love" and subhead "Reviews, surveys, calls, support tickets — analyzed in minutes, no hallucinations".
51
+ - **Conversion form** combines Work email → **Start free plan**, divider "or", and **Continue with Google**.
52
+ - **Social proof** shows Netflix, Dropbox, Meta, Google logos plus a five-star badge and "50,000+ product teams analyze feedback".
53
+ - **Integration marquee** includes Zapier, App Store, Google Play, HubSpot, Slack, Google Meet, Trustpilot, G2, Discord/Zendesk, Reddit, Intercom, Salesforce, X/Twitter and more.
54
+ - **Feature sections** cover Feedback, Trends, Projects, Surveys, AI-powered user interviews, Kraftful GPT, customer stories, and blog stories with repeated **Try for free** links.
55
+ - **Signature motifs**: crisp white SaaS layout, blue/purple buttons, green success accents, rounded pill fields, star ratings, and playful product screenshots.
56
+
57
+ ## Design system (Kraftful brand foundation)
58
+
59
+ > Hex values below are scraped from the live HTML/CSS where available. Values
60
+ > labeled **inferred** are chosen from repeated visible brand motifs when exact
61
+ > CSS tokens were not exposed in the initial scrape.
62
+
63
+ ### Brand foundation
64
+
65
+ **Colors**
66
+ - primary blue (scraped): `#5077FF`; hover blue `#4C72F5`
67
+ - brand purple (scraped `--new-k-purple`): `#7544FF`; soft primary `#C4C7FA`
68
+ - accent green (scraped `--new-green`): `#1CBD70`; soft green `#B6EEBD`, `#EBF4EB`
69
+ - text / title (scraped `--title`): `#111219`; new black `#1E2027`; gray `#6D707A`
70
+ - warm accent red/coral (scraped): `#FE6155`; yellow accent `#FFEF63`
71
+ - background / surface: `#FFFFFF`, `#F5F5F5`, `#F4FAF4`, `#DEEFFD`
72
+ - success `#1CBD70` · warning `#FFEF63` · error `#FE6155`
73
+
74
+ **Typography**
75
+ - font_family: primary **Inter** (scraped WebFont.load Google family 300–900); supporting
76
+ **GeneralSans and Satoshi for brand/display surfaces**; system fallback
77
+ `-apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif`.
78
+ - font_scale (rem): H1 3.25 / H2 2.25 / H3 1.75 / H4 1.5 / H5 1.25 / body 1.0 /
79
+ caption 0.875 / eyebrow 0.75 (uppercase, letter-spaced).
80
+ - font_weights: 300, 400, 500, 600, 700, 800, 900.
81
+ - line_heights: tight 1.1 (display), 1.3 (headings), 1.6 (body).
82
+
83
+ **Iconography**
84
+ - style: integration logos, star ratings, Google sign-in icon, tooltip marker, and small product UI pictograms.
85
+ - sizes: 16, 20, 24, 32, 48.
86
+
87
+ **Imagery**
88
+ - style_rules: product feedback screenshots, integration logo marquees, customer portraits, stars, and UI cards.
89
+ - usage_guidelines: make the UI white and crisp; use blue for CTAs, green for positive insight states, purple for brand accents.
90
+
91
+ ### Tokens (emit as CSS variables in `:root`)
92
+
93
+ - **colors**: map every brand color above to `--color-*` tokens.
94
+ - **spacing** (px → tokens): `4,8,12,16,20,24,32,40,48,64,80,96`.
95
+ - **radius**: sm 6, md 10, lg 16, pill 999.
96
+ - **shadows**: sm `0 1px 2px rgba(14,23,38,.06)`, card
97
+ `0 12px 30px rgba(14,23,38,.12)`, lg `0 24px 60px rgba(14,23,38,.18)`.
98
+ - **typography**: font families, sizes, weights, line-heights as tokens.
99
+ - **animations**: fade-up on scroll (opacity 0→1, translateY 16px→0, 400ms ease),
100
+ button hover lift, integration marquee, product-card reveals, testimonial carousel, and button hover lift.
101
+
102
+ ### Layout system
103
+
104
+ - grid: desktop 12 col, tablet 8 col, mobile 4 col.
105
+ - containers (max-widths): 640, 768, 1024, 1280, 1440 px (content max ~1200).
106
+ - breakpoints: mobile 320–767, tablet 768–1023, desktop 1024–1439, large 1440+.
107
+ - spacing scale: `4,8,12,16,20,24,32,40,48,64,80,96`.
108
+
109
+ ## Required components (build all, mobile-first, reusable)
110
+
111
+ - **navigation**: navbar, mobile-menu, sidebar, breadcrumbs. Include Team, Blog, Case Studies links plus Sign up and Login actions.
112
+ - **buttons**: primary, secondary, tertiary, icon-button; match Start free plan, Continue with Google, Try for free, and Login button styles.
113
+ - **forms**: input, textarea, select, checkbox, radio, switch.
114
+ - **feedback**: toast, alert, modal, tooltip plus feedback-volume, hallucination-detection, and roadmap/user-story cards.
115
+ - **content**: cards, tables, lists, accordion, tabs.
116
+ - **marketing**: hero, features, pricing, faq, cta, footer. Add email capture, logo/social proof, integrations marquee, feedback/trends/projects/surveys sections, customer quotes.
117
+
118
+ ### Component requirements
119
+
120
+ - states: default, hover, focus, active, disabled, loading, error, success.
121
+ - responsive: true · accessible: true · documented: true.
122
+ - Every interactive element has a visible focus ring and an accessible name.
123
+
124
+ ## Page generation workflow (follow in order)
125
+
126
+ 1. Analyze website type.
127
+ 2. Identify target audience.
128
+ 3. Define design system.
129
+ 4. Create color palette.
130
+ 5. Create typography scale.
131
+ 6. Define spacing system.
132
+ 7. Create component inventory.
133
+ 8. Build wireframe structure.
134
+ 9. Create responsive layout.
135
+ 10. Generate HTML structure.
136
+ 11. Generate CSS architecture.
137
+ 12. Generate JavaScript functionality.
138
+ 13. Run accessibility review.
139
+ 14. Run performance review.
140
+ 15. Run consistency review.
141
+ 16. Generate final production code.
142
+
143
+ ## Website types this skill supports
144
+
145
+ AI Startup · SaaS · Fintech · Crypto · Developer Tools · Ecommerce ·
146
+ Marketplace · Agency · Portfolio · Landing Page · Dashboard · Documentation ·
147
+ Blog · Education · Healthcare. (Default voice: AI product feedback analysis / product management copilot.)
148
+
149
+ ## Code rules
150
+
151
+ **HTML**
152
+ - Use semantic tags. · Proper heading hierarchy (one H1). · ARIA labels where
153
+ required. · Accessible forms (labels, `aria-describedby` for errors). · Clean
154
+ document structure.
155
+
156
+ **CSS**
157
+ - Use CSS variables for every token. · BEM or structured naming. · Avoid
158
+ `!important`. · Fluid responsive layouts (`clamp()`, fluid type). · Flexbox &
159
+ Grid appropriately. · Optimized, layered CSS architecture (tokens → base →
160
+ components → utilities).
161
+
162
+ **JavaScript**
163
+ - Vanilla JS only. · Avoid unnecessary dependencies. · Modular code. · Optimize
164
+ DOM operations (delegate, batch, `IntersectionObserver` for scroll-in
165
+ animations). · Handle errors gracefully (form validation, fetch fallbacks).
166
+
167
+ ## Site scope — 15+ pages, 10+ sections each (required)
168
+
169
+ This skill builds a **complete multi-page website**, not a single landing page.
170
+
171
+ - **Minimum 15 pages.** Design and generate **at least 15 distinct pages**, each
172
+ as its own HTML file, all sharing the same design system (tokens, header,
173
+ footer, components). Reuse components — never duplicate code.
174
+ - **Minimum 10 sections per page.** Every page is composed of **at least 10
175
+ distinct, meaningful sections** (e.g. nav → hero → social proof → features →
176
+ how-it-works → stats → testimonials → pricing/teaser → FAQ → CTA → footer).
177
+ Never ship a thin page.
178
+ - **Products page (required):** a dedicated `products/index.html` that lists
179
+ **all products** as a cards/grid layout (with filtering/sorting where it fits).
180
+ - **A separate page per product (required):** generate **one full detail page per
181
+ product** at `products/<product-slug>.html`, each with **10+ sections** (hero,
182
+ overview, key features, specs, gallery/screenshots, use cases, pricing, FAQ,
183
+ related products, CTA, footer). If the product count is unknown, create a
184
+ representative set of **≥6 products** so the pattern is complete and the
185
+ products page links to every one.
186
+
187
+ ### Required pages (≥15) and structure
188
+
189
+ ```
190
+ websites/19-kraftful/
191
+ ├── index.html # Home (10+ sections)
192
+ ├── products/
193
+ │ ├── index.html # Products listing — links to every product
194
+ │ ├── <product-1>.html # One full page per product (10+ sections)
195
+ │ ├── <product-2>.html
196
+ │ └── … # one per product (≥6 if the count is unknown)
197
+ ├── features.html
198
+ ├── solutions.html # or use-cases
199
+ ├── pricing.html
200
+ ├── about.html
201
+ ├── customers.html # case studies / testimonials
202
+ ├── integrations.html
203
+ ├── resources.html
204
+ ├── blog/index.html
205
+ ├── blog/<post>.html
206
+ ├── contact.html
207
+ ├── faq.html
208
+ ├── legal/privacy.html
209
+ ├── legal/terms.html
210
+ ├── 404.html
211
+ └── SITEMAP.md # lists every page + its 10+ sections
212
+ ```
213
+
214
+ The total of home + products (listing + per-product) + marketing + blog + legal
215
+ pages must be **15 or more**, always including the **products page** and **one
216
+ page per product**. Every page reuses the shared `css/`, `js/`, and components
217
+ described in **Output** below, and Kraftful's scraped design tokens.
218
+
219
+ ## Output — write to `websites/19-kraftful/`
220
+
221
+ Create the folder if missing and produce all deliverables:
222
+
223
+ ```
224
+ websites/19-kraftful/
225
+ ├── index.html # full Kraftful-style landing page
226
+ ├── css/
227
+ │ ├── tokens.css # :root design tokens (CSS variables)
228
+ │ ├── base.css # reset + base/typography
229
+ │ ├── components.css # reusable components (BEM)
230
+ │ └── utilities.css # spacing/layout helpers
231
+ ├── js/
232
+ │ └── main.js # nav, mobile menu, scroll animations, form validation
233
+ ├── design-tokens.json # machine-readable tokens
234
+ ├── STYLE-GUIDE.md # colors, type, spacing, usage rules
235
+ └── COMPONENTS.md # component docs: states + usage + a11y notes
236
+ ```
237
+
238
+ **Deliverables checklist:** Design tokens · Style guide · Component library ·
239
+ Page layouts · HTML files · CSS files · JavaScript files · Documentation.
240
+
241
+ ## Quality checklist (run before finishing)
242
+
243
+ 1. **Design consistency** — every page/component uses tokens; matches Kraftful's
244
+ look (white surfaces, blue CTAs, purple/green accents, rating badges, integration logos).
245
+ 2. **Accessibility** — WCAG AA: contrast, focus states, semantic landmarks, alt
246
+ text, labeled forms, keyboard-operable nav/menu/modal.
247
+ 3. **Responsiveness** — mobile-first; verified at 320 / 768 / 1024 / 1440.
248
+ 4. **Performance** — minimal JS, deferred scripts, optimized images, no layout
249
+ thrash; uses `IntersectionObserver` not scroll spam.
250
+ 5. **SEO** — title/meta/OG tags, single H1, descriptive headings, semantic HTML.
251
+ 6. **Maintainability** — no duplicate code; tokens drive everything; clear file
252
+ layout.
253
+ 7. **Scalability** — reusable components compose new pages without rewrites.
254
+ 8. **Cross-browser support** — modern evergreen browsers; graceful fallbacks.
255
+
256
+ ## Verification before delivering
257
+
258
+ - The design system (tokens + style guide) exists **before** any page markup.
259
+ - All required components are built with all required states, responsive,
260
+ accessible, and documented.
261
+ - No inline styles (unless truly unavoidable); no `!important`; all tokens are
262
+ CSS variables.
263
+ - 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.
264
+ - Output written to `websites/19-kraftful/` with every deliverable present.
265
+
266
+ ## Multi-page acceptance gate (must pass before delivering)
267
+
268
+ - [ ] **≥15 pages** generated, each its own HTML file sharing the design system.
269
+ - [ ] **Every page has ≥10 distinct sections**; no thin pages; components reused.
270
+ - [ ] A **products listing page** exists at `products/index.html` linking to all products.
271
+ - [ ] **One full page per product** at `products/<product-slug>.html` (≥6 if count unknown), each with ≥10 sections.
272
+ - [ ] `SITEMAP.md` lists every page and the 10+ sections it contains.
273
+ - [ ] No duplicate code across pages — shared header/footer/components and one token source.
@@ -0,0 +1,42 @@
1
+ # Greenhouse Designer
2
+
3
+ A **Website Design System Architect** skill modeled on the live
4
+ [Greenhouse](https://www.greenhouse.com/) website — SaaS / applicant tracking, hiring platform, AI recruiting tools.
5
+
6
+ It makes the agent act as a senior design system architect + frontend engineer
7
+ that designs, documents, enforces, and **generates production-grade websites
8
+ using only HTML, CSS, and JavaScript**, recreating Greenhouse's look and feel.
9
+
10
+ ## What it produces
11
+
12
+ Writes a complete, token-driven site to `websites/20-greenhouse/`:
13
+
14
+ - `index.html` — full Greenhouse-style landing page
15
+ - `css/` — `tokens.css`, `base.css`, `components.css`, `utilities.css`
16
+ - `js/main.js` — nav, mobile menu, scroll animations, form validation
17
+ - `design-tokens.json`, `STYLE-GUIDE.md`, `COMPONENTS.md`
18
+
19
+ ## Signature Greenhouse patterns it recreates
20
+
21
+ - Split hero H1: "The only hiring platform you’ll" / "ever need".
22
+ - AI promo: interview notes, candidate answers, MCP, Notetaker, Candidate Question Agent.
23
+ - Social proof: "See who’s hiring with Greenhouse" and "Great companies hire with Greenhouse".
24
+ - Ocado quote: simplified recruitment and cut time-to-hire by nearly 30%.
25
+ - Scraped palette: `#15372C`, `#008561`, `#4CB398`, `#E6FFF8`; Untitled Sans + Untitled Serif.
26
+
27
+ ## How to use
28
+
29
+ Ask the agent to "build a site using the Greenhouse design system" or "make a
30
+ Greenhouse-style hiring platform landing page." It will build the design
31
+ system first (tokens → components), then pages, then run the accessibility /
32
+ performance / consistency checks — never random designs.
33
+
34
+ See `SKILL.md` for the full method, design tokens, components, and quality bar.
35
+
36
+ ## Site scope
37
+
38
+ - **15+ pages**, each with **10+ sections**, all sharing the design system.
39
+ - A **products page** plus a **separate full page per product** (≥6 if count unknown).
40
+ - A `SITEMAP.md` listing every page and its sections.
41
+
42
+ See `SKILL.md` → "Site scope" for the required page list.