Prompts - Page 2 | Toolshed

from my article How to use Claude Code subagents for parallel work Use Claude Code subagents when a focused task can stand alone. Split independent checks, ask for one combined result, and keep dependent work with one owner.

from my article Installing Claude Code without the old Node.js setup Install Claude Code with Anthropic's current native installer on Windows, macOS, or Linux. No Node.js, no npm, and the fixes for when the command is not found.

from my article Keeping your Claude Code project organized Give each file an obvious home, document the stable rules, and test what your deployment actually includes.

from my article Klarna's AI U-turn isn't a failure story Klarna reported faster support and stable satisfaction, while its CEO later said its customer-service cost-cutting went too far. Product leaders need to read both.

from my article Making it look good (and fixing what doesn't) On this site, building the structure was the short part. I spent much longer refining the design.

from my article Most of my AI pipeline isn't AI By volume, most of my AI pipeline is plain Python. The model is a small, expensive part I call as little as possible. The script-first split, and why it wins.

from my article My AI was smart. It just couldn't see my job. My work context was scattered across email, meetings, documents, and notes. So I wired it into a private Obsidian vault Claude Code can read.

from my article One app, many markets: the central vs. local paradox Build centrally and local markets hate you. Build locally and you drown in fragmentation. The model that actually works for multi-market digital products.

from my article One command a day: the skills that run the vault The whole control layer of my work system is a folder of markdown files. How a real workflow is built from Claude Code skills, rules, and parallel sub-agents.

from my article Planning before you build with Claude Code Write down the pages, content, and design constraints before Claude creates files. A short plan gives you something concrete to review and reduces avoidable rebuilding.

from my article Saving your work with Git and going live Two problems to solve: keep a recoverable copy of your work and publish the site without exposing private files.

from my article Stop trying to digitalize everything The biggest trap empowered digital teams fall into: trying to replace every legacy process. Solve for 80% of cases with clean journeys. The rest? Let it go.

from my article Teaching Claude Code your standards with rule files Use CLAUDE.md for project-wide facts and rule files for detailed standards, including rules that load only for matching paths.

from my article The app consolidation playbook Most app portfolios are 80% accident, 20% strategy. The interesting bit isn't deciding what to kill. It's keeping what works locally without paying for it everywhere.

from my article The Claude Code plugins I built and run I put the Claude Code tools I reuse across projects into one public toolshed: generators, workflow commands, anti-slop checks, search visibility, rule packs, and prompts.

from my article The laundry list trap: why half your roadmap doesn't matter We analyzed engagement across an entire app feature set. Over 40% of the scope generated less than 2% of engagement. This is how to avoid building features nobody uses.

from my article The permission tax: when growing teams ship less, not more It took a month to build and three to four months to get permission. Team growth can slow delivery when every decision needs another approval.

from my article The person logging in is not always the customer. Login proves who is at the screen. It does not prove what they own, may manage, or can buy. Model those questions separately before the edge cases arrive.

from my article What is vibe coding (and why you already know how to do it) Andrej Karpathy called it "fully giving in to the vibes." Collins Dictionary made it Word of the Year. What vibe coding actually means, when it works, and how everything you've learned so far has been building toward it.

from my article What using Claude Code actually looks like Using Claude Code is a loop: ask, change, check, decide. Here is what a normal session looks like, six commands worth learning first, and how to recover when it goes wrong.