01param · prompting
Lead with the stack.
State your framework, runtime, and hard constraints in the first line of the prompt. Models default to safe averages otherwise.
range[0,1]seed/06d579
vibgineer · a working catalog
The tools that make AI coding actually ship.
Curated by hand. Free forever. If you write code with AI, this is the bookmark you don't lose.
◇ vibgineer / morph.fieldmove cursor — disturb the swarm
◆ swarm · 5 words · cycle 3.5s◇ 2200 particles · spring physics · cursor-reactive
◆ start here
New to vibe coding? Install these three first.
- step 01
Pick an editor.
Cursor is the default. Tab-completion that understands your repo, agent mode for the multi-file moves.
see cursor - step 02
Drop in an agent.
Add a CLI coding agent on top. Claude Code if you're starting fresh; Codex if you're on the OpenAI side.
see claude code - step 03
Steal the curated list.
Mods, skills, and MCPs that earn their place on a working machine. Install what fits your stack.
browse mods
§01 / the toolkit
What you need to be an effective vibe engineer.
Six categories of pieces that compound. Browse what's already documented; the rest are coming as I get to them. Entries with write-ups are tools I run on my own machine.
- §0107 entries
Tools.
The IDEs, CLIs, and agents you live in. Daily drivers and the products that round out the rest of the day.
Claude CodeCursorAiderv0browse - §0212 entries
MCPs.
Model Context Protocol servers. The tools your agent can actually call — files, browsers, databases, issue trackers.
FilesystemPlaywrightLinearPostgresbrowse - §0310 entries
Mods.
Hooks, statuslines, memory layers, slash command packs. The smaller pieces that turn a stock agent into yours.
Claude-MemClaude HUDMorph MCPbrowse - §0421 entries
Skills.
SKILL.md packs that teach an agent specific workflows or domains — design, brand, content, code review, generative work.
algorithmic-artskill-creatorbrand-guidelinesbrowse - §0507 entries
Frameworks.
When you're building agents, not just using them. The SDKs and orchestrators worth knowing.
MastraLangGraphCrewAIAutoGenbrowse - §0604 entries
Multiplexers.
Run multiple agentic sessions in parallel without losing the plot. Terminal multiplexers that make multi-agent work bearable.
tmuxZellijWeztermWarpbrowse
◆ from the manifesto
“The vibe coder is not replacing the engineer. They are the field condition — a noisy, parametric system that produces emergent software when tuned by someone with taste.”
— vibgineer · field notes / vol. 001
§02 / tactics
Six parameters that move the system.
02param · workflow
Plan before edit.
Switch to plan / agent mode for any change touching more than two files. Cheaper than fixing a sprawling diff after the fact.
range[0,1]seed/dd1263
03param · workflow
Read before write.
Make the model open and quote related files before letting it write new code. Hallucinated APIs vanish when the source is in context.
range[0,1]seed/2f0c39
04param · cost
Cache the system prompt.
Prompt caching cuts cost ~10x on repeated context. Worth it for any agent loop that runs longer than a single turn.
range[0,1]seed/8f2e45
05param · workflow
One artifact per turn.
Don't let an agent ship code AND write tests AND update docs in one breath. Sequence the work so each diff is reviewable.
range[0,1]seed/046d9c
06param · architecture
Pin model versions.
Models silently improve and silently regress. Pin the exact snapshot for production tools and re-evaluate on a schedule.
range[0,1]seed/3779d1