Claude Code Guide
Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent.
Works with
--- name: Claude Code Guide description: Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent. license: MIT --- # Claude Code Guide ## Purpose To provide a comprehensive reference for configuring and using Claude Code (the agentic coding tool) to its full potential. This skill synthesizes best practices, configuration templates, and advanced usage patterns. ## Configuration (`CLAUDE.md`) When starting a new project, create a `CLAUDE.md` file in the root directory to guide the agent. ### Template (General) ```markdown # Project Guidelines ## Commands - Run app: `npm run dev` - Test: `npm test` - Build: `npm run build` ## Code Style - Use TypeScript for all new code. - Functional components with Hooks for React. - Tailwind CSS for styling. - Early returns for error handling. ## Workflow - Read `README.md` first to understand project context. - Before editing, read the file content. - After editing, run tests to verify. ``` ## Advanced Features ### Thinking Keywords Use these keywords in your prompts to trigger deeper reasoning from the agent: - "Think step-by-step" - "Analyze the root cause" - "Plan before executing" - "Verify your assumptions" ### Debugging If the agent is stuck or behaving unexpectedly: 1. **Clear Context**: Start a new session or ask the agent to "forget previous instructions" if confused. 2. **Explicit Instructions**: Be extremely specific about paths, filenames, and desired outcomes. 3. **Logs**: Ask the agent to "check the logs" or "run the command with verbose output". ## Best Practices 1. **Small Contexts**: Don't dump the entire codebase into the context. Use `grep` or `find` to locate relevant files first. 2. **Iterative Development**: Ask for small changes, verify, then proceed. 3. **Feedback Loop**: If the agent makes a mistake, correct it immediately and ask it to "add a lesson" to its memory (if supported) or `CLAUDE.md`. ## Reference Based on [Claude Code Guide by zebbern](https://github.com/zebbern/claude-code-guide).
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

