What problem does it solve?
Creating a consistent customer use-case page is time-consuming and error-prone, especially when you must match the existing layout, typography, CTA routing rules, and data sources.
Core Features & Use Cases
- Customer-page scaffolding: Generates the full page structure at src/pages/customers/<slug>.js by following the canonical template and shared CustomerStory primitives.
- Factual content and safety guardrails: Enforces “never invent claims” rules and requires user confirmation before writing the page with computed CTAs and testimonial details.
- CTA routing by use case: Determines the correct hero and bottom CTA href/labels from the customer’s described integration focus, based on the provided routing table.
- Registry-ready customer metadata: Guides updates to src/components/patterns/CustomerStory/customers.js so the new customer appears in all related listings.
Quick Start
Provide the customer name, website URL, and a factual description of how they use Microlink, then confirm the proposed hero CTA href/label pair and the bottom CTA href/label before generating src/pages/customers/<slug>.js and adding the customer to customers.js.