Tencent SkillHub · Developer Tools

10x Patterns

Patterns and practices that dramatically accelerate development velocity. Covers parallel execution, automation, feedback loops, workflow optimization, and anti-pattern avoidance. Use when starting projects, planning sprints, optimizing workflows, or onboarding developers.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: README.md, SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

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.

New install

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.

Upgrade existing

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.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.0

Provenance

Publisher: wpank
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 15 sections Open source page

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.

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

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

Development Velocity Patterns

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

Leverage Points

High effort-to-impact ratio — small investments that pay dividends repeatedly. Leverage 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

Time Sink Detection

Common time wasters and how to eliminate them. Time 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

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

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

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

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

Anti-Patterns

Patterns that feel productive but destroy velocity. Anti-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

Measurement — DORA Metrics

Track these four metrics to objectively measure engineering velocity. MetricEliteHighMediumLowDeployment 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

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

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

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

2 Docs

SKILL.md Primary doc
README.md Docs