Self Improve

Guidelines for continuously improving Windsurf rules based on emerging code patterns and best practices.

PublishedJun 7, 2026

Loading actions...

5 minBeginnerprompt5 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (4)

Rule Improvement Triggers:
- New code patterns not covered by existing rules
- Repeated similar implementations across files
- Common error patterns that could be prevented
- New libraries or tools being used consistently
- Emerging best practices in the codebase
Analysis Process:
- Compare new code with existing rules
- Identify patterns that should be standardized
- Look for references to external documentation
- Check for consistent error handling patterns
- Monitor test patterns and coverage
Rule Updates:
- Add New Rules When:
  - A new technology/pattern is used in 3+ files
  - Common bugs could be prevented by a rule
  - Code reviews repeatedly mention the same feedback
  - New security or performance patterns emerge
- Modify Existing Rules When:
  - Better examples exist in the codebase
  - Additional edge cases are discovered
  - Related rules have been updated
  - Implementation details have changed

Example Pattern Recognition:

// If you see repeated patterns like:
const data = await prisma.user.findMany({
  select: { id: true, email: true },
  where: { status: 'ACTIVE' }
});

// Consider adding to [prisma.md](.windsurf/rules/prisma.md):
// - Standard select fields
// - Common where conditions
// - Performance optimization patterns

Rule Quality Checks:
- Rules should be actionable and specific
- Examples should come from actual code
- References should be up to date
- Patterns should be consistently enforced
Continuous Improvement:
- Monitor code review comments
- Track common development questions
- Update rules after major refactors
- Add links to relevant documentation
- Cross-reference related rules
Rule Deprecation:
- Mark outdated patterns as deprecated
- Remove rules that no longer apply
- Update references to deprecated rules
- Document migration paths for old patterns
Documentation Updates:
- Keep examples synchronized with code
- Update references to external docs
- Maintain links between related rules
- Document breaking changes Follow windsurf_rules.md for proper rule formatting and structure.

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

160

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

127

Jan 15, 2026