How-To Guides

1 Navigate to Baseline Directory

cd {{BASELINE_ROOT}}

2 Run the Script

.\new-project.ps1 `
    -ProjectName "MyAwesomeApp" `
    -DestinationPath "{{PROJECT_PATH}}"

3 Add Optional Parameters (if needed)

.\new-project.ps1 `
    -ProjectName "MyAwesomeApp" `
    -DestinationPath "{{PROJECT_PATH}}" `
    -CompanyName "ACME Corporation" `
    -InitGit `
    -Verbose

-CompanyName replaces {{COMPANY_NAME}} in templates
-InitGit creates a git repository
-Verbose shows detailed output

4 Review Output

The script will:

• Create directory structure
• Copy baseline documentation
• Copy coding standards
• Replace template variables
• Create claude_wip/ directory
• Initialize git (if requested)
• Verify all files

5 Open Your New Project

cd {{PROJECT_PATH}}
code .

1 Preview Changes (Dry-Run)

Always start with a dry-run to see what would happen:

.\add-baseline-to-existing-project.ps1 `
    -ProjectPath "[YOUR-PROJECT-PATH]" `
    -DryRun

This shows you what would be copied/created without actually doing it.

2 Review Conflicts

The dry-run will report any conflicts:

CONFLICT: [YOUR-PROJECT-PATH]\CLAUDE.md already exists
CONFLICT: [YOUR-PROJECT-PATH]\docs\baseline\README.md already exists

Choose a conflict resolution strategy:
- skip: Skip conflicting files (safest)
- suffix: Add .baseline suffix to new files
- interactive: Ask for each conflict
- alternate-directory: Place in baseline_proposed/

3 Choose Conflict Resolution

Select the strategy that fits your needs:

# Option A: Skip conflicts (safest)
.\add-baseline-to-existing-project.ps1 `
    -ProjectPath "[YOUR-PROJECT-PATH]" `
    -ConflictStrategy "skip"

# Option B: Add suffix to new files
.\add-baseline-to-existing-project.ps1 `
    -ProjectPath "[YOUR-PROJECT-PATH]" `
    -ConflictStrategy "suffix"

# Option C: Interactive prompts
.\add-baseline-to-existing-project.ps1 `
    -ProjectPath "[YOUR-PROJECT-PATH]" `
    -ConflictStrategy "interactive"

# Option D: Alternate directory
.\add-baseline-to-existing-project.ps1 `
    -ProjectPath "[YOUR-PROJECT-PATH]" `
    -ConflictStrategy "alternate-directory"

4 Apply Changes

Run without -DryRun to apply:

.\add-baseline-to-existing-project.ps1 `
    -ProjectPath "[YOUR-PROJECT-PATH]" `
    -ConflictStrategy "skip" `
    -BackupStrategy "selective"

5 Verify Results

Check the output for:

• Backup location (e.g., .baseline-backup-20250115-143022/)
• Files copied successfully
• Conflicts skipped or resolved
• Rollback instructions (if needed)

1 Copy Agent Templates

Copy agents to Claude Code's agent directory:

# Create agents directory if it doesn't exist
mkdir C:\Users\{{USERNAME}}\.claude\agents -Force

# Copy agent templates
copy {{BASELINE_ROOT}}\agents\*.md C:\Users\{{USERNAME}}\.claude\agents\

2 Verify Installation

dir C:\Users\{{USERNAME}}\.claude\agents

You should see all 8 agent .md files.

1 Invoke an Agent

In Claude Code, type the agent name:

@gen-docs

2 Provide Context

Give the agent the files or code to work with:

@gen-docs Please document the API endpoints in src/api/endpoints.php

3 Review and Refine

The agent will generate output based on its specialization. You can then:

• Ask for revisions
• Request different formats
• Add more context
• Combine with other agents

1 Identify the Standard to Modify

Standards are modular - find the one you need:

coding-standards/
├── 01-pseudo-code-standards.md
├── 02-php-standards.md
├── 03-javascript-standards.md
└── ... (13 total)

2 Make a Backup

copy coding-standards\02-php-standards.md coding-standards\02-php-standards.md.backup

3 Edit the Standard

Open in your editor and modify:

code coding-standards\02-php-standards.md

4 Update Cross-References

If you change section names, update references in:

• coding-standards/README.md (navigation hub)
• Other standards that reference this one
• CLAUDE.md if applicable

5 Document Your Changes

Add a note at the top of the modified standard:

# PHP Coding Standards

**Customized for ACME Corporation - Last Updated: 2025-01-15**

**Changes from baseline:**
- Added Symfony-specific guidelines
- Modified namespace conventions
- Added company-specific security requirements

1 Template Files Contain Variables

Example from README.md:

# {{PROJECT_NAME}}

**Company:** {{COMPANY_NAME}}
**Repository:** {{REPO_PATH}}
**Last Updated:** {{DATE}}

2 Script Replaces Variables

When you run new-project.ps1:

.\new-project.ps1 `
    -ProjectName "MyAwesomeApp" `
    -CompanyName "ACME Corp" `
    -DestinationPath "{{PROJECT_PATH}}"

3 Result is Customized

The created file becomes:

# MyAwesomeApp

**Company:** ACME Corp
**Repository:** {{PROJECT_PATH}}
**Last Updated:** 2025-01-15

1 Edit the PowerShell Script

Add your variable to new-project.ps1:

# Add parameter
param(
    [string]$ProjectName,
    [string]$Author,  # New parameter
    # ... other params
)

# Add to replacement map
$replacements = @{
    '{{PROJECT_NAME}}' = $ProjectName
    '{{AUTHOR}}' = $Author  # New variable
    # ... other replacements
}

2 Use in Templates

Add to baseline templates:

**Author:** {{AUTHOR}}
**Contact:** {{AUTHOR}}@company.com

3 Use When Creating Projects

.\new-project.ps1 `
    -ProjectName "MyApp" `
    -Author "John Smith" `
    -DestinationPath "[YOUR-PROJECT-PATH]"

Execution Policy Error

Error: "cannot be loaded because running scripts is disabled"

Solution:

# Check current policy
Get-ExecutionPolicy

# Set to allow scripts (run as Administrator)
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Path with Spaces Error

Error: Script fails when path contains spaces

Solution: Use quotes around paths:

.\new-project.ps1 `
    -ProjectName "MyApp" `
    -DestinationPath "[YOUR Projects\myapp"  # Quoted path

Permission Denied

Error: "Access to the path is denied"

Solution:

• Run PowerShell as Administrator
• Check folder permissions
• Ensure destination folder is not open in another program

Variables Not Replaced

Symptom: Created files still contain {{PROJECT_NAME}} etc.

Solutions:

• Verify you're using the latest script version
• Check that variable names match exactly (case-sensitive)
• Use -Verbose flag to see replacement details

Git Init Fails

Error: "git is not recognized"

Solution:

• Install Git from git-scm.com
• Add Git to PATH
• Or omit -InitGit flag

Agent Not Found

Error: "@gen-docs not recognized"

Solution:

• Verify agents are installed in ~/.claude/agents/
• Check file extensions are .md
• Restart Claude Code