๐Ÿ Playbooks 3.2 Check-In
This one is foundational. The folder structure you build locally is what GitHub stores and serves. Get this right and Claude Code wastes zero tokens figuring out your project.
๐Ÿ’ฌ Drop Your Answer in the Comments
1. Open your .gitignore file right now. How many lines are in it? Bonus: is there anything in there you don't recognize?
2. How long is your CLAUDE.md? The target is 30-50 lines. If you're over 100, what could you move into a folder-level README instead?
3. Have you ever accidentally pushed something that should have stayed local? No judgment. Share so others can learn from it.
โœ… Action Step
If you haven't done this yet: create a throwaway repo, upload any index.html file, turn on Pages, confirm you get a live URL. Three minutes. Do it before moving to Lesson 3.3.
Post your GitHub Pages URL in the comments when it's live.
Quick Gut Check
Why does folder structure matter for Claude Code?
๐Ÿ—‚๏ธ It looks more professional
๐Ÿงญ Claude reads CLAUDE.md and knows exactly where to go
๐Ÿ’พ GitHub requires a specific layout
๐ŸŽจ It makes the website load faster
9 votes
3
2 comments
Matthew Creamer
7
๐Ÿ Playbooks 3.2 Check-In
Clief Notes
skool.com/quantum-quill-lyceum-1116
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by