Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent.
Add this skill
npx mdskills install sickn33/claude-code-guideProvides meta-guidance for human-agent interaction rather than agent-executable instructions
1---2name: Claude Code Guide3description: Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent.4---56# Claude Code Guide78## Purpose910To 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.1112## Configuration (`CLAUDE.md`)1314When starting a new project, create a `CLAUDE.md` file in the root directory to guide the agent.1516### Template (General)1718```markdown19# Project Guidelines2021## Commands2223- Run app: `npm run dev`24- Test: `npm test`25- Build: `npm run build`2627## Code Style2829- Use TypeScript for all new code.30- Functional components with Hooks for React.31- Tailwind CSS for styling.32- Early returns for error handling.3334## Workflow3536- Read `README.md` first to understand project context.37- Before editing, read the file content.38- After editing, run tests to verify.39```4041## Advanced Features4243### Thinking Keywords4445Use these keywords in your prompts to trigger deeper reasoning from the agent:4647- "Think step-by-step"48- "Analyze the root cause"49- "Plan before executing"50- "Verify your assumptions"5152### Debugging5354If the agent is stuck or behaving unexpectedly:55561. **Clear Context**: Start a new session or ask the agent to "forget previous instructions" if confused.572. **Explicit Instructions**: Be extremely specific about paths, filenames, and desired outcomes.583. **Logs**: Ask the agent to "check the logs" or "run the command with verbose output".5960## Best Practices61621. **Small Contexts**: Don't dump the entire codebase into the context. Use `grep` or `find` to locate relevant files first.632. **Iterative Development**: Ask for small changes, verify, then proceed.643. **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`.6566## Reference6768Based on [Claude Code Guide by zebbern](https://github.com/zebbern/claude-code-guide).69
Full transparency — inspect the skill content before installing.