Skip to content

aiskillstore/marketplace / skills/0xsero/architect

architect

Verified

Design systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.

FileKindSize
SKILL.mdskill md936 B
skill-report.jsonconfig7.8 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-04T14:23:02.343Z",
    "slug": "0xsero-architect",
    "source_url": "https://github.com/0xSero/orchestra/tree/main/examples/orchestra/.opencode/skill/architect",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "bbbd7c31cbce58a1d3b089ba0b3a18b6e1bd632fb42b0253309ccf107e071c19",
    "tree_hash": "58e84837e76917ccd062a730d9d2642183d8bba7186d33c8d9094ea8480367ca",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "architect",
    "description": "Plan complex software features, compare architecture options, and document technical decisions with clear tradeoffs and rollout risks.",
    "summary": "Design software architecture plans with tradeoffs, risks, and phased implementation guidance.",
    "icon": "📦",
    "version": "1.0.1",
    "author": "0xSero",
    "license": "MIT",
    "category": "coding",
    "tags": [
      "architecture",
      "system-design",
      "technical-planning",
      "decision-review",
      "implementation-strategy"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": []
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "Static analysis reported no suspicious patterns, no executable code, and no detected risk factors. Manual review found this is a prompt-only architecture planning skill with no evidence of malicious intent.",
    "remediation": [],
    "risk_factor_evidence": [],
    "static_findings": [],
    "finding_verdicts": [],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 31,
    "audit_model": "codex",
    "audited_at": "2026-07-04T14:23:02.343Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Plan Software Architecture",
    "value_statement": "Complex features often fail when architecture decisions are unclear. This skill helps Claude, Codex, and Claude Code compare options, expose risks, and produce implementation plans.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "software architecture",
      "system design",
      "implementation planning",
      "technical decisions",
      "architecture review",
      "feature planning",
      "rollout strategy"
    ],
    "actual_capabilities": [
      "Clarifies requirements and constraints before proposing a design.",
      "Compares architecture alternatives with pros and cons.",
      "Identifies technical risks, dependencies, and rollout concerns.",
      "Produces structured plans and architecture overviews.",
      "Highlights decisions that need stakeholder alignment."
    ],
    "limitations": [
      "Does not edit files or execute commands.",
      "Requires project context for accurate design recommendations.",
      "Does not replace formal security, reliability, or compliance review.",
      "Cannot validate runtime behavior without user-provided evidence."
    ],
    "use_cases": [
      {
        "title": "Plan a Complex Feature",
        "description": "Break a large feature into architecture decisions, dependencies, phases, and risks before implementation starts.",
        "target_user": "Product engineers"
      },
      {
        "title": "Review a Technical Direction",
        "description": "Compare competing design options and identify tradeoffs that should be resolved before a team commits.",
        "target_user": "Engineering leads"
      },
      {
        "title": "Prepare an Architecture Brief",
        "description": "Turn loose requirements into a concise system overview for stakeholders and implementation teams.",
        "target_user": "Technical founders"
      }
    ],
    "prompt_templates": [
      {
        "title": "Clarify Requirements",
        "scenario": "Beginner request for shaping a feature idea.",
        "prompt": "Help me clarify the requirements and constraints for this feature: [feature]. Ask focused questions before proposing architecture."
      },
      {
        "title": "Compare Options",
        "scenario": "Intermediate request for choosing between designs.",
        "prompt": "Compare these architecture options for [system]: [option A], [option B], and [option C]. Include pros, cons, risks, and decision criteria."
      },
      {
        "title": "Create an Implementation Plan",
        "scenario": "Advanced request for sequencing technical work.",
        "prompt": "Create a phased implementation plan for [feature]. Include dependencies, migration steps, validation points, rollback options, and stakeholder decisions."
      },
      {
        "title": "Review Architecture Risks",
        "scenario": "Advanced review before committing to a design.",
        "prompt": "Review this architecture proposal for [system]. Identify scaling, reliability, security, data, operational, and delivery risks with mitigation options."
      }
    ],
    "output_examples": [
      {
        "input": "Plan an event-driven notification system for a SaaS product.",
        "output": "A structured architecture overview with components, event flow, delivery guarantees, failure modes, phased rollout steps, and open decisions."
      },
      {
        "input": "Compare a monolith module, internal service, and managed platform for billing.",
        "output": "A tradeoff matrix covering ownership, complexity, data consistency, compliance, migration cost, and recommended decision criteria."
      },
      {
        "input": "Review a proposed migration from REST endpoints to GraphQL.",
        "output": "A risk-focused review covering client impact, schema governance, caching, authorization, observability, rollout sequence, and stakeholder alignment."
      }
    ],
    "best_practices": [
      "Provide current architecture, constraints, and nonfunctional requirements.",
      "Ask for tradeoffs when multiple designs appear viable.",
      "Use the plan as input for implementation, review, and stakeholder discussion."
    ],
    "anti_patterns": [
      "Do not ask for a final design without sharing system context.",
      "Do not treat recommendations as verified production behavior.",
      "Do not skip security, reliability, or data reviews for high-risk systems."
    ],
    "faq": [
      {
        "question": "What does this skill help with?",
        "answer": "It helps plan software architecture, compare design options, and outline implementation phases."
      },
      {
        "question": "Can it write or edit code?",
        "answer": "No. The skill is configured for planning and review, not file editing or command execution."
      },
      {
        "question": "Which tools does it support?",
        "answer": "It supports Claude, Codex, and Claude Code through the marketplace metadata."
      },
      {
        "question": "What context should I provide?",
        "answer": "Provide goals, constraints, existing architecture, expected scale, data boundaries, and deadlines."
      },
      {
        "question": "Is it useful for early product ideas?",
        "answer": "Yes. It can clarify requirements and identify decisions before implementation planning begins."
      },
      {
        "question": "Does it replace an architecture review?",
        "answer": "No. Use it to prepare review material and surface risks for human decision makers."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 31
    }
  ]
}
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall