This repository contains Claude Code configuration files and development rules for Movable Ink projects.

Do not clone this repository directly. Local configuration files will cause dirty changes on your machine.

Recommended: Fork using GitHub CLI (fastest)

# Fork and clone to ~/.claude automatically
gh repo fork nicksteffens/claude-config --clone --target-directory ~/.claude

This will fork to your account and clone directly to ~/.claude where Claude Code expects the configuration.

Alternative: Manual fork via GitHub web UI

# 1. Fork on GitHub: https://github.com/nicksteffens/claude-config/fork
# 2. Clone your fork to ~/.claude
git clone https://github.com/YOUR-USERNAME/claude-config.git ~/.claude

If you cloned the original repo first (forgot to fork):

cd ~/.claude

# Fork and set up remotes automatically (recommended)
gh repo fork --remote

# This will:
# - Fork the repo to your account
# - Set the fork as your 'origin' remote
# - Keep the original as 'upstream' remote

Or manually:

# Update remote to point to your fork
git remote set-url origin https://github.com/YOUR-USERNAME/claude-config.git

Then follow the setup steps below and create branches for contributions.

This way, your personal configuration stays separate and doesn't pollute your working directory.

• CLAUDE.md - Development rules and protocols for Claude Code sessions
• settings.example.json - Example settings file with auth tokens and permissions
• .gitignore - Excludes sensitive files like actual settings.json with real tokens
• commands/ - Slash command files for common workflows
• agents/ - Specialized agent configurations

# Copy example settings to create your settings file
cp settings.example.json settings.json

Then edit settings.json and replace placeholders with your actual values:

• ANTHROPIC_AUTH_TOKEN: Your Claude API token
• ANTHROPIC_BASE_URL: Your proxy URL (if using one)
• additionalDirectories: Paths to your project directories

The actual settings.json file is excluded from git to prevent token exposure. Only commit the example file.

Slash commands are invoked by typing /command-name in Claude Code. Available commands:

• /repo-assess - Repository assessment and safety checks (run first in any new repo)
• /branch-create - Create feature branch with proper naming conventions
• /daily-log - Update session log with accomplishments and insights
• /commit-conventional - Guide for conventional commit formatting
• /github-workflow - GitHub CLI-first operations with safety checks
• /pr-review - Pull request review workflows
• /pr-audit - Comprehensive audit of open PRs with priority scoring and Shortcut integration
• /add-reviewers - Add reviewers to pull requests

Specialized agents for complex tasks:

• frontend-architecture-lead (pfe) - Expert guidance on frontend architecture, infrastructure, and technical decisions
• pr-reviewer - Autonomous pull request reviews with design system compliance and quality gates

ask pfe how should I structure this new component?
ask pfe what's the best way to handle this API integration?
ask pr-reviewer to review PR #9789

Our collaborative sessions are systematically documented to track progress, insights, and lessons learned. Each session includes objectives, accomplishments, challenges, and follow-up items with performance ratings.

Key Features:

• Organized by year and month for easy navigation
• Standardized template questions ensure comprehensive coverage
• Version controlled for historical tracking and analysis
• Migrated from gist to repository structure (August 2025)

Usage: Run /daily-log at the end of each session to update the current month's log file.

See daily-logs/README.md for complete documentation and usage instructions.

• Claude Personalities - Swap Claude's tone, statusline quips, and spinner verbs with Star Wars droid personalities. Install via /plugin marketplace add nicksteffens/claude-personalities.

Additional setup guides and documentation:

• Shortcut MCP Setup - Configure Shortcut integration for story management and workflow automation

See CLAUDE.md for detailed development protocols including:

• Git workflow requirements
• Commit message conventions
• Branch naming strategies
• Pre-approved permissions