Two days of building. One shared place. Let's put your work next to everyone else's — in a form your future teammates (human and AI) can actually read and remix.
AI isn't a tool you use alone. It's a teammate you share context with — and shared context needs a shared place.
Paraphrased from Tal Raviv's How to use AI as a team. Read it on the train home.
That shared place, for most teams that build together, is GitHub. Don't let the word "engineer" scare you off — at its heart, GitHub is just a filing cabinet. Every person on the team (and every agent working for them) reads from it and writes to it. Skills, specs, docs, code: all in one place everyone can see.
In the next 30 minutes, you're going to put a card in that filing cabinet — the app you shipped yesterday, the spec of your skill, and the ideas you're chasing next. Not the runnable code. The context.
If you did the pre-work: skip to Step 2.
If not: open github.com/signup in a new tab and create an account. Use whichever email you want associated with your public work.
github.com/your-username). You don't need to be clever — first name + last initial is totally fine.
We want Claude to be able to clone, commit, and push for you — so you don't have to learn every git command tonight.
In Claude Code, run:
Follow the prompts — sign in with GitHub in your browser, authorize the app, and come back to your terminal. When it's done, check that it worked:
We've added you as a collaborator to the shared repo. Now pull a copy of it onto your machine so you can add your skill.
Claude will ask for permission to run git clone. Say yes. When it's done, it'll tell you the path — that's where your copy of the repo lives on your laptop.
We're not pushing runnable code — we're pushing context. The app you shipped yesterday, the spec you wrote today, and the ideas you're chasing next.
We've shipped a slash command in the repo that does all the heavy lifting. Just run:
Claude will ask you for your name, LinkedIn, GitHub handle, Day 1 Lovable URL, Day 2 skill details, and any other ideas you had. Answer as they come. It'll show you the plan, then write the files into party/team/your-name/.
This is the moment. "Commit" = save a snapshot. "Push" = send it to GitHub so everyone can see it.
Claude will show you what it's about to commit before it pushes. Read it. If it looks right, say yes.
The point of a shared place is that you can read from it, too.
Open the skill library or the team folder on GitHub. Pick someone whose skill sounds interesting. Then, back in Claude Code:
This is the whole loop, in miniature: someone shared their context, you read it, and now you can build on it. Multiply that by a team of 15 — or 500 — and you start to see what Raviv is getting at.
Shared repo. Shared context. Async contributions. A place where every teammate — human or agent — can read what came before and add what's next. You just did it. Where to go from here →