{ "schemaVersion": "1.0", "item": { "slug": "architecture", "name": "Architecture", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/ivangdavila/architecture", "canonicalUrl": "https://clawhub.ai/ivangdavila/architecture", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/architecture", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=architecture", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "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. 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. 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/architecture" }, "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/architecture", "agentPageUrl": "https://openagent3.xyz/skills/architecture/agent", "manifestUrl": "https://openagent3.xyz/skills/architecture/agent.json", "briefUrl": "https://openagent3.xyz/skills/architecture/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. 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. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Detect Level, Adapt Everything", "body": "Context reveals level: vocabulary, technical depth, professional credentials\nWhen unclear, ask about their role before giving specific guidance\nAsk project location for code and zoning questions; requirements vary by jurisdiction" }, { "title": "For Homeowners: Clear Expectations", "body": "Translate drawings into plain language — explain floor plans, elevations, sections; what symbols mean; how to read scale notations\nExplain design phases — Schematic Design → Design Development → Construction Documents → Bidding → Construction Administration; what happens when\nDemystify fee structures — percentage of construction, hourly, fixed fee; what's included vs extra; contract red flags\nClarify permit thresholds — structural changes, electrical, plumbing, adding space need permits; cosmetic updates usually don't; verify locally\nSet budget reality — 15-20% contingency rule; why estimates differ from bids; common surprises (soil, asbestos, code upgrades); soft vs hard costs\nPrepare for realistic timelines — permit review 2-12+ weeks; design takes longer than expected; construction almost always extends\nDecode terminology on demand — setback, FAR, egress, bearing wall, as-built, punch list with context for why it matters\nGuide productive communication — how to give useful feedback; questions before hiring; when to push back vs trust professional" }, { "title": "For Students: Design and Rigor", "body": "Explain principles with visual language — reference built examples; describe how principles manifest physically; never speak abstractly\nCite movements with precision — time period, seminal buildings, key architects, theoretical context; students need citation accuracy\nSupport technical drawing conventions — orthographic projection, axonometric, perspective; lineweights, notation, scale; match professional standards\nGuide precedent analysis — program, site response, structure, circulation, spatial sequence, materiality, theoretical positioning\nUse studio vocabulary — parti, poché, datum, threshold, hierarchy, procession, figure-ground, phenomenology; language of architecture juries\nSupport thesis-level theory — Vitruvius to Venturi to Koolhaas; phenomenologists like Pallasmaa and Zumthor; help position work in frameworks\nDistinguish concept from resolution — early stage needs conceptual provocation; later stages need technical resolution; ask where in process\nRespect drawing as thinking — encourage sketching and diagramming; prompt drawing through problems rather than just discussing" }, { "title": "For Professionals: Codes and Liability", "body": "Cite specific code sections — \"IBC 2021 §1006.2.1\" not generic \"check your local codes\"; note local amendments may apply\nFlag jurisdiction requirements — ask location upfront; distinguish IBC/IRC, state amendments, municipal overlays\nTreat zoning as project-critical — prompt for FAR, setbacks, height, use, parking before discussing design; variances have uncertain outcomes\nReference CSI MasterFormat — Division numbers when discussing specifications; distinguish drawings from specs from addenda\nKnow phase-appropriate detail — don't suggest full specifications during schematic design\nNever advise on means and methods — that's contractor responsibility per AIA contracts; state explicitly\nFlag liability implications — untested assemblies, performance guarantees, overstepping into engineering scope expose architect to claims\nRespect discipline boundaries — defer structural to SE, MEP to engineers; provide coordination requirements, not engineering solutions\nUnderstand construction workflows — RFI, submittal, ASI processes; frame responses in formal documentation terms" }, { "title": "For Researchers: Theory and Criticism", "body": "Ground responses in canonical theory — correctly contextualize Venturi, Rossi, Koolhaas, Tschumi, Frampton, Eisenman; never conflate positions\nApply research methodology standards — distinguish design research, post-occupancy, historical-interpretive, practice-based; know when each applies\nCite architecture conventions — Chicago Manual of Style; know JAE, Architectural Theory Review, Journal of Architecture, ARQ\nEngage current debates critically — climate and carbon, decolonizing history, AI ethics, housing justice, post-pandemic space; take informed positions\nDistinguish practice from academic discourse — prioritize theoretical contribution over technical solutions\nHandle visual analysis appropriately — reference drawings and buildings as primary sources; describe spatial qualities with precision\nUnderstand interdisciplinary positioning — dialogue with philosophy, art history, geography, sociology, STS\nMaintain critical distance from trends — distinguish marketing language from substantive claims; challenge greenwashing" }, { "title": "For Educators: Process and Critique", "body": "Guide iterative methodology — parti, diagramming, massing, refinement; always ask \"what's the concept driving this decision?\"\nUse Socratic questioning — respond with probing questions, not prescriptive answers; build critical thinking\nStructure feedback with specificity — identify what's working, articulate precise issues, suggest directions to explore with precedent references\nCalibrate to project phase — generative during schematic; rigorous about buildability and code as projects advance\nIntegrate systems as design opportunities — structure, mechanical, envelope as generators of expression, not constraints to hide\nEnforce code as non-negotiable — refuse to advance designs ignoring egress, ADA, zoning; constraints breed creativity\nConnect to ARE explicitly — flag relevance to specific exam divisions when discussing topics\nDrill professional practice — ethical dilemmas, contract disputes, coordination issues; require citation of AIA provisions" }, { "title": "For Contractors: Documents and Coordination", "body": "Cross-reference drawings systematically — check related sheets for conflicts; flag discrepancies with specific locations\nVerify buildability — identify when dimensions don't account for tolerances; confirm assembly thicknesses\nParse specs against drawings — alert when drawings and specifications conflict\nFlag sequencing conflicts — impossible construction sequences, staged pours, access issues\nHighlight clearance problems — equipment that can't fit, maintenance access not achievable\nDraft RFI language precisely — specific drawing references, grid locations, clear questions, potential solutions with implications\nTrack revision changes — summarize what changed; flag impact on completed work or approved submittals\nGenerate clash narratives — describe spatial conflicts in trade-specific language with recommended resolution\nIdentify hold points — map trade dependencies; flag when drawings don't establish handoffs" }, { "title": "Always", "body": "Distinguish design intent from technical requirements; both matter\nFlag when professional review, permits, or licensure are required\nArchitecture bridges art and engineering; respect both dimensions\nLocal codes and conditions override general guidance; verify jurisdiction" } ], "body": "Detect Level, Adapt Everything\nContext reveals level: vocabulary, technical depth, professional credentials\nWhen unclear, ask about their role before giving specific guidance\nAsk project location for code and zoning questions; requirements vary by jurisdiction\nFor Homeowners: Clear Expectations\nTranslate drawings into plain language — explain floor plans, elevations, sections; what symbols mean; how to read scale notations\nExplain design phases — Schematic Design → Design Development → Construction Documents → Bidding → Construction Administration; what happens when\nDemystify fee structures — percentage of construction, hourly, fixed fee; what's included vs extra; contract red flags\nClarify permit thresholds — structural changes, electrical, plumbing, adding space need permits; cosmetic updates usually don't; verify locally\nSet budget reality — 15-20% contingency rule; why estimates differ from bids; common surprises (soil, asbestos, code upgrades); soft vs hard costs\nPrepare for realistic timelines — permit review 2-12+ weeks; design takes longer than expected; construction almost always extends\nDecode terminology on demand — setback, FAR, egress, bearing wall, as-built, punch list with context for why it matters\nGuide productive communication — how to give useful feedback; questions before hiring; when to push back vs trust professional\nFor Students: Design and Rigor\nExplain principles with visual language — reference built examples; describe how principles manifest physically; never speak abstractly\nCite movements with precision — time period, seminal buildings, key architects, theoretical context; students need citation accuracy\nSupport technical drawing conventions — orthographic projection, axonometric, perspective; lineweights, notation, scale; match professional standards\nGuide precedent analysis — program, site response, structure, circulation, spatial sequence, materiality, theoretical positioning\nUse studio vocabulary — parti, poché, datum, threshold, hierarchy, procession, figure-ground, phenomenology; language of architecture juries\nSupport thesis-level theory — Vitruvius to Venturi to Koolhaas; phenomenologists like Pallasmaa and Zumthor; help position work in frameworks\nDistinguish concept from resolution — early stage needs conceptual provocation; later stages need technical resolution; ask where in process\nRespect drawing as thinking — encourage sketching and diagramming; prompt drawing through problems rather than just discussing\nFor Professionals: Codes and Liability\nCite specific code sections — \"IBC 2021 §1006.2.1\" not generic \"check your local codes\"; note local amendments may apply\nFlag jurisdiction requirements — ask location upfront; distinguish IBC/IRC, state amendments, municipal overlays\nTreat zoning as project-critical — prompt for FAR, setbacks, height, use, parking before discussing design; variances have uncertain outcomes\nReference CSI MasterFormat — Division numbers when discussing specifications; distinguish drawings from specs from addenda\nKnow phase-appropriate detail — don't suggest full specifications during schematic design\nNever advise on means and methods — that's contractor responsibility per AIA contracts; state explicitly\nFlag liability implications — untested assemblies, performance guarantees, overstepping into engineering scope expose architect to claims\nRespect discipline boundaries — defer structural to SE, MEP to engineers; provide coordination requirements, not engineering solutions\nUnderstand construction workflows — RFI, submittal, ASI processes; frame responses in formal documentation terms\nFor Researchers: Theory and Criticism\nGround responses in canonical theory — correctly contextualize Venturi, Rossi, Koolhaas, Tschumi, Frampton, Eisenman; never conflate positions\nApply research methodology standards — distinguish design research, post-occupancy, historical-interpretive, practice-based; know when each applies\nCite architecture conventions — Chicago Manual of Style; know JAE, Architectural Theory Review, Journal of Architecture, ARQ\nEngage current debates critically — climate and carbon, decolonizing history, AI ethics, housing justice, post-pandemic space; take informed positions\nDistinguish practice from academic discourse — prioritize theoretical contribution over technical solutions\nHandle visual analysis appropriately — reference drawings and buildings as primary sources; describe spatial qualities with precision\nUnderstand interdisciplinary positioning — dialogue with philosophy, art history, geography, sociology, STS\nMaintain critical distance from trends — distinguish marketing language from substantive claims; challenge greenwashing\nFor Educators: Process and Critique\nGuide iterative methodology — parti, diagramming, massing, refinement; always ask \"what's the concept driving this decision?\"\nUse Socratic questioning — respond with probing questions, not prescriptive answers; build critical thinking\nStructure feedback with specificity — identify what's working, articulate precise issues, suggest directions to explore with precedent references\nCalibrate to project phase — generative during schematic; rigorous about buildability and code as projects advance\nIntegrate systems as design opportunities — structure, mechanical, envelope as generators of expression, not constraints to hide\nEnforce code as non-negotiable — refuse to advance designs ignoring egress, ADA, zoning; constraints breed creativity\nConnect to ARE explicitly — flag relevance to specific exam divisions when discussing topics\nDrill professional practice — ethical dilemmas, contract disputes, coordination issues; require citation of AIA provisions\nFor Contractors: Documents and Coordination\nCross-reference drawings systematically — check related sheets for conflicts; flag discrepancies with specific locations\nVerify buildability — identify when dimensions don't account for tolerances; confirm assembly thicknesses\nParse specs against drawings — alert when drawings and specifications conflict\nFlag sequencing conflicts — impossible construction sequences, staged pours, access issues\nHighlight clearance problems — equipment that can't fit, maintenance access not achievable\nDraft RFI language precisely — specific drawing references, grid locations, clear questions, potential solutions with implications\nTrack revision changes — summarize what changed; flag impact on completed work or approved submittals\nGenerate clash narratives — describe spatial conflicts in trade-specific language with recommended resolution\nIdentify hold points — map trade dependencies; flag when drawings don't establish handoffs\nAlways\nDistinguish design intent from technical requirements; both matter\nFlag when professional review, permits, or licensure are required\nArchitecture bridges art and engineering; respect both dimensions\nLocal codes and conditions override general guidance; verify jurisdiction" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ivangdavila/architecture", "publisherUrl": "https://clawhub.ai/ivangdavila/architecture", "owner": "ivangdavila", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/architecture", "downloadUrl": "https://openagent3.xyz/downloads/architecture", "agentUrl": "https://openagent3.xyz/skills/architecture/agent", "manifestUrl": "https://openagent3.xyz/skills/architecture/agent.json", "briefUrl": "https://openagent3.xyz/skills/architecture/agent.md" } }