spirewise 1.7.1 → 1.9.0

package/skills/enterprise-data-viz-design-system/website-generation-rules.md

@@ -0,0 +1,196 @@
+# Website Generation Rules — Enterprise Data Visualization
+
+How an agent turns this design system into a **production-ready, multi-page, data-dense
+website**. Output clean, semantic **pure HTML + CSS + vanilla JavaScript** plus design tokens.
+The signature: dashboards, charts, KPIs, and tables rendered **honestly and accessibly**, with
+**charts hand-built in inline SVG/Canvas (no chart library)**. (The token/spec system can be
+exported for other agents — but the site itself is pure vanilla.)
+
+## Technology stack (MANDATORY — no frameworks, no libraries)
+
+Build everything — including all charts — with **HTML5 + CSS3 + vanilla JavaScript only**. The
+generated site must contain **zero** of:
+
+> ❌ React · ❌ Vue · ❌ Angular · ❌ Svelte/Next/Nuxt · ❌ Bootstrap · ❌ Tailwind ·
+> ❌ jQuery · ❌ Chart.js · ❌ D3 · ❌ ECharts · ❌ Highcharts · ❌ Plotly · ❌ ApexCharts ·
+> ❌ any UI/CSS framework · ❌ any charting/visualization/animation library
+
+**Charts are authored as inline SVG** (preferred — crisp, stylable, accessible) **or
+`<canvas>`** (for very large datasets), with axes/scales/paths computed in plain JS. No build
+step, no npm, no CDN kits. Exporting `tokens.json` (and sample `data/*.json`) is allowed;
+shipping the site in a framework/charting library is not.
+
+## Mandatory scale & structure (read first)
+- **Multipage: build 15+ pages (recommended ~20)** — a full site map, not one page.
+- **Every page has at least 10 sections (recommend 12)**, leading with data where it fits.
+- **No borders or dividers between sections** — separate with **whitespace, surface elevation
+  (cards/panels), and background tone (`--bg-900`/`--bg-800`)**. In CSS: `.section { border: 0 }`;
+  never `<hr>`/divider or `border-top/bottom` between sections. (Chart gridlines, card edges, and
+  table row rules are *inside* components — not section dividers.)
+- **Honest, accessible data:** right chart for the message; sensible baselines (no truncated/
+  inverted axes); **every chart has a data-table equivalent** + `aria` summary; color-blind-safe.
+- **Clean, extensionless, Vercel-ready URLs** (`/pricing`, not `/pricing.html`).
+
+## Required pages (build all — 15+; ~20 recommended)
+Home `/` · Platform `/platform` · Solutions `/solutions` · Products `/products` ·
+Features `/features` · AI Agents `/ai-agents` · Enterprise `/enterprise` · Security
+`/security` · Pricing `/pricing` · Customers `/customers` · Case Studies `/case-studies` ·
+Developers `/developers` · Documentation `/docs` · About `/about` · Careers `/careers` · Blog
+`/blog` · Contact `/contact` · Partners `/partners` · Resources `/resources` · FAQ `/faq`. Add
+analytics/observability/integration subpages freely.
+
+## Required sections (every page — ≥10, recommend 12)
+Hero (dashboard/metric) · Feature Sections · Product Highlights · Trust Signals (logos) ·
+Testimonials · Use Cases · Statistics (KPI row) · Integrations · CTA · Footer. Add more (Chart
+grid, Data table, Security, Enterprise, Code/Terminal) to reach 12.
+
+## Site types this must support
+Landing pages · startup websites · AI company websites · enterprise SaaS · developer platforms ·
+agentic-AI startups · infrastructure/observability/analytics startups. (See `example-page-structures.md`.)
+
+## What to generate
+- **HTML** — semantic, accessible, one file per page; charts in `<figure>` with data-tables.
+- **CSS** — `tokens.css` (`:root` vars incl. data scales) + `styles.css` (base + charts + tables
+  + components).
+- **JavaScript** — vanilla chart/table engine (SVG/Canvas renderers, scales, axes, tooltips,
+  sort, filter, count-up) + nav/menu/accordion — all reduced-motion-aware; usable without JS
+  (server-rendered SVG + tables).
+- **`vercel.json`** + **`sitemap.xml`** + **`robots.txt`**; optional `data/*.json` sample datasets.
+- **Design tokens** — `tokens.json` (token export only).
+- **Component specifications** — when asked for the *system*, emit chart/table/KPI markup + tokens.
+- **Accessibility + responsive guidance** inline (comments) and honored.
+
+## File/output layout (default — flat files + clean URLs)
+```
+website/
+├── index.html              # served at /
+├── platform.html  solutions.html  products.html  features.html  ai-agents.html
+├── enterprise.html  security.html  pricing.html  customers.html  case-studies.html
+├── developers.html  docs.html  about.html  careers.html  blog.html  contact.html
+├── partners.html  resources.html  faq.html
+├── css/  { tokens.css, styles.css }
+├── js/   { main.js, charts.js }   # vanilla SVG/Canvas chart + table engine
+├── data/ { *.json }               # sample datasets for charts (optional)
+├── assets/  tokens.json  sitemap.xml  robots.txt  vercel.json
+```
+Alternative: folder-per-page `platform/index.html`. Either way **all internal links are
+extensionless** (`href="/pricing"`).
+
+## Clean URLs & Vercel (MANDATORY)
+- **No `.html` in any URL**, no `page.html` links, no ugly query params.
+- Emit **`vercel.json`** so `.html` is stripped, refresh works, and deep links resolve:
+```json
+{
+  "cleanUrls": true,
+  "trailingSlash": false,
+  "headers": [
+    { "source": "/assets/(.*)", "headers": [
+      { "key": "Cache-Control", "value": "public, max-age=31536000, immutable" } ] }
+  ]
+}
+```
+  `cleanUrls: true` serves `platform.html` at `/platform` and 301-redirects `.html`. Provide a
+  `404.html`. Every nav/footer/internal link is extensionless.
+
+## Navigation system (vanilla JS)
+- **Desktop nav** with optional product/solutions dropdown/mega-menu; keyboard +
+  `aria-expanded`/`aria-haspopup`.
+- **Mobile nav**: full-screen overlay, accordion, focus-trap, ESC.
+- **Multi-level nav** + **breadcrumbs** on deep pages; `aria-current="page"`.
+
+## Hard rules
+1. **Vanilla only; charts are inline SVG/Canvas** — no charting/UI library.
+2. **Data-led + honest.** Lead with dashboards/KPIs/charts; right chart for the message;
+   sensible baselines; **every chart has a data-table equivalent** + summary; color-blind-safe;
+   never color-only; **no chart-junk** (3D/shadows/heavy gradients on data).
+3. **Tabular numerals** for all metrics/tables/axes; right-align numeric columns; consistent units/format.
+4. **Tokens first, once** (incl. categorical/sequential/diverging scales); no scattered hex/px.
+5. **No section borders.** Separate with space + surface/tone. `.section{border:0}`.
+6. **Mobile-first + responsive**; dashboards collapse columns; tables scroll/stack; charts stay
+   legible (fewer ticks) — no unintended horizontal page scroll.
+7. **Semantic + accessible** per `accessibility-system.md` (figure+table charts, scoped/sortable
+   tables, focus, reduced motion, live-region on filter). Non-negotiable.
+8. **Components from the library** (charts/KPI/table/dashboard). Every component responsive,
+   accessible, reusable, production-ready.
+9. **Performance:** SVG for typical sizes, `<canvas>` for >~2k points; compute scales once;
+   rAF-throttle interactions; `content-visibility` offscreen; lazy media; high Lighthouse (90+).
+10. **Real, plausible data** (not lorem numbers); mark guesses `[PLACEHOLDER]`.
+11. **Self-verify** against anti-patterns + every companion checklist before done.
+
+## SEO requirements (every page)
+Unique `<title>` + meta description (150–160); **Open Graph** + **Twitter card**
+(`summary_large_image`) + OG image; **canonical** (clean URL); **JSON-LD** (`Organization` +
+`WebSite` site-wide; `Product`, `FAQPage`, `BreadcrumbList`, `Dataset` for notable data pages,
+`Article` for blog); **`sitemap.xml`** + **`robots.txt`**. (Charts are SVG + real `<table>` data
+in the HTML, so the numbers are crawlable.)
+
+## Performance requirements
+Crisp SVG charts (canvas for huge datasets), scales computed once, rAF-throttled tooltips/sort,
+`content-visibility` on offscreen heavy dashboards, lazy media, cached assets (via `vercel.json`),
+no libraries — high Lighthouse.
+
+## Boilerplate `<head>`
+```html
+<!doctype html><html lang="en"><head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta name="color-scheme" content="dark light">
+<title><!-- Page · Brand --></title>
+<meta name="description" content="<!-- 150–160 chars -->">
+<link rel="canonical" href="https://brand.com/path">
+<meta property="og:type" content="website">
+<meta property="og:title" content="<!-- Page · Brand -->">
+<meta property="og:description" content="<!-- … -->">
+<meta property="og:url" content="https://brand.com/path">
+<meta property="og:image" content="https://brand.com/assets/og.png">
+<meta name="twitter:card" content="summary_large_image">
+<link rel="stylesheet" href="/css/tokens.css">
+<link rel="stylesheet" href="/css/styles.css">
+<script type="application/ld+json"><!-- Organization / WebSite JSON-LD --></script>
+</head>
+<body>
+  <a class="skip-link" href="#main">Skip to content</a>
+  <header><!-- Navbar (links extensionless: /platform, /pricing) --></header>
+  <main id="main"><!-- dashboard hero + 10–12 sections, no dividers --></main>
+  <footer><!-- Footer --></footer>
+  <script src="/js/charts.js" defer></script>
+  <script src="/js/main.js" defer></script>
+</body></html>
+```
+
+## Required base CSS (no section borders; data-first)
+```css
+html, body { background: var(--bg-base); color: var(--text-secondary); }
+.section { padding-block: var(--section-y); border: 0; }   /* no borders/dividers between sections */
+.section--alt { background: var(--bg-800); }               /* alternate tone by COLOR, not lines */
+.section + .section { border-top: 0; }
+.visually-hidden { position:absolute; width:1px; height:1px; padding:0; margin:-1px;
+  overflow:hidden; clip:rect(0 0 0 0); white-space:nowrap; border:0; }  /* for chart data-tables */
+/* Separation = whitespace + surface elevation + background tone. Chart gridlines/table rules/
+   card edges are INSIDE components, never section dividers; no <hr> between sections. */
+```
+
+## tokens.json shape (excerpt)
+```json
+{
+  "color": { "bg": {"base":"#0b0e14","900":"#0f131b","800":"#141923"},
+             "surface": {"1":"#161c27","2":"#1c2330"},
+             "text": {"primary":"#eef1f6","secondary":"#b3bccb","muted":"#8893a5"},
+             "accent":"#3b82f6", "good":"#22c55e","bad":"#ef4444","warn":"#f59e0b",
+             "categorical": ["#5b9dff","#f59e0b","#22c55e","#c084fc","#f472b6","#2dd4bf"],
+             "grid":"rgba(255,255,255,0.07)" },
+  "space": { "4":"16px","6":"24px","8":"32px","16":"64px" },
+  "radius": { "md":"8px","lg":"12px","xl":"16px","pill":"999px" },
+  "type": { "body":"0.9375rem","kpi":"clamp(1.75rem,1.3rem + 1.8vw,2.75rem)","numerals":"tabular-nums" }
+}
+```
+
+## Definition of done
+**15+ pages (≈20), each with ≥10 sections (≈12), leading with dashboards/KPIs/charts where it
+fits, no borders/dividers between sections.** Pure HTML/CSS/vanilla JS with **charts hand-built
+in inline SVG/Canvas (no chart library)**; every chart honest + **has a data-table equivalent** +
+`aria` summary + color-blind-safe; tabular numerals throughout; clean extensionless URLs with
+`vercel.json` (refresh + deep links work); desktop nav + mobile + breadcrumb; per-page SEO +
+sitemap; tokens centralized (incl. data scales); fully responsive (dashboards/tables reflow); AA
+accessible; restrained functional motion with reduced-motion fallback; high Lighthouse; zero
+anti-patterns; could sit next to Datadog/Stripe/Linear — precise, data-rich, and trustworthy.

package/skills/f6s-copywriting/README.md

@@ -1,9 +1,9 @@
 # f6s-copywriting
 
 Generate complete, ready-to-paste copy for an **F6S (f6s.com)** startup/company
-profile — written like a senior unicorn-startup marketer: humanized,
-attention-grabbing, and conversion-focused, with **every field kept under its
-character limit**.
+profile **and** accelerator/investor application answers — written like a senior
+unicorn-startup marketer: humanized, attention-grabbing, and conversion-focused,
+with **every field kept under its character limit**.
 
 ## Install
 
@@ -26,14 +26,17 @@ npx spirewise remove -s f6s-copywriting -a claude,cursor -sc both
 After installing, ask your agent:
 
 > "Write our F6S profile copy"
+> "Answer this F6S accelerator application: <paste questions>"
 
 It gathers your company details, then writes **`f6s/f6s-profile-copy.txt`** in
 your project root.
 
 ## Output
 
-`f6s/f6s-profile-copy.txt` — every F6S field (name, tagline, short/full
-description, product, business model, traction, needs, team, etc.) with a live
+`f6s/f6s-profile-copy.txt` — every F6S field (name, tagline, elevator pitch,
+short/full description, product, problem, solution, business model, market &
+competitors, traction, unfair advantage, needs, use of funds, milestones, team,
+links, video/deck) plus any program application answers, with a live
 `(count/limit)` next to each length-limited field.
 
 ## Character limits (kept under, ~10% headroom)
@@ -42,12 +45,19 @@ description, product, business model, traction, needs, team, etc.) with a live
 |---|---|
 | Company name | 50 |
 | Tagline / one-liner | 140 |
+| Elevator pitch | 200 |
 | Short description | 255 |
 | Full description | 2000 |
 | Product description | 1000 |
+| Problem / Solution (each) | 1000 |
 | Business model | 500 |
+| Market & competitors | 1000 |
 | Traction / achievements | 1000 |
+| Unfair advantage | 600 |
 | Needs / seeking | 500 |
+| Use of funds | 600 |
+| Milestones (6–12 mo) | 800 |
 | Team member bio (each) | 500 |
 
-See `SKILL.md` for the full voice/quality standard and output template.
+See `SKILL.md` for the full field guidance, humanization toolkit, application
+mode, and output template.

package/skills/f6s-copywriting/SKILL.md

@@ -2,38 +2,54 @@
 name: f6s-copywriting
 description: >-
   Generate complete, ready-to-paste copywriting for an F6S (f6s.com) startup/company
-  profile page, written like a senior unicorn-startup marketer — humanized,
-  attention-grabbing, and conversion-focused. Use when the user asks to "write our
-  F6S profile", "create F6S copy", "fill out F6S page", or prepare content for an
-  accelerator / investor application on F6S. Produces a single .txt file under an
+  profile AND F6S accelerator/investor application answers — written like a senior
+  unicorn-startup marketer: humanized, attention-grabbing, and conversion-focused.
+  Use when the user asks to "write our F6S profile", "create F6S copy", "fill out
+  F6S page", "answer this accelerator application", or prepare content for an
+  accelerator / investor program on F6S. Produces a single .txt file under an
   `f6s/` folder in the project root, with every field kept STRICTLY under its
   character limit.
 ---
 
-# F6S Profile Copywriting
+# F6S Profile & Application Copywriting
 
-Produce field-by-field copy for an F6S company profile, save it to a plain-text
-file, and guarantee every field stays **below** the platform character limits.
+Produce field-by-field copy for an F6S company profile **and** the open-ended
+application questions F6S programs ask, save it to a plain-text file, and
+guarantee every length-limited field stays **below** the platform's caps.
 
 ## When to use
 
-The user wants copy for their F6S page (startup directory, accelerator/investor
-applications, hiring, or funding). If you lack details about the company, ask a
-few focused questions first (see "Inputs needed").
+The user wants copy for their F6S presence: the public startup profile, an
+accelerator/investor program application, hiring posts, or a funding round. Two
+modes, often used together:
+
+- **Profile mode** — the evergreen company page (name, tagline, descriptions,
+  traction, team, links).
+- **Application mode** — the open-ended Q&A a specific program asks (problem,
+  solution, unfair advantage, ask, use of funds, milestones, video link).
+
+If you lack details about the company, ask a few focused questions first (see
+"Inputs needed"). If the user pasted a specific program's questions, answer
+*those* verbatim in their order — don't force them into the generic template.
 
 ## Inputs needed
 
 Before writing, gather (ask the user, or infer from the repo/website if available):
 
-- Company name and a one-line description of what it does
-- Industry / market and target customer
-- Stage (idea, MVP, pre-revenue, seed, scale, etc.) and business model
-- Key traction (users, revenue, growth, partnerships, awards, press)
-- What they are seeking (funding, talent, partners, customers)
-- Founders / key team, location, founded date, website, social links
+- Company name + a one-line description of what it does, for whom
+- Industry / market, target customer, and the core problem you remove
+- Stage (idea, MVP, pre-revenue, seed, scale) and business model
+- Traction: users, revenue (MRR/ARR), growth %, retention, partnerships, awards, press
+- Market size (TAM/SAM/SOM) and 1–3 real competitors + your wedge vs. them
+- Unfair advantage / unique insight (why this team, why now)
+- What you're seeking (amount + use of funds, talent, partners, customers)
+- Roadmap / milestones for the next 6–12 months
+- Founders & key team, location, founded date, website, social links
+- Pitch video URL and pitch deck link, if any
 
 If the user says "just draft it", make reasonable, clearly-marked placeholder
-assumptions (e.g. `[FOUNDED: 2023]`) rather than blocking.
+assumptions (e.g. `[FOUNDED: 2023]`, `[MRR: $X]`) rather than blocking. Mark
+every guess so it's obvious what still needs a real number.
 
 ## Output location
 
@@ -47,21 +63,51 @@ Treat these as ceilings. **Always stay below the limit** — leave ~10% headroom
 and never emit a field that reaches or exceeds the cap. After writing each field,
 count the characters and trim if needed.
 
-| Field                  | Limit (chars) | Target (stay under) | Notes |
-|------------------------|---------------|---------------------|-------|
-| Company name           | 50            | ≤ 40                | Public/legal name |
-| Tagline / one-liner    | 140           | ≤ 120               | Plain, specific, no hype |
-| Short description      | 255           | ≤ 230               | 1–2 sentences, what + for whom |
-| Full description       | 2000          | ≤ 1800              | Mission, product, differentiation, goals |
-| Product description    | 1000          | ≤ 900               | Features + what makes it different |
-| Business model         | 500           | ≤ 450               | How you make money |
-| Traction / achievements| 1000          | ≤ 900               | Concrete metrics, awards, press |
-| Needs / what we seek   | 500           | ≤ 450               | Funding / talent / partners |
-| Team member bio (each) | 500           | ≤ 450               | Per person |
-| Market / industry tags | n/a (select)  | —                   | Pick from F6S list |
+| Field                    | Limit (chars) | Target (stay under) | Notes |
+|--------------------------|---------------|---------------------|-------|
+| Company name             | 50            | ≤ 40                | Public/legal name |
+| Tagline / one-liner      | 140           | ≤ 120               | Plain, specific, no hype |
+| Elevator pitch (1 sentence)| 200         | ≤ 180               | The whole company in one breath |
+| Short description        | 255           | ≤ 230               | 1–2 sentences, what + for whom |
+| Full description         | 2000          | ≤ 1800              | Mission, product, differentiation, goals |
+| Product description      | 1000          | ≤ 900               | Features + what makes it different |
+| Problem                  | 1000          | ≤ 900               | Who hurts, how much, why it matters now |
+| Solution                 | 1000          | ≤ 900               | How you remove the pain, your wedge |
+| Business model           | 500           | ≤ 450               | How you make money |
+| Market & competitors     | 1000          | ≤ 900               | TAM/SAM/SOM + 1–3 rivals + your edge |
+| Traction / achievements  | 1000          | ≤ 900               | Concrete metrics, awards, press |
+| Unfair advantage         | 600           | ≤ 540               | Why this team, why now, what's hard to copy |
+| Needs / what we seek      | 500          | ≤ 450               | Amount + use of funds / talent / partners |
+| Use of funds             | 600           | ≤ 540               | Where the money goes, expected outcome |
+| Milestones (6–12 mo)     | 800           | ≤ 720               | What proof you'll hit next |
+| Team member bio (each)   | 500           | ≤ 450               | Per person |
+| Market / industry tags   | n/a (select)  | —                   | Pick from F6S list |
 
 If the platform shows a different live limit than above, obey the live limit and
-keep the same "stay under" headroom rule.
+keep the same "stay under" headroom rule. Program application boxes vary — when
+in doubt, aim for 600–900 characters per open question and front-load the answer.
+
+## Per-field micro-guidance (with before → after)
+
+Each field has a job. Hit the job, then stop.
+
+- **Tagline** — one specific outcome, not a slogan.
+  - ❌ "Empowering the future of work." → ✅ "Scheduling software that fills empty
+    shifts for restaurants in under a minute."
+- **Elevator pitch** — `[Who]` gets `[outcome]` because `[wedge]`.
+  - ✅ "Riverside helps 400+ clinics cut no-shows by 30% with text reminders
+    patients actually reply to."
+- **Problem** — name the person and the cost, with a number if you have one.
+  - ❌ "Hiring is inefficient and broken." → ✅ "A 12-person agency spends ~9 hours
+    a week copy-pasting candidates between five tools. Good people slip through
+    while recruiters fight their spreadsheets."
+- **Solution** — what you do, then why it's hard to copy. No feature dump.
+- **Traction** — only real, checkable numbers. Growth %, MRR, retention, logos,
+  waitlist, press. If a number is missing, write `[METRIC NEEDED]`, never invent it.
+- **Unfair advantage** — proprietary data, distribution, founder-market fit, or a
+  hard-won insight. "We work hard" is not an advantage.
+- **Use of funds** — turn money into proof: "18 months of runway to reach $1M ARR
+  and a Series A," not "for growth and marketing."
 
 ## Copy rules (F6S style)
 
@@ -70,6 +116,8 @@ keep the same "stay under" headroom rule.
 - Use real numbers for traction; if unknown, insert a clear `[PLACEHOLDER]`.
 - Write in third person or first-person plural ("we") consistently.
 - No keyword stuffing; F6S profiles are read by humans (accelerators/investors).
+- Front-load every answer — reviewers skim hundreds. The first sentence must
+  carry the point on its own.
 
 ## Voice & quality standard — write like a unicorn-startup marketer
 
@@ -79,45 +127,65 @@ Linear, Ramp, Airbnb). The copy an accelerator partner or investor reads should
 feel sharp, confident, and unmistakably human. Non-negotiable bar:
 
 **1. Humanized — sounds like a real person, never "AI-generated".**
-- Vary sentence length. Mix short, punchy lines with one longer, rhythmic one.
+- Vary sentence length on purpose. A three-word sentence next to a longer,
+  rhythmic one creates a human cadence. Two medium sentences in a row feel like a
+  machine.
 - Use plain, concrete language a smart 12-year-old could follow. Cut jargon.
 - Write with a point of view and a pulse — confident, not corporate-bland.
+- Prefer the verbs and nouns a founder would actually say out loud in a meeting.
 - Read it aloud in your head; if a sentence sounds robotic, rewrite it.
 
 **2. Banned "AI tells" — never use these.**
 - Filler verbs/phrases: "leverage", "utilize", "seamlessly", "robust",
   "cutting-edge", "state-of-the-art", "empower", "unlock", "elevate",
   "revolutionize", "game-changer", "in today's fast-paced world",
-  "we are committed to", "at the intersection of".
+  "we are committed to", "passionate about", "at the intersection of",
+  "designed to", "aims to", "solutions provider", "one-stop shop".
 - Hype with no proof: "best", "#1", "world-class", "industry-leading".
-- Em-dash overuse, three-item lists on autopilot, and symmetrical "not only…
-  but also" scaffolding. Break the pattern; write like a human, not a template.
-
-**3. Attracting & focused — earn the next 5 seconds of attention.**
+- Em-dash overuse, three-item lists on autopilot ("fast, simple, and powerful"),
+  and symmetrical "not only… but also" scaffolding. Break the pattern; write like
+  a human, not a template.
+- Hedge words that drain confidence: "very", "really", "quite", "things",
+  "stuff", "various", "numerous".
+
+**3. The humanization toolkit (use these on purpose).**
+- **Burstiness:** deliberately alternate long and short sentences. End a section
+  on a short line for impact.
+- **Specificity beats adjectives:** swap "huge market" for "$14B spent yearly,"
+  "many customers" for "40+ teams," "fast" for "from 3 weeks to 2 days."
+- **Name real things:** customers, cities, tools, dollar amounts, dates. Concrete
+  nouns read as human; abstractions read as filler.
+- **One human detail:** a founder origin moment, a customer quote, the exact
+  frustration that started the company. One genuine detail outperforms a paragraph
+  of polish.
+- **Active voice, present tense, strong verbs:** "We cut onboarding to two days,"
+  not "Onboarding is able to be reduced."
+- **Contractions are fine** ("we're", "doesn't") — they sound like a person.
+
+**4. Attracting & focused — earn the next 5 seconds of attention.**
 - Hook first. The opening line must make the reader want the next one.
 - One core idea per field. If it does two jobs, split or cut.
-- Specific > vague every time: real numbers, named customers, concrete outcomes.
-  "Cut onboarding from 3 weeks to 2 days for 40+ teams" beats "improves
-  efficiency".
 - Lead with the customer's problem and the outcome, not your feature list.
-- Active voice, present tense, strong verbs. Subject does the thing.
 
-**4. Investor/accelerator lens (this is F6S).**
+**5. Investor/accelerator lens (this is F6S).**
 - Make the *why now*, the *traction*, and the *wedge* obvious fast.
 - Show momentum with evidence (growth %, revenue, retention, logos, waitlist).
 - Sound fundable and grounded — ambitious vision backed by real proof.
 
-**5. Final humanization pass (always run before saving).**
+**6. Final humanization pass (always run before saving).**
 - Remove every banned word above; replace with plain, specific language.
 - Delete adjectives that aren't earned by a fact.
 - Tighten: if a word can be cut without losing meaning, cut it.
 - Ensure no two consecutive sentences share the same shape or opener.
-- Confirm it reads like one confident human voice end to end.
+- Confirm at least one concrete, human detail appears in the long fields.
+- Read the whole thing aloud once. If any line makes you wince or sounds like a
+  brochure, rewrite it. It should read like one confident human voice end to end.
 
 ## Required .txt output template
 
 Write the file using exactly this structure. Put the live character count in
-brackets after each filled field, e.g. `(118/140)`.
+brackets after each filled field, e.g. `(118/140)`. Omit a section only if the
+field genuinely doesn't apply; otherwise use a `[PLACEHOLDER]`.
 
 ```
 F6S PROFILE COPY — <Company Name>
@@ -129,6 +197,9 @@ Generated: <YYYY-MM-DD>
 [TAGLINE / ONE-LINER]    (xx/140)
 <value>
 
+[ELEVATOR PITCH]         (xx/200)
+<value>
+
 [SHORT DESCRIPTION]      (xx/255)
 <value>
 
@@ -138,15 +209,33 @@ Generated: <YYYY-MM-DD>
 [PRODUCT DESCRIPTION]    (xx/1000)
 <value>
 
+[PROBLEM]                (xx/1000)
+<value>
+
+[SOLUTION]               (xx/1000)
+<value>
+
 [BUSINESS MODEL]         (xx/500)
 <value>
 
+[MARKET & COMPETITORS]   (xx/1000)
+<value>
+
 [TRACTION & ACHIEVEMENTS](xx/1000)
 <value>
 
+[UNFAIR ADVANTAGE]       (xx/600)
+<value>
+
 [NEEDS / SEEKING]        (xx/500)
 <value>
 
+[USE OF FUNDS]           (xx/600)
+<value>
+
+[MILESTONES — NEXT 6–12 MONTHS]  (xx/800)
+<value>
+
 [MARKET / INDUSTRY]
 <comma-separated tags>
 
@@ -159,6 +248,12 @@ Generated: <YYYY-MM-DD>
 [WEBSITE]
 <url>
 
+[PITCH VIDEO]
+<url or [PLACEHOLDER]>
+
+[PITCH DECK]
+<url or [PLACEHOLDER]>
+
 [SOCIAL LINKS]
 LinkedIn: <url>
 X/Twitter: <url>
@@ -166,8 +261,26 @@ Other: <url>
 
 [TEAM]
 - <Name> — <Role> — <≤450 char bio> — <LinkedIn url>
+
+---
+[PROGRAM APPLICATION ANSWERS]   (only if the user gave specific questions)
+Q: <exact question as asked>
+A: <answer, front-loaded, ~600–900 chars unless the form states a limit>
 ```
 
+## Application mode (program-specific questions)
+
+When the user pastes a specific accelerator/investor application:
+- Answer each question **in its original order and wording**.
+- Respect any stated character/word limit on each box; if none is given, target
+  600–900 characters and put the answer in the first sentence.
+- Common questions to be ready for: one-sentence pitch, the problem, the solution
+  and why it's better, traction, unfair advantage / unique insight, competitors
+  and your difference, how you make money, what you want from the program, use of
+  funds, team & relevant experience, pitch video link, next 6–12 month milestones,
+  target market & size, prior funding, and a free-text "anything else."
+- Keep the same humanized voice — these are read by partners, not bots.
+
 ## Verification checklist (run before finishing)
 
 1. The `f6s/` folder exists in the project root and contains `f6s-profile-copy.txt`.
@@ -175,5 +288,8 @@ Other: <url>
 3. No field is empty unless intentionally a `[PLACEHOLDER]`.
 4. No banned hype words; tone is factual and specific.
 5. Confirm counts programmatically (e.g. `awk`/`wc -m` per field) — do not trust eyeballing.
-6. Humanization pass done: zero banned "AI tells", varied sentence shapes, reads
-   like one confident human marketer wrote it, and every claim is specific.
+6. Every traction/market number is real or clearly marked `[PLACEHOLDER]` — no invented metrics.
+7. Humanization pass done: zero banned "AI tells", varied sentence shapes, at least
+   one concrete human detail in the long fields, and it reads aloud like one
+   confident human marketer wrote it.
+8. If application mode: every supplied question is answered in order and within its limit.