Eng

Anonymous Staff Engineer

Staff Engineer · Expert · 3y w/ AI · Updated 1 month ago

My Stack

01
Plan

"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."

Claude APIInternal tooling
Templatesystem prompt patterns repodoc
Outputan internal tool nobody else has to build
02
Build

"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."

CursorPrimary IDE
Templatefeature branch conventionconvention
Outputa working PR ready to push
Borrowed by 5Ian Alexander + 4 more
ClaudeInline pair
Template context loaded from open files
Outputfewer rewrites than VS Code
Borrowed by 3
Borrowed by 6
03
Review

"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."

GitHubPR review + record
TemplatePR description templatetemplate
Outputa self-explaining merge
04
Ship

"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."

VercelPreview + prod
TemplatePR-triggered preview conventionconvention
Outputproduction from one click
05
Automate

"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."

Raycast AIKeyboard-driven flow
Template configured per-action, no template
Outputno clicks for routine ops
Borrowed by 2
n8nBackground workflows
TemplateLinear-to-Slack notifier workflowtemplate
Outputfewer pings to remember
Borrowed by 1
Borrowed by 2
06
Document

"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."

LinearIssue-as-doc
Templateissue-as-doc conventionconvention
Outputa searchable engineering trail

Borrow Anonymous's stack

You've seen the whole workflow. Get the stack + every template by email.

3designers borrowed this stack this month

The how

Configs, templates, and conventions Anonymous works from. Open or copy the URL — these stay on the original source.

system prompt patterns repo
Claude APIPlanDoc
View →
feature branch convention
CursorBuildConvention
View →
composer prompt
ClaudeBuild
context loaded from open files
PR-triggered preview convention
VercelShipConvention
View →
command palette config
Raycast AIAutomate
configured per-action, no template
Linear-to-Slack notifier workflow
n8nAutomateTemplate
View →
issue-as-doc convention
LinearDocumentConvention
View →

Retired

What's changed recently

Authors log meaningful updates here when their stack changes.

2 weeks ago
Added n8n for cross-tool automation. Cut Zapier.
6 weeks ago
Built first internal Claude API CLI. Now have 6.
3 months ago
Switched from VS Code to Cursor. Never went back.

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."

Suggested by readers · 1Cline + Sonnet @devon
+ Suggest a tool

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."

Suggested by readers · 2CodeRabbit @ianGreptile @priya
+ Suggest a tool