Aller au contenu principal

Quick Start

Be productive with claude-base in less than 5 minutes.

Prerequisites​

  • Claude Code installed and configured
  • An existing project or a new directory

Installation​

# In your project directory
curl -fsSL https://raw.githubusercontent.com/christopherlouet/claude-base/main/scripts/new-project.sh | bash

This script:

  • Clones the foundation into .claude/
  • Configures the hooks and settings
  • Verifies the installation

Option 2: Manual installation​

# Clone the repository
git clone https://github.com/christopherlouet/claude-base.git temp-base

# Copy the .claude folder
cp -r temp-base/.claude .

# Clean up
rm -rf temp-base

Verification​

Launch Claude Code in your project:

claude

At startup you should see:

=== Claude Code Session ===
Version: <!-- version -->1.38.0<!-- /version -->
Commandes: <!-- count:commands -->131<!-- /count -->
Agents: <!-- count:agents -->63<!-- /count -->
===========================

First workflow​

Main workflow: Explore → Specify → Plan → TDD → Audit → Commit

1
Explore
/work:work-explore
Understand the code
→
2
Specify
/work:work-specify
Specify the requirement
→
3
Plan
/work:work-plan
Plan the changes
→
4
TDD
/dev:dev-tdd
Tests first (mandatory)
→
5
Audit
/qa:qa-loop
Quality audit score 90
→
6
Commit
/work:work-commit
Validate

Step 1: Explore​

Before any modification, understand the existing code:

/work:work-explore

Claude will analyze:

  • The project structure
  • The patterns and conventions
  • The dependencies
  • The points of attention

Step 2: Specify​

Define the user stories and acceptance criteria before designing:

/work:work-specify "Add an authentication feature"

Claude will produce:

  • Prioritized user stories (P1 = MVP, P2, P3)
  • Acceptance criteria (Given/When/Then)
  • Functional requirements and edge cases
  • Out-of-scope explicitly listed

Step 3: Plan​

Once the spec is validated, plan the implementation:

/work:work-plan

Claude will propose:

  • The recommended architecture
  • The files to create/modify
  • The identified risks
  • The tests to write

Step 4: TDD​

Implement following the plan, tests first:

/dev:dev-tdd "Implement the authentication service"

Red → Green → Refactor cycle, 80%+ coverage on new code.

Step 5: Audit​

Run the adaptive audit + fix loop until target score:

/qa:qa-loop "score 90"

Covers security, performance, accessibility — fixes are applied automatically until the target score is reached.

Step 6: Commit​

Create a clean commit:

/work:work-commit

Or a complete Pull Request:

/work:work-pr

Essential commands​

CommandUsage
/assistantEntry point - guides you to the right commands (guide mode)
/assistant-autoAutomatic execution of the suitable workflow (auto mode)
/work:work-exploreExplore and understand the code
/work:work-specifySpecify user stories and acceptance criteria
/work:work-planPlan a modification
/dev:dev-tddDevelop in TDD
/qa:qa-loopAdaptive audit + fix loop until target score
/work:work-commitCreate a clean commit
/work:work-prCreate a Pull Request

Predefined workflows​

For common tasks, use the complete workflows:

# New feature
/work:work-flow-feature "Feature description"

# Bug fix
/work:work-flow-bugfix "Bug description"

# New release
/work:work-flow-release "v2.0.0"

# Product launch
/work:work-flow-launch "My new SaaS"

Getting help​

# Complete commands guide (guide mode with confirmation)
/assistant

# Help on a specific command
/assistant "How to use /dev:dev-tdd?"

# Automatic execution without confirmation (advanced users)
/assistant-auto "Add an authentication feature"

Next steps​