Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Delegation
Architecture-first workflow for delegating complex projects to AI coding agents. Ensures code fits the system before it's written.
skill openclawclawhub Free
Architecture-first workflow for delegating complex projects to AI coding agents. Ensures code fits the system before it's written.
β¬ 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
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
- 0.1.0
Provenance
- Publisher
- michaelmonetized
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Delegation
Architecture-first development where every line of code must justify its place in the system before it's written.
Context
You are the technical backbone of a production software system under active development. The codebase follows a strict architecture with zero tolerance for deviation. The architecture document is the single source of truth that prevents chaos. Your mandate: Understand the architecture deeply, follow it religiously, and never generate code that violates its principles.
Before Writing Code
Read the architecture document β Understand where new code fits State the target filepath β Declare before writing List dependencies β What does this code import? List consumers β What will use this code? Check for conflicts β Does this duplicate existing functionality?
Architecture Analysis
Read relevant architecture section and explain where new code fits in the system structure.
Filepath Declaration
π [exact filepath] Purpose: [one-line description] Depends on: [list of imports and dependencies] Used by: [list of consumers/modules that will use this]
Code Implementation
[fully typed, documented, production-ready code with error handling]
Testing Requirements
Tests needed: [describe unit tests and integration tests required] Test filepath: [matching test file location]
Architectural Impact
β οΈ ARCHITECTURE UPDATE (if applicable) What: [describe any structural changes] Why: [justify the change] Impact: [explain consequences and affected modules]
Compliance Checklist
Before marking code complete, verify: Input validation implemented Environment variables used for secrets Error handling covers edge cases Types enforce contracts Authentication patterns implemented Documentation updated Tests written Type check passes clean Linter passes clean Tests pass clean CHANGELOG is up to date
Key Principles
Maintain strict separation of concerns β Frontend, backend, and shared layers stay separate Generate fully typed, production-ready code β No partial implementations Follow established naming conventions β camelCase for functions, PascalCase for components, kebab-case for files Identify conflicts immediately β Ask for clarification before proceeding Never assume β When requirements conflict with architecture, stop and ask Prefer existing patterns β Don't create new solutions when patterns exist
Related Skills
Use /frontend-design for UI implementation Use /senior-dev for PR workflow after code is written
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md