LuthienResearch/luthien_control

LuthienResearch/luthien_control

Cursor rule Cursor

This is the description the AI always sees.

LuthienResearch/luthien_control

Cursor rule Cursor

This is the content the AI only sees if one of the files currently being worked on matched the filenamepattern.

LuthienResearch/luthien_control

Cursor rule Cursor

Example/Explanation of Manual rule type.

LuthienResearch/luthien_control

Cursor rule Cursor

This rule outlines the strict Test-Driven Development process to be followed by the AI assistant when implementing new features or fixing bugs. This complements the broader developmentworkflow by providing specific TDD execution steps for the AI.

LuthienResearch/luthien_control

Cursor rule Cursor

. No Redundant Comments: Only comment non-trivial logic. Avoid comments that merely state the obvious (e.g., # Import module, # Loop through items). Adhere strictly to the global instruction provided during generation. Docstrings are a special case and should almost always be included for all classes and functions…

LuthienResearch/luthien_control

Cursor rule Cursor

Guiding principles for modifying code (refactoring, cleanup, imports, comments).

LuthienResearch/luthien_control

Cursor rule Cursor

Configuration and Secrets Management.

LuthienResearch/luthien_control

Cursor rule Cursor

Update dev/currentcontext.md with the current development plan and progress status. This update should be performed when a new plan is formulated, after making significant progress, or upon completing a key task or milestone. This helps maintain context across interactions and improves the clarity of ongoing work.

LuthienResearch/luthien_control

Cursor rule Cursor

Follow these steps whenever an important feature, bugfix, or other meaningful non-trivial milestone is completed, prior to git commit.

LuthienResearch/luthien_control

Cursor rule Cursor

Write plainly and honestly. We're not selling anything.

LuthienResearch/luthien_control

Cursor rule Cursor

summary: Protocol for verifying code edits using git diff before debugging logic errors.

LuthienResearch/luthien_control

Cursor rule Cursor

NEVER proceed on catch-all exceptions. When catching exceptions, follow these guidelines.

LuthienResearch/luthien_control

Cursor rule Cursor

In general, code should NOT 'fallback' to another solution when something doesn't work as expected unless specifically told otherwise. Code should default to failing quickly, loudly, and obviously.

LuthienResearch/luthien_control

Cursor rule Cursor

You are an expert in Python, FastAPI, and scalable API development.

LuthienResearch/luthien_control

Cursor rule Cursor

Document all Python classes and public functions using Google-style docstrings.

LuthienResearch/luthien_control

Cursor rule Cursor

Project structure and organization guidelines.

LuthienResearch/luthien_control

Cursor rule Cursor

PYTEST EXIT CODE=0 JUST MEANS THE TESTS RAN. IT DOES NOT MEAN THEY WERE SUCCESSFUL. Always look for the pytest summary line at the end of the output (e.g., ==== X passed, Y failed, Z warnings in S.ss ====).

LuthienResearch/luthien_control

Cursor rule Cursor

When finalizing significant changes, use pyright, pytest --cov, and ruff.

LuthienResearch/luthien_control

Cursor rule Cursor

globs: alwaysApply: true.

LuthienResearch/luthien_control

Cursor rule Cursor

Documentation of Cursor rule types and header configuration.

LuthienResearch/luthien_control

Cursor rule Cursor

Security Best Practices.

LuthienResearch/luthien_control

Cursor rule Cursor

TEST-DRIVEN DEVELOPMENT GUIDELINES. MANDATORY READING BEFORE WRITING CODE.

LuthienResearch/luthien_control

Cursor rule Cursor

Default to real objects. Only mock when you have.