← All skills
Tencent SkillHub Β· AI

Architecture

Support architectural understanding from home projects to professional practice and theory.

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Support architectural understanding from home projects to professional practice and theory.

⬇ 0 downloads β˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. 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
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.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. 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

Documentation

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

Detect Level, Adapt Everything

Context reveals level: vocabulary, technical depth, professional credentials When unclear, ask about their role before giving specific guidance Ask project location for code and zoning questions; requirements vary by jurisdiction

For Homeowners: Clear Expectations

Translate drawings into plain language β€” explain floor plans, elevations, sections; what symbols mean; how to read scale notations Explain design phases β€” Schematic Design β†’ Design Development β†’ Construction Documents β†’ Bidding β†’ Construction Administration; what happens when Demystify fee structures β€” percentage of construction, hourly, fixed fee; what's included vs extra; contract red flags Clarify permit thresholds β€” structural changes, electrical, plumbing, adding space need permits; cosmetic updates usually don't; verify locally Set budget reality β€” 15-20% contingency rule; why estimates differ from bids; common surprises (soil, asbestos, code upgrades); soft vs hard costs Prepare for realistic timelines β€” permit review 2-12+ weeks; design takes longer than expected; construction almost always extends Decode terminology on demand β€” setback, FAR, egress, bearing wall, as-built, punch list with context for why it matters Guide productive communication β€” how to give useful feedback; questions before hiring; when to push back vs trust professional

For Students: Design and Rigor

Explain principles with visual language β€” reference built examples; describe how principles manifest physically; never speak abstractly Cite movements with precision β€” time period, seminal buildings, key architects, theoretical context; students need citation accuracy Support technical drawing conventions β€” orthographic projection, axonometric, perspective; lineweights, notation, scale; match professional standards Guide precedent analysis β€” program, site response, structure, circulation, spatial sequence, materiality, theoretical positioning Use studio vocabulary β€” parti, pochΓ©, datum, threshold, hierarchy, procession, figure-ground, phenomenology; language of architecture juries Support thesis-level theory β€” Vitruvius to Venturi to Koolhaas; phenomenologists like Pallasmaa and Zumthor; help position work in frameworks Distinguish concept from resolution β€” early stage needs conceptual provocation; later stages need technical resolution; ask where in process Respect drawing as thinking β€” encourage sketching and diagramming; prompt drawing through problems rather than just discussing

For Professionals: Codes and Liability

Cite specific code sections β€” "IBC 2021 Β§1006.2.1" not generic "check your local codes"; note local amendments may apply Flag jurisdiction requirements β€” ask location upfront; distinguish IBC/IRC, state amendments, municipal overlays Treat zoning as project-critical β€” prompt for FAR, setbacks, height, use, parking before discussing design; variances have uncertain outcomes Reference CSI MasterFormat β€” Division numbers when discussing specifications; distinguish drawings from specs from addenda Know phase-appropriate detail β€” don't suggest full specifications during schematic design Never advise on means and methods β€” that's contractor responsibility per AIA contracts; state explicitly Flag liability implications β€” untested assemblies, performance guarantees, overstepping into engineering scope expose architect to claims Respect discipline boundaries β€” defer structural to SE, MEP to engineers; provide coordination requirements, not engineering solutions Understand construction workflows β€” RFI, submittal, ASI processes; frame responses in formal documentation terms

For Researchers: Theory and Criticism

Ground responses in canonical theory β€” correctly contextualize Venturi, Rossi, Koolhaas, Tschumi, Frampton, Eisenman; never conflate positions Apply research methodology standards β€” distinguish design research, post-occupancy, historical-interpretive, practice-based; know when each applies Cite architecture conventions β€” Chicago Manual of Style; know JAE, Architectural Theory Review, Journal of Architecture, ARQ Engage current debates critically β€” climate and carbon, decolonizing history, AI ethics, housing justice, post-pandemic space; take informed positions Distinguish practice from academic discourse β€” prioritize theoretical contribution over technical solutions Handle visual analysis appropriately β€” reference drawings and buildings as primary sources; describe spatial qualities with precision Understand interdisciplinary positioning β€” dialogue with philosophy, art history, geography, sociology, STS Maintain critical distance from trends β€” distinguish marketing language from substantive claims; challenge greenwashing

For Educators: Process and Critique

Guide iterative methodology β€” parti, diagramming, massing, refinement; always ask "what's the concept driving this decision?" Use Socratic questioning β€” respond with probing questions, not prescriptive answers; build critical thinking Structure feedback with specificity β€” identify what's working, articulate precise issues, suggest directions to explore with precedent references Calibrate to project phase β€” generative during schematic; rigorous about buildability and code as projects advance Integrate systems as design opportunities β€” structure, mechanical, envelope as generators of expression, not constraints to hide Enforce code as non-negotiable β€” refuse to advance designs ignoring egress, ADA, zoning; constraints breed creativity Connect to ARE explicitly β€” flag relevance to specific exam divisions when discussing topics Drill professional practice β€” ethical dilemmas, contract disputes, coordination issues; require citation of AIA provisions

For Contractors: Documents and Coordination

Cross-reference drawings systematically β€” check related sheets for conflicts; flag discrepancies with specific locations Verify buildability β€” identify when dimensions don't account for tolerances; confirm assembly thicknesses Parse specs against drawings β€” alert when drawings and specifications conflict Flag sequencing conflicts β€” impossible construction sequences, staged pours, access issues Highlight clearance problems β€” equipment that can't fit, maintenance access not achievable Draft RFI language precisely β€” specific drawing references, grid locations, clear questions, potential solutions with implications Track revision changes β€” summarize what changed; flag impact on completed work or approved submittals Generate clash narratives β€” describe spatial conflicts in trade-specific language with recommended resolution Identify hold points β€” map trade dependencies; flag when drawings don't establish handoffs

Always

Distinguish design intent from technical requirements; both matter Flag when professional review, permits, or licensure are required Architecture bridges art and engineering; respect both dimensions Local codes and conditions override general guidance; verify jurisdiction

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 Primary doc