claude-guide

Configure Claude Code and organize CLAUDE.md, rules, commands, skills, and agents.

9|Updated Jan 31, 2017
One-click install
npx skills add https://github.com/ssiumha/dots --skill claude-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-guide
Source: https://github.com/ssiumha/dots/tree/main/prompts/skills/claude-guide
Command: npx skills add https://github.com/ssiumha/dots --skill claude-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code setup guidance helps teams structure CLAUDE.md, rules, commands, skills, and agents, and reviews CLAUDE.md to streamline Claude-based automation across projects.

Core Features & Use Cases

  • Clear overview of Claude Code configuration types: CLAUDE.md, rules/, commands/, skills/, agents/
  • Review and align CLAUDE.md with project needs
  • Recommendations on what to include in CLAUDE.md and when to create additional skills or agents
  • Use cases: project onboarding, consistent governance, scalable automation

Quick Start

Example: request "설정" or "가이드" to review CLAUDE.md, then adapt to the project, and decide which sections to populate first.

Frequently Asked Questions about claude-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure CLAUDE.md for Claude Code projects?

CLAUDE.md serves as the core configuration file for Claude Code automation. Organize it with modular folders: rules/ for governance, commands/ for quick shortcuts, skills/ for reusable packages, and agents/ for independent workflows. This structure determines load order and enables scalable, project-wide guidance while keeping core rules centralized and accessible.

What should I include in CLAUDE.md versus separate skills or agents?

Include in CLAUDE.md: core rules, environment variables, deployment steps, troubleshooting guidance, and service endpoints. Create separate skills for reusable, modular task packages and agents for independent workflows. Review your CLAUDE.md regularly to align with project needs and decide which sections to populate first based on team priorities.

How do I review and align my existing CLAUDE.md with project requirements?

Review CLAUDE.md by auditing its coverage against functional requirements: documented rules, quick commands, service endpoints, environment variables, deployment steps, and troubleshooting. Adapt sections to your project context, then decide which folders to populate first. This alignment streamlines Claude-based automation and ensures consistent governance across teams.

Can I use Claude Code configuration for project onboarding?

Yes. A well-structured CLAUDE.md with clear rules, commands, and deployment guidance accelerates onboarding by giving new team members instant access to project conventions, quick shortcuts, and troubleshooting steps. Organize modular skills and agents so contributors understand which components to reference for their tasks.

What's the difference between rules, commands, skills, and agents in Claude Code?

Rules define governance and constraints applied project-wide. Commands provide quick shortcuts for frequent tasks. Skills are reusable, modular packages solving specific problems independently. Agents are independent workflows orchestrating multiple actions. CLAUDE.md centralizes rules and core guidance; separate folders enable skill separation planning and scalable automation.

How do I plan skill separation and decide when to create a new skill?

Create a new skill when you have a reusable, self-contained task package with clear inputs and outputs that serve multiple workflows. CLAUDE.md templates guide skill definition. Plan separation by identifying modular functions, ensuring each skill has independent components, and documenting how skills interact within your agents.