The Playground
becomes a playground.
Six sessions taught the stack. Starting now, the Thursday hour is not a lecture — it is an open build room. Bring a problem. Bring a use case. Bring a half-broken idea. Problem-solvers and problem-creators, together. One hour. One problem. Solved, started, or scoped.
The shift
The first six sessions were scaffolding. Vibe coding, GitHub, knowledge bases, CLI, hooks, skills, protocol, build, and — in S6 — the collective craft. Enough. From here on, the scaffolding stops being the subject and becomes the substrate. We build on top of it, together, on real problems.
Each Thursday introduced a concept — tools, CLI, skills, plugins, protocol. One host, one topic, a room that mostly listened. It got everyone to basecamp.
Thursdays are now working sessions. People bring real problems from real projects. The room works them out together. If a session turns up a concept worth teaching, we teach it — but only when the room needs it.
What stays. What changes.
- What stays: Thursday, 5:00–6:00 PM. The room. The recordings. The site. The readings. The willingness to be wrong in public.
- What changes: There is no default speaker. No pre-written agenda. The content is whatever the room brings. A session exists only if someone walks in with a problem or an interest.
- What grows: The Skills Portal, the Design Library, the shared guardrails, the AI groups. Every working session produces reusable output that gets pushed back into these.
Three kinds of people in the room
You walk in with a real thing you’re trying to solve — a build, a bug, a client ask, a half-idea. The room works it with you. Your problem becomes the session.
You’ve done the thing before. You jump in, unblock the bringer, share the skill or the trick, and move on. Nihaan, Ankit, Aditya, Abhinav, Harshdeep — most weeks, at least one is in the room.
You’re curious, not stuck. You come to get inspired, to learn by watching, or to spot a problem worth solving that nobody has named yet. Silent is welcome. Curious is welcome.
You don’t need to pick a role in advance. Walk in as one, leave as another.
How a Thursday runs
Bring a problem
What counts as a problem.
Anything you’re stuck on, curious about, or half-building. Don’t pre-polish it. The messy ones are the best ones.
- A Claude Code flow that doesn’t quite work yet.
- A Frappe DocType pattern you’re not sure is the right one.
- A client ask that sounds like three smaller asks in a trench coat.
- A skill you want to write but keep postponing.
- A piece of the mGrant or mForm codebase that nobody has looked at in two quarters.
- A question about security, design, or data that keeps coming up and never gets answered.
Next Thursday
Six sessions in, the scoreboard
The rules of the room
Come if you can. Leave when you must. No attendance register. No guilt. The sessions are optional and meant to be valuable because of that.
Problems beat presentations. If you have a problem, it outranks anyone’s prepared deck. The room’s time is for the real thing, not the rehearsed thing.
Did someone already solve this? First question, every time. Check the AI groups, the Skills Portal, the Design Library. Use theirs, or contribute a PR.
No stupid questions. Stupid answers, sometimes. If you don’t know, don’t pretend. If someone else doesn’t know, don’t make them feel it.
The artifact is the point. Every session should leave behind something reusable — a skill, a PR, a checklist, an MCP, a note. If nothing gets pushed, nothing happened.
Problem-creators are welcome to sit silent. You don’t have to speak to be in the room. Curiosity is a contribution.