// Add a new team member to Langfuse's canonical team data and shared team table. Use when onboarding a new employee who needs to appear on the website team, press, about, careers, or handbook pages.
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.
Create a new Langfuse integration page in the langfuse-docs repo. Use this skill whenever the user wants to add, create, draft, or scaffold an integration page, cookbook, or docs page for a new tool/framework/model-provider/gateway in Langfuse — triggers include "new integration", "integration page", "docs page for <X>", "cookbook for <X>", "add <X> to langfuse docs", or any request that results in a new `cookbook/integration_*.ipynb`. Also use when the user pastes working integration code, a link to a partner's docs, or rough notes and wants them turned into the standard Langfuse integration notebook. The skill produces a correctly formatted Jupyter notebook, updates `cookbook/_routes.json`, and tries to fetch the partner logo into `public/images/integrations/`.
| name | add-yourself-to-team-langfuse |
| description | Add a new team member to Langfuse's canonical team data and shared team table. Use when onboarding a new employee who needs to appear on the website team, press, about, careers, or handbook pages. |
Add a new team member to Langfuse. Ask the user for the following information before proceeding:
public/images/people/<key>.jpgOnce you have the information, update the following source files:
data/authors.jsonAdd a new entry at the end (before the closing }). Use a lowercase, no-special-chars version of the name as the key (e.g. annabellschafer):
"<key>": {
"firstName": "<first name>",
"name": "<full name>",
"title": "<role>",
"image": "/images/people/<key>.jpg",
"twitter": "<twitter handle>", // omit if not provided
"github": "<github username>", // omit if not provided
"linkedin": "<linkedin handle>" // omit if not provided
}
components-mdx/team-members.mdxThis is the canonical website team list. It is rendered by the press, about, careers, and handbook team pages. Append a new table row at the end:
| **<Full Name>** | <Role> | [Twitter](https://x.com/<twitter>), [LinkedIn](https://www.linkedin.com/in/<linkedin>/), [GitHub](https://github.com/<github>) |
Omit any social links that were not provided.
Do not add team rows directly to any other page. Those pages should import and render the canonical component:
import TeamMembers from "@/components-mdx/team-members.mdx";
<TeamMembers />
If a page has a hand-written team table or list, replace it with the shared
TeamMembers import instead of adding another copy. Please do a quick search for some team members to confirm that there are no copies of this table.