{
  "schemaVersion": "1.0",
  "item": {
    "slug": "software-architect",
    "name": "Software Architect",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/ivangdavila/software-architect",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/software-architect",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/software-architect",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=software-architect",
    "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-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.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/software-architect"
    },
    "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/software-architect",
    "agentPageUrl": "https://openagent3.xyz/skills/software-architect/agent",
    "manifestUrl": "https://openagent3.xyz/skills/software-architect/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/software-architect/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": "Design Principles",
        "body": "Simple until proven insufficient — complexity is a cost, not a feature\nSeparate what changes from what stays stable — boundaries at change boundaries\nDesign for the next 10x, not 100x — over-engineering wastes resources\nMake decisions reversible when possible — defer irreversible ones until necessary\nConstraints clarify design — embrace limitations, don't fight them early"
      },
      {
        "title": "System Boundaries",
        "body": "Define clear interfaces between components — contracts enable independent evolution\nBoundaries where teams split — Conway's Law is real, design with it\nData ownership at boundaries — one source of truth per entity\nAsync communication for loose coupling — sync calls create distributed monoliths\nFail independently — one component's failure shouldn't cascade"
      },
      {
        "title": "Trade-off Analysis",
        "body": "Every decision has costs — articulate what you're giving up\nConsistency vs availability vs partition tolerance — pick two (CAP theorem)\nPerformance vs maintainability — optimize hot paths, keep the rest readable\nBuild vs buy — build differentiators, buy commodities\nDocument the \"why not\" for rejected alternatives — future you needs context"
      },
      {
        "title": "Scalability",
        "body": "Stateless services scale horizontally — state makes scaling hard\nCache aggressively, invalidate carefully — caching solves and creates problems\nDatabase is usually the bottleneck — read replicas, sharding, or denormalization\nQueue work that can be async — users don't need to wait for everything\nScale for expected load, prepare for 3x spikes — headroom prevents outages"
      },
      {
        "title": "Data Architecture",
        "body": "Schema design constrains everything — get it right early, migrations are expensive\nNormalize for writes, denormalize for reads — optimize for access patterns\nEvent sourcing when audit trail matters — reconstruct state from events\nCQRS when read/write patterns differ significantly — separate models for each\nData gravity is real — processing moves to data, not vice versa"
      },
      {
        "title": "Reliability",
        "body": "Design for failure — everything fails eventually, handle it gracefully\nTimeouts on all external calls — hung connections cascade into outages\nCircuit breakers prevent cascade failures — fail fast, recover gradually\nIdempotency for retries — duplicate messages shouldn't corrupt state\nGraceful degradation over total failure — partial functionality beats error pages"
      },
      {
        "title": "Security",
        "body": "Defense in depth — multiple layers, no single point of failure\nLeast privilege — minimal permissions for each component\nEncrypt in transit and at rest — assume networks and disks are hostile\nValidate at boundaries — don't trust input from outside your system\nSecrets management from day one — retrofitting is painful"
      },
      {
        "title": "Evolution",
        "body": "Design for replacement, not immortality — components will be rewritten\nIncremental migration over big bang — strangler fig pattern works\nBackwards compatibility for APIs — breaking changes break trust\nFeature flags decouple deploy from release — ship dark, enable gradually\nMonitor before, during, and after changes — data beats intuition"
      },
      {
        "title": "Documentation",
        "body": "Document decisions, not just structures — ADRs capture reasoning\nDiagrams at multiple zoom levels — C4 model: context, containers, components\nKeep docs near code — separate wikis go stale\nUpdate docs when architecture changes — wrong docs are worse than none\nDocument operational aspects — runbooks, SLOs, failure modes"
      },
      {
        "title": "Communication",
        "body": "Translate technical decisions to business impact — stakeholders need context\nPresent options with trade-offs — don't just recommend, explain\nListen to operators — they know what breaks\nInvolve security early — bolt-on security is weak security\nDecisions need buy-in — imposed architecture breeds resentment"
      }
    ],
    "body": "Software Architecture Rules\nDesign Principles\nSimple until proven insufficient — complexity is a cost, not a feature\nSeparate what changes from what stays stable — boundaries at change boundaries\nDesign for the next 10x, not 100x — over-engineering wastes resources\nMake decisions reversible when possible — defer irreversible ones until necessary\nConstraints clarify design — embrace limitations, don't fight them early\nSystem Boundaries\nDefine clear interfaces between components — contracts enable independent evolution\nBoundaries where teams split — Conway's Law is real, design with it\nData ownership at boundaries — one source of truth per entity\nAsync communication for loose coupling — sync calls create distributed monoliths\nFail independently — one component's failure shouldn't cascade\nTrade-off Analysis\nEvery decision has costs — articulate what you're giving up\nConsistency vs availability vs partition tolerance — pick two (CAP theorem)\nPerformance vs maintainability — optimize hot paths, keep the rest readable\nBuild vs buy — build differentiators, buy commodities\nDocument the \"why not\" for rejected alternatives — future you needs context\nScalability\nStateless services scale horizontally — state makes scaling hard\nCache aggressively, invalidate carefully — caching solves and creates problems\nDatabase is usually the bottleneck — read replicas, sharding, or denormalization\nQueue work that can be async — users don't need to wait for everything\nScale for expected load, prepare for 3x spikes — headroom prevents outages\nData Architecture\nSchema design constrains everything — get it right early, migrations are expensive\nNormalize for writes, denormalize for reads — optimize for access patterns\nEvent sourcing when audit trail matters — reconstruct state from events\nCQRS when read/write patterns differ significantly — separate models for each\nData gravity is real — processing moves to data, not vice versa\nReliability\nDesign for failure — everything fails eventually, handle it gracefully\nTimeouts on all external calls — hung connections cascade into outages\nCircuit breakers prevent cascade failures — fail fast, recover gradually\nIdempotency for retries — duplicate messages shouldn't corrupt state\nGraceful degradation over total failure — partial functionality beats error pages\nSecurity\nDefense in depth — multiple layers, no single point of failure\nLeast privilege — minimal permissions for each component\nEncrypt in transit and at rest — assume networks and disks are hostile\nValidate at boundaries — don't trust input from outside your system\nSecrets management from day one — retrofitting is painful\nEvolution\nDesign for replacement, not immortality — components will be rewritten\nIncremental migration over big bang — strangler fig pattern works\nBackwards compatibility for APIs — breaking changes break trust\nFeature flags decouple deploy from release — ship dark, enable gradually\nMonitor before, during, and after changes — data beats intuition\nDocumentation\nDocument decisions, not just structures — ADRs capture reasoning\nDiagrams at multiple zoom levels — C4 model: context, containers, components\nKeep docs near code — separate wikis go stale\nUpdate docs when architecture changes — wrong docs are worse than none\nDocument operational aspects — runbooks, SLOs, failure modes\nCommunication\nTranslate technical decisions to business impact — stakeholders need context\nPresent options with trade-offs — don't just recommend, explain\nListen to operators — they know what breaks\nInvolve security early — bolt-on security is weak security\nDecisions need buy-in — imposed architecture breeds resentment"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/software-architect",
    "publisherUrl": "https://clawhub.ai/ivangdavila/software-architect",
    "owner": "ivangdavila",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/software-architect",
    "downloadUrl": "https://openagent3.xyz/downloads/software-architect",
    "agentUrl": "https://openagent3.xyz/skills/software-architect/agent",
    "manifestUrl": "https://openagent3.xyz/skills/software-architect/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/software-architect/agent.md"
  }
}