Minimal starter, .windsurfrules
The stack-neutral starter as a Windsurf workspace rules file: same content.
Composed from the starter rules pack. Same file from the CLI: aibysitter init --packs starter --format windsurf
Written for this site, CC0, scored by this linter, not tested against any agent.
- File
- .windsurfrules, 26 lines
- Format
- .windsurfrules Legacy format
- Save as
.windsurfrules- Category
- General
- Tags
- License
- CC0 1.0, public domain. No attribution needed.
Download .windsurfrules Lint a copy
Aibysitter lint score
100 / 100 — A
Ruleset v4
No deductions.
Badge
Markdown for a README:
[](https://aibysitting.net/Gallery/minimal-starter-windsurf)
.windsurfrules
# Project rules Fill in the bracketed parts. Delete any line that does not apply. Keep this file under 60 lines. ## Stack - Language and version: [C# 13 on .NET 10] - Frameworks: [ASP.NET Core, EF Core] - Package manager: [NuGet] ## Commands - Build: `[build command]` - Test: `[test command]` - Format or lint: `[format command]` ## Rules - Run the test command before reporting a task complete. - Change only the files the task names, plus their tests. - Match the code style of the file being edited. - Ask before adding a dependency. - Ask before deleting a file. - Do not commit secrets, keys, or `.env` files. ## Done - Build and tests pass. - New behavior has a test that asserts the result. - The PR description lists what changed and how it was tested.
Project rules
Fill in the bracketed parts. Delete any line that does not apply. Keep this file under 60 lines.
Stack
- Language and version: [C# 13 on .NET 10]
- Frameworks: [ASP.NET Core, EF Core]
- Package manager: [NuGet]
Commands
- Build:
[build command] - Test:
[test command] - Format or lint:
[format command]
Rules
- Run the test command before reporting a task complete.
- Change only the files the task names, plus their tests.
- Match the code style of the file being edited.
- Ask before adding a dependency.
- Ask before deleting a file.
- Do not commit secrets, keys, or
.envfiles.
Done
- Build and tests pass.
- New behavior has a test that asserts the result.
- The PR description lists what changed and how it was tested.