agentsclimarketplace

Claude code guide skills sickn33 claude code guide

Skill bg-szy/TOP-SKILLS/skills/marketplace/claude-code-guide__skills-sickn33-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.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill claude-code-guide__skills-sickn33-claude-code-guide

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 435 tokens by cl100k_base, as published. Nobody here has run it

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)

# 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.

What ships with it: 1 file

17.2 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,286. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.