Claude System

A collaborative, project-structured configuration system for Claude Code that streamlines onboarding and accelerates developer productivity. Set up rules, commands, and output styles just once—then share them across your team with a single command. Easily extensible and maintainable for teams of any size.

This system was created as part of my process and designed to be sharable, extendible and very flexible. The goal for this initial template is to provide any engineer interested in Claude Code an initial toolkit.

I've already shared this with several fellow engineers who have found it useful as a starting point in their Code Claude journey.

This system is actively evolving as part of my workflow.

Quick Start

For anyone setting up this configuration system (requires Claude Code CLI installed):

1. Clone and copy the configuration repository to your Claude configs directory

git clone git@github.com:0xjuanma/claude-system.git /tmp/claude-configs && cp -r /tmp/claude-configs/* ~/.claude/configs/ && rm -rf /tmp/claude-configs

1. Start Claude

claude

1. Run the initialization "magic" command; just tell Claude the following:

"Please read ~/.claude/configs/INITIALIZE.md and set everything up"

This will copy the repository locally to ~/.claude/configs/ and tell Claude Code to configure everything: rules, commands, output styles, mcps, context-patterns, presets and discovery tools.

What the initialization does:

• Installs Rules: Commit formats, coding standards, company guidelines - Claude follows these automatically
• Links Commands: Slash commands like /commit, /document become available in your repos
• Activates Output Styles: Switch Claude's behavior with /output-style concise-dev or teaching-mode
• Enables Context Presets: Load complete working contexts (backend, review-mode) instantly
• Installs Tools: claude-rules for discovery, claude-scaffold for project creation
• Configures MCP Servers: Templates for extending Claude with external tools and data sources
• Sets Context Patterns: .claudeignore and .claudecontext templates for controlling file visibility

System Overview

A scalable framework for defining and extending Claude configurations. Global rules provide defaults, project directories add team-specific extensions, and the system grows as you add new projects. Project rules override global rules when conflicts exist.

~/.claude/configs/
├── global/              # Base universal configurations (defaults)
│   ├── rules/           # Claude behavior, commit format
│   ├── commands/        # Universal commands (/commit, /plan, /optimize)
│   ├── output-styles/   # Universal styles (concise-dev, code-reviewer)
│   ├── presets/         # Context presets (backend, review-mode)
│   ├── mcp-servers/     # MCP server configurations (filesystem, git, github)
│   └── context-patterns/# Context file templates (.claudeignore, .claudecontext)
├── project-name/        # Project-specific extensions (team-shareable)
│   ├── rules/           # Project coding standards, MR/PR templates
│   ├── commands/        # Project-specific commands
│   ├── output-styles/   # Project-specific styles
│   └── presets/         # Project context presets
├── meta/                # System management (rule framework, templates)
├── bin/                 # Tools (claude-rules, claude-scaffold)
└── INITIALIZE.md        # Complete setup instructions

Usage Examples

Daily Development

# Discovery tools
claude-rules
claude-rules projects                    # List all projects
claude-rules list global                 # Show global rules

# Generate documentation
/document path/to/service

# Start analysis
/analysis function_name

# Start teaching output style
/output-style teaching-mode
...

# Switch back to default(concise-dev output-style)
/reset 

# Explanation command
/explain subject

# Detailed analysis of function focused on optimizations
/optimize function_C