Guide Claude for Optimal Code Generation

This skill is a comprehensive reference for configuring and using Claude Code, the agentic coding tool, synthesizing best practices, configuration templates, and advanced usage patterns. It centers on the CLAUDE.md project-guideline file, created in a project's root directory to guide the agent, with a general template covering commands, code style, and workflow:

# Project Guidelines

• Run app: npm run dev
• Test: npm test
• Build: npm run build

• Use TypeScript for all new code.
• Functional components with Hooks for React.
• Tailwind CSS for styling.
• Early returns for error handling.

• Read README.md first to understand project context.
• Before editing, read the file content.
• After editing, run tests to verify.

It also documents "thinking keywords" that trigger deeper reasoning in prompts ("Think step-by-step", "Analyze the root cause", "Plan before executing", "Verify your assumptions"), debugging steps for a stuck or unexpectedly-behaving agent (clearing context / starting a new session, being extremely specific about paths and filenames, asking the agent to check logs or run with verbose output), and best practices around context size (locate relevant files with grep/find rather than dumping the whole codebase into context), iterative development (small changes, verify, then proceed), and feedback loops (correct a mistake immediately and ask the agent to add a lesson to its memory or CLAUDE.md).

Use it when setting up a new project for Claude Code, writing or refining a CLAUDE.md file, or troubleshooting an agent that is stuck, confused, or producing unexpected output. It is not a substitute for environment-specific validation, testing, or expert review of the agent's output.

The input is the situation at hand: a new project needing a CLAUDE.md, a prompt that needs a thinking keyword to get deeper reasoning, or a debugging scenario. The output is the relevant template or technique: a filled-in CLAUDE.md covering commands/style/workflow, a specific thinking-keyword phrase to add to a prompt, or a concrete debugging step (clear context, be more explicit, check logs).

Developers configuring or troubleshooting Claude Code on a project, who want a synthesized reference of configuration templates and usage patterns instead of re-deriving best practices from scratch. Based on the Claude Code Guide by zebbern.