prepcli

prepcli

stop re-explaining.
start building.

The AI that already knows your project.

works withClaude CodeCursorAntigravityCodex
01

every session starts from scratch.

You open an AI session on a project you've been building for months. The AI has no idea who you are, what you've built, or what matters. It asks the same basic questions it asked last week. You paste the same context block you always paste. Explain the same constraints. And the conversation that should start with solving your problem starts with onboarding the AI — again.

what the AI asks every single time
? what tech stack are you using?
? are there any rules or files to avoid?
? what have you already tried?
? what was decided in the last session?
? any third-party services involved?
same questions. different day. no memory.
02

the "why" behind every decision disappears.

Someone removed a library three months ago. You don't remember why. The code doesn't say. The commit message says 'cleanup'. An AI working on the same feature today will confidently suggest that exact library again — because it has no idea it was a deliberate choice. That's not just annoying. It's how hours get wasted rediscovering decisions that were already made.

looking at your codebase 6 months later
commit: removed date-fns library
commit: auth middleware made read-only
commit: switched away from Redis sessions
why any of this happened: no record.
what was tried before: no record.
03

nothing you teach the AI ever sticks.

Every correction you make after hitting GO is gone by the next session. Every constraint you explain, every pattern you establish, every 'don't do it that way' — erased. You're not building shared understanding with your AI. You're filling a bucket that empties every time you close the tab. And the AI keeps suggesting the same things you keep rejecting.

the AI, session after session
suggestion: use date-fns for dates
suggestion: try moment.js as a fallback
suggestion: add Redis for session storage
all three: already removed or ruled out.
the AI has no memory of any of it.

then the AI
remembered.

01

the AI walks in already knowing your project.

After a one-time setup, every AI session starts with your full project knowledge already loaded — silently, before the first word. Your tech stack, your team's rules, recent decisions, things that are off-limits, and unresolved questions. The AI doesn't ask what framework you're using. It doesn't suggest what you've already rejected. It operates as if it's been on your team for months.

loaded before the session begins
stack: Next.js 15 · TypeScript 5 · tRPC · Prisma
rule: date-fns is removed — causes timezone bugs
rule: auth module is off-limits (legal requirement)
rule: keep bundle under 200kb — no heavy libraries
last decision: JWT tokens expire after 7 days max
open question: payment retry logic still unresolved
ready. no re-explanation needed.
02

every important decision is saved and searchable.

When a session ends, prepcli quietly records what was done, why that approach was chosen, what was tried and rejected, and what constraints were in play. That record travels with your codebase — anyone who clones the repo can see the full reasoning, linked to the exact code change it produced. Six months from now, when someone asks 'why is it built this way?' — the answer is already there.

prepcli log — your full decision history
May 24 · debug · 3 turns · commit a4f2c1d
fixed calendar — removed date-fns
why: UTC+5:30 half-hour offsets break silently
tried: dayjs, moment.js — same root issue
ruled out: all external timezone libraries
May 20 · plan · 5 turns · commit def456
JWT refresh: sliding window, hard 7-day cap
03

a new teammate hits the ground running.

Your project's full history — every decision, every rule, every lesson learned — travels with the repository. When a new developer joins, they run two commands and immediately have the same context the rest of the team built over months. The AI they work with is already calibrated to your codebase. No ramp-up wiki. No 'ask the senior dev.' No re-learning what was already figured out.

new teammate · day one · two commands
$ git clone github.com/company/project
$ prepcli auth login && prepcli install
stack loaded: Next.js 15 · TypeScript · tRPC
41 team decisions available from history
12 active rules applied to this session
same context as the rest of the team. day one.

Six structured workflows installed into your AI tool. Each starts with your project context already loaded and ends with a decision record saved automatically.

prepcli workflows
/debug
diagnose a bug — properly
Starts with your full project context already loaded. Asks four sharp questions about the specific bug — informed by how similar issues have played out in your codebase before. Gives you a structured diagnosis with root cause and fix, not a generic guess.
/plan
plan before you write a line
Catches every ambiguity and hidden conflict before any code is written. Checks what you are planning against your existing rules and past decisions. Surfaces integration risks. Saves hours of rework.
/prep
turn a rough idea into a precise brief
Takes your messy task description and turns it into a complete, scoped prompt — with context, constraints, and boundaries made explicit. The AI knows exactly what to do before you say GO.
/refactor
clean up code — without breaking things
Knows which parts of the codebase are off-limits, what patterns your team uses, and what was already tried and rejected. Improves the code without undoing decisions that were made on purpose.
/review
review against your actual standards
Reviews code against your team's real conventions — not generic internet advice. Catches violations specific to your codebase. Doesn't flag decisions your team made deliberately.
/write
write docs that match reality
Writes documentation that reflects how your project actually works today — your terminology, your architecture, your decisions. Not a generic template with your project name filled in.
# 1. install globally — once, any machine
$curl -fsSL https://prepcli.in/install.sh | bash
or: npm install -g @prepcli/prepcli
# 2. sign in with just your email
$prepcli auth login
# 3. read your project once — remembers it forever
$prepcli init
↳ context saved. never needs to repeat.
# 4. add six commands to your AI tool
$prepcli install
↳ /debug /plan /prep /refactor /review /write
↳ Claude Code · Cursor · Antigravity · Codex
set up once, never configure again
Run one command in your project folder. prepcli reads your codebase and builds a picture of it. From the next session onward, every AI you work with starts already knowing your project.
works inside the tools you already use
No new app to learn. No browser tab to switch to. prepcli adds six commands directly inside Claude Code, Cursor, Antigravity, or Codex — the tools your team already uses every day.
your codebase stays completely clean
Nothing extra gets added to your main code. All the history prepcli tracks is stored invisibly alongside your project — readable by your team, invisible to anyone just looking at the code.
free to start, no credit card
The full core experience — all six commands, the decision log, and session recording — is completely free. Upgrade when you want the AI to start improving its questions automatically over time.
live now
  • prepcli installdrops all six commands into Claude Code, Cursor, Antigravity, and Codex
  • prepcli auth loginsign in with just your email — no passwords, no third-party accounts
  • prepcli initreads your project once, remembers it forever
  • prepcli contextsee exactly what the AI knows about your project right now
  • prepcli logbrowse every AI decision linked to the commit where it happened
  • prepcli session addrecords each AI turn as it happens — works offline, no login needed
  • prepcli recordsave any decision to the history yourself, any time
  • 6 slash commands/debug /plan /prep /refactor /review /write
coming soon
  • quality trackingsee how many corrections you had to make after saying GO — and watch it drop
  • smarter questionsquestions that learn from your sessions and stop missing the same things twice
  • session analyticswhich workflows are improving, which gaps keep coming up, and how it trends
  • team sharingshared rules and history across the whole team — not just your own sessions
  • setup checkone command that tells you exactly what is not configured and how to fix it
  • before vs after reportshow much back-and-forth you had 3 months ago vs today

start building
with memory.

Works with Claude Code, Cursor, Antigravity, and Codex. Two commands to set up — from the next session, the AI already knows your project.