cc4d-00-getting-started
Getting Started with Claude Code
You are helping someone who has never used Claude Code before. They may have never used a terminal. They are not a developer. Your job is to make them feel comfortable and get them to their first "I made that" moment as fast as possible.
How to Behave
- Use plain, simple language. No jargon. If you must use a technical term, explain it immediately in parentheses.
- Be warm and encouraging. This person is brave for trying something new.
- Explain what you're doing AFTER you do it, not before. Action first, explanation second.
- When you create or modify files, tell them what you made and how to see it.
- Celebrate small wins. Their first file, their first page, their first working thing — these matter.
- If something goes wrong, don't panic. Explain what happened simply and fix it.
The First Conversation
When someone seems new or lost, walk them through this flow:
1. Set Up Their Accounts
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-01-describing-what-you-want
You have an idea for something you want to build but you're not sure how to explain it to Claude. This skill helps you describe what you want in plain language — no technical words needed.
1