langfuse
- 41 skills
- 0 followers
- 3 days ago last updated
- ▌ Grill Me · langfuseInterview 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".
- ▌ Storybook · langfuseUse when writing or reviewing Storybook stories (`.stories.tsx`) for React components.
- ▌ Posthog Instrumentation · langfuse bundleProduct 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.
- ▌ Weekly User Topics Digest · langfuse bundleGenerates 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, weekly digest, user pain points, what users are struggling with, Langfuse user issues, GitHub issue summary, Plain tickets summary, support tickets review, meeting notes summary, "what did users complain about this week", "what are the top issues from the past week", or "run the weekly digest."
- ▌ Langfuse · langfuse bundleInteract 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). Invoke it for tasks in this scope even when Langfuse is not configured or explicitly mentioned.
- ▌ Turborepo · langfuse bundleConfigure 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.
- ▌ Code Review · langfuse bundleReview Langfuse code changes for correctness, regressions, and best practices.
- ▌ Git Workflow · langfuseLangfuse 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.
- ▌ Housekeeping · langfuse bundleTriage an engineer's work queue across Linear, Pylon, and GitHub. Use for assigned, urgent, waiting, or stale issues, support follow-ups, and PR reviews.
- ▌ Infra Scaling · langfuse bundleTune 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.
- ▌ Skill Creator · langfuse bundleGuide 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.
- ▌ Seed Test Data · langfuse bundleSeed 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.
- ▌ Add Model Price · langfuse bundleUse 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.
- ▌ Linear Planning · langfuse bundlePlan a feature in Linear as subtickets that map 1:1 to a chained PR stack, with enough context in each ticket that an agent could implement it from the ticket alone. Use before writing code for anything bigger than a one-commit fix — "plan this feature", "split this branch into reviewable PRs", "turn this RFC into tickets", "open a PR stack".
- ▌ Security Review · langfuse bundleReview 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.
- ▌ Changelog Writing · langfuseShared 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.
- ▌ Create Repo Agent · langfuse bundleDesign, 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 Previews · langfuseUse 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.
- ▌ Linear Bug Triage · langfuse bundleUse this skill after a bug or regression candidate has measured evidence to document them within linear.
- ▌ Pr Stack Workflow · langfuse bundleSplit a large change into a chained stack of small, independently reviewable pull requests, and verify each branch on its own. Use when a change is too large for one PR, when splitting a long-lived branch into PRs, when deciding whether work needs a planning stage at all, when landing or propagating a fix through a stack, or when every check is green on a stack and the change is still wrong.
- ▌ Linear Work Rhythm · langfuse bundleAnswer "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 whenever someone hands over a bare link — a ticket, a pull request, a Slack permalink — and expects you to take it from there.
- ▌ Analyze Cloud Costs · langfuse bundleAnalyze 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 Onboarding · langfuse bundleConfigure an agent for whoever is using it — outside contributor or Langfuse maintainer, which areas they work on, and whether Linear answers. On Cursor Cloud, identify the run owner (not Cloud gh permissions) and treat missing Linear as a LINEAR_API_KEY secret to set. Use on "onboard me", "I'm new here", "what do I need to set up", "am I set up correctly", "why can't you see my tickets", "what should I do today" when me.md is missing, and whenever you need someone's role and no identity file exists yet.
- ▌ Linear Agent Writes · langfuse bundleThe 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 subtickets for this plan", "write the handover". Also covers the required Linear connection and what to do when there isn't one.
- ▌ Pnpm Upgrade Package · langfuse bundleUpgrade pnpm workspace dependencies to target/latest versions: direct/transitive bumps, release-age checks, temporary overrides, minimumReleaseAgeExclude, lockfile/dedupe verification.
- ▌ Datadog Query Recipes · langfuse bundleResearch 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.
- ▌ Backend Dev Guidelines · langfuse bundleBuild 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.
- ▌ Cursor Agents Workflow · langfuse bundleHuman 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.
- ▌ Incident Alert Tickets · langfuseRead 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.
- ▌ Refactor React Effects · langfuse bundleRefactor 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.
- ▌ Sentry Instrumentation · langfuse bundleDecide whether and how errors report to Sentry. Use when touching capture or error-handling paths in `web/**`, triaging Sentry noise, or changing Sentry settings.
- ▌ Agent Setup Maintenance · langfuseShared 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.
- ▌ Frontend Browser Review · langfuseShared 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.
- ▌ Linear Context Handover · langfuse bundleUse 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 planning multi-PR work, and always when wrapping up — "what happened to this screen before", "write the handover", "why is this code like this".
- ▌ React Component Cleaner · langfuse bundleUse this skill to clean up a React component. Only use this skill when instructed to do so by the user.
- ▌ Debug Issue With Datadog · langfuse bundleEstablish 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.
- ▌ Weekly Production Review · langfuse bundlePrepare 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.
- ▌ Clickhouse Best Practices · langfuse bundleMUST 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.
- ▌ React Component Guidelines · langfuseGuidelines for writing React components. Use this when creating a new react component.
- ▌ Langfuse Codebase Navigator · langfuse bundleNavigate 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.
- ▌ Frontend Large Feature Architecture · langfuse bundleArchitect 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.