$ groundwork --start_
Overview
Start as a vibe coder. Learn to think like an engineer.
You can build real software with AI today, before you know a single keyboard shortcut. That's the on-ramp. Groundwork is written for adult learners: start with a quick win, then build the hours, taste, and verification habits that move you toward "I shipped this and I can defend every line."
Want a configured machine now? On a Mac, run the bootstrap below; on Linux, WSL, or a headless workspace, follow Platforms. Want to understand what it did? Start with The path, then use the reference pages when a tool earns its place.
macOS gets the full desktop setup: Homebrew apps, browser helpers, Raycast, Anybox, BetterDisplay, and selected system defaults. Linux/WSL and headless workspaces share the terminal, Git, editor, shell, and agent-instruction layer while skipping Mac-only GUI pieces. See Platforms for the exact split.
$ bash -c "$(curl -fsSL https://raw.githubusercontent.com/jasondockery/groundwork/main/bootstrap-mac.sh)"
#The two modes you're moving between
Groundwork treats AI-native development as a climb, not a gatekeeping exercise. Start with momentum. Then build the judgment, habits, and verification muscles that let you keep moving fast without losing the plot.
Vibe coding
Talk to an agent, accept, run, paste the error back, and ship something that did not exist before. It raises the floor: more people can build sooner. Its ceiling is real: you may not yet understand the system you created.
Agentic engineering
Orchestrate agents while staying accountable for the spec, quality bar, tests, security, and architectural taste. Same speed, professional responsibility. That is the discipline this guide helps you practice.
The useful framing from Andrej Karpathy is simple: vibe coding raises the floor; agentic engineering raises the ceiling. Groundwork is for the person who wants both: the joy of building early and the chops to defend the work later. Read more in Vibe → agentic.
#The path at a glance
You do not learn these tools by reading a catalog. You learn each one when it solves a pain you can feel. The docs are now organized around that journey.
#Why the hours still matter
AI can draft the code. It cannot give you understanding by osmosis. The reps in this guide are how you notice when an agent edited the wrong file, introduced a brittle abstraction, skipped a security boundary, or wrote a test that proves too little.
Ship early. Then put in the reps. The tools fade into the background, your judgment moves to the front, and you build toward moving at AI speed without lowering the bar.
#Use the docs two ways
Why Groundwork
The case for an AI-native development foundation that teaches judgment, not just tools.
journeyThe path
A staged route from first build toward agentic engineering.
referenceCheat sheet
The keyboard and command shortcuts once you know what you are practicing.
machineSetup & chezmoi
What gets installed, how apply works, and how to inspect changes.
ai-nativeAI agents & rules
Project instructions, adapters, skills, and the shared north star.
trackFPS Browser
Build a substantial Three.js arena shooter with AI, read the JavaScript, tune game feel, and ship a URL.
trackFPS Unity
Build the same hard one-week shooter arc in Unity 6 with C#, prefabs, NavMesh, UI, profiling, and WebGL.
trackWeb & sites
Build a single page, style it, add JavaScript, fetch data, and deploy it.
trackApps
Build a small task app with a spec, database, tests, diff review, and deploy.
trackImage & video
Build a reproducible generative-media pipeline with model APIs, seeds, manifests, evaluation, and shipped assets.
learningDevelopment
Deeper routes for Apple apps, web, games, Rust, Python, ML, and LLMs.
outside studyResource library
Books, courses, videos, and practice options for going deeper.