Skip to content

About

My reference for choosing tech stacks: API styles, real-time, databases, hosting. Built to attach to Claude sessions.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

3 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Choose Your Stack

My personal reference for picking the right tech stack when starting a new project or refactoring an old one. Attach a guide to a Claude session (or point Claude Code at this repo) and ask it to recommend a stack using these criteria.

Guides

Guide Covers Status
API styles REST, GraphQL, gRPC, SOAP, Webhooks, SSE, WebSockets, WebRTC, MQTT, message queues Done
Databases Postgres, SQLite, Mongo, Redis, Supabase, vector DBs Planned
Frontend & mobile Next.js, Astro, React Native/Expo, plain HTML Planned
Hosting & deploy Vercel, Railway, Cloudflare, Supabase, VPS Planned
Auth & payments Supabase Auth, Clerk, Stripe, local gateways Planned

Quick picker: API style

Pick one main API, then add a style for every "yes" below.

flowchart TD
    start([New project]) --> q1{A partner system<br/>only speaks SOAP?}
    q1 -- yes --> soap[SOAP, wrapped in REST]
    q1 -- no --> q2{Several frontends need<br/>different data slices?}
    q2 -- yes --> gql[GraphQL]
    q2 -- no --> rest[REST - the default]

    subgraph addons [Add-ons: one for every yes]
        direction LR
        a1{Server pushes live updates,<br/>one way only?} --> sse[SSE]
        a2{Both sides message often,<br/>in real time?} --> ws[WebSockets]
        a3{React to another<br/>service's events?} --> wh[Webhooks]
        a4{Audio, video or<br/>screen sharing?} --> rtc[WebRTC via LiveKit/Daily]
        a5{Devices or sensors<br/>sending telemetry?} --> mqtt[MQTT]
        a6{Slow work that can<br/>finish later?} --> mq[Message queue]
        a7{Internal services need<br/>fast, typed calls?} --> grpc[gRPC]
    end

    soap --> addons
    gql --> addons
    rest --> addons
Loading

If every add-on question is a no, the main API is enough. Full details are in guides/api-styles.md.

How to use this repo with Claude

In a Claude chat: download the guide's .md file and attach it, then paste:

Use the attached guide. Here is my project: [what it does, who uses it, web/mobile/IoT, real-time needs, team size, existing stack]. Recommend the main API style and any add-ons, explain why using the guide's criteria, and flag anything I'm likely to regret later.

In Claude Code: clone this repo next to your projects, or add a line to a project's CLAUDE.md:

For stack decisions, follow ~/Choose-Your-Stack/guides/ and record the result in ~/Choose-Your-Stack/decisions/.

From anywhere: use the raw URL of a guide, for example https://raw.githubusercontent.com/SamGhaddar/Choose-Your-Stack/main/guides/api-styles.md

Recording decisions

Each time I pick a stack for a project, I copy decisions/TEMPLATE.md to decisions/<project>.md and fill it in. Later I can see what I chose and why, and whether it held up.

Repo layout

Choose-Your-Stack/
├── README.md            this page + quick picker
├── CLAUDE.md            instructions for Claude sessions
├── guides/              one decision guide per topic
│   └── api-styles.md
├── decisions/           one record per project
│   ├── README.md
│   └── TEMPLATE.md
└── .github/ISSUE_TEMPLATE/
    └── new-guide.md     track a guide to write next

About

My reference for choosing tech stacks: API styles, real-time, databases, hosting. Built to attach to Claude sessions.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors