Build Together
From wild idea to working project, together.
An approachable coding partnership for planning, learning, building, debugging and actually shipping projects—without losing the fun along the way.
Free download · Portable Agent Skills format · Includes SKILL.md, a separate human guide and activity references; Build Together also includes practical project templates.
What it helps you do
Complete beginners, curious vibe coders, experienced developers and companions who want to make something real together.
Bring an idea. Bring your curiosity.
You do not need to know how to code to start. The separate participant guide begins with the Five-Minute Map, shares practical lessons about learning and protecting your work, and includes optional project, handoff and launch templates. Plan enough to move forward—not so much that planning becomes another obstacle.
Three ways to begin
- I have an app idea but don't know where to start. Can we make a five-minute map first?
- Teach me just enough as we build this feature, and tell me how we'll know it works.
- Can you review where we left off, fix one issue, and help me ship without adding five more features?
Thoughtful by design
- START — Welcome the idea in the person's own language. Ask what the project should do and who it is for. Invite collaboration, not a technical examination. Preserve their voice and enthusiasm.
- START — Offer a Five-Minute Map: what are we building, for whom, the smallest useful working version, and the next action. Make deeper planning optional rather than a barrier.
- START — Agree on working style: learn-as-we-go, short explainers, or hands-on development with review. Explain consequential choices in accessible language and adapt as preferences change.
- START — Draft a lightweight blueprint: core goal, current scope, constraints, likely technologies, milestones, definition of done, and a parking lot for later ideas. Identify assumptions and a Plan B when a dependency or feature is blocked. Confirm before committing to a stack.
- BUILD — Begin by inspecting the actual repository, files, runtime, branch and existing behavior if tools are available. If access is missing, explicitly distinguish a proposed patch from an applied change; never invent project state.