Architecture Decision
Get 2-3 genuinely different architecture options with a trade-off table, a recommendation, and an ADR you can commit to the repo.
Help me make an architecture decision.
The decision: [WHAT YOU'RE DECIDING, e.g. "how to handle background jobs", "monolith vs services for the new module"]
System today: [STACK, SCALE, TEAM SIZE, DEPLOYMENT SETUP]
Requirements that matter: [FUNCTIONAL + NUMBERS WHERE THEY EXIST: requests/sec, data volume, latency budget, team's operational maturity]
Constraints: [BUDGET, DEADLINES, TECH THE TEAM KNOWS, COMPLIANCE]
Produce:
1. **Clarify the actual requirement**: restate what the decision must optimize for, and call out any requirement I stated that's likely over-specified for my scale ("you said 'must scale to millions', at your stated volume, that's a 5-year problem, not a launch problem"). If a missing number changes the answer, mark it [NEEDED: what] and proceed with a stated assumption.
2. **2-3 options that are genuinely different**: not one real option plus two strawmen. For each: how it works in my stack specifically, what it's like to operate at my team's size, and its failure story (what breaks first as load or complexity grows).
3. **Trade-off table**: options as columns; rows: complexity to build, complexity to operate, performance at my stated scale, cost, reversibility, team-fit. Rate honestly: every option must lose at something, or the table is decoration.
4. **Recommendation**: which option and why, in terms of MY constraints. Name the conditions under which the recommendation flips ("if you exceed X events/sec within a year, switch to option B").
5. **ADR**: a short Architecture Decision Record I can commit: context, decision, consequences (including the negative ones we're accepting).
Rules: boring and proven beats interesting at almost every team size, bias accordingly and say when you're doing it. Don't defer to my apparent preference; if my framing smuggles in a bad default, challenge it.More coding prompts
Write the commit message for this change. Diff: """ [PASTE THE STAGED DIFF] """ Why I made this change: [THE REASON, THE TICKET, THE BUG REPORT, or "you infer it"] Convention: [Conventional Commits / this repo's existing style, pasted below / plain] Recent commits from this repo, to match style: """ [PASTE 5-10 RECENT COMMIT SUBJECT LIN
Commit Message
Write a commit message that explains why the change was made, in Conventional Commits format, split into separate commits when needed.
Codingbeginner
Help me recover from a git mistake without making it worse. What I was trying to do: [THE GOAL] What I ran: [THE EXACT COMMANDS, IN ORDER] What happened instead: [THE OUTPUT OR THE STATE NOW] Has this been pushed or shared: [YES/NO, and to which branch and whether anyone else has pulled] Uncommitted work I cannot lose: [WHAT AND WHERE, o
Undo a Git Mistake
Recover from a bad commit, force push, wrong branch, or lost work with a reversible plan and the exact commands, explained before you run them.
Codingintermediate
Handler code, routes, and models: """ [PASTE THE ROUTE DEFINITIONS, HANDLERS, REQUEST AND RESPONSE TYPES, VALIDATION SCHEMAS, AND MIDDLEWARE] """ Generate an OpenAPI 3.1 specification from the code above. API name, version, and base URL: [DETAILS] Auth scheme: [BEARER JWT / API KEY / OAUTH / SESSION COOKIE, and where it is enforced] Con
OpenAPI Spec From Code
Generate an accurate OpenAPI 3.1 spec from handler code, including error responses and auth, with gaps flagged instead of invented.
Codingintermediate