{
  "schemaVersion": "1.0",
  "item": {
    "slug": "10x-patterns",
    "name": "10x Patterns",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/wpank/10x-patterns",
    "canonicalUrl": "https://clawhub.ai/wpank/10x-patterns",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/10x-patterns",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=10x-patterns",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "README.md",
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/10x-patterns"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/10x-patterns",
    "agentPageUrl": "https://openagent3.xyz/skills/10x-patterns/agent",
    "manifestUrl": "https://openagent3.xyz/skills/10x-patterns/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/10x-patterns/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "10x Development Patterns (Meta-Skill)",
        "body": "Patterns that compress timelines, eliminate waste, and multiply output. These are the habits and systems that separate high-velocity teams from the rest."
      },
      {
        "title": "OpenClaw / Moltbot / Clawbot",
        "body": "npx clawhub@latest install 10x-patterns"
      },
      {
        "title": "When to Use",
        "body": "Starting a new project — set up the right foundations from day one\nPlanning sprints — prioritize work that compounds\nOptimizing workflow — identify and remove bottlenecks\nReviewing velocity — measure and improve throughput\nOnboarding developers — teach high-leverage habits\nRetrospectives — diagnose why things are slow"
      },
      {
        "title": "Core Principles",
        "body": "PrincipleDescriptionExampleParallel executionDon't serialize independent tasks; run them concurrentlyRun linting, tests, and type-checking in parallel CI jobsEarly validationValidate assumptions before buildingPrototype the riskiest part first, not the easiestReuse over rebuildLeverage existing solutions before writing custom codeUse shadcn/ui instead of building a component libraryAutomation firstAutomate any repetitive task on the second occurrenceScript database seeding, not manual SQL insertsFail fastCatch errors at the earliest possible stageStrict TypeScript, pre-commit hooks, schema validationMinimize context switchingBatch similar work togetherHandle all PR reviews in one block, not scatteredShortest feedback loopReduce time between change and feedbackHot reload, preview deploys, co-located tests"
      },
      {
        "title": "Development Velocity Patterns",
        "body": "PatternWhat It DoesSpeed MultiplierHot reload / fast refreshSee changes instantly without losing state3-5x faster UI iterationType-driven developmentDefine types/interfaces first, then implementCatches 40%+ of bugs at write timeTest-driven developmentWrite tests for complex logic before implementationFewer regressions, faster debuggingFeature flagsShip incomplete features safely behind togglesContinuous delivery without riskVertical slicingBuild full-stack thin slices end-to-endFaster feedback, smaller PRsMonorepoShare code, types, and config across packagesEliminates cross-repo sync overheadCode generationGenerate boilerplate from schemas or templatesMinutes instead of hours for CRUDAI-assisted developmentUse Cursor, Copilot for acceleration2-5x faster for boilerplate and explorationTemplate repositoriesStart new projects from proven templatesSkip setup entirelyShared component librariesReusable, tested UI building blocksConsistent UI, no re-implementationPreview deploymentsEvery PR gets a live URL (Vercel, Netlify)Instant stakeholder feedbackTrunk-based developmentShort-lived branches, frequent merges to mainEliminates merge hellContinuous deploymentEvery merge to main auto-deploysZero manual deploy overheadDatabase migrations as codeVersion-controlled, repeatable schema changesNo manual DB modificationsInfrastructure as codeTerraform, Pulumi, SST for infraReproducible environments in minutesAPI-first designDefine API contracts before implementationFrontend and backend work in parallelStorybook / component devDevelop UI components in isolationNo need to navigate full app for UI work"
      },
      {
        "title": "Leverage Points",
        "body": "High effort-to-impact ratio — small investments that pay dividends repeatedly.\n\nLeverage PointEffortImpactPayoff TimelineAutomation scripts (seed, reset, deploy)1-2 hoursSaves 10+ min/day per developerDaysShared utilities (formatting, validation, logging)2-4 hoursEliminates repeated code across servicesWeeksCI/CD pipelines4-8 hoursRemoves all manual build/deploy stepsImmediatelyDocumentation (ADRs, onboarding, runbooks)2-3 hoursCuts onboarding time by 50%+WeeksDeveloper tooling (linters, formatters, git hooks)1-2 hoursPrevents entire categories of bugsImmediatelyDatabase seed scripts1-2 hoursInstant realistic local environmentsDaysError monitoring (Sentry, Axiom)1-2 hoursFind production bugs before users report themImmediately"
      },
      {
        "title": "Time Sink Detection",
        "body": "Common time wasters and how to eliminate them.\n\nTime SinkHours Wasted/WeekSolutionManual testing3-8 hoursAutomated tests, Playwright for E2E, CI checksEnvironment setup2-5 hours (new devs)Docker Compose, devcontainers, seed scriptsManual deployment1-3 hoursCI/CD pipeline, one-click deploysCode review bottlenecks2-6 hours waitingSmall PRs, async reviews, max 24h SLAMeeting overload5-10 hoursAsync standups, written updates, office hoursDebugging without logs2-4 hoursStructured logging, error tracking, source mapsDependency conflicts1-3 hoursLock files, renovate bot, monorepo toolingUnclear requirements3-8 hours reworkSpike tickets, design docs, early prototypes"
      },
      {
        "title": "Daily Workflow Template",
        "body": "Morning (high energy)\n  1. Review overnight CI results and alerts\n  2. Tackle the hardest problem first (deep work)\n  3. Batch code reviews (one block, not scattered)\n\nMidday\n  4. Meetings and collaboration (if unavoidable)\n  5. Respond to async threads\n\nAfternoon\n  6. Implementation work (flow state)\n  7. Write tests for today's code\n  8. Open PRs, update tickets, write context for tomorrow"
      },
      {
        "title": "Essential IDE Shortcuts",
        "body": "ActionmacOSWhy It MattersGo to fileCmd+PNever browse the file treeGo to symbolCmd+Shift+OJump directly to functions/classesFind in projectCmd+Shift+FFind anything across the codebaseRename symbolF2Safe, project-wide renamingQuick fixCmd+.Auto-import, auto-fix linter issuesToggle terminalCtrl+`Stay in the editorMulti-cursorCmd+DEdit multiple occurrences at onceMove lineAlt+Up/DownReorder code without cut/paste"
      },
      {
        "title": "CLI Aliases & Scripts",
        "body": "# Git acceleration\nalias gs='git status'\nalias gc='git commit'\nalias gp='git push'\nalias gl='git log --oneline -20'\nalias gco='git checkout'\nalias gcb='git checkout -b'\nalias gpr='gh pr create --fill'\n\n# Development\nalias dev='npm run dev'\nalias build='npm run build'\nalias lint='npm run lint'\nalias test='npm run test'\n\n# Docker\nalias dc='docker compose'\nalias dcu='docker compose up -d'\nalias dcd='docker compose down'\nalias dcl='docker compose logs -f'\n\n# Project navigation\nalias repo='cd ~/dev/myproject'"
      },
      {
        "title": "Shell Scripts Worth Writing",
        "body": "ScriptPurposeTime Saved./scripts/setup.shOne-command local environment setupHours per new dev./scripts/seed.shReset and seed database with test data10 min/day./scripts/deploy.shBuild, test, and deploy in sequence15 min/deploy./scripts/new-feature.shScaffold feature (route, component, test)20 min/feature./scripts/db-reset.shDrop, recreate, migrate, seed database10 min/occurrence"
      },
      {
        "title": "Anti-Patterns",
        "body": "Patterns that feel productive but destroy velocity.\n\nAnti-PatternWhat HappensInstead DoOver-engineeringBuild abstractions for problems you don't haveSolve today's problem; refactor when patterns emergePremature optimizationOptimize code that isn't a bottleneckProfile first, optimize the measured bottleneckGold platingPolish features beyond requirementsShip the 80% solution, iterate based on feedbackYak shavingFix tangential problems endlesslyTime-box tangents to 15 min, then create a ticketNot-invented-hereRebuild what open source already solvedEvaluate existing solutions before writing custom codeBikesheddingDebate trivial decisions at lengthSet a 5-min timer; if no consensus, the proposer decidesCargo cultingCopy patterns without understanding whyUnderstand the problem before adopting a solution"
      },
      {
        "title": "Measurement — DORA Metrics",
        "body": "Track these four metrics to objectively measure engineering velocity.\n\nMetricEliteHighMediumLowDeployment frequencyOn-demand (multiple/day)WeeklyMonthlyQuarterlyLead time for changes< 1 hour< 1 week< 1 month> 1 monthChange failure rate< 5%< 10%< 15%> 15%Mean time to recovery< 1 hour< 1 day< 1 week> 1 week"
      },
      {
        "title": "How to Improve Each",
        "body": "Deployment frequency — CI/CD, feature flags, trunk-based development\nLead time — Small PRs, automated testing, preview deploys\nChange failure rate — Type safety, comprehensive tests, canary deploys\nMTTR — Observability, runbooks, feature flag kill switches"
      },
      {
        "title": "NEVER Do",
        "body": "NEVER manually deploy to production — always use CI/CD pipelines\nNEVER merge without automated checks — require passing CI before merge\nNEVER keep long-lived feature branches — merge within 1-2 days or break it smaller\nNEVER skip writing types/interfaces — the 30 seconds you save costs hours later\nNEVER copy-paste code more than once — extract to a shared utility immediately\nNEVER ignore flaky tests — fix or delete them; flaky tests erode trust in the suite\nNEVER optimize without measuring — profile first, gut feelings are usually wrong"
      }
    ],
    "body": "10x Development Patterns (Meta-Skill)\n\nPatterns that compress timelines, eliminate waste, and multiply output. These are the habits and systems that separate high-velocity teams from the rest.\n\nInstallation\nOpenClaw / Moltbot / Clawbot\nnpx clawhub@latest install 10x-patterns\n\nWhen to Use\nStarting a new project — set up the right foundations from day one\nPlanning sprints — prioritize work that compounds\nOptimizing workflow — identify and remove bottlenecks\nReviewing velocity — measure and improve throughput\nOnboarding developers — teach high-leverage habits\nRetrospectives — diagnose why things are slow\nCore Principles\nPrinciple\tDescription\tExample\nParallel execution\tDon't serialize independent tasks; run them concurrently\tRun linting, tests, and type-checking in parallel CI jobs\nEarly validation\tValidate assumptions before building\tPrototype the riskiest part first, not the easiest\nReuse over rebuild\tLeverage existing solutions before writing custom code\tUse shadcn/ui instead of building a component library\nAutomation first\tAutomate any repetitive task on the second occurrence\tScript database seeding, not manual SQL inserts\nFail fast\tCatch errors at the earliest possible stage\tStrict TypeScript, pre-commit hooks, schema validation\nMinimize context switching\tBatch similar work together\tHandle all PR reviews in one block, not scattered\nShortest feedback loop\tReduce time between change and feedback\tHot reload, preview deploys, co-located tests\nDevelopment Velocity Patterns\nPattern\tWhat It Does\tSpeed Multiplier\nHot reload / fast refresh\tSee changes instantly without losing state\t3-5x faster UI iteration\nType-driven development\tDefine types/interfaces first, then implement\tCatches 40%+ of bugs at write time\nTest-driven development\tWrite tests for complex logic before implementation\tFewer regressions, faster debugging\nFeature flags\tShip incomplete features safely behind toggles\tContinuous delivery without risk\nVertical slicing\tBuild full-stack thin slices end-to-end\tFaster feedback, smaller PRs\nMonorepo\tShare code, types, and config across packages\tEliminates cross-repo sync overhead\nCode generation\tGenerate boilerplate from schemas or templates\tMinutes instead of hours for CRUD\nAI-assisted development\tUse Cursor, Copilot for acceleration\t2-5x faster for boilerplate and exploration\nTemplate repositories\tStart new projects from proven templates\tSkip setup entirely\nShared component libraries\tReusable, tested UI building blocks\tConsistent UI, no re-implementation\nPreview deployments\tEvery PR gets a live URL (Vercel, Netlify)\tInstant stakeholder feedback\nTrunk-based development\tShort-lived branches, frequent merges to main\tEliminates merge hell\nContinuous deployment\tEvery merge to main auto-deploys\tZero manual deploy overhead\nDatabase migrations as code\tVersion-controlled, repeatable schema changes\tNo manual DB modifications\nInfrastructure as code\tTerraform, Pulumi, SST for infra\tReproducible environments in minutes\nAPI-first design\tDefine API contracts before implementation\tFrontend and backend work in parallel\nStorybook / component dev\tDevelop UI components in isolation\tNo need to navigate full app for UI work\nLeverage Points\n\nHigh effort-to-impact ratio — small investments that pay dividends repeatedly.\n\nLeverage Point\tEffort\tImpact\tPayoff Timeline\nAutomation scripts (seed, reset, deploy)\t1-2 hours\tSaves 10+ min/day per developer\tDays\nShared utilities (formatting, validation, logging)\t2-4 hours\tEliminates repeated code across services\tWeeks\nCI/CD pipelines\t4-8 hours\tRemoves all manual build/deploy steps\tImmediately\nDocumentation (ADRs, onboarding, runbooks)\t2-3 hours\tCuts onboarding time by 50%+\tWeeks\nDeveloper tooling (linters, formatters, git hooks)\t1-2 hours\tPrevents entire categories of bugs\tImmediately\nDatabase seed scripts\t1-2 hours\tInstant realistic local environments\tDays\nError monitoring (Sentry, Axiom)\t1-2 hours\tFind production bugs before users report them\tImmediately\nTime Sink Detection\n\nCommon time wasters and how to eliminate them.\n\nTime Sink\tHours Wasted/Week\tSolution\nManual testing\t3-8 hours\tAutomated tests, Playwright for E2E, CI checks\nEnvironment setup\t2-5 hours (new devs)\tDocker Compose, devcontainers, seed scripts\nManual deployment\t1-3 hours\tCI/CD pipeline, one-click deploys\nCode review bottlenecks\t2-6 hours waiting\tSmall PRs, async reviews, max 24h SLA\nMeeting overload\t5-10 hours\tAsync standups, written updates, office hours\nDebugging without logs\t2-4 hours\tStructured logging, error tracking, source maps\nDependency conflicts\t1-3 hours\tLock files, renovate bot, monorepo tooling\nUnclear requirements\t3-8 hours rework\tSpike tickets, design docs, early prototypes\nWorkflow Optimization\nDaily Workflow Template\nMorning (high energy)\n  1. Review overnight CI results and alerts\n  2. Tackle the hardest problem first (deep work)\n  3. Batch code reviews (one block, not scattered)\n\nMidday\n  4. Meetings and collaboration (if unavoidable)\n  5. Respond to async threads\n\nAfternoon\n  6. Implementation work (flow state)\n  7. Write tests for today's code\n  8. Open PRs, update tickets, write context for tomorrow\n\nEssential IDE Shortcuts\nAction\tmacOS\tWhy It Matters\nGo to file\tCmd+P\tNever browse the file tree\nGo to symbol\tCmd+Shift+O\tJump directly to functions/classes\nFind in project\tCmd+Shift+F\tFind anything across the codebase\nRename symbol\tF2\tSafe, project-wide renaming\nQuick fix\tCmd+.\tAuto-import, auto-fix linter issues\nToggle terminal\tCtrl+`\tStay in the editor\nMulti-cursor\tCmd+D\tEdit multiple occurrences at once\nMove line\tAlt+Up/Down\tReorder code without cut/paste\nCLI Aliases & Scripts\n# Git acceleration\nalias gs='git status'\nalias gc='git commit'\nalias gp='git push'\nalias gl='git log --oneline -20'\nalias gco='git checkout'\nalias gcb='git checkout -b'\nalias gpr='gh pr create --fill'\n\n# Development\nalias dev='npm run dev'\nalias build='npm run build'\nalias lint='npm run lint'\nalias test='npm run test'\n\n# Docker\nalias dc='docker compose'\nalias dcu='docker compose up -d'\nalias dcd='docker compose down'\nalias dcl='docker compose logs -f'\n\n# Project navigation\nalias repo='cd ~/dev/myproject'\n\nShell Scripts Worth Writing\nScript\tPurpose\tTime Saved\n./scripts/setup.sh\tOne-command local environment setup\tHours per new dev\n./scripts/seed.sh\tReset and seed database with test data\t10 min/day\n./scripts/deploy.sh\tBuild, test, and deploy in sequence\t15 min/deploy\n./scripts/new-feature.sh\tScaffold feature (route, component, test)\t20 min/feature\n./scripts/db-reset.sh\tDrop, recreate, migrate, seed database\t10 min/occurrence\nAnti-Patterns\n\nPatterns that feel productive but destroy velocity.\n\nAnti-Pattern\tWhat Happens\tInstead Do\nOver-engineering\tBuild abstractions for problems you don't have\tSolve today's problem; refactor when patterns emerge\nPremature optimization\tOptimize code that isn't a bottleneck\tProfile first, optimize the measured bottleneck\nGold plating\tPolish features beyond requirements\tShip the 80% solution, iterate based on feedback\nYak shaving\tFix tangential problems endlessly\tTime-box tangents to 15 min, then create a ticket\nNot-invented-here\tRebuild what open source already solved\tEvaluate existing solutions before writing custom code\nBikeshedding\tDebate trivial decisions at length\tSet a 5-min timer; if no consensus, the proposer decides\nCargo culting\tCopy patterns without understanding why\tUnderstand the problem before adopting a solution\nMeasurement — DORA Metrics\n\nTrack these four metrics to objectively measure engineering velocity.\n\nMetric\tElite\tHigh\tMedium\tLow\nDeployment frequency\tOn-demand (multiple/day)\tWeekly\tMonthly\tQuarterly\nLead time for changes\t< 1 hour\t< 1 week\t< 1 month\t> 1 month\nChange failure rate\t< 5%\t< 10%\t< 15%\t> 15%\nMean time to recovery\t< 1 hour\t< 1 day\t< 1 week\t> 1 week\nHow to Improve Each\nDeployment frequency — CI/CD, feature flags, trunk-based development\nLead time — Small PRs, automated testing, preview deploys\nChange failure rate — Type safety, comprehensive tests, canary deploys\nMTTR — Observability, runbooks, feature flag kill switches\nNEVER Do\nNEVER manually deploy to production — always use CI/CD pipelines\nNEVER merge without automated checks — require passing CI before merge\nNEVER keep long-lived feature branches — merge within 1-2 days or break it smaller\nNEVER skip writing types/interfaces — the 30 seconds you save costs hours later\nNEVER copy-paste code more than once — extract to a shared utility immediately\nNEVER ignore flaky tests — fix or delete them; flaky tests erode trust in the suite\nNEVER optimize without measuring — profile first, gut feelings are usually wrong"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/wpank/10x-patterns",
    "publisherUrl": "https://clawhub.ai/wpank/10x-patterns",
    "owner": "wpank",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/10x-patterns",
    "downloadUrl": "https://openagent3.xyz/downloads/10x-patterns",
    "agentUrl": "https://openagent3.xyz/skills/10x-patterns/agent",
    "manifestUrl": "https://openagent3.xyz/skills/10x-patterns/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/10x-patterns/agent.md"
  }
}