customer-story

Scaffold Microlink customer pages as Next.js files with registry updates.

142|31|Updated Jul 13, 2017
One-click install
npx skills add https://github.com/microlinkhq/www --skill customer-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-story
Source: https://github.com/microlinkhq/www/tree/main/.cursor/skills/customer-story
Command: npx skills add https://github.com/microlinkhq/www --skill customer-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about customer-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new customer story page in Next.js?

To scaffold a customer story page in Next.js, provide the customer name, website URL, and factual integration details. The system generates a structured page at src/pages/customers/<slug>.js using existing CustomerStory primitives and updates the shared customers registry.

How does CTA routing work for customer use-case pages?

CTA routing for customer pages determines the correct hero and bottom CTA href/labels by analyzing the customer's described integration focus against a predefined routing table. You must confirm the proposed CTA pairs before the page is generated.

What's the best way to ensure my generated React page passes linting and template compliance?

To ensure React page template compliance and linting, the scaffolding process applies deterministic template mirroring, enforces placeholder elimination verification, and satisfies Standard linting rules automatically during page generation.

How do I add a new customer to the content registry without breaking existing listings?

To add a new customer to the content registry safely, the scaffolding process guides updates to src/components/patterns/CustomerStory/customers.js, ensuring the new entry aligns with existing page content and appears correctly across all related listings.

Can I use placeholder text when generating customer story pages?

You cannot use placeholder text when generating customer story pages. The process enforces placeholder elimination verification and strictly prohibits invented claims, requiring factual user-provided details and explicit confirmation before writing the final page.