Screenshot → microservice — opportunistic learning loop
Operators who've never opened a terminal stall on the disciplined kickoff prompt. Watch a video; screenshot a concept; agent builds it.
What
First-week method for an operator who has never opened a terminal: open Claude Code in a folder. While watching a lecture / podcast / video on a phone or second screen, screenshot any concept that catches the eye. Paste directly into the terminal: "what is this? could I build a microservice that does this on my data?" Agent explains in plain language, then implements. Patterns discovered through accumulation, not pre-planning.
Why it matters
One operator verified by witness ("never opened terminal before this") shipped his first ~5 microservices using this loop while his family was at home with him — i.e. in fragmented attention. The opportunistic format is dramatically more accessible than the disciplined kickoff-prompt approach assumed by most vibe-coding playbooks (A-025).
End-to-end
- Open Claude Code in a folder named
screenshots/. Set the working directory. - Configure Cmd-Shift-4 (Mac) or Win+Shift+S (Windows) to save to that folder.
- While watching: snap any screenshot of a concept that interests you.
- Drag into the Claude terminal. Type: "what is this? can I make a microservice for my data?"
- Agent explains. If interesting, ask: "build it for my data — here's a sample CSV." Drag in your data.
- Iterate inline. The conversation IS the learning; don't context-switch to docs.
- End of week: review the screenshots folder + Claude outputs. Patterns will repeat.
Gotchas
- Don't try to plan a 4-week roadmap with this method on day one. The whole point is opportunistic discovery; the planning is a separate exercise (see A-040). Skipping discovery for planning is how a non-technical operator stalls in week 1.
Tools
- Claude Code CLI (with image / paste-image support)
- A screenshot folder + a fast shortcut
- A few sample data CSVs from your own work