My Stack
"Claude API powers internal CLI tools the team uses daily — code search across our docs, summary generation, PR triage. We have six custom CLIs built on Claude. Saves ~2 hrs/dev/week, easy."
"Cursor with Claude is the entire IDE story. Branch off main, never on main. Compose mode for any change touching 3+ files. Inline for typos and renames. The accept/reject UI is what makes the workflow stick."
"GitHub PR description is the engineering record. If my summary disagrees with what the diff actually does, my code is wrong. AI-generated PR summaries catch this every time."
"Vercel preview is our staging. We don't have a separate env. PR opens → preview URL → I share it for review. Merge to main triggers prod. No drama, no manual steps."
"Raycast AI runs every keyboard shortcut. n8n stitches Linear ↔ Slack ↔ GitHub for the things that need stitching. About 12 workflows running right now. Tools shouldn't make me think."
"Linear issue + PR description is the entire engineering record. If it's not in the issue or the PR, it doesn't exist. I don't keep separate engineering docs."
Borrow Anonymous's stack
You've seen the whole workflow. Get the stack + every template by email.
The how
Configs, templates, and conventions Anonymous works from. Open or copy the URL — these stay on the original source.
Retired
What's changed recently
Authors log meaningful updates here when their stack changes.
Still looking for the perfect…
Composer-mode parity in VS Code Copilot
"The day Copilot adds composer-mode, I'd consider switching back. Until then, Cursor wins on the only feature I actually use."
AI that reviews my own PRs like a senior dev would
"Not Copilot's auto-review — something that knows our codebase and pushes back on architecture, not just style."