vibecodingnav
中/EN
Toolbox/Project rules/android-agents
A

Android AGENTS.md

Prompt

Conventions for an Android repo: tests, Compose, and ViewModel first.

Why this, and when not

Why It turns constraints that show up in bench migrations into checks the repo can run.

Skip it Do not force Compose rules onto View screens you are not migrating yet.

One line for the agent

AGENTS.md Prompt
- 每次修改后运行 ./gradlew test lint
- UI 使用 Compose + Material 3,禁止新增 XML
- 新功能先写 ViewModel 单测,再写界面

Peers

Appears in

Source