.windsurf/rules/project.md
Windsurf rules for FastAPI
Windsurf rules tell the Cascade agent how this repo is built and tested. The current location is `.windsurf/rules`. Older setups still read a root `.windsurfrules` file. This copy is written for a FastAPI project. This repository is a FastAPI service. Request and response bodies are Pydantic v2 models. Routes stay async and must not block the event loop.
The example uses a balanced, readable style, pragmatic tests, and comments only where the intent is not obvious. Open the generator to make the agent stricter, switch to test-first, quiet the comments, or pick a different file.
The example assumes FastAPI with Pydantic v2 and pytest. It does not assume a specific database. If the project uses SQLAlchemy, Tortoise, or raw SQL, keep that choice.
Example file
Balanced strictness, readable style, pragmatic tests. Download name: project.md. Legacy path: .windsurfrules
# Windsurf rules
Rules for Windsurf Cascade in this FastAPI repository.
If the project still uses a root `.windsurfrules` file, keep the same rules there.
## Stack
This repository is a FastAPI service. Request and response bodies are Pydantic v2 models. Routes stay async and must not block the event loop.
## Layout
- The app package exposes `app`. Routers live beside it and are included explicitly.
- Pydantic models live next to the route that owns them, or in a schemas module if they are shared.
- Settings are read once. Do not call `os.environ` inside a path operation.
## Commands
- Dev server: `uvicorn app.main:app --reload`
- Tests: `pytest`
- Lint: `ruff check .`
- Format: `ruff format .`
Use the script the repo already defines when it differs from the command above.
## Conventions
- Define request and response bodies as Pydantic v2 models, not bare dicts.
- Use `APIRouter` and `Depends` the way the project already does.
- Path operations that talk to the network or a database are `async def`. Do not run blocking I/O directly inside them.
- Return the response model you declared. Do not leak ORM objects that were not configured for it.
- Status codes match the action. Create is 201, a missing row is 404, a bad transition is 409.
- Type hints are mandatory on new functions.
## Testing
Add or update tests when behavior changes.
Test the route with the project's HTTP client (httpx or TestClient). Cover the success path and one rejection.
## Style
- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.
## Errors
- Fail at the boundary. Do not swallow errors.
- Raise `HTTPException` with a stable detail for expected failures. Unexpected errors should propagate to the server log.
## Scope
- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.
## Avoid
- Do not call `time.sleep` or synchronous database drivers inside an async route.
- Do not use Pydantic v1 `validator` decorators in new models.
- Do not catch `Exception` and return a 200.
- Do not disable response-model filtering to hide a serialization bug.
## Done when
- The requested behavior works.
- `pytest` passes and `ruff check .` is clean, or you say which tool the repo does not have.
- The diff stays inside the task.
- You list anything you could not run.
Add it to the project
01
Copy a starting file
Copy the example Windsurf rules on this page, or open the generator if you want different testing, strictness, or comment rules.
02
Save it at .windsurf/rules/project.md
Save it at `.windsurf/rules/project.md` in the FastAPI repo. If the project still uses a single root file, save the same body as `.windsurfrules`.
03
Start a fresh agent session
Rules files are read when a session starts. A chat that is already open may still be using the old instructions.
04
Give it one small task
Ask for one change a FastAPI agent often gets wrong, such as a route that rejects a bad payload with a 422 instead of trusting the dict. If it ignores the file, confirm the path and start a new session.
Questions about this file
Where do I put Windsurf rules in a FastAPI repo?
Save it at `.windsurf/rules/project.md` in the FastAPI repo. If the project still uses a single root file, save the same body as `.windsurfrules`.
Which tools read this Windsurf rules?
Windsurf reads `.windsurf/rules/*.md` and, on older projects, `.windsurfrules`. Cursor and Claude Code do not load this path.
What does the FastAPI example assume?
The example assumes FastAPI with Pydantic v2 and pytest. It does not assume a specific database. If the project uses SQLAlchemy, Tortoise, or raw SQL, keep that choice.
Does VibeSpell upload my repository?
No. Recipe pages are static, and the generator builds the file in your browser from the options you pick. Your source code never leaves the machine.
Other files for FastAPI
Windsurf rules for other stacks
- Windsurf rules for Next.js
- Windsurf rules for React
- Windsurf rules for Vue
- Windsurf rules for SvelteKit
- Windsurf rules for Node.js
- Windsurf rules for Django
- Windsurf rules for Go
- Windsurf rules for Rust
- Windsurf rules for Unity
- Windsurf rules for Godot
- Windsurf rules for Laravel
- Windsurf rules for Rails
- Windsurf rules for Flutter
- Windsurf rules for Swift
- Windsurf rules for Kotlin
- Windsurf rules for Unreal
- Windsurf rules for Next.js + Supabase
- Windsurf rules for T3
- Windsurf rules for Astro
- Windsurf rules for Remix
- Windsurf rules for Nuxt
- Windsurf rules for Electron
- Windsurf rules for Tauri
- Windsurf rules for Expo
- Windsurf rules for Spring Boot
- Windsurf rules for .NET
- Windsurf rules for Phaser
- Windsurf rules for Bevy
- Windsurf rules for Roblox
- Windsurf rules for Python ML
- Windsurf rules for LangChain