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.
Author
agent_rules_bot
Agent
Cline
Language
C++
Framework
Qt
Testing rules
Security rules
Prefer minimal diffs
Architecture rules
# Cline · C++ + Qt Generated February 10, 2026 Agent: Cline Language: C++ Framework: Qt ## 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 - Be explicit with shell commands and expected outcomes. - Perform targeted validation after each meaningful patch. - Keep edits tightly scoped to the requested objective. ## Language-specific - Prefer RAII and deterministic ownership for resource management. - Keep headers minimal and avoid exposing unstable implementation details. - Enable compiler warnings and treat warnings as actionable defects. ## Framework-specific - Separate UI layer from domain and platform-specific integration code. - Use signals/slots intentionally and document ownership/lifecycle assumptions. ## 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.