description	alwaysApply
Branch only for code; documentation commits on main	true

Git workflow (Neon Sprawl)

Agent: Never run git commit without explicit user instruction; the user reviews diffs first. See commit-and-review.

Documentation-only work — Commit directly on main. This means Markdown (.md) under docs/, root and nested README.md files, neon_sprawl_vision.plan.md, and other prose docs. No feature branch required.
Code or implementation changes — Use a branch, then merge to main when ready. Branch names must start with the Jira key (e.g. NS-14-click-to-move); commit subjects must start with the same key (e.g. NS-14: …). See jira-git-naming. This includes application source (C#, GDScript), Godot scenes and project files, docker-compose.yml, .csproj / build config, CI workflows, JSON/YAML game data under content/, and JSON Schema when it ships with data pipelines—not standalone doc prose.

When a change mixes documentation and code, treat it as a code change (use a branch).