Menú
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
Basado en la clasificación ocupacional SOC
AR/VR/XR development with Unity XR, WebXR, ARKit, ARCore, Meta Quest SDK, and spatial computing. Use when building augmented reality, virtual reality, mixed reality applications, or spatial experiences.
Solidity smart contracts, Web3 development, DeFi protocols, NFTs, EVM chains, Hardhat/Foundry tooling, and blockchain security. Use when writing smart contracts, building dApps, auditing contract security, or integrating Web3 wallets.
SOC2, HIPAA, GDPR, PCI-DSS, FedRAMP compliance implementation in code. Audit logging, data encryption, access controls, privacy by design, and regulatory requirement mapping. Use when implementing compliance controls, preparing for audits, or building privacy-compliant systems.
ETL/ELT pipelines, data warehousing (BigQuery, Snowflake, Redshift), stream processing (Kafka, Spark Streaming), orchestration (Airflow, Dagster, Prefect), dbt transformations, and data lake architecture. Use when building data pipelines, designing warehouse schemas, or implementing real-time data processing.
Developer experience (DX) engineering, SDK design patterns, API ergonomics, CLI tooling design, documentation-driven development, and developer onboarding. Use when designing SDKs, improving API ergonomics, building developer tools, or creating developer documentation.
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
| name | core-workflow |
| description | Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards. |
Comprehensive development workflow reference. This loads on-demand for detailed patterns.
Quick links to rules: ~/.claude/rules/ for stack-specific and task-type checklists.
# 1. Sync with remote (ALWAYS FIRST)
git fetch origin main && git merge origin/main --no-edit
# or: git fetch origin master && git merge origin/master --no-edit
# 2. Get context
git log -3
# 3. Check for existing work
ls tasks/*.md 2>/dev/null || echo "No active tasks"
CRITICAL: Check <env> section for today's date. NEVER guess dates.
# 1. Verify
npm run test && npm run type-check # or project equivalent
# 2. Archive completed work
mv tasks/<completed-task>.md .archive/completed-tasks/
# 3. Commit with comprehensive message
git add .
git commit # See Git Conventions below
git push origin main
Stop dev server after testing: lsof -ti:PORT | xargs kill (or Windows equivalent)
For complex features spanning days/weeks, use GSD.
| Complexity | Use GSD? | Workflow |
|---|---|---|
| Simple fix (<30 min) | No | Direct execution |
| Single feature (30min-2hr) | No | Task file + TodoWrite |
| Multi-phase feature (days) | Yes | GSD workflow |
| New project/app | Yes | GSD from start |
/gsd:new-project # Initialize with brief + config
/gsd:create-roadmap # Create phases and state tracking
/gsd:plan-phase 1 # Create detailed plan for phase
/gsd:execute-plan <path> # Execute the plan
| Command | Purpose |
|---|---|
/gsd:progress | Check status, route to next action |
/gsd:resume-work | Resume from previous session |
/gsd:pause-work | Create handoff when pausing |
/gsd:plan-phase <n> | Create detailed phase plan |
/gsd:execute-plan <path> | Execute a PLAN.md |
/gsd:add-phase <desc> | Add phase to roadmap |
/gsd:insert-phase <after> <desc> | Insert urgent work |
/gsd:complete-milestone <ver> | Archive and tag release |
/gsd:help | Full command reference |
.planning/
├── PROJECT.md # Vision and requirements
├── ROADMAP.md # Phase breakdown
├── STATE.md # Project memory (context accumulation)
├── config.json # Workflow mode (interactive/yolo)
└── phases/
└── 01-foundation/
├── 01-01-PLAN.md
└── 01-01-SUMMARY.md
feat | fix | refactor | perf | test | docs | chore
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
## Testing
- All tests passing
- Manual verification done
When a task or plan is complete, automatically commit without being asked.
# 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"
| Condition | Action |
|---|---|
| User's own repo | Auto-commit + push |
External repo (no_push) | Never commit - read-only |
| Submodule (external) | Never commit - read-only |
| Uncommitted secrets detected | Block - warn user |
textContent not innerHTMLunknown type for external data| Metric | Target |
|---|---|
| Initial bundle | <100KB gzipped |
| Page load | <1s |
| Interaction latency | <100ms |
| Lighthouse Performance | 95+ |
| Accessibility | WCAG AA minimum |
| Type | Location | When |
|---|---|---|
| Unit | src/**/__tests__/ | Every function |
| Component | Same | Every component |
| Integration | tests/integration/ | Critical paths |
| E2E | tests/e2e/ | Before release |
Before committing: npm run test && npm run type-check
Use structured decision-making for complex choices:
| Decision Type | Framework |
|---|---|
| Long-term implications | /consider:10-10-10 |
| Root cause analysis | /consider:5-whys |
| Prioritization | /consider:eisenhower-matrix |
| Innovation | /consider:first-principles |
| Risk identification | /consider:inversion |
| Simplification | /consider:occams-razor |
| Focus | /consider:one-thing |
| Tradeoffs | /consider:opportunity-cost |
| Optimization | /consider:pareto |
| Consequences | /consider:second-order |
Use debug-like-expert skill for systematic approach.
We build features. We use utilities.
Give high-level updates, not spam:
✅ Added authentication middleware (3 files)
✅ Updated user store with new fields
⏳ Testing login flow...
Use AskUserQuestion when:
@-embed large docs by default/clear after completing work units| Situation | Action |
|---|---|
| Context >100k tokens | Create prompt → delegate to fresh context |
| Moderate complexity | /create-prompt → /run-prompt |
| Multi-stage features | /create-meta-prompt |
| Approaching limits | /whats-next for handoff document |
npm run dev # Start dev server
npm run build # Production build
npm run test # Run tests
npm run type-check # TypeScript check
| Type | Convention | Example |
|---|---|---|
| Components | PascalCase | UserCard.tsx |
| Hooks | use prefix | useAuth.ts |
| Utilities | camelCase | utils.ts |
| Tests | .test.ts | utils.test.ts |
~/.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