跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

customer-story-setup

Converts draft customer-story Markdown into Langfuse website MDX (Fumadocs), collects missing metadata and assets, wires meta.json and authors. Use when adding or converting a customer case study, user story, or /users page, or when the user mentions customer story setup, cresta/canva-style posts, or CustomerStoryCTA/BlogHeader for customers.

langfuse · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add langfuse/langfuse-docs --skill customer-story-setup

技能说明


name: customer-story-setup description: >- Converts draft customer-story Markdown into Langfuse website MDX (Fumadocs), collects missing metadata and assets, wires meta.json and authors. Use when adding or converting a customer case study, user story, or /users page, or when the user mentions customer story setup, cresta/canva-style posts, or CustomerStoryCTA/BlogHeader for customers.

Single source of truth: maintain this skill under .agents/skills/customer-story-setup/ only. Claude and Cursor load projected copies under .claude/skills/customer-story-setup and .cursor/skills/customer-story-setup.

Customer story setup (MD -> MDX)

Turns a plain Markdown draft into content/customers/<slug>.mdx in the same pattern as content/customers/canva.mdx and cresta.mdx.

Before writing any file: collect missing input

Do not guess. If any item below is missing from the user's draft or message, ask explicitly and wait for answers (or confirm defaults).

Content & publishing

TopicAsk
Company nameLegal/marketing name for copy and quotes
Company websitePublic URL for the [Company](https://...) link in About <Company>
SlugFilename: <slug>.mdx (lowercase, hyphens), e.g. cresta -> cresta.mdx
Page titleH1 string for BlogHeader + YAML title (often "How <Company> ... with Langfuse")
Short descriptionYAML description + BlogHeader description (SEO/social; 1-2 sentences)
Publish dateYAML date + BlogHeader date (e.g. March 26, 2026)
OG imageOptional ogImage: path; if unset, leave empty like other stories

Authors (BlogHeader authors={["..."]})

TopicAsk
Byline author(s)Who should appear under the title (keys from data/authors.json)
External / guest speakerIf not in authors.json: collect name, title, optional socials, and headshot path under public/images/people/ or public/images/customers/<slug>/, then add an entry to data/authors.json (see existing entries). Every authors key must resolve in authors.json.

Branding & Users index card

TopicAsk
LogosPaths for customerLogo and customerLogoDark (light + dark mode), usually under public/images/customers/<slug>/
Pull quotecustomerQuote (short, for grid card)
Quote attributionquoteAuthor, quoteRole, quoteCompany
Speaker headshot (optional)quoteAuthorImage for card/SEO if you use the same as Canva
Show on /usersshowInCustomerIndex: true | false

Images (screenshots & diagrams)

Produce a numbered checklist for the user (and keep it in the PR description if useful):

  1. Folder: public/images/customers/<slug>/
  2. For each asset: filename, purpose, where it appears (section + suggested alt text)
  3. Remind: customer posts use <Frame fullWidth> around markdown images, e.g. ![Alt](mdc:/images/customers/<slug>/file.png) per site conventions
  4. Size each image by aspect ratio (run sips -g pixelWidth -g pixelHeight <file> to get dimensions):
    • Portrait / square (ratio <= 1:1) -> <div className="flex justify-center"><Frame fullWidth className="w-1/2">...</Frame></div>
    • Landscape (~1.5:1) -> <div className="flex justify-center"><Frame fullWidth className="w-2/3">...</Frame></div>
    • Panoramic (> 2:1) -> <Frame fullWidth className="w-full">...</Frame> (no centering wrapper needed)

If the draft says "screenshot here" without files, list placeholders in MDX with consistent paths so the user can drop files in later.

Docs links (optional but recommended)

Ask whether to add sparse internal links. Default policy: only link major product concepts (match what we used on Cresta):

阅读完整来源 ↗