MCP-Template / rules
Cursor rule1 starsChanged 5 months agoMITView on GitHub
Langfuse is an LLM observability tool used to monitor LLM behavior in our application. It uses decorators and callbacks to record LLM inference. Always use it in LLM-related modules to ensure traceability. Decorator-based usage (unchanged from v3): Low-level observation creation (v4 pattern): Key changes from v3: 1. .generation() and .span() removed - use start_observation(as_type=...). 2. .end(**kwargs) no longer accepts output/model/level - split into .update() + .end(). 3. Use TraceContext dict with trace_id and optional parent_span_id instead of positional args. 4.…
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent.mdcCursor rule
- .cursor/rules/coding_style.mdcCursor rule
- .cursor/rules/commit_msg.mdcCursor rule
- .cursor/rules/common.mdcCursor rule
- .cursor/rules/deprecated.mdcCursor rule
- .cursor/rules/github_actions.mdcCursor rule
- .cursor/rules/llm.mdcCursor rule
- .cursor/rules/long_run_code.mdcCursor rule
- .cursor/rules/makefile-commands.mdCursor rule
- .cursor/rules/package-management.mdCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/typing.mdcCursor rule
- .cursor/rules/uv.mdcCursor rule
- frontend-design-principlesSkill
- goose-gui-e2eSkill
- local-sandboxSkill
- manage-agent-configSkill
- new-agent-ruleSkill
- onboardingSkill
- push-releaseSkill
- cleanupSkill
- code-qualitySkill
- prek-precommit-hookSkill
- thermo-nuclear-code-quality-reviewSkill
- usageSkill
- waitSkill
- gmail-mcpSkill
The file
We split this langfuse.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 52
Use TraceContext dict with trace_id and optional parent_span_id instead of positional args.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description:
globs: *.py
alwaysApply: false
---
Langfuse is an LLM observability tool used to monitor LLM behavior in our application. It uses decorators and callbacks to record LLM inference. Always use it in LLM-related modules to ensure traceability.
### Langfuse v4 API Guide
As of Langfuse SDK v4.x, the low-level observation API uses `start_observation()`.
**Decorator-based usage (unchanged from v3):**
```python
from langfuse import observe, get_client
@observe()
def function_name(...):
get_client().update_current_span(name=f"descriptive_name_{id}")
trace_id = get_client().get_current_trace_id()
observation_id = get_client().get_current_observation_id()
```
**Low-level observation creation (v4 pattern):**
```python
from langfuse import Langfuse, LangfuseGeneration, LangfuseTool
from langfuse.types import TraceContext
langfuse = Langfuse()
# Create a generation observation
trace_context: TraceContext = {"trace_id": trace_id}
if parent_observation_id:
trace_context["parent_span_id"] = parent_observation_id
span = langfuse.start_observation(
name="model_name",
as_type="generation", # or "span", "tool", "agent", etc.
input=user_input,
trace_context=trace_context,
metadata={...},
)
# End an observation: update first, then end (v4 .end() only accepts end_time)
span.update(output=result, model=model_name, level="DEFAULT")
span.end()
```
**Key changes from v3:**
1. `.generation()` and `.span()` removed - use `start_observation(as_type=...)`.
2. `.end(**kwargs)` no longer accepts output/model/level - split into `.update()` + `.end()`.
3. Use `TraceContext` dict with `trace_id` and optional `parent_span_id` instead of positional args.
4. New observation types available: `LangfuseTool`, `LangfuseAgent`, etc.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

