What is Get Shit Done?
Get Shit Done (GSD) is a plugin for Claude Code that applies the principles of context engineering. Instead of asking Claude to build an app in a single prompt, Get Shit Done:
- Automatically breaks down the project into phases
- Creates a file
state.mdthat tracks progress - Lets you clear the context regularly without losing progress
- Enforces checkpoints to test before continuing
Installation
To install Get Shit Done in Claude Code:
# Installation globale (recommande)
npx get-shit-done-cc --claude --global
# Ou installation locale dans le projet
npx get-shit-done-cc --claude --local
Once installed, the command /gsd becomes available. Type /gsd new project to start a new project.
The phase structure
Get Shit Done automatically creates a folder structure:
mon-app/
├── planning/
│ ├── phases/
│ │ ├── phase-01-setup.md
│ │ ├── phase-02-auth.md
│ │ ├── phase-03-database.md
│ │ └── ...
│ ├── roadmap.md
│ └── state.md # Progression (ex: 67%)
└── src/
Each phase contains precise instructions and validation checkpoints.
Context engineering
The key principle: clear the context regularly and let the file state.md serve as memory. At the start of each new session:
- Type
/clearto clear the context - Paste the next GSD command (e.g.:
gsd create roadmap) - Claude picks up exactly where it left off
This avoids hallucinations and keeps Claude focused on the current task.
Setting up Supabase
Get Shit Done integrates naturally with Supabase for the database and authentication:
- Automatic table creation via SQL
- Configuring the file
.envwith the keys - Magic link authentication
The author shows how to use Playwright (d-chrome) so Claude can configure Supabase directly in the browser.
Aliases and permissions
To speed up the workflow, the author uses a shell alias cdd that:
- Launches Claude with
--dangerously-skip-permissions - Automatically enables Chrome (
d-chrome)
This avoids having to say "yes" for every action and lets Claude act autonomously.
Tests and checkpoints
At the end of each phase, Get Shit Done enforces a checkpoint :
- Launch the app (
npm run dev) - Test the listed features
- Confirm everything works before moving on
This methodical approach is what prevents building a broken app.
OpenAI integration
The example app ("Clear List") uses the OpenAI API to analyze tasks and prioritize them intelligently. The integration is simple:
# .env
OPENAI_API_KEY=sk-...
Get Shit Done automatically manages the AI integration phase in its roadmap.
Payments and tiers
To monetize the app, the author mentions:
- Supabase to manage user tiers (free, pro)
- Stripe in sandbox mode to test payments
- Ngrok to test webhooks locally
Deployment
Once the project is at 100%, deployment happens in three steps:
- GitHub : Push the code to a repository
- Vercel : Connect the repo and deploy automatically
- Environment variables : Configure the keys in Vercel
Claude can manage all of this via Playwright if you have it enabled d-chrome.
Key takeaways
- Context engineering : Clear the context regularly, let state.md remember
- Structured phases : Don't skip steps, test at every checkpoint
- Troubleshooting : Take screenshots and send them to Claude to debug
- Learn by building : Ask Claude to explain what it's doing
In my last video, I showed you how to use Playwright to access your browser via Claude Code in VS Code. Today, I'm going to show you how to build a complete app with Claude Code using a context engineering tool called Get Shit Done.
I spent a few hours building this client intake form. It's connected to a lawyer portal that lets you see all submitted cases. And the coolest part is that each case is analyzed by AI. The Get Shit Done plugin told me it took about 3 hours.
I'll show you how to generate your own idea, install Get Shit Done in Claude Code, and use it to generate your first app while keeping in mind the important layers of a real application.
Get Shit Done will create a folder structure with phases. Instead of just giving a prompt and saying "Claude, build this app," we'll have a structure that follows engineering principles, protects client security, helps set up databases, and ensures there's human interaction at every step to test.
One of the best parts of Get Shit Done is that it lets you clear the context regularly and resume with a fresh context. How does it remember everything? It creates a state.md file that lists exactly where things stood. That's context engineering.