- Add Model PriceUse when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI, Anthropic, Bedrock, Vertex, Azure, or Gemini model pricing.langfuse/langfuse35,162
- Agent Setup MaintenanceShared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.langfuse/langfuse35,162
- Analyze Cloud CostsAnalyze Langfuse Cloud infrastructure cost structure using Metabase cost marts. Use when asked about cloud spend, AWS versus ClickHouse cost splits, cost drivers by provider/service/usage type/account, daily cost per tracing event, infra cost dashboards, or cost regressions visible in Metabase.langfuse/langfuse35,162
- Backend Dev GuidelinesBuild or review Langfuse backend code. Use for tRPC routers, public REST APIs, BullMQ processors, services, middleware, Prisma or ClickHouse access, OpenTelemetry, Zod, environment configuration, or backend tests.langfuse/langfuse35,162
- Changelog WritingShared workflow for writing Langfuse changelog entries after a feature is complete. Use when a branch is ready for merge and a changelog entry or changelog draft is needed.langfuse/langfuse35,162
- Clickhouse Best PracticesMUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.langfuse/langfuse35,162
- Code ReviewReview Langfuse code changes for correctness, regressions, and best practices.langfuse/langfuse35,162
- Create Repo AgentDesign, implement, review, or harden Langfuse repo-owned autonomous agents. Use for LLM-powered GitHub Actions, scheduled or dispatched agents, agent-created PRs, prompts, allowlists, tokens, untrusted content, or self-updating instructions.langfuse/langfuse35,162
- Cursor Agents WorkflowHuman handoff, Linear branch names, reviewable (non-draft) PRs, the `cursor` GitHub label, Claude, Greptile, and Codex review comments, preview test steps, proof of work posted on the GitHub PR, and review-doubt notes for Cursor agents. Use when a Cursor Cloud or Cursor desktop agent implements a Linear issue, opens a GitHub PR, asks a human to test, posts screenshots or videos, or handles Claude, Greptile, or Codex code-review comments.langfuse/langfuse35,162
- Datadog Query RecipesResearch Langfuse production telemetry with reusable Datadog queries. Use for tenant or project activity, API usage, queue behavior, spans, logs, metrics, or ad hoc measurements across production regions; pair with debug-issue-with-datadog for root-cause analysis.langfuse/langfuse35,162
- Debug Issue With DatadogEstablish root cause by combining Datadog telemetry with the Langfuse repo. Use when investigating or triaging a user report, Linear or GitHub issue, incident, or pasted production error.langfuse/langfuse35,162
- Frontend Browser ReviewShared workflow for browser-based review of user-visible frontend changes in Langfuse. Use when a change affects UI behavior, layout, styling, navigation, or browser-visible regressions and should be checked with available browser automation before signoff.langfuse/langfuse35,162
- Frontend Large Feature ArchitectureArchitect large or state-heavy Langfuse frontend features. Use for virtualized lists, large tables, controllers, Zustand stores, row selection, high-frequency state, rendering performance, or before adding useEffect, useMemo, useCallback, or form defaults derived from loaded data.langfuse/langfuse35,162
- Git WorkflowLangfuse repo Git, GitHub, commit, branch, pull request, issue search, release, and production-promotion workflow. Use when staging, committing, pushing, opening PRs, choosing a Linear git branch name, handling Claude, Greptile, or Codex review comments, searching GitHub issues, or changing release/promotion behavior.langfuse/langfuse35,162
- Grill MeInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".langfuse/langfuse35,162
- HousekeepingTriage an engineer's work queue across Linear, Pylon, and GitHub. Use for assigned, urgent, waiting, or stale issues, support follow-ups, and PR reviews.langfuse/langfuse35,162
- Incident Alert TicketsRead and record root causes in the Linear `incident-alert` knowledge base. Use before and after investigating a named Datadog monitor, incident.io alert or incident, or on-call page to find or record root causes.langfuse/langfuse35,162
- Infra ScalingTune and review Langfuse autoscaling for web, web-iso, and web-ingestion. Use for Terraform scale settings, RPM targets, scaling bounds, task counts, cost/performance tradeoffs, or Datadog evidence in the infrastructure repo.langfuse/langfuse35,162
- Langfuse Codebase NavigatorNavigate Langfuse repositories, code areas, and agent skills. Use to locate code, choose the right repo or skill, search across the Langfuse organization, or orient before implementation, debugging, documentation, support, or operations.langfuse/langfuse35,162
- Langfuse PreviewsUse Langfuse's disposable per-PR previews at pr-N.preview.langfuse.com (synthetic data only). Use for preview access, failed deployments, test-data seeding, kubectl debugging, or waking sleeping previews.langfuse/langfuse35,162
- Linear Agent WritesThe org policy for what an agent may write to Linear, and how it must be marked. Read this before creating a ticket, editing a description, or commenting on a ticket as an agent — "file this in Linear", "comment on the ticket", "create a subticket", "write the handover". Default those writes to a short human description; expand with research only when asked. Also covers the required Linear connection and what to do when there isn't one.langfuse/langfuse35,162
- Linear Bug TriageUse this skill after a bug or regression candidate has measured evidence to document them within linear.langfuse/langfuse35,162
- Linear Context HandoverUse Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it. Use when starting work on an existing feature, when splitting a large change, and always when wrapping up — "what happened to this screen before", "write the handover", "why is this code like this".langfuse/langfuse35,162
- Linear Work RhythmAnswer "what should I do today" for a Langfuse maintainer, from the tracker rather than from memory: which projects you lead, which owe an update before the Monday engineering weekly, what shipped but is not finished, what waits on your decision, and what colleagues are working on that overlaps. Use on "what should I do today", "what's on my plate", "what should I work on next", "prep my Monday update", "what did I say last week", "who else is working on this", "who should review this", and whenlangfuse/langfuse35,162
- Pnpm Upgrade PackageUpgrade pnpm workspace dependencies to target/latest versions: direct/transitive bumps, release-age checks, temporary overrides, minimumReleaseAgeExclude, lockfile/dedupe verification.langfuse/langfuse35,162
- Posthog InstrumentationProduct analytics with posthog. Use when adding a meaningful user action or feature in `web/**`, touching PostHog capture code, changing session replay or its privacy boundaries, or answering product-usage questions.langfuse/langfuse35,162
- React Component CleanerUse this skill to clean up a React component. Only use this skill when instructed to do so by the user.langfuse/langfuse35,162
- React Component GuidelinesGuidelines for writing React components. Use this when creating a new react component.langfuse/langfuse35,162
- Refactor React EffectsRefactor avoidable React useEffect usage in Langfuse frontend code. Use when adding, reviewing, or removing effects; initializing forms or local UI state from query data; synchronizing client and server state; moving mutations or async workflows out of components; cleaning every effect from a frontend submodule; or reviewing whether an effect has a valid external-system owner.langfuse/langfuse35,162
- Security ReviewReview Langfuse changes for SSRF, tenant isolation, secret handling, unsafe redirects or uploads, RBAC drift, and client telemetry privacy. Use when a design or change accepts URLs or host fields, handles secrets or cross-tenant data, makes outbound requests, adds an integration, follows redirects, widens permissions, or can send customer-controlled UI data through analytics, monitoring, or session replay.langfuse/langfuse35,162
- Seed Test DataSeed reproducible local Langfuse data in ClickHouse and Postgres. Use for complex traces, long sessions, v3/v4 events, bulk list data, or frontend rendering and performance tests; never use ad hoc scripts or raw inserts.langfuse/langfuse35,162
- Sentry InstrumentationDecide whether and how errors report to Sentry. Use when touching capture or error-handling paths in `web/**`, triaging Sentry noise, or changing Sentry settings.langfuse/langfuse35,162
- Skill CreatorGuide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.langfuse/langfuse35,162
- StorybookUse when writing or reviewing Storybook stories (`.stories.tsx`) for React components.langfuse/langfuse35,162
- TurborepoConfigure and troubleshoot Turborepo monorepos. Use for turbo.json, task pipelines, dependsOn, caching, filters, affected packages, CI optimization, environment variables, package boundaries, or shared internal packages.langfuse/langfuse35,162
- Vercel Composition PatternsReact composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.langfuse/langfuse35,162
- Vercel React Best PracticesReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.langfuse/langfuse35,162
- Weekly Production ReviewPrepare Langfuse weekly production reviews covering failures, fixes, open issues, and tracking gaps. Use for "what broke last week," production bugs, Datadog alerts or error patterns, incident.io activity, or pager load.langfuse/langfuse35,162
- LangfuseInteract with Langfuse and access its documentation: tracing, monitoring, creating datasets, running experiments, and evaluating AI applications. Use when needing to (1) query or modify Langfuse data, (2) look up Langfuse documentation, concepts, integration guides, a feature or SDK usage, or (3) do any AI engineering task (AI observability, prompt engineering/management, evaluation and evaluator management, experimentation, dataset management, evaluation-driven CI/CD, feedback collection). Involangfuse/skills289
- Skill CreatorGuide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.langfuse/skills289
- Add Customer To User ListAdd or update a company in the Langfuse /users adopters table. Use when the user asks to add a customer, adopter, or company to the users list, /users page, or adopters table — including "add X to the user list", "list as Langfuse Customer", or pasting a public blog/job/case-study link to cite. Always check for an existing user story before choosing the Reference cell.langfuse/langfuse-docs246
- Add Yourself To Team LangfuseAdd 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.langfuse/langfuse-docs246
- Customer Story SetupConverts 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/langfuse-docs246
- Langfuse Integration PageCreate 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 lilangfuse/langfuse-docs246
- Weekly User Topics DigestGenerates a weekly digest of real user topics by pulling from three sources: (1) Circleback meeting notes from the past 7 days, (2) Plain support tickets from the past 7 days, and (3) GitHub issues filed or updated on the langfuse/langfuse repo in the past 7 days. Synthesizes into a ranked summary of genuine user topics — not just bugs, but friction, confusion, missing features, and workflow blockers that affect real users significantly. Use this skill whenever the user asks for: weekly summary,langfuse/langfuse-examples40