Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Software Engineer
Write production-ready code with clean architecture, proper error handling, and pragmatic trade-offs between shipping fast and building right.
skill openclawclawhub Free
Write production-ready code with clean architecture, proper error handling, and pragmatic trade-offs between shipping fast and building right.
โฌ 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.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, architecture.md, patterns.md, testing.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. 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. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
When to Use
Agent needs to write, review, or refactor code. Handles implementation decisions, architecture trade-offs, and code quality across any language or framework.
Quick Reference
TopicFileCode patternspatterns.mdArchitecture decisionsarchitecture.mdTesting practicestesting.md
1. Read Before Write
Check existing code style, patterns, and conventions before writing new code Respect the current stack โ never swap libraries without explicit request Match naming conventions, formatting, and project structure already in place
2. Code That Compiles
Every code block must: Have correct imports for the actual library versions in use Use APIs that exist in the project's dependency versions Pass basic syntax checks โ no placeholder // TODO: implement
3. Minimal First
Solve the specific problem, not hypothetical future problems One abstraction when you have three concrete cases, not before Features that might be needed โ skip. Features that are needed โ implement
4. Errors as First-Class Citizens
โ catch (e) {} โ catch (e) { console.log(e) } โ catch (e) { logger.error('context', { error: e, input }); throw new DomainError(...) } Typed errors over generic strings Include context: what operation failed, with what input Distinguish recoverable vs fatal errors
5. Boundaries and Separation
LayerContainsNever ContainsHandler/ControllerHTTP/CLI parsing, validationBusiness logic, SQLService/DomainBusiness rules, orchestrationInfrastructure detailsRepository/AdapterData access, external APIsBusiness decisions
6. Explicit Trade-offs
When making architectural choices, state: What you chose and why What you traded away When to revisit the decision Example: "Using SQLite for simplicity. Trade-off: no concurrent writes. Revisit if >1 write/sec needed."
7. PR-Ready Code
Before delivering any code: No dead code, commented blocks, or debug statements Functions under 30 lines No magic numbers โ use named constants Early returns over nested conditionals Edge cases handled: null, empty, error states
Code Quality Signals
Senior code reads like prose: Names explain "what" and "why", not "how" A junior understands it in 30 seconds No cleverness that requires comments to explain The best code is boring: Predictable patterns Standard library over dependencies when reasonable Explicit over implicit
Common Traps
TrapConsequencePreventionInventing APIsCode doesn't compileVerify method exists in docs firstOver-engineering3 hours instead of 30 minAsk: "Do I have 3 concrete cases?"Ignoring contextSuggests wrong stackRead existing files before suggestingCopy-paste without understandingHidden bugs surface laterExplain what the code doesEmpty error handlingSilent failures in productionAlways log + type + rethrowPremature abstractionComplexity without benefitYAGNI until proven otherwise
Pragmatic Shipping
Critical paths (do it right): Authentication, authorization Payment processing Data integrity, migrations Secrets management Experimental paths (ship fast, iterate): UI/UX features Admin panels Analytics Anything unvalidated with users Test for critical path: "Can this wake me at 3am or lose money?"
Security & Privacy
This skill does NOT: Store any data externally Make network requests Access files outside the current project All code suggestions are generated in context of the conversation.
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
4 Docs
- SKILL.md
- architecture.md
- patterns.md
- testing.md