core-workflow

Core Workflow Patterns

Comprehensive development workflow reference. This loads on-demand for detailed patterns.

Quick links to rules: ~/.claude/rules/ for stack-specific and task-type checklists.

Session Protocol

Start Checklist

# 1. Sync first: default branch from origin/HEAD, fetch + prune, fast-forward
git fetch --prune origin && git merge --ff-only "$(git symbolic-ref --short refs/remotes/origin/HEAD)"

# 2. Get context
git log -3

# 3. Check for existing work
ls tasks/*.md 2>/dev/null || echo "No active tasks"

Take today's date from the environment context rather than inferring it.

End Checklist

# 1. Verify by review: re-read the request and the whole diff (no test/type-check ladder)

# 2. Archive completed work
mv tasks/<completed-task>.md .archive/completed-tasks/

# 3. Commit with comprehensive message
git add -A  # all pending changes, any session's
git commit  # See Git Conventions below
git push    # or the configured push runner, when one is defined; never force

Stop any dev server you started: lsof -ti:PORT | xargs kill (or Windows equivalent)

Sizing Work

Git Conventions

Commit Types

feat | fix | refactor | perf | test | docs | chore

Commit Message Format

type: Short summary (50 chars max)

## What Changed
- File X: Added feature Y
- File Z: Updated config for A

## Why
- User requested feature Y
- Config A needed update

## Verification
- Diff reviewed against the request, callers, and edge cases

Auto-Commit on Task Completion

When a task or plan is complete, automatically commit without being asked.

Pre-Commit Checks

# 1. Check this is a user-owned repo (not external)
git remote get-url origin | grep -q "travisjneuman" && echo "OK: User repo"

# 2. Check push is not blocked
git remote get-url --push origin | grep -q "no_push" && echo "SKIP: External repo"

Rules

Security Checklist

Frontend

• [ ] textContent not innerHTML
• [ ] unknown type for external data
• [ ] No exposed API keys
• [ ] HTTPS for external requests
• [ ] Input sanitization

Backend

• [ ] Input validation on all endpoints
• [ ] Auth guards on protected routes
• [ ] Parameterized queries (no raw SQL)
• [ ] Secrets in environment variables

Performance Targets

Accessibility (WCAG AA)

• [ ] Semantic HTML structure
• [ ] Alt text for meaningful images
• [ ] Keyboard navigation (Tab, Enter, Escape)
• [ ] Focus indicators visible
• [ ] Color contrast >= 4.5:1
• [ ] ARIA labels on interactive elements
• [ ] Touch targets >= 44x44px

Thinking Frameworks

Use structured decision-making for complex choices:

Debugging Protocol

Standard Issues

1. Reproduce the issue
2. Read relevant code
3. Identify root cause
4. Fix the root cause
5. Verify by review of the diff and the output the fix already produces

Intermittent/Complex Issues

Use the debug-systematic skill for a systematic approach.

Build vs Buy Philosophy

We build features. We use utilities.

• Build: All feature logic, business rules, UI/UX, data models
• Use: Low-level abstractions (D3, Recharts, Lexical, Konva)
• Criterion: We own the feature, library handles complexity

License Requirements

• Must use: MIT, Apache 2.0, BSD
• Never use: GPL, AGPL (blocks commercialization)

Communication Standards

Progress Updates

Give high-level updates, not spam:

"Added authentication middleware (3 files) and updated the user store with the new fields; now reviewing the login flow."

When to Ask

Use AskUserQuestion only when:

• An essential choice is missing and changes the outcome
• Instructions conflict and precedence doesn't settle it
• A destructive or external target can't be identified exactly
• The step needs authority the request didn't give

Otherwise pick the reasonable option, proceed, and state the assumption.

Directness Protocol

• Logic over feelings
• Correctness over validation
• Direct feedback over diplomacy
• Best solution over agreement

Context Hygiene

Reduce Token Usage

• Short, high-signal summaries over long logs
• Don't @-embed large docs by default
• Reference paths + when to read them
• Use /clear after completing work units

Delegation Patterns

Quick Reference

Common Commands

npm run dev          # Start dev server
npm run build        # Production build
npm run test         # Run tests (only when the user asks)
npm run type-check   # TypeScript check (only when the user asks)

File Naming

Resources

Official

• Claude Code Docs
• Anthropic Best Practices

Community

• awesome-claude-code
• awesome-claude-md

See Also

• ~/.claude/docs/reference/checklists/ - Task-type specific checklists
• ~/.claude/docs/reference/stacks/ - Stack-specific patterns
• ~/.claude/docs/reference/tooling/ - Tool configuration guides
• ~/.claude/skills/MASTER_INDEX.md - Full skills catalog
• ~/.claude/agents/README.md - Agents directory