AgentMD - AI Agent Rules Library icon AgentMD - AI Agent Rules Library

Create better AI coding workflows with curated rule templates, framework-specific presets, and reusable standards for secure, testable, maintainable code.

Get access

Windsurf · Kotlin · Ktor · Popular baseline

Status: Published · Visibility: Public

Author

agent_rules_bot

Agent

Windsurf Windsurf

Language

Kotlin Kotlin

Framework

Ktor Ktor

Testing rules Security rules Prefer minimal diffs Architecture rules
# Windsurf · Kotlin + Ktor  
Generated February 10, 2026  
Agent: Windsurf  
Language: Kotlin  
Framework: Ktor

## Global rules
- Start by reading existing project instructions and architecture docs before changing behavior.

- Prefer minimal diffs and preserve existing code style and naming conventions.

- State assumptions and call out risks before making breaking or cross-module changes.

- When behavior changes, add or update tests in the closest existing test layer.

- Never commit secrets, tokens, credentials, or generated private keys.

Start by reading existing project instructions and architecture docs before changing behavior.

Prefer minimal diffs and preserve existing code style and naming conventions.

State assumptions and call out risks before making breaking or cross-module changes.

When behavior changes, add or update tests in the closest existing test layer.

Never commit secrets, tokens, credentials, or generated private keys.

## Agent-specific
- Bias toward implementation momentum while preserving correctness constraints.

- Surface blockers early and propose concrete unblock options.

## Language-specific
- Prefer immutable data classes and explicit nullability.

- Keep coroutine usage structured and cancellation-aware.

- Separate transport DTOs from domain models.

## Framework-specific
- Use typed request models and explicit routing modules.

- Keep plugin configuration centralized and documented.

## Options

### Testing rules
- Require tests for changed behavior or document why tests were not added.

- Run the smallest relevant test subset first, then broaden if needed.

### Architecture rules
- Preserve module boundaries and avoid leaking internal abstractions.

- Prefer incremental refactors over large rewrites.

### Security rules
- Validate and sanitize all user-controlled input.

- Apply least-privilege defaults for data access and actions.

### Prefer minimal diffs
- Limit changes to the smallest set of files and lines needed.

- Defer unrelated cleanup to separate follow-up changes.
Back to public rule sets