10x Patterns

10x Development Patterns (Meta-Skill)

Patterns that compress timelines, eliminate waste, and multiply output. These are the habits and systems that separate high-velocity teams from the rest.

Installation

OpenClaw / Moltbot / Clawbot

npx clawhub@latest install 10x-patterns

When to Use

• Starting a new project — set up the right foundations from day one
• Planning sprints — prioritize work that compounds
• Optimizing workflow — identify and remove bottlenecks
• Reviewing velocity — measure and improve throughput
• Onboarding developers — teach high-leverage habits
• Retrospectives — diagnose why things are slow

Core Principles

Development Velocity Patterns

Leverage Points

High effort-to-impact ratio — small investments that pay dividends repeatedly.

Time Sink Detection

Common time wasters and how to eliminate them.

Workflow Optimization

Daily Workflow Template

Morning (high energy)
  1. Review overnight CI results and alerts
  2. Tackle the hardest problem first (deep work)
  3. Batch code reviews (one block, not scattered)

Midday
  4. Meetings and collaboration (if unavoidable)
  5. Respond to async threads

Afternoon
  6. Implementation work (flow state)
  7. Write tests for today's code
  8. Open PRs, update tickets, write context for tomorrow

Essential IDE Shortcuts

CLI Aliases & Scripts

# Git acceleration
alias gs='git status'
alias gc='git commit'
alias gp='git push'
alias gl='git log --oneline -20'
alias gco='git checkout'
alias gcb='git checkout -b'
alias gpr='gh pr create --fill'

# Development
alias dev='npm run dev'
alias build='npm run build'
alias lint='npm run lint'
alias test='npm run test'

# Docker
alias dc='docker compose'
alias dcu='docker compose up -d'
alias dcd='docker compose down'
alias dcl='docker compose logs -f'

# Project navigation
alias repo='cd ~/dev/myproject'

Shell Scripts Worth Writing

Anti-Patterns

Patterns that feel productive but destroy velocity.

Measurement — DORA Metrics

Track these four metrics to objectively measure engineering velocity.

How to Improve Each

• Deployment frequency — CI/CD, feature flags, trunk-based development
• Lead time — Small PRs, automated testing, preview deploys
• Change failure rate — Type safety, comprehensive tests, canary deploys
• MTTR — Observability, runbooks, feature flag kill switches

NEVER Do

1. NEVER manually deploy to production — always use CI/CD pipelines
2. NEVER merge without automated checks — require passing CI before merge
3. NEVER keep long-lived feature branches — merge within 1-2 days or break it smaller
4. NEVER skip writing types/interfaces — the 30 seconds you save costs hours later
5. NEVER copy-paste code more than once — extract to a shared utility immediately
6. NEVER ignore flaky tests — fix or delete them; flaky tests erode trust in the suite
7. NEVER optimize without measuring — profile first, gut feelings are usually wrong