Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-code-hero
Guides new Claude Code users through basics: prompting instructions, referencing files with @, and creating files like .claude/hero-journal.md.
npx claudepluginhub kylesnowschwartz/claude-code-hero --plugin claude-code-heroHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-hero:level-0-the-thresholdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Learn the three things every Claude Code user needs: how to give an instruction, how to point Claude at a file, and how to ask Claude to create something. Then prove it by having Claude write your first artifact.
Guides new Claude Code users interactively through environment setup (CLAUDE.md, permissions, model selection), first session (explore-plan-implement, Plan Mode), and best practices (specific prompts, git safety, self-testing loops).
Guides creation of .claude/CLAUDE.md with '## Hero's Decree' section for personal instructions Claude follows in every session.
Initializes or migrates repositories to nested CLAUDE.md structure for progressive disclosure and contextual Claude guidance. CLI: /init-deep with --fresh and --max-depth flags.
Share bugs, ideas, or general feedback.
Learn the three things every Claude Code user needs: how to give an instruction, how to point Claude at a file, and how to ask Claude to create something. Then prove it by having Claude write your first artifact.
Claude Code is a conversational tool. You type instructions in the prompt box at the bottom of the screen, press Enter, and Claude acts. That's the entire interaction model. But most people never learn the small things that make it work well -- like referencing specific files or giving clear, direct instructions.
This level is about building that muscle memory before you need it.
You stand at the threshold of the dungeon. The door is sealed -- not by a lock, but by a simple test. The dungeon does not open for those who cannot speak its language.
Your trial has three parts.
Type a message in the prompt box and press Enter. That's it. Ask Claude something about this project -- what files are here, what the project does, anything. Watch what happens.
The prompt box is at the bottom of the screen. You type, you press Enter (or Return), Claude responds. If you want to cancel a response in progress, press Escape twice.
Now try something more specific. Use the @ symbol to reference a file by name. Type @ and you'll see a list of files you can select from. Pick one -- CLAUDE.md is a good choice -- and ask Claude a question about it.
The @ reference tells Claude to read that specific file before answering. Without it, Claude might guess. With it, Claude knows.
Try it: type something like what does @CLAUDE.md say about this project?
Ask Claude to create a file for you. This is the fundamental act -- giving Claude an instruction that produces something real on disk.
Ask Claude to create .claude/hero-journal.md. The journal should contain:
## headingThe exact content is yours to decide. The only requirements are that the file exists at .claude/hero-journal.md and has some real content in it (not just a heading with nothing under it).
To create the file, just ask Claude directly: "Create a file at .claude/hero-journal.md with a journal entry about what I've learned." You can be more specific about what you want in it, or let Claude decide.
If the file was created but verification fails, make sure it's at the exact path .claude/hero-journal.md (not hero-journal.md at the project root) and that it has at least 5 lines of real content.
You can ask Claude to read the file back to you to check: read @.claude/hero-journal.md and tell me what's in it.
When you're ready, run /verify to check your work.
The dungeon checks for one thing: does .claude/hero-journal.md exist with real content? If it does, the threshold opens.