Every modern AI coding agent reads a rules file at the start of each session — CLAUDE.md for Claude Code, .cursorrules for Cursor, GEMINI.md for Gemini CLI, and so on. Sprintra generates these files for your repo so every agent automatically follows your ticket-key conventions, workflow rules, and PR formatting.
Sprintra's GitHub integration auto-links pull requests to stories by reading the PR's title, body, and branch name for ticket references like PROJ-42. If the agent opening the PR doesn't include the ticket, the PR is captured but not linked — the story doesn't move.
The rules file is how you tell the agent “always include the ticket key in PR bodies you create.” Once the file is in your repo, the agent reads it every session and behaves accordingly. No per-PR reminder needed.
| File | Used by | Auto-generated today |
|---|---|---|
CLAUDE.md | Claude Code | Yes |
AGENTS.md | Antigravity | Yes |
GEMINI.md | Gemini CLI | Roadmap |
.cursorrules | Cursor | Roadmap |
.codex/instructions.md | OpenAI Codex CLI | Roadmap |
.github/pull_request_template.md | All humans + agents | Roadmap |
The recommended workflow:
# From your repo root
npx @sprintra/cli@latest plugin link --project=<your-project-id>This writes the .sprintra/project.json marker (so Sprintra knows which workspace this repo belongs to) and generates the rules files supported today. The files are checked into git so your whole team gets them.
Inside Claude Code specifically, you can also ask the agent: “Generate a fresh CLAUDE.md for this project” — it'll call the Sprintra MCP tool that builds the file from your current project state.
Sprintra-generated files include:
PROJ) so the agent knows what prefix to use.For mixed human + agent workflows, a .github/pull_request_template.md file gives both groups a clear nudge. A minimal one:
## Summary
<!-- What does this PR do? -->
## Linked story
Closes: PROJ-____
## Test plan
- [ ] ...GitHub shows the template every time someone opens a PR. The Closes: PROJ-____ line is enough for Sprintra's linker to recognize the ticket once the user fills it in.
Rules files are guidance, not enforcement. An agent can technically open a PR without reading the file; a human can ignore the PR template. Sprintra captures the ticketless PR but doesn't move any story status. For teams that need a hard gate, a future Sprintra status check (sprintra/has-ticket) will block merges of PRs that don't reference a story — on the roadmap.