Claude Code Standards

Overview

Centralized repository for Claude Code commands, agents, and skills. Copy resources to your projects for instant productivity.

Why this exists: Single source of truth for Claude Code standards across all teams.

What's New (v3.0.0)

• ✅ Single .claude/ at root: Simplified structure, domain-organized
• ✅ Cross-domain support: Commands that work across frontend + backend
• ✅ Apps directory: Local clones for agent visibility across codebases
• ✅ 33 shared commands: Git, quality, tickets, utilities (deduplicated)
• ✅ 13 frontend commands: Framework-specific only (Ember/React/Figma)
• ✅ 11 agents: Categorized (review, analysis, refactor, generation)
• ✅ 14 skills: Auto-activating validation
• 🆕 CodeRabbit AI integration: Pre-push AI review with auto-generated fix plans
• 🆕 Architect-Editor pattern: /quick-plan + /build-from-spec for surgical implementations

Latest Updates (Dec 16, 2025) ⭐

• 🆕 Skill naming alignment with Platform standards: All 14 skills renamed to gerund form
  • Follows official Platform best practices
  • Examples: validating-design-system, generating-tests, documenting-code
  • See /docs/SKILL_NAMING_MIGRATION.md for complete mapping
  • Updated all documentation: SKILL_GUIDELINES.md, INDEX.md, README.md
• ✅ Enhanced validating-design-system skill: 100% CSS property coverage (40+ properties)
  • Comprehensive hardcoded value detection (spacing, sizing, typography, borders, outlines)
  • Real MR review examples from team feedback
  • Verified: Caught 65/65 violations in production testing
• ✅ Integrated quality-review workflow: Design system validation now built-in
  • Explicit skill invocation before CodeRabbit (saves review cycles)
  • Section 6a adds comprehensive SCSS validation
  • Prevents "lets use variables" reviewer comments
• 🆕 Pre-merge quality review workflow: Complete documentation
  • 5-step sequential validation process
  • Real-world examples with actual output
  • Quick reference cheat sheet
  • Location: .claude-context/workflows/pre-merge-quality-review-workflow.md

Quick Start

For immediate use:

# 1. Clone standards repo
git clone https://gitlab.com/shift4payments/legacy/lighthouse/alexandria/claude-code-standards.git
cd claude-code-standards

# 2. Sync to your project (one command!)
./sync-to-project.sh /path/to/your/project

# 3. Start using
cd /path/to/your/project
# In Claude Code: /quality-review

That's it! ✅ You now have 90+ commands, 11 agents, 14 skills, and ADW automation (coming soon).

---

Full Installation Guide

Prerequisites

• Claude Code Desktop App
• Node.js 18+ (for MCP servers)
• Git

Installation Options

Option 1: Automated Sync (Recommended)

# 1. Clone this repository
git clone https://gitlab.com/shift4payments/legacy/lighthouse/alexandria/claude-code-standards.git
cd claude-code-standards

# 2. Sync to your project (preserves existing work)
./sync-to-project.sh /path/to/your/project

Option 2: Manual Copy

# 1. Clone this repository  
git clone https://gitlab.com/shift4payments/legacy/lighthouse/alexandria/claude-code-standards.git
cd claude-code-standards

# 2. Navigate to your project ROOT (where IDE opens)
cd /path/to/your/project

# 3. Copy BOTH Claude folders to project root
cp -r ~/claude-code-standards/.claude .
cp -r ~/claude-code-standards/.claude-context .

Verify structure:

your-project/
├── .claude/           ← Commands and resources  
├── .claude-context/   ← Generated artifacts
├── app/ (or src/)     ← Your application code
└── package.json       ← Project files

4. Update .gitignore

cat >> .gitignore << 'EOF'

Claude Code

.claude/.local/ .claude/scratch/ .claude-context/tickets/* !.claude-context/tickets/TEMPLATE/ .claude-context/local/ EOF

5. Commit

git add .claude/ .claude-context/tickets/TEMPLATE/ git commit -m "feat: add Claude Code standards"

### Updating to Latest Standards

**Get latest updates (preserves your work):**
```bash
# From standards repo directory
cd claude-code-standards
git pull origin main
./sync-to-project.sh /path/to/your/project

✅ Smart sync: Updates .claude/ folder, preserves existing tickets in .claude-context/

Verification

# Check setup
ls -la .claude/commands/
ls -la .claude-context/tickets/TEMPLATE/

# Test command
# In Claude Code: /quality-review

MCP Setup (Optional)

# In Claude Code
/setup-mcp user

See MCP Configuration Guide.

---

Repository Structure

claude-code-standards/
├── .claude/                     # All resources at root
│   ├── commands/
│   │   ├── shared/             # Cross-domain (33 commands)
│   │   ├── frontend/           # Frontend-specific (13 commands)
│   │   ├── backend/            # Backend-specific
│   │   └── cross-domain/       # Multi-domain orchestration
│   ├── agents/                 # 11 agents (categorized)
│   ├── skills/                 # 14 skills
│   ├── ai_docs/                # AI context documentation
│   ├── templates/              # Resource templates
│   └── config/                 # Configuration
│
├── .claude-context/            # RFC-compliant context
│   ├── tickets/TEMPLATE/       # Ticket workflow template
│   ├── templates/              # MR templates
│   └── design-specs/           # Figma extractions
│
├── apps/                       # Local clones (gitignored)
│   ├── frontend/               # Your frontend repo
│   ├── backend/                # Your backend repo
│   └── infrastructure/         # Your infra repo
│
└── docs/                       # Documentation
    ├── usage/                  # Usage guides
    ├── architecture/           # Architecture decisions
    └── guides/                 # How-to guides

---

Resources

Commands by Domain

Shared (35 commands):

• Git (5): commit-refs, create-branch, squash-commits, generate-mr, pre-commit-check
• Quality (8): quality-review, lint-all, lint-changed, clean-comments, implementation-review, quick-review, validate-components, validate-implementation
• Tickets (7): start-ticket, ticket-context, ticket-impl, cleanup-ticket, resume-context, spawn-agents, migrate-ticket
• Planning (2): 🆕 quick-plan, build-from-spec (Architect-Editor pattern)
• GitLab (2): gitlab-review, gitlab-review-extract
• Utilities (3): setup-mcp, analyze-problem, discover-code
• Maintenance (2): sync-resources, update-ember-conventions-skill
• Bugs (2): bug-quick-fix, bug-resolve
• Learning (2): fetch-docs, skills-sharpener
• Docs (1): generate-presentation
• Execution (1): implement

Frontend (13 commands):

• Figma (6): Design extraction and specification generation
• Design (3): Design QA and validation workflows
• Bugs (1): Ember-specific bug resolution
• Git (1): React-specific pre-commit checks
• GitLab (1): Frontend pipeline status checks
• Tickets (1): Ember implementation planning

Backend:

• Ready for expansion

Cross-Domain:

• Multi-domain coordination (coming soon)

Agents (11 total)

Review: code-reviewer, implementation-reviewer, gitlab-mr-code-review-extractor Analysis: code-cleanup, skills-enrichment-agent Refactor: refactoring Generation: (Ready for expansion)

Skills (14 total)

Naming Convention: All skills use gerund form (verb + -ing) per Platform best practices

Code Quality: validating-code-cleanup, validating-design-system ⭐ (enhanced Dec 15), handling-errors, analyzing-security Performance: analyzing-performance, optimizing-databases Development: debugging, generating-tests, documenting-code Styling: styling-with-scss, validating-markdown-style Presentation: generating-presentations Framework: enforcing-ember-conventions Project Management: creating-jira-tickets

Highlighted: validating-design-system now has 100% CSS property coverage (40+ properties validated)

---

Documentation

Getting Started

• Quick Start - Installation and setup
• CONTRIBUTING.md - How to contribute
• 🆕 Agentic Workflow Diagram - Visual SDLC workflow guide

Core Documentation

• CLAUDE.md - Repository guidance for Claude Code instances
• Apps Usage Guide - Using commands from apps/ directory
• MCP Configuration - MCP server setup

Development

• 🆕 Action Items - Development roadmap with missing workflows & improvements
• Changelog - Version history and changes
• Organization Guide - Repository structure rules
• Skill Guidelines - Skill development standards
• 🆕 Skill Best Practices - Managing skills across projects
• 🆕 Skill Naming Migration - Gerund form naming alignment (Dec 16, 2025)

Architecture

• Repository Structure - Current repository organization and deployment model
• Restructure Analysis - MVP restructure impact assessment

Templates

• Command Template - Create new commands
• Skill Template - Create new skills

---

Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

Quick contribution steps:

1. Fork repository
2. Create feature branch from development
3. Use templates for new resources
4. Test in real project
5. Submit PR to development

---

Team

Maintainer: Simon Cheam (@simoncheam)

Contributors: Frontend Team, Standards Team

---

Links

• GitLab Repository
• Issue Tracker
• Internal RFC v2.0 - Implementation review & Phase 2 roadmap
• Original RFC (Confluence) - Historical reference

---