- 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/langfuse30,377
- 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/langfuse30,377
- 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/langfuse30,377
- Backend Dev GuidelinesShared backend guide for Langfuse's Next.js, tRPC, BullMQ, and TypeScript monorepo. Use when creating or reviewing tRPC routers, public REST endpoints, BullMQ queue processors, backend services, middleware, Prisma or ClickHouse data access, OpenTelemetry instrumentation, Zod validation, env configuration, or backend tests across web, worker, or packages/shared.langfuse/langfuse30,377
- 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/langfuse30,377
- 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/langfuse30,377
- Code ReviewShared code review workflow for Langfuse. Use when reviewing a PR, branch, diff, or local changes for correctness, regressions, risk, and missing tests. Start with references/review-checklist.md for repo-specific review rules and use package AGENTS.md files plus any matching shared skills when the change touches those areas.langfuse/langfuse30,377
- Create Repo AgentUse when designing, implementing, reviewing, or hardening Langfuse repo-owned autonomous agents, especially GitHub Actions that invoke Claude, Codex, or another LLM agent on a schedule or workflow_dispatch, create pull requests, update workflow prompts or allowlists, handle GitHub tokens/secrets, use untrusted web content, or self-improve repo agent instructions.langfuse/langfuse30,377
- Datadog Query RecipesLangfuse-specific Datadog query recipes for production telemetry research. Use when asked to investigate tenant or project activity, public API endpoint usage, queue consumer behavior, spans, logs, metrics, or ad hoc production questions across prod-us, prod-eu, prod-hipaa, and prod-jp. This skill is for reusable query shapes and measured research; pair it with debug-issue-with-datadog when the task is an incident or root-cause analysis.langfuse/langfuse30,377
- Debug Issue With DatadogDebug a user-reported issue, Linear ticket, or incident report by combining Datadog (APM, logs, metrics) with the Langfuse repo to establish a root cause. Use when given a Linear issue URL/ID (e.g. LFE-XXXX), a GitHub issue, or a pasted error/report and asked to investigate, root-cause, or triage. Produces a structured analysis — error breakdown, hypothesis-by-class, suggested patches with code references.langfuse/langfuse30,377
- 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 the Playwright MCP server before signoff.langfuse/langfuse30,377
- Frontend Large Feature ArchitectureUse when building, changing, or refactoring large Langfuse frontend features, virtualized lists, large tables, controller components, local feature state, Zustand stores, row selection, high-frequency UI state, or rendering-performance issues.langfuse/langfuse30,377
- Git WorkflowLangfuse repo Git, GitHub, commit, branch, pull request, issue search, release, and production-promotion workflow. Use when staging, committing, pushing, opening PRs, searching GitHub issues, or changing release/promotion behavior.langfuse/langfuse30,377
- HousekeepingReview an engineer's recurring work queue across Linear, Pylon, and GitHub. Use when asked to triage assigned issues, waiting or urgent work, customer-support follow-ups, stale tickets, or pull requests where the engineer is a direct or team reviewer; return concrete action recommendations and gate all writes on explicit human approval.langfuse/langfuse30,377
- Infra ScalingTune Langfuse infrastructure autoscaling safely across web, web-iso, and web-ingestion. Use when Codex needs to review or change Terraform scale settings, RPM targets, scale-up/scale-down boundaries, min/max task counts, cost/performance tradeoffs, dashboard scaling markers, Datadog event-loop metrics, trace/span evidence, GitHub pull requests, or Linear follow-up tickets for `web`, `web-iso`, or `web-ingestion` containers in the langfuse/infrastructure repository.langfuse/langfuse30,377
- Langfuse Codebase NavigatorNavigate Langfuse repositories, code areas, and agent skills. Use when a user or agent asks where Langfuse code lives, which Langfuse repo to inspect, which Langfuse skill applies, how to search across Langfuse repositories, or how to orient in the Langfuse org before implementing, debugging, documenting, supporting, or operating Langfuse.langfuse/langfuse30,377
- Linear Bug TriageDeduplicate measured bug or regression evidence against Linear, then either add evidence comments to related existing issues or create concise Linear bug issues in Triage. Use when Codex has confirmed evidence from Datadog, benchmarks, traces, timings, flamegraphs, logs, or production measurements and needs Linear search, comments, labels, Datadog links, or bug ticket creation without fix suggestions, but only after a human has approved sharing the findings in Linear.langfuse/langfuse30,377
- Pnpm Upgrade PackageUpgrade pnpm workspace dependencies to target/latest versions: direct/transitive bumps, release-age checks, temporary overrides, minimumReleaseAgeExclude, lockfile/dedupe verification.langfuse/langfuse30,377
- Security ReviewSecurity review patterns for Langfuse. Use during code review, design, or planning whenever a change accepts user-supplied URLs, host/endpoint/baseURL fields, secrets, cross-tenant data, new outbound HTTP requests, new integrations (webhooks, blob storage, LLM connections, image proxies), redirect-following behavior, or new auth/permission scopes. Covers SSRF/outbound URL validation today and is intentionally extensible to other recurring security findings (tenant isolation, secret handling, redlangfuse/langfuse30,377
- Seed Test DataSeed local Langfuse test data with one command: large/branching observation trees (v3 and v4 events), long sessions, bulk traces for list performance. Use whenever a task needs ClickHouse/Postgres test data — e.g. "seed a complex trace", "make a tough session", "fill the trace list", "test v4 events UI", or when debugging trace/session/list rendering or performance. Never write ad-hoc seed scripts or raw ClickHouse inserts.langfuse/langfuse30,377
- 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/langfuse30,377
- StorybookUse when writing or reviewing Storybook stories (`.stories.tsx`) for React components.langfuse/langfuse30,377
- TurborepoTurborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.langfuse/langfuse30,377
- 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/langfuse30,377
- 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/langfuse30,377
- Weekly Production ReviewPrepare Langfuse weekly production reviews that audit what broke, what was fixed, what remains open, and where Datadog, incident.io, or Linear tracking needs cleanup. Use when asked for a production review, "what broke last week", fixed/open production bugs, Datadog alerted monitors/pages, Datadog error log patterns, incident.io incidents, incident.io alert load, pager load by engineer or time of day, or a source-table engineering review across incident.io, Linear bugs, Datadog alerts, and Datadlangfuse/langfuse30,377
- 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-docs216
- 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-docs216
- 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-docs216
- LangfuseInteract with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods.langfuse/skills189
- 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/skills189
- 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-examples30