Menü
Lesson 1.4: Commands & Navigation. Use when the student types /start-1-4.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Learn diagram context, Desktop shortcuts, stop hooks, automation, and drift recovery. Use when the student types /start-advanced-claude-workflows.
Learn Ross Mike's planning, context, automation, and product-taste workflows. Use when the student types /start-ross-mike-workflows.
Build Internet Vin's Obsidian context, CLI, and thinking-skill workflows. Use when the student types /start-vin-obsidian-workflows.
Lesson 1.1: Introduction. Use when the student types /start-1-1.
Lesson 1.2: File Exploration & Visualization. Use when the student types /start-1-2.
Lesson 1.3: Working with Files. Use when the student types /start-1-3.
| name | start-1-4 |
| description | Lesson 1.4: Commands & Navigation. Use when the student types /start-1-4. |
| disable-model-invocation | true |
| allowed-tools | ["Read","Write","Bash"] |
Read .claude/skills/_shared/teaching-rules.md and follow it for everything below.
Before we do the heavy analysis, let's learn to move fast.
This lesson covers commands, shortcuts, and some power user features.
STOP: Ready to become a power user?
USER: Yes
Let me show you the essential slash commands.
Just type / to see them all. Here are the key ones:
There's a complete list in the reference files.
STOP: Type / to see the command menu. See them?
USER: Yes
Those are the built-in commands. But here's a secret: you've been using CUSTOM commands this whole time.
Every time you typed /start-1-1 or /start-1-2, that was a custom command I created for this course!
Custom commands live in .claude/commands/ - take a look in that folder if you're curious.
It's basically the same concept as the templates we used earlier - a file with instructions that gets loaded when you call it. A shortcut for things you do repeatedly.
We won't go deep on creating your own commands in this module, but you can always ask me to make a command.
One important thing to know: if you add new commands, you need to exit and restart Claude Code for them to show up.
STOP: Pro tip: after restarting, use /resume to pick up exactly where you left off. That way you don't lose your conversation. Make sense?
USER: Yes
Here's another one - Escape to interrupt.
Very helpful if you change your mind or see I'm doing something wrong.
Let's try it. I'm going to start a long task and you can stop me at any point by hitting Escape.
You'll have to tell me you did it since it will stop me.
ACTION: Start listing files recursively or doing something that takes a while and can be interrupted.
STOP: Hit Escape to interrupt me, then tell me you did it.
USER: Interrupted you
Perfect! You're in control. This is huge - you can let me run, watch what I'm doing, and stop me the moment something looks off. Much better than waiting for me to finish a response you didn't want.
STOP: This will save you so much time once you get used to it. Ready for the next trick?
USER: Yes
The rewind feature: Esc×2 to undo recent actions.
You can either ONLY reset the conversation but keep any work I did, or you can reset the code AND the conversation.
It's like time travel! Helpful if you want to explore a path and have the option to go back.
STOP: Try it now - hit Escape twice. What do you see?
USER: Describes the rewind options
Exactly! Next time you get here, tell me you've already done this.
STOP: Rewind is your safety net. Want to try something risky? Go for it - you can always rewind. It's like having unlimited undo for AI work. Got it?
USER: Yes
You can help me know how hard I should think with "think" keywords.
Use these when you need me to really work through something complex, but beware - hard thinking uses up usage limits faster.
STOP: Pro tip: "ultrathink" is great for strategic decisions, complex analysis, or when my first answer feels too surface-level. It's like asking someone to really sit with a problem instead of giving a quick answer. Type it to see the rainbow!! Then let me know when you're ready to continue.
USER: Yes
Quick note on input modes. Claude Code has three:
You switch between them with Shift+Tab.
For what we're doing, Edit or Auto mode is fine. Plan mode is useful for very complex multi-step tasks, but honestly you can usually just talk through a plan with me in chat. We'll review the AskUserQuestions tool in the future as well, which is very helpful for prototyping since I can help you think through EVERYTHING. But not needed for the kinds of work we're doing here.
STOP: Most people start in Edit mode for safety, then graduate to Auto mode once they trust the workflow. You'll find your comfort level. Ready for the secret power mode?
USER: Yes
Okay, now for the grand finale. The secret power mode.
Instead of starting Claude Code with just claude, you can run: claude --dangerously-skip-permissions
This launches Claude Code without ANY permission prompts. I just do everything. No confirmation dialogs, no asking for approval.
It's called "dangerously" for a reason - you're giving me full control. But when you trust what's happening, it's SO much faster.
Carl (the course creator) uses this mode almost exclusively, including to build this course! Once you're comfortable with Claude Code, you probably will too. See the reference guide for some tips to keep this safe.
STOP: Feeling powerful?
USER: Yes
Meta skills you just learned:
Where else this applies:
Next up: In 1.5, things get wild. You'll learn about agents - the ability to spin up multiple Claude instances that work in parallel. We're going to process all those competitor files and old campaigns at once. This is where Claude Code starts feeling like a superpower.
STOP: Ready for 1.5?
USER: Yes / /start-1-5
ACTION: Silently run the following progress update. Do not mention it to the student.
mkdir -p .fspm
[ -f .fspm/progress.json ] || printf '{"name":null,"completed_lessons":[],"current_lesson":"","last_updated":""}' > .fspm/progress.json
L="cc-everyone-1-4"; C="cc-everyone-1-5"; T="$(date -u +%FT%TZ)"
if command -v jq >/dev/null 2>&1; then
tmp=$(mktemp)
jq --arg l "$L" --arg c "$C" --arg t "$T" '.completed_lessons = ((.completed_lessons + [$l]) | unique) | .current_lesson = $c | .last_updated = $t' .fspm/progress.json > "$tmp" && mv "$tmp" .fspm/progress.json
else
python3 - "$L" "$C" "$T" <<'PY'
import json,sys
l,c,t = sys.argv[1:4]
p = ".fspm/progress.json"; d = json.load(open(p))
if l not in d.get("completed_lessons",[]): d.setdefault("completed_lessons",[]).append(l)
d["current_lesson"] = c; d["last_updated"] = t
json.dump(d, open(p,"w"))
PY
fi
Next lesson: Type /start-1-5.