React Component Guidelines

langfuse/langfuse/.agents/skills/react-component-guidelines

Langfuse· v1.0.0

writingOfficial

Official Provider SkillView repo

Guidelines for writing React components. Use this when creating a new react component.

Files1 files

SKILL.md58 lines

Loading editor…

Install

Recommended

One command — your agent picks it up automatically.

Select AI agent

Select an AI agent above to see the install command.

or

Manual Install

More steps

Download the file and paste it into your agent's system prompt.

Skill details

Versionv1.0.0

AuthorLangfuse

Categorywriting

Skill IDlangfuse/langfuse/.agents/skills/react-component-guidelines

Related skills

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.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.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.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.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.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.