Repo Prompt Generator

Rules

• Prefer current repo docs over intuition.
• Keep doc lists minimal and task-specific.
• Always include AGENTS.md.
• Add backend/AGENTS.md only when backend, schema, API, auth, or scripts are touched.
• Add frontend/AGENTS.md when UI, routes, request states, responsive behavior, or frontend guidance are touched.
• Add brand/BRAND_CONSTRAINTS.md when visual tone or branding matters.
• When docs and code may disagree, tell the implementing agent to document:
  • current state
  • gap
  • recommended target
• For doc-only prompts, require extraction order:
  • code
  • config
  • migrations or bootstrap scripts
  • existing docs
• For implementation prompts, require priority order:
  • docs
  • code or config
  • validation
• Keep references/doc-routing.md in sync with the repo.

Output

• optional assumptions
• one ready-to-send prompt in a fenced code block