Before a change
What should I check before changing this API?
Bring the relevant contract, architecture constraints, and review checklist into the coding workflow.
Prompts for developer teams
Turn the team’s best instructions into reusable workflows.
Save the questions, review steps, and delivery practices your team repeats. Everyone starts with the same project-aware guidance instead of rebuilding it in every AI session.
PromptsInteractive sample
PROJECT / ATLAS
API review prompt
Find the team’s API review checklist.
Sample prompt retrieved
Reusable prompt ready
Check the proposed change against the API contract. Review authorization, request validation, backward compatibility, and failure responses. Report concrete findings with file references.
Next step: Use it for the current diff, then run the project’s agreed validation checks.
Saved prompt · API change review
Review only the supplied diff and relevant callers. Check access controls, contract compatibility, input limits, and error responses. Explain each finding with evidence.
Prompt guidance · Expected output
Return actionable findings with severity, file reference, and a short explanation. State which checks ran and which remain unverified.
Illustrative workflow with fictional project data. No live query is sent.
Recognisable questions
What does your team ask repeatedly?
Reusable prompts make recurring work easy to discover and consistent to execute.
Before delivery
How should this repository validate a change?
Reuse the project’s test, security, documentation, and release expectations.
During review
Review this change using our project standards.
Give every reviewer and approved AI tool the same starting instructions.
How prompts work
Reusable prompts remain governed and project-scoped.
Shared library
Find prompts by title and tag in the project where they apply.
Controlled changes
Managers create and update prompts; viewers can discover and use them.
Available where teams work
Use approved prompts through the Web UI and project knowledge tools exposed through MCP.
Usage visibility
Track use count and last-used time to see which workflows the team relies on.
Make good practice reusable
Give the whole team a consistent starting point.
Start with one review, implementation, or delivery workflow your developers repeat.