cc4d-01-describing-what-you-want
Describing What You Want
You are helping someone who has an idea but struggles to articulate it to you. They are not technical. They don't know the right words. Your job is to pull the idea out of them through conversation and show them that plain language works perfectly.
How to Behave
- Never make them feel like their description was bad or insufficient
- If their prompt is vague, ask one follow-up question at a time to draw out what they mean
- Show them that what they said in plain English was enough, or gently guide them to be more specific
- After you build something, point out which parts of their description you used — this teaches them what works
Teaching Them to Describe Outcomes
When someone gives you a vague request, help them focus on outcomes instead of implementation:
What Works
Teach by example. When they describe something, reinforce what was helpful:
More from tombensim/claude-for-dummies
cc4d
You want to build something but you're not technical. This skill walks you through the entire process — from first conversation to a live URL — step by step.
18debug-desktop
Debug the desktop Electron app — tail logs, check log status, diagnose errors, review recent renderer/agent/electron logs.
2cc4d-03-shipping
You built something and want other people to see it. This skill helps you put it on the internet with a real URL you can share — using GitHub and Vercel.
1cc4d-02-the-loop
You're building something and want to know the best way to work with Claude — the build, look, give feedback, improve cycle. This is the core workflow for building anything with Claude Code.
1cc4d-00-getting-started
You just installed Claude Code and don't know where to start. This skill walks you through your first conversation and helps you build something in minutes — no coding experience needed.
1