Amit Pitaru

As the march toward the March 2nd grand opening of the Open Vector public commons project approaches, I want to add to the discourse today explaining a real workflow I am doing right now with #claudecode #mural #firefox and just a pretty vanilla IDE stack. The flow: 1️⃣ I work with Julian (Claude Desktop + Google Drive, Github, and Desktop Commander extensions, and Notion MCP connection) to describe what I want, the behaviors, the intent, the user experience, etc. 2️⃣ Julian makes a PRD for the feature, the whole vision for a discrete, contained interaction and experience model. We riff on it, and I say to turn into phased prompts. 3️⃣ Julian makes the prompts as MD files and puts them in a Prompt Hopper in Notion. I then give them to the agents as appropriate (Siddig does backend and API, Heavy does front end, Sellivan does repo management, etc). 4️⃣ The named agents are set to "dangerously ignore permissions" and I set them to plan mode, and paste the prompt which is usually 300-400 lines. NOTE: I never write the initial prompts, my follow up prompts are 1-2 lines. Julian handles the prompts and continuity. 5️⃣ The agent, i.e. Heavy runs the plan and asks questions as needed, and then we "Accept and bypass permissions" and Heavy YOLOs the code. Why do I trust this? 1) I read the plan, 2) we commit after each prompt, 3) we make a branch per feature, 4) we make a worktree when I want to do something big. 6️⃣ When it's done, I check it in the browser, try it out, and either quickly dictate changes directly to the agent, or I paste the agent's prompt-by-prompt standup back to Julian. In cases like the screenshot, I purposfully went light on the layout spec because I knew I would want to wireframe AFTER getting it in the browser. 7️⃣ We repeat this until I like what I see, adding tweaks and enhancements as we go. And, as this is all being built on the principles and guidelines contained in the CLAUDE.md for each agent, the project VECTOR.md, and the extensive REPO-BIBLE/*.md that dictates architecture, usually any console errors or bugs are immediately resolved. 8️⃣ We do this for an hour or 2, and when the feature is done, we tag the branch, merge it, and start over. 🏁 The above would normally be a 2 week sprint. This is not vibe coding. This is not capricious. This is not unstable. This is the future. I am working on a plan to create cirriculum to scale this to teams of any size. You may be asking: but where do you ideate? Where is the design system, the brand, the visual styles? They are wherever you want them to be, the CSS rendering is abstracted out. Pictured: - Left: Claude Desktop (Julian) giving me its optical assessment of my wireframe out of Mural (right). Julian can literally just look at my Mural sketch and interpret it with 100% accuracy, - Right: a screenshot of my 1st-draft UI screenshotted right out of Firefox and pasted into Mural so I could see it. - Right: A Mural-primitives wireframe of the changes I wanted.

18

3 Comments