All examples

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

• Template
• Any stack
• Windsurf

License

CC0 1.0, public domain. No attribution needed.

Download .windsurfrules Lint a copy

Badge

Markdown for a README:

[![Aibysitter lint score: A 100](https://aibysitting.net/gallery/minimal-starter-windsurf/badge.svg)](https://aibysitting.net/Gallery/minimal-starter-windsurf)

.windsurfrules

View rendered

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

1. # Project rules
3. Fill in the bracketed parts. Delete any line that does not apply. Keep this file under 60 lines.
5. ## Stack
6. - Language and version: [C# 13 on .NET 10]
7. - Frameworks: [ASP.NET Core, EF Core]
8. - Package manager: [NuGet]
10. ## Commands
11. - Build: `[build command]`
12. - Test: `[test command]`
13. - Format or lint: `[format command]`
15. ## Rules
16. - Run the test command before reporting a task complete.
17. - Change only the files the task names, plus their tests.
18. - Match the code style of the file being edited.
19. - Ask before adding a dependency.
20. - Ask before deleting a file.
21. - Do not commit secrets, keys, or `.env` files.
23. ## Done
24. - Build and tests pass.
25. - New behavior has a test that asserts the result.
26. - The PR description lists what changed and how it was tested.