- Use tasks defined in Taskfile.yml as the source of truth and first choice for running project commands.
- If a needed operation is not represented as a task, you may use direct commands that are appropriate for the repository.
- Keep Taskfile focused on project workflows; routine shell/git commands
(for example
git,ls,rm) do not need Taskfile targets.
- If a command is explicitly documented in a prompt file under
.github/prompts/, that command is allowed when running that specific prompt. - If both a Taskfile task and an explicit prompt command exist for the same operation, prefer the Taskfile task.
- For recurring workflows, add/update a Taskfile task and then update the prompt to call the task so the workflow remains single-sourced.
- Canonical coding policies live in
.github/instructions/. AGENTS.mdfiles are cross-agent adapters and should reference canonical instruction files instead of duplicating their policy bodies.
backend/: apply.github/instructions/backend.instructions.mdand.github/instructions/python.instructions.md.frontend/: apply.github/instructions/frontend.instructions.mdand.github/instructions/typescript.instructions.md.ios/: apply.github/instructions/swiftui.instructions.md.
- The most specific
AGENTS.mdin scope applies first (for example,backend/AGENTS.md,frontend/AGENTS.md, orios/AGENTS.mdover this file for matching paths). - Avoid policy duplication across
AGENTS.mdand.github/instructions/*.instructions.md.