01
Understand
Clarify the work before implementation starts.
Minimal jargon, because the goal is understanding.Short sections, because attention is precious.Visible proof, because trust should be earned.
Workflow Garden
A calmer way to understand the workflow behind the shipping.
Workflow Garden now behaves like an archive instead of a single long explainer. Start with an article, jump into a project, or browse the diary when you want to see how the workflow looks in real use.
The workflow beats
A system for turning fuzzy work into visible, provable progress.
The workflow joins planning, implementation, proof, and shipping instead of treating them as separate chores. Each step answers a different question and leaves behind evidence another person can inspect.
02
Build
Build on a ticket branch that maps cleanly to one issue.
03
Prove
Treat proof as evidence, not as a polite summary.
04
Ship
Only call it done once deploy, merge, and cleanup line up.
Tool map
Major tools and when to use them.
The site keeps the original educational framing, but presents each lane like an archive module instead of a generic tab set.
Navigation 01
When the work is still fuzzy
Understand
Start by turning the idea into something everyone can agree on.
This lane is for turning a vague idea into a plan. It keeps the work from jumping straight into code before anyone knows what success looks like.
repo-bootstrap
Set up a new repo so the next agent knows the workflow, commands, and proof bar.
write-a-prd
Translate a rough product idea into a plain-language PRD with clear user stories.
prd-to-plan
Turn that PRD into thin, demoable phases instead of one giant to-do list.
prd-to-issues
Create the actual execution issues that branches and PRs will follow.
Navigation 02
When the shape is clear
Build
Use reliable primitives, then spend creativity on composition and clarity.
Build mode is about small, reversible changes. Mature primitives reduce risk. Strong page composition keeps the work from looking like a stack of generic cards.
shadcn-ui
De-risk the tricky basics like tabs, accordions, buttons, and sheets.
frontend-design
Choose a real visual direction instead of shipping generic AI-looking layouts.
critique
Challenge the design early so structural problems get fixed before polish.
gh + Linear
Keep the implementation branch, PR, and planning state lined up.
Navigation 03
When the page works
Prove
Passing code checks is useful. Visible evidence is what builds trust.
Proof mode asks a simple question: can another person see that this actually works and actually looks right? If the answer is unclear, the proof is not done yet.
audit
Run a quality pass across accessibility, responsive behavior, and anti-patterns.
polish
Fix the last alignment, spacing, copy, and interaction details before shipping.
design-proof
Fail the pass if normal desktop, wide desktop, or mobile screenshots are compositionally weak.
acceptance-proof
Run the real user journey in a browser and fail if the screenshots do not hold up.
Navigation 04
When the evidence is strong
Ship
Close the loop all the way through deploy, merge, and cleanup.
Shipping is not just pushing code. It means the work is live, the issue state is accurate, the proof exists, and the implementation branch is no longer lingering around.
vercel
Push the MVP to a real public URL so the proof can reference a live surface.
gh
Reuse one PR, merge it cleanly, and close the linked issue from the merge.
Linear
Move planning state only when the proof and merge state genuinely line up.
README proof screenshots
Turn internal proof artifacts into a public, inspectable record of the shipped result.
Reading room
Articles that turn repeated names into real explanations.
Instead of leaving tool names and workflow terms floating around the page, the archive now gives them a place to land.
Planning chain
How write-a-prd, prd-to-plan, and prd-to-issues fit together
The workflow separates idea, plan, and execution issue so each stage stays readable and auditable.
Planning · 5 min
Proof bar
What proof means: design-proof vs acceptance-proof
design-proof checks whether the page looks coherent, while acceptance-proof checks whether the real user journey works and can be inspected.
Proof · 4 min
Skill article
Why repo-bootstrap exists
repo-bootstrap sets the rules, commands, docs, and proof bar before feature work starts.
Skills · 4 min
Foundation
What agent skills are
Skills are reusable instruction packs that let the workflow stay consistent instead of depending on one-off chat context.
Foundation · 4 min
Projects
Concrete examples, not just workflow theory.
Project pages connect the explanation to real repos, live URLs, and diary evidence so visitors can see how the workflow behaves in practice.
Featured project
Workflow Garden
A public educational site that turns an issue-driven AI workflow into something a visitor can understand.
Live · Educational site
Proof-heavy example
Proof Pack
A public project centered on visible evidence, browser proof, and inspectable output.
Live · Proof workflow
Live example
Choice Compass
A weighted decision helper prototype built through the full workflow chain.
Live · Decision helper
Setup path
Start small, keep the proof bar high, and do not skip the cleanup.
This first-run path mirrors the behavior of the workflow itself. It helps you bootstrap the repo, write the plan, ship from a branch with a ticket attached, and then prove the result before merge.
- 01
Bootstrap a clean repo
Create the folder, set the repo rules, and make the README useful from the first day.
repo-bootstrapgh repo creategit init -b main - 02
Write the plan in normal language
Turn a rough product idea into a PRD, then slice it into independently shippable work.
write-a-prdprd-to-planprd-to-issues - 03
Ship from one ticket branch
Keep the implementation narrow enough that one issue, one branch, and one PR still feel natural.
git checkout -b raj-37-…gh pr creategh pr merge --delete-branch - 04
Require proof before celebration
Run the real browser flow, inspect the screenshots, then decide whether the work actually passes.
playwright-clidesign-proofacceptance-proof
Deeper notes
Expand each step only when you need the deeper explanation.
The overview stays skim-friendly, while the accordion keeps the real commands and proof expectations available at the point of need.
Automated diary
Daily coding activity, filtered until it becomes worth reading.
The diary generator scans file changes under /Users/rajeev/Code, looks for a meaningful signal, and only then creates entries. That keeps the public story curated and readable.
Open the full diary archiveWhat the generator ignores
Tiny one-file nudges, noisy build output, and other low-signal churn do not become diary entries. The site would rather be quiet than noisy.
Multi Agent Orchestration DemoExplainer
Multi Agent Orchestration Demo: Retry slow generations on a faster model lane and Harden and ship multi-agent orchestration demo
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on Retry slow generations on a faster model lane and Harden and ship multi-agent orchestration demo.
It turns workflow claims into something visitors can inspect instead of simply trust.
The what
Multi Agent Orchestration Demo spent the day on Retry slow generations on a faster model lane, Harden and ship multi-agent orchestration demo, and pull request template.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Today
2026-03-23
3 projects produced archive-worthy movement, with the strongest signals landing in interface work, educational content, and proof and validation.
Read this day in detailPi Mono
Article
Broad move
Pi Mono: Add [Unreleased] section for next cycle and Release v0.62.0
At a glance
The strongest movement landed in educational content, testing, and configuration, with visible work on Add [Unreleased] section for next cycle and Release v0.62.0.
The what
Pi Mono spent the day on Add [Unreleased] section for next cycle, Release v0.62.0, and complete changelog entries for unreleased changes.
So what
It makes the archive more dependable and less reliant on manual cleanup or heroic memory.
Explore next
Explore agent skills next to see the public context around this work.
Concrete moves
- Add [Unreleased] section for next cycle
- Release v0.62.0
- complete changelog entries for unreleased changes
gitignoreCHANGELOGthe repo command surfacemodels.generated
Research
Explainer
Deep move
Research: Category shortlists and followed profiles top repos
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on category shortlists and followed profiles top repos.
The what
Research spent the day on category shortlists, followed profiles top repos, and inventory analysis.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore agent skills next to see the public context around this work.
Concrete moves
- category shortlists
- followed profiles top repos
- inventory analysis
category shortlistsfollowed profiles top reposinventory analysisgitignore
Sun 22 Mar
2026-03-22
3 projects produced archive-worthy movement, with the strongest signals landing in interface work, educational content, and proof and validation.
Read this day in detailWorkflow Garden
Explainer
Steady move
Workflow Garden: Refresh diary publishable outputs and Repair diary refresh publish loop
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on Refresh diary publishable outputs and Repair diary refresh publish loop.
The what
Workflow Garden spent the day on Refresh diary publishable outputs, Repair diary refresh publish loop, and Deepen diary detail and copy quality.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore Workflow Garden next to see the public context around this work.
Concrete moves
- Refresh diary publishable outputs
- Repair diary refresh publish loop
- Deepen diary detail and copy quality
the environment contractthe plain-language READMEthe project pagesthe operator docs
Rajeevg.com
Explainer
Steady move
Rajeevg.com: Ui: keep mermaid diagrams readable on narrow screens and content: remove duplicate article h1
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on ui: keep mermaid diagrams readable on narrow screens and content: remove duplicate article h1.
The what
Rajeevg.com spent the day on ui: keep mermaid diagrams readable on narrow screens, content: remove duplicate article h1, and site: simplify public content and refresh about page.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore What proof means: design-proof vs acceptance-proof next to see the public context around this work.
Concrete moves
- ui: keep mermaid diagrams readable on narrow screens
- content: remove duplicate article h1
- site: simplify public content and refresh about page
the plain-language READMEdocker gcloud deploymentfrom ai pilots to business valuehello world
Openrouter Model Workbook Maintainer V2
Showcase
Broad move
Openrouter Model Workbook Maintainer V2: Gh-3 Relax rate-limit fallback match and gh-3 Add rate-limit fallback for daily refresh
At a glance
The strongest movement landed in interface work, educational content, and workflow setup, with visible work on gh-3 Relax rate-limit fallback match and gh-3 Add rate-limit fallback for daily refresh.
The what
Openrouter Model Workbook Maintainer V2 spent the day on gh-3 Relax rate-limit fallback match, gh-3 Add rate-limit fallback for daily refresh, and gh-3 Make daily refresh fall back to repo secrets.
So what
It makes the workflow easier to understand at a glance, which is where public trust starts.
Explore next
Explore OpenRouter Model Workbook Maintainer V2 next to see the public context around this work.
Concrete moves
- gh-3 Relax rate-limit fallback match
- gh-3 Add rate-limit fallback for daily refresh
- gh-3 Make daily refresh fall back to repo secrets
the environment contractcidaily refreshgitignore
Sat 21 Mar
2026-03-21
3 projects produced archive-worthy movement, with the strongest signals landing in interface work, educational content, and proof and validation.
Read this day in detailWorkflow Garden
Explainer
Deep move
Workflow Garden: Implement selective linked diary pipeline and Build the project content hub
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on Implement selective linked diary pipeline and Build the project content hub.
The what
Workflow Garden spent the day on Implement selective linked diary pipeline, Build the project content hub, and Fix tools tabs overlap proof gap.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore Workflow Garden next to see the public context around this work.
Concrete moves
- Implement selective linked diary pipeline
- Build the project content hub
- Fix tools tabs overlap proof gap
the environment contractpull request templategitignoreinfisical
Proof Pack
Explainer
Broad move
Proof Pack: Add proof screenshots to the project readme and fix wide-screen composition in the project
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on add proof screenshots to the project readme and fix wide-screen composition in the project.
The what
Proof Pack spent the day on add proof screenshots to the project readme, fix wide-screen composition in the project, and rebuild the landing composition and harden the design gate.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore Proof Pack next to see the public context around this work.
Concrete moves
- add proof screenshots to the project readme
- fix wide-screen composition in the project
- rebuild the landing composition and harden the design gate
the environment contractpull request templategitignoreinfisical
Choice Compass
Explainer
Broad move
Choice Compass: Add explicit design gate for mobile task order and refresh live proof after redeploy
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on add explicit design gate for mobile task order and refresh live proof after redeploy.
The what
Choice Compass spent the day on add explicit design gate for mobile task order, refresh live proof after redeploy, and polish mobile flow and add PR workflow.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore Choice Compass next to see the public context around this work.
Concrete moves
- add explicit design gate for mobile task order
- refresh live proof after redeploy
- polish mobile flow and add PR workflow
the environment contractpull request templategitignorethe repo workflow guide
Fri 20 Mar
2026-03-20
3 projects produced archive-worthy movement, with the strongest signals landing in educational content, workflow setup, and automation.
Read this day in detailProperty Search
Tutorial
Broad move
Property Search: : cover crawl smoke registry fallback and : harden crawl smoke source pinning
At a glance
The strongest movement landed in educational content, workflow setup, and automation, with visible work on : cover crawl smoke registry fallback and : harden crawl smoke source pinning.
The what
Property Search spent the day on : cover crawl smoke registry fallback, : harden crawl smoke source pinning, and Finish RAJ-10 crawl smoke source selection.
So what
It lowers the barrier for someone who is curious about the workflow but not yet fluent in developer tooling.
Explore next
Explore Property Search next to see the public context around this work.
Concrete moves
- : cover crawl smoke registry fallback
- : harden crawl smoke source pinning
- Finish RAJ-10 crawl smoke source selection
the environment contractpull request templatecicodeql
Pi Mono
Tutorial
Broad move
Pi Mono: Add [Unreleased] section for next cycle and Release v0.61.1
At a glance
The strongest movement landed in educational content, workflow setup, and plain-language docs, with visible work on Add [Unreleased] section for next cycle and Release v0.61.1.
The what
Pi Mono spent the day on Add [Unreleased] section for next cycle, Release v0.61.1, and update unreleased changelog entries.
So what
It lowers the barrier for someone who is curious about the workflow but not yet fluent in developer tooling.
Explore next
Explore agent skills next to see the public context around this work.
Concrete moves
- Add [Unreleased] section for next cycle
- Release v0.61.1
- update unreleased changelog entries
oss weekendwrthe plain-language READMECHANGELOG
Tools
Showcase
Deep move
Tools: The plain-language README and CLAUDE
At a glance
The strongest movement landed in interface work, educational content, and automation, with visible work on the plain-language README and CLAUDE.
The what
Tools spent the day on the plain-language README, CLAUDE, and gitignore.
So what
It makes the workflow easier to understand at a glance, which is where public trust starts.
Explore next
Explore agent skills next to see the public context around this work.
Concrete moves
- the plain-language README
- CLAUDE
- gitignore
the plain-language READMECLAUDEgitignorethe repo workflow guide
Thu 19 Mar
2026-03-19
3 projects produced archive-worthy movement, with the strongest signals landing in educational content, workflow setup, and testing.
Read this day in detailPi Mono
Showcase
Broad move
Pi Mono: /model shows stale scoped models and approve contributor zmberber
At a glance
The strongest movement landed in educational content, workflow setup, and testing, with visible work on /model shows stale scoped models and approve contributor zmberber.
The what
Pi Mono spent the day on /model shows stale scoped models, approve contributor zmberber, and add resizable share sidebar.
So what
It makes the workflow easier to understand at a glance, which is where public trust starts.
Explore next
Explore Why one issue, one branch, and one PR matters next to see the public context around this work.
Concrete moves
- /model shows stale scoped models
- approve contributor zmberber
- add resizable share sidebar
APPROVED CONTRIBUTORSconfigispr
Property Search
Tutorial
Broad move
Property Search: Align CI pnpm version with packageManager and Add initial project scaffold, docs, and fixtures
At a glance
The strongest movement landed in educational content, workflow setup, and automation, with visible work on Align CI pnpm version with packageManager and Add initial project scaffold, docs, and fixtures.
The what
Property Search spent the day on Align CI pnpm version with packageManager, Add initial project scaffold, docs, and fixtures, and config.toml.
So what
It lowers the barrier for someone who is curious about the workflow but not yet fluent in developer tooling.
Explore next
Explore Property Search next to see the public context around this work.
Concrete moves
- Align CI pnpm version with packageManager
- Add initial project scaffold, docs, and fixtures
- config.toml
config.tomlthe environment contractcigitignore
Auto Audit Harness
Explainer
Broad move
Auto Audit Harness: ARCHITECTURE and QUALITY SCORE
At a glance
The strongest movement landed in interface work, educational content, and proof and validation, with visible work on ARCHITECTURE and QUALITY SCORE.
The what
Auto Audit Harness spent the day on ARCHITECTURE, QUALITY SCORE, and the plain-language README.
So what
It turns workflow claims into something visitors can inspect instead of simply trust.
Explore next
Explore audit next to see the public context around this work.
Concrete moves
- ARCHITECTURE
- QUALITY SCORE
- the plain-language README
ARCHITECTUREQUALITY SCOREthe plain-language READMERELIABILITY