I am comparing tools and still learning Claude Code basics
Start with the free cheatsheet. It gives you the command patterns, review reminders, and safe workflow habits you need before paying for anything.
Get the free cheatsheet
Revenue path: free PDF -> paid guide -> consultation
Claude Code Products
Start with the free PDF if you are new. Move to the prompt pack or setup guide when the bottleneck becomes repeatability, quality, or rollout.
If you landed here from a comparison article, do not buy by price alone. Pick the product that matches your current bottleneck.
Best next step after a comparison
Choose by bottleneck, not by tool hype
Most people do not need every product. Use the path below that matches what is blocking you right now.
I already chose Claude Code, but my prompts are inconsistent
Use the prompt pack if the real problem is output quality. It is the fastest upgrade when you keep rewriting review, debugging, and refactoring requests.
Get the prompt packI need a reliable setup for work or team rollout
Use the setup guide when permissions, CLAUDE.md structure, hooks, MCP setup, or team rules matter more than a few better prompts.
Get the setup guideRead before you buy
Three short reads that clarify the next step
If you are not sure whether you need the free PDF, a paid guide, or consultation, start with the article that matches your current bottleneck.
Start safely
First repo audit checklist
Read this first if you need to map a real codebase before giving Claude Code edit permissions.
Set permissions
Permission safety ladder
Use this when setup quality and approval gates are the real blockers before paid workflow materials.
Keep momentum
Obsidian to CLAUDE.md
Start here if your notes are useful but Claude Code still needs the same context explained every session.
Article to offer path
Use the article that matches the bottleneck, then take the next paid step
The latest operational articles are arranged as a funnel. Start with the problem, then follow the suggested product path instead of guessing.
New repo audit
First repo audit checklist
Use this before a first edit so Claude Code maps scope, protected areas, proof commands, and revenue CTA paths.
Best next product
Free cheatsheet -> Setup guide
Permission path
Permission safety ladder
Use this when you need to move from read-only to proof commands, limited edits, and deploy checks without losing control.
Best next product
Setup guide -> Consultation
Context workflow
Obsidian to CLAUDE.md
Use this when notes contain the right context but every Claude Code session still starts from repeated explanations.
Best next product
Prompt pack -> Setup guide
CHEATSHEET
Free
Claude Code Quick Reference Cheatsheet
The free one-page reference for daily Claude Code work.
Keep the essential commands, file-reference patterns, CLAUDE.md reminders, prompting habits, review cues, and debugging workflow notes next to your editor.
Best for
Best first step if you are still learning the commands and safe workflow basics.
Free
View on Gumroad
PROMPT 50
Best Seller
50 Battle-Tested Claude Code Prompt Templates
Copy, paste, ship. 50 production-ready prompts.
A hand-picked collection of prompts for code review, debugging, refactoring, documentation, architecture, and test generation.
Best for
Best when you already use Claude Code but keep rewriting the same prompts.
$9.99
View on Gumroad
SETUP
Guide
The Complete Claude Code Setup & Configuration Guide
From install to a team-ready workflow foundation.
Installation, CLAUDE.md patterns, hooks, MCP servers, permissions, IDE setup, workflow optimization, and CI/CD usage with copy-paste examples.
Best for
Best when the bottleneck is setup quality, permissions, or making Claude Code reliable at work.
$14.99
View on Gumroad
Pick the next step by bottleneck
Get the free cheatsheet if you want commands, prompt reminders, and safer day-one habits next to your editor.
Buy the prompt pack if you already use Claude Code but lose time retyping review, debugging, and documentation requests.
Buy the setup guide if you need better CLAUDE.md structure, permissions, hooks, MCP setup, or team-ready workflow rules.
Book a consultation if the real problem is rollout, workflow design, or turning content traffic into a measurable funnel.
Need a human walkthrough?
Consultation for teams and solo operators
Get a focused session on onboarding, safe permissions, workflow design, or revenue-aware content operations.
In progress
The next English products are being completed one by one. They are not on sale yet because the goal is quality and buyer usefulness, not listing volume.
How to use the draft pipeline
Do not wait blindly. Each draft below already has a matching article that tells you whether the free PDF, an existing paid guide, consultation, or the future product is the right next step.
Claude Code First 30 Minutes Field Guide
DraftBest for first-week users who need one safe win before a bigger rollout.
Read first
Claude Code First 30 Minutes ChecklistUse the free cheatsheet now, then move to this guide when you want a more structured first-session playbook.
Read the matching articleCLAUDE.md Template Pack for Real Projects
DraftBest for people who know the bottleneck is repeated setup drift, not missing commands.
Read first
CLAUDE.md Starter TemplateRead the starter template article first, then decide whether you need multiple project-ready versions.
Read the matching articleClaude Code Code Review System
DraftBest for reviewers who want a reusable severity rubric and stronger review prompts.
Read first
Prompt Library MaintenanceUse the prompt pack now if your review prompts are inconsistent, then upgrade when you need a full review system.
Read the matching articleClaude Code Team Workflow & CI/CD Playbook
DraftBest for leads who need review, branching, CI, and deployment rules across multiple people.
Read first
Permission Safety LadderBook consultation if permissions and deploy gates already affect production, or wait for this playbook if self-serve material is enough.
Read the matching articleClaude Code Debugging & Error Dictionary
DraftBest for developers who lose time translating build, test, deploy, and framework errors into next actions.
Read first
Build Error Triage LoopUse the prompt pack now for reusable debugging prompts, then watch this product if recurring error patterns are the real bottleneck.
Read the matching article