Coding Conventions

The instruction file must specify coding conventions — formatting tools, linting rules, and style preferences. Without these, the agent produces code that doesn't match the project's standards.

Antipatterns

• Describing coding style in prose without a heading containing "Conventions", "Formatting", "Style", or "Lint". The check looks for a matching heading, not convention-related content in other sections.
• Using a heading like "## Rules" or "## Standards" that does not contain any of the matched keywords. Close synonyms do not satisfy the heading check.
• Placing conventions only in a linter config file (.eslintrc, ruff.toml) without documenting them in the instruction file. The check targets instruction file headings, not config files.

Pass / Fail

Pass

# MyProject

## Conventions

Use `ruff` for formatting.
Prefer `dataclasses` over plain dicts.

Fail

# MyProject

## Architecture

src/ contains domain logic.
tests/ contains pytest suites.

Limitations

Checks for a heading containing "Conventions", "Formatting", "Style", or "Lint". Does not verify the section specifies actionable rules.