@starlein/paperclip-plugin-company-wizard 0.2.1

package/templates/modules/user-testing/agents/qa/skills/user-testing.md

@@ -0,0 +1,30 @@
+# Skill: User Testing
+
+You are the QA engineer and user-facing quality is your core domain. You own test strategy, automation, and usability validation.
+
+## User Testing Process
+
+1. Review the company goal, product description, and user personas
+2. Design test scenarios covering critical user flows
+3. Define success metrics for each scenario (task completion, error rate, time-on-task)
+4. Build test automation for repeatable user flow validation
+5. Execute evaluations and document in `docs/USER-TESTING.md`:
+   - **Functional testing**: Verify all user flows work end-to-end
+   - **Heuristic analysis**: Apply usability heuristics to key screens and flows
+   - **Edge case coverage**: Test boundary conditions, error states, and recovery flows
+   - **Accessibility review**: Check against WCAG standards (contrast, keyboard nav, screen reader)
+6. Rate each finding by severity:
+   - **Critical**: Prevents task completion
+   - **Major**: Significant friction or confusion
+   - **Minor**: Cosmetic or low-impact usability issues
+7. Create follow-up issues for critical and major findings:
+   - `POST /api/companies/{companyId}/issues` with finding details and reproduction steps. Include the active `projectId` (and `goalId` / `parentId` when applicable).
+8. Record summary in your daily notes
+
+## Rules
+
+- Evidence over opinion. Back findings with specific observations and reproduction steps.
+- Test real user flows, not isolated screens.
+- Automate regression tests for critical paths — manual testing doesn't scale.
+- Prioritize by impact — focus on what blocks or frustrates users most.
+- Update findings when the product changes significantly.

package/templates/modules/user-testing/agents/ux-researcher/skills/user-testing.fallback.md

@@ -0,0 +1,18 @@
+# Skill: User Testing (Fallback)
+
+The QA engineer primarily owns test strategy and usability validation. You are the fallback — step in only if QA is absent or hasn't started testing.
+
+## User Testing (Fallback)
+
+1. If no `docs/USER-TESTING.md` exists and QA hasn't started:
+   - Design test scenarios covering critical user flows from a user-centered perspective
+   - Conduct heuristic evaluation against usability principles
+   - Document findings in `docs/USER-TESTING.md`
+   - Focus on user experience quality — task flows, cognitive load, error recovery
+2. If QA is active, skip this entirely.
+
+## Rules
+
+- This is a safety net. Focus on user-centered evaluation — your strength as a researcher.
+- Let QA own test automation and systematic regression testing.
+- Prioritize findings by user impact, not technical severity.

package/templates/modules/user-testing/docs/user-testing-template.md

@@ -0,0 +1,37 @@
+# User Testing
+
+## Test Objectives
+
+- _What are we evaluating?_
+- _What questions do we want to answer?_
+
+## User Personas
+
+- **Persona 1**: _Name, role, technical level, key goals_
+- **Persona 2**: _Name, role, technical level, key goals_
+
+## Test Scenarios
+
+| # | Scenario | Persona | Steps | Success Criteria | Result |
+|---|----------|---------|-------|------------------|--------|
+| 1 | _..._    | _..._   | _..._ | _..._            | _..._  |
+| 2 | _..._    | _..._   | _..._ | _..._            | _..._  |
+
+## Findings
+
+| # | Finding | Severity | Scenario | Evidence | Recommendation |
+|---|---------|----------|----------|----------|----------------|
+| 1 | _..._   | _Critical / Major / Minor_ | _..._    | _..._    | _..._          |
+| 2 | _..._   | _Critical / Major / Minor_ | _..._    | _..._    | _..._          |
+
+## Recommendations
+
+_Prioritized recommendations based on findings above._
+
+## Follow-up Issues
+
+- [ ] _Issue title — severity, linked finding #_
+- [ ] _Issue title — severity, linked finding #_
+
+---
+_Generated by Clipper. Fill in during user-testing task._

package/templates/modules/user-testing/module.meta.json

@@ -0,0 +1,23 @@
+{
+  "name": "user-testing",
+  "description": "Designs and runs user tests to validate product decisions with real feedback.",
+  "capabilities": [
+    {
+      "skill": "user-testing",
+      "owners": [
+        "qa",
+        "ux-researcher",
+        "product-owner",
+        "ceo"
+      ],
+      "fallbackSkill": "user-testing.fallback"
+    }
+  ],
+  "issues": [
+    {
+      "title": "Design and execute initial usability evaluation",
+      "assignTo": "capability:user-testing",
+      "description": "Define test scenarios based on the company goal, identify target user personas, create a test plan, execute evaluations, and document findings in docs/USER-TESTING.md."
+    }
+  ]
+}

package/templates/modules/user-testing/skills/user-testing.md

@@ -0,0 +1,27 @@
+# Skill: User Testing
+
+You own usability evaluations and user testing. This ensures the product meets real user needs and surfaces issues before they reach production.
+
+## User Testing Process
+
+1. Review the company goal, product description, and user personas
+2. Design test scenarios covering critical user flows
+3. Define success metrics for each scenario (task completion, error rate, time-on-task)
+4. Execute evaluations and document in `docs/USER-TESTING.md`:
+   - **Heuristic analysis**: Apply usability heuristics to key screens and flows
+   - **Task flow evaluation**: Walk through core tasks as target personas would
+   - **Accessibility review**: Check against basic accessibility standards (contrast, keyboard nav, screen reader)
+5. Rate each finding by severity:
+   - **Critical**: Prevents task completion
+   - **Major**: Significant friction or confusion
+   - **Minor**: Cosmetic or low-impact usability issues
+6. Create follow-up issues for critical and major findings:
+   - `POST /api/companies/{companyId}/issues` with finding details and reproduction steps. Include the active `projectId` (and `goalId` / `parentId` when applicable).
+7. Record summary in your daily notes
+
+## Rules
+
+- Evidence over opinion. Back findings with specific observations from test scenarios.
+- Test real user flows, not isolated screens.
+- Prioritize by impact — focus on what blocks or frustrates users most.
+- Update findings when the product changes significantly.

package/templates/modules/vision-workshop/agents/ceo/skills/vision-workshop.md

@@ -0,0 +1,23 @@
+# Skill: Vision Workshop
+
+You own the company vision. Refine the initial goal into a strategic foundation that guides all downstream work.
+
+## Vision Workshop Process
+
+1. Review the company goal and any existing context (market analysis, team composition)
+2. Define and document in `docs/VISION.md`:
+   - **Vision statement**: One sentence describing the desired future state
+   - **Mission**: How the company achieves that vision
+   - **Success metrics**: 3-5 measurable KPIs with target values and timeframes
+   - **Strategic milestones**: Ordered list of milestones that lead to the vision
+   - **Non-goals**: What the company explicitly does NOT do (prevents scope creep)
+3. Create issues for the first milestone's deliverables:
+   - `POST /api/companies/{companyId}/issues` with milestone context. Include the active `projectId` (and `goalId` / `parentId` when applicable).
+4. Share the vision doc with the team via daily notes
+
+## Rules
+
+- The vision must be specific enough to say "no" to distractions.
+- Success metrics must be measurable — no vague aspirations.
+- Milestones should be achievable in 1-2 sprint cycles each.
+- Revisit and update when the company goal or market shifts significantly.

package/templates/modules/vision-workshop/agents/ux-researcher/skills/vision-workshop.md

@@ -0,0 +1,19 @@
+# Skill: Vision Workshop — User Research Perspective
+
+When the CEO is running the vision workshop, contribute the user-centered perspective.
+
+## UX Contributions to Vision
+
+Coordinate with the CEO on the vision by providing:
+- **User validation**: Are the success metrics actually measurable from the user's perspective?
+- **Journey mapping**: What does the user's journey look like from first contact to power user?
+- **Metrics reality check**: Propose user-centered KPIs (retention, task completion, satisfaction)
+- **Non-goals validation**: Are we correctly excluding things users don't need?
+
+Document your research inputs in `docs/VISION.md` under a `## User Research Inputs` section.
+
+## Rules
+
+- Don't override the CEO's strategic decisions.
+- Ground your contributions in user behavior insights.
+- Propose measurable metrics, not aspirational ones.

package/templates/modules/vision-workshop/docs/vision-template.md

@@ -0,0 +1,28 @@
+# Company Vision
+
+## Vision Statement
+
+_One sentence describing the desired future state._
+
+## Mission
+
+_How the company achieves that vision._
+
+## Success Metrics
+
+| Metric | Target | Timeframe |
+|--------|--------|-----------|
+| _KPI_  | _Value_| _When_    |
+
+## Strategic Milestones
+
+1. **Milestone 1**: _Description_ — _Target date_
+2. **Milestone 2**: _Description_ — _Target date_
+3. **Milestone 3**: _Description_ — _Target date_
+
+## Non-Goals
+
+- _What the company explicitly does NOT do_
+
+---
+_Generated by Clipper. Fill in during vision-workshop task._

package/templates/modules/vision-workshop/module.meta.json

@@ -0,0 +1,12 @@
+{
+  "name": "vision-workshop",
+  "description": "Clarifies company vision, success metrics, and strategic milestones. Creates the north star before any work begins.",
+  "capabilities": [],
+  "issues": [
+    {
+      "title": "Define company vision, success metrics, and strategic milestones",
+      "assignTo": "ceo",
+      "description": "Refine the company goal into a clear vision statement, define measurable success metrics, and establish strategic milestones. Document in docs/VISION.md. This becomes the north star for all downstream planning."
+    }
+  ]
+}

package/templates/modules/website-relaunch/agents/ui-designer/skills/site-audit.md

@@ -0,0 +1,65 @@
+# Site Audit — Design & Content Perspective
+
+You are responsible for auditing an existing website with a focus on visual design, content quality, and user experience. Your audit informs the relaunch design direction.
+
+## Process
+
+### Step 1: Discover all pages
+
+Starting from the homepage, browse the site page by page. Use WebFetch (or Chrome if available) for each page. Build a complete URL inventory:
+
+| URL | Title | Status | Page Type |
+|-----|-------|--------|-----------|
+| /   | Home  | 200    | landing   |
+
+Continue until the site is fully mapped.
+
+### Step 2: Visual & layout analysis
+
+For each page type, document:
+- **Layout pattern** — grid structure, column count, content zones (hero, body, sidebar, CTA, footer)
+- **Visual hierarchy** — heading sizes, spacing rhythm, how the eye flows down the page
+- **Color usage** — primary, secondary, accent colors observed; background patterns; contrast quality
+- **Typography** — font families (inspect source), size scale, weight usage, line heights
+- **Imagery** — style (photography, illustration, icons), quality, consistency, sizing patterns
+- **Component patterns** — recurring UI elements (cards, buttons, forms, nav bars, modals)
+- **Responsive behavior** — how layouts adapt (if detectable from source/meta viewport)
+
+### Step 3: Content assessment
+
+For each page:
+- **Content quality** — is copy clear, current, and on-brand? Flag outdated or placeholder content
+- **Content structure** — heading hierarchy (H1 → H2 → H3), content length, scannability
+- **Media inventory** — images with dimensions, videos, downloads; note missing alt text
+- **CTAs** — what actions does each page drive? Are they clear and consistent?
+- **Brand voice** — tone consistency across pages, alignment with brand positioning
+
+### Step 4: UX observations
+
+- **Navigation** — is the structure intuitive? Dead ends? Orphan pages?
+- **User flows** — identify the primary journeys (e.g., homepage → product → contact)
+- **Friction points** — broken links, confusing labels, inconsistent patterns
+- **Accessibility** — heading hierarchy, image alt text, form labels, color contrast (visual estimate)
+
+### Step 5: Migration recommendations
+
+For each page, recommend:
+- **Keep** — design and content are strong, migrate as-is
+- **Redesign** — layout or visual treatment needs rethinking
+- **Rewrite** — content is outdated or off-brand
+- **Merge** — combine with another page
+- **Drop** — no longer relevant
+
+Note which visual patterns from the current site should be preserved vs. replaced in the new design.
+
+## Output
+
+Write the complete audit to `docs/SITE-AUDIT.md` with sections:
+1. Page Inventory (table of all URLs with page type and status)
+2. Visual Design Patterns (current color palette, typography, component library)
+3. Content Assessment (quality, structure, and brand voice per page)
+4. UX Observations (navigation, user flows, friction points)
+5. Content Migration Plan (keep/redesign/rewrite/merge/drop per page)
+6. Design Direction Notes (what to preserve, what to rethink, opportunities)
+
+This document is the foundation for all relaunch planning.

package/templates/modules/website-relaunch/module.meta.json

@@ -0,0 +1,168 @@
+{
+  "name": "website-relaunch",
+  "title": "Website Relaunch",
+  "description": "Audits the current site, ingests new designs, and plans a full website relaunch.",
+  "adapterOverrides": {
+    "chrome": true
+  },
+  "capabilities": [
+    {
+      "skill": "design-ingestion",
+      "owners": [
+        "ui-designer",
+        "engineer",
+        "ceo"
+      ],
+      "fallbackSkill": null
+    },
+    {
+      "skill": "site-audit",
+      "owners": [
+        "ui-designer",
+        "engineer",
+        "ceo"
+      ],
+      "fallbackSkill": null
+    }
+  ],
+  "issues": [
+    {
+      "title": "Technical site audit",
+      "assignTo": "engineer",
+      "description": "Crawl the current website and document the technical baseline:\n- Complete page inventory (every URL, status codes)\n- Navigation structure and sitemap\n- Tech stack and hosting (framework, CMS, CDN)\n- SEO baseline (meta tags, structured data, robots.txt, sitemap.xml)\n- Analytics and tracking scripts\n\nUse WebFetch or Chrome to access each page. Output: `docs/SITE-AUDIT.md`."
+    },
+    {
+      "title": "Visual and UX audit of current website",
+      "assignTo": "capability:site-audit",
+      "description": "Audit the current website visually — design patterns, content quality, UX observations, accessibility. Follow the `site-audit` skill. Append to `docs/SITE-AUDIT.md` or create `docs/DESIGN-AUDIT.md`."
+    },
+    {
+      "title": "Analyze design assets and create design spec",
+      "assignTo": "engineer",
+      "description": "Process all design files in the `designs/` directory. Follow the `design-ingestion` skill for the full process.\n\n**How to read design files:**\n- **PDFs:** Use the Read tool with the `pages` parameter (e.g., pages 1–5, then 6–10) to view each page visually. Do NOT use text extraction as primary method — design PDFs are visual artifacts.\n- **PNG/SVG/JPG:** Use the Read tool directly to view each image.\n- **Fallback for precise values:** Use `markitdown` or `docling` (install via pip) to supplement visual analysis with extracted metadata. Use `pdffonts` for embedded font names.\n\n**Extract:**\n1. Design tokens — colors (hex/oklch), typography, spacing scale, border radii, shadows\n2. Component inventory — recurring UI components\n3. Page layouts — grid system, responsive breakpoints\n4. Asset catalog — images, icons, illustrations\n\nOutput: `docs/DESIGN-SPEC.md` with all extracted tokens, components, and layouts."
+    },
+    {
+      "title": "Technical site audit",
+      "description": "Crawl the current website and document the technical baseline:\n- Complete page inventory (every URL, status codes)\n- Navigation structure and sitemap\n- Content types per page (text, images, videos, downloads)\n- Tech stack and hosting (framework, CMS, CDN, response headers)\n- SEO baseline (meta tags, structured data, canonical URLs, robots.txt, sitemap.xml)\n- Analytics and tracking scripts\n- Performance baseline (page weight, render-blocking resources)\n\nUse WebFetch or Chrome to access each page. Output: `docs/SITE-AUDIT.md`.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Visual and UX audit of current website",
+      "description": "Audit the current website from a design and user experience perspective. Use Chrome to browse the site visually. Follow the `site-audit` skill.\n\nFor each page type, document:\n- **Layout patterns** — grid structure, content zones, visual hierarchy\n- **Design tokens in use** — colors, typography, spacing, component patterns\n- **Content quality** — is copy clear, current, and on-brand? Flag outdated or placeholder content\n- **UX observations** — navigation intuitiveness, user flows, friction points, dead ends\n- **Accessibility** — heading hierarchy, image alt text, color contrast (visual estimate)\n\nFor each page, recommend: **keep** (design is strong), **redesign** (layout needs rethinking), **rewrite** (content is outdated), **merge**, or **drop**.\n\nAppend findings to `docs/SITE-AUDIT.md` under a 'Visual Design & UX' section, or create `docs/DESIGN-AUDIT.md` if the technical audit is already complete.",
+      "priority": "high",
+      "assignTo": "ui-designer"
+    },
+    {
+      "title": "Content audit of current website",
+      "description": "Crawl every page of the current website and audit the existing content to inform the redesign:\n\nFor each page, document:\n- **Content type** — hero copy, body text, testimonials, FAQs, CTAs, legal, blog posts\n- **Key messages** — what is the page trying to communicate? What value propositions are present?\n- **Content quality** — is the copy clear, current, and on-brand? Flag outdated, placeholder, or thin content\n- **Media assets** — images, videos, downloads — note which are reusable vs need replacement\n- **SEO content** — headings, meta descriptions, alt text — what's working, what's missing\n- **Gaps** — messaging that should exist but doesn't (e.g., missing social proof, no pricing clarity)\n\nFor each page, recommend a migration strategy:\n- **Keep** — content is strong, migrate as-is into the new design\n- **Rewrite** — message is right but copy needs updating for the new design/voice\n- **Merge** — overlapping content across pages, consolidate\n- **Drop** — no longer relevant, redirect or remove\n\nOutput: `docs/CONTENT-AUDIT.md` — this is a key input for the design handoff and content migration milestones.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Create content inventory spreadsheet",
+      "description": "Based on the site audit and content review, create a structured content inventory:\n- Page URL, title, word count, images, last updated\n- Content status from review (keep / rewrite / merge / drop)\n- Content owner (if identifiable)\n- Migration priority: critical (homepage, key landing pages) vs secondary\n\nOutput: `docs/CONTENT-INVENTORY.md`.",
+      "priority": "high",
+      "assignTo": "ceo"
+    },
+    {
+      "title": "Provide design assets",
+      "description": "Upload the design files from the external agency. Accepted formats:\n- **PDF** — design comps, style guides (will be visually analyzed page by page)\n- **PNG/SVG** — logos, icons, illustrations, page mockups\n- **ZIP** — archive containing any of the above\n- **URL** — link to a shared folder, Figma file, or hosted assets\n\nPlace files in the `designs/` directory of the project, or paste a download URL in a comment on this issue.\n\nThis issue blocks all implementation work.",
+      "priority": "critical",
+      "assignTo": "user"
+    },
+    {
+      "title": "Analyze design assets and create design spec",
+      "description": "Process all design files in the `designs/` directory. Follow the `design-ingestion` skill for the full process.\n\n**How to read design files:**\n- **PDFs:** Use the Read tool with the `pages` parameter (e.g., pages 1–5, then 6–10) to view each page visually. Do NOT use text extraction as primary method — design PDFs are visual artifacts.\n- **PNG/SVG/JPG:** Use the Read tool directly to view each image.\n- **Fallback for precise values:** Use `markitdown` or `docling` (install via pip) to supplement visual analysis with extracted metadata. Use `pdffonts` for embedded font names.\n\n**Extract:**\n1. Design tokens — colors (hex/oklch), typography, spacing scale, border radii, shadows\n2. Component inventory — recurring UI components\n3. Page layouts — grid system, responsive breakpoints\n4. Asset catalog — images, icons, illustrations\n\nOutput: `docs/DESIGN-SPEC.md` with all extracted tokens, components, and layouts.",
+      "priority": "critical",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Implement core page layouts",
+      "description": "Configure the project for the new design, then build the primary page templates:\n\n**Project setup:**\n- CSS/styling approach (Tailwind, CSS modules, etc.) configured with design tokens from `docs/DESIGN-SPEC.md`\n- Component library structure\n- Framework configuration matching design spec requirements\n\n**Core pages:**\n- Homepage\n- Key landing pages\n- Standard content page layout\n- Navigation (header, footer, mobile menu)\n\nApply design tokens (colors, typography, spacing) from the spec. Ensure responsive behavior matches the design breakpoints.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Implement remaining pages and components",
+      "description": "Build all remaining pages and UI components identified in the design spec. Ensure consistent use of design tokens and component patterns. Include interactive elements (forms, accordions, modals) as specified.",
+      "priority": "medium",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Migrate content from old site",
+      "description": "Using the content inventory (`docs/CONTENT-INVENTORY.md`), migrate content to the new site:\n- Transfer text content, updating formatting for the new design\n- Download and optimize images from the old site\n- Preserve SEO-critical content (headings, meta descriptions, alt text)\n- Flag content marked for rewrite and create issues for each\n\nVerify no content is lost by cross-referencing the inventory.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Create URL redirect map",
+      "description": "Map every old URL to its new equivalent:\n- 1:1 redirects for pages that moved\n- Pattern-based redirects for structural changes\n- 410 Gone for intentionally removed pages\n- Verify no orphaned URLs (old pages with no redirect)\n\nOutput: redirect configuration file appropriate for the hosting platform. Test all redirects locally.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Cross-browser testing and performance optimization",
+      "description": "Test across Chrome, Firefox, Safari, and mobile viewports. Optimize:\n- Image formats (WebP/AVIF with fallbacks)\n- Lazy loading for below-fold content\n- Font loading strategy (preload, swap)\n- Bundle size and code splitting\n- Core Web Vitals targets: LCP < 2.5s, CLS < 0.1, INP < 200ms",
+      "priority": "medium",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Pre-launch checklist and go-live",
+      "description": "Final verification before launch:\n- [ ] All redirects configured and tested\n- [ ] DNS records updated (or ready to switch)\n- [ ] TLS/SSL certificate active\n- [ ] Analytics and tracking re-installed\n- [ ] robots.txt and sitemap.xml updated\n- [ ] Social meta tags (Open Graph, Twitter cards)\n- [ ] 404 page designed and implemented\n- [ ] Monitoring and alerting configured\n\nDeploy to production and verify with smoke test.",
+      "priority": "critical",
+      "assignTo": "engineer"
+    }
+  ],
+  "routines": [
+    {
+      "title": "Broken link and redirect check",
+      "description": "Crawl the site and verify all internal links resolve, external links are reachable, and redirects from the old URL map return correct status codes.",
+      "schedule": "0 6 * * *",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Performance and Core Web Vitals check",
+      "description": "Run Lighthouse or equivalent against key pages. Track LCP, CLS, and INP. Flag regressions against baseline.",
+      "schedule": "0 7 * * 1",
+      "assignTo": "engineer"
+    }
+  ],
+  "goal": {
+    "title": "Website Relaunch",
+    "description": "Relaunch an existing website with a new design. Audit the current site, ingest design assets from an external agency, implement the new design, migrate content, and go live.",
+    "project": true,
+    "subgoals": [
+      {
+        "id": "discovery",
+        "title": "Discovery & audit",
+        "level": "team",
+        "description": "Audit the current website — document page structure, content inventory, navigation, tech stack, and SEO baseline. Identify what to keep, migrate, or drop. A site audit document exists with page inventory, content map, tech stack notes, and migration decisions."
+      },
+      {
+        "id": "design-handoff",
+        "title": "Design handoff",
+        "level": "team",
+        "description": "Receive and process design assets from the external agency. Extract color palette, typography, component patterns, layout structure, and responsive breakpoints. Design spec document exists with extracted tokens (colors, fonts, spacing), component inventory, and page layouts documented."
+      },
+      {
+        "id": "implementation",
+        "title": "Implementation",
+        "level": "team",
+        "description": "Build the new site from the design spec. Set up the project, implement components, integrate content, and ensure responsive behavior. All pages from the design are implemented, responsive, and content is integrated. Local dev environment shows the complete site."
+      },
+      {
+        "id": "content-migration",
+        "title": "Content migration",
+        "level": "team",
+        "description": "Migrate content from the old site to the new structure. Set up redirects for changed URLs. Verify no content is lost. All content from the old site is present in the new site. Redirect map covers all changed URLs. No broken internal links."
+      },
+      {
+        "id": "qa-launch",
+        "title": "QA & launch",
+        "level": "team",
+        "description": "Cross-browser testing, accessibility audit, performance optimization, SEO verification, and go-live. Site passes accessibility audit, loads under 3s, all redirects work, DNS is configured, and site is live."
+      }
+    ]
+  }
+}

package/templates/modules/website-relaunch/skills/design-ingestion.md

@@ -0,0 +1,111 @@
+# Design Asset Ingestion
+
+You are responsible for processing design assets provided by an external agency and producing a structured design specification that the engineering team can implement from.
+
+## Input Sources
+
+Design assets may arrive in any of these forms:
+
+| Source | Action |
+|--------|--------|
+| Files in `designs/` directory | Scan directory recursively |
+| ZIP archive in `designs/` | Extract with `unzip`, then scan |
+| URL in issue comment or description | Download with WebFetch, save to `designs/` |
+| GitHub repository link | Clone to `designs/` |
+
+## How to Read Design Files
+
+**Every file must be analyzed visually, not as text.** Design PDFs contain visual comps, mockups, and style guides — you need to *see* each page.
+
+### Reading PDFs (visual analysis)
+
+Use the **Read tool** with the `pages` parameter to view PDF pages as images:
+
+1. First, read pages 1–5 to understand the document scope
+2. Continue in batches of up to 20 pages until you've seen every page
+3. For large PDFs (50+ pages), first read pages 1–3 to identify the table of contents or structure, then target the most relevant sections
+
+**Important:** Do NOT use text extraction tools (pdftotext, pdfgrep) as primary analysis — design PDFs are visual artifacts. Colors, spacing, typography, and layout can only be determined by looking at the pages.
+
+### Reading images (PNG, SVG, JPG)
+
+Use the **Read tool** directly — it displays images visually. Read each mockup, icon, and illustration file individually.
+
+### Fallback: CLI extraction tools
+
+If visual analysis is insufficient for precise values (exact hex codes, font names embedded in metadata), use CLI tools as a supplement:
+
+```bash
+# markitdown — converts PDF/images to structured markdown (pip install markitdown)
+markitdown designs/styleguide.pdf > /tmp/styleguide-extracted.md
+
+# Or docling — structured document extraction (pip install docling)
+docling designs/styleguide.pdf --output /tmp/
+
+# For embedded font names
+pdffonts designs/styleguide.pdf
+
+# For color profiles / metadata
+exiftool designs/styleguide.pdf
+```
+
+Install these tools if not available (`pip install markitdown` or `pip install docling`). Use extracted text/metadata to **supplement** your visual analysis, not replace it.
+
+## Design Analysis Process
+
+### Step 1: Catalog all assets
+
+Scan the `designs/` directory and list every file with:
+- File path, format, dimensions
+- Content description (what the file shows)
+- Category: page mockup, component detail, icon, illustration, photo, style guide
+
+### Step 2: Extract design tokens
+
+From the visual analysis, extract:
+
+**Colors** — every distinct color used, with hex values. Group by role:
+- Primary, secondary, accent
+- Background, surface, border
+- Text colors (heading, body, muted)
+- Semantic (success, warning, error, info)
+
+**Typography** — identify all font families, sizes, weights, and line heights:
+- Headings (h1–h6)
+- Body text, small text, captions
+- Button text, nav links, labels
+
+**Spacing** — identify the spacing scale (margins, padding, gaps between elements)
+
+**Other tokens** — border radii, shadows, transitions, breakpoints
+
+### Step 3: Component inventory
+
+Identify every recurring UI pattern:
+- Navigation (header, footer, sidebar, mobile menu)
+- Buttons (variants: primary, secondary, ghost, sizes)
+- Cards, tiles, list items
+- Forms (inputs, selects, checkboxes, textareas)
+- Modals, drawers, tooltips
+- Hero sections, CTAs, testimonials
+- Media (image containers, galleries, video embeds)
+
+For each component, document: visual appearance, states (hover, active, disabled), responsive behavior.
+
+### Step 4: Page layouts
+
+For each distinct page design:
+- Grid structure (columns, max-width, gutters)
+- Section ordering and spacing
+- Responsive breakpoints and layout shifts
+- Content zones (where text, images, and CTAs go)
+
+## Output
+
+Write the complete specification to `docs/DESIGN-SPEC.md` with sections:
+1. Design Tokens (colors, typography, spacing, etc.)
+2. Component Library (each component with description and states)
+3. Page Layouts (each page with structure and responsive notes)
+4. Asset Inventory (list of images, icons, illustrations to use)
+
+This document is the single source of truth for implementation.

package/templates/modules/website-relaunch/skills/site-audit.md

@@ -0,0 +1,54 @@
+# Site Audit
+
+You are responsible for auditing an existing website and producing a structured report that informs the relaunch.
+
+## Process
+
+### Step 1: Discover all pages
+
+Starting from the homepage, crawl the site by following internal links. Use WebFetch for each page. Build a complete URL inventory:
+
+| URL | Title | Status | Content Type |
+|-----|-------|--------|-------------|
+| /   | Home  | 200    | landing     |
+
+Continue until no new internal links are found or the site is fully mapped.
+
+### Step 2: Document structure
+
+For each page, record:
+- **Navigation** — header, footer, sidebar links; how they change across pages
+- **Content zones** — hero, body, sidebar, CTA sections
+- **Content types** — text blocks, images, videos, downloads, embedded widgets
+- **Word count** — approximate content volume
+- **Images** — count, formats, approximate dimensions, alt text presence
+
+### Step 3: Technical analysis
+
+- **Tech stack** — framework, CMS, hosting provider (check response headers, source HTML, meta generators)
+- **Performance** — page weight, number of requests, render-blocking resources
+- **SEO baseline** — meta titles, descriptions, Open Graph tags, structured data (JSON-LD), canonical URLs, robots.txt, sitemap.xml
+- **Analytics** — identify tracking scripts (Google Analytics, Tag Manager, etc.)
+- **Accessibility quick check** — heading hierarchy, image alt text, form labels, color contrast (visual estimate)
+
+### Step 4: Migration assessment
+
+For each page, recommend one of:
+- **Keep** — content is current and valuable, migrate as-is
+- **Rewrite** — content is outdated or needs restructuring
+- **Merge** — combine with another page
+- **Drop** — no longer relevant
+
+Flag any external integrations (forms, payment, chat widgets) that need replacement or re-integration.
+
+## Output
+
+Write the complete audit to `docs/SITE-AUDIT.md` with sections:
+1. Page Inventory (table of all URLs with metadata)
+2. Site Structure (navigation, information architecture)
+3. Technical Stack (framework, hosting, integrations)
+4. SEO Baseline (current meta tags, structured data, sitemap status)
+5. Content Migration Plan (keep/rewrite/merge/drop decisions per page)
+6. Risk Register (broken links, missing redirects, integration dependencies)
+
+This document is the foundation for all relaunch planning.

package/templates/presets/build-api/preset.meta.json

@@ -0,0 +1,16 @@
+{
+  "name": "build-api",
+  "description": "Design and implement a REST API from schema to documentation. Data modeling, endpoint implementation, authentication, and auto-generated API docs.",
+  "constraints": [],
+  "modules": [
+    "build-api",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "ci-cd",
+    "stall-detection"
+  ],
+  "roles": [
+    "engineer"
+  ]
+}