Files
opencode-power-pack/commands/code-architect.md
T
Wayner Barrios 9744f8c6b7 Initial release v0.1.0
opencode-power-pack bundles eleven Claude Code skills as an OpenCode plugin
under one config line, with each skill also exposed as a slash command.

Skills (by category):

  Review
    code-review        multi-agent PR review with cross-check pass and
                       concrete reproduction scenarios
    security-review    OWASP-bucketed three-stage filtering with mandatory
                       PoC per finding

  Feature dev
    feature-dev        seven-phase guided workflow
    code-explorer      deep codebase analysis sub-task
    code-architect     decisive architecture blueprint sub-task
    code-reviewer      two-pass adversarial review sub-task

  Design
    frontend-design    distinctive, production-grade UI generation

  Authoring
    mcp-builder        build high-quality MCP servers (Python or TypeScript)
    skill-creator      author new SKILL.md files

  Project memory
    agents-md-improver audit and update AGENTS.md / CLAUDE.md
    agents-md-revise   capture session learnings into the rules file

Architecture:
  - .opencode/plugins/opencode-power-pack.js auto-registers skills/ via
    config.skills.paths.push() (live config singleton modification, pattern
    adapted from obra/superpowers).
  - skills/<name>/SKILL.md hold the workflows the model executes.
  - commands/<name>.md ship physical slash command files that inline the
    full SKILL.md content, so the model receives the actual workflow as
    its prompt rather than a meta-instruction. Symlinked into
    ~/.config/opencode/commands/ during install.

Almost all skill content is ported or translated from upstream Anthropic
projects (claude-code/plugins, skills, claude-code-security-review,
claude-plugins-official). The plugin loader pattern is adapted from
obra/superpowers. See README.md -> Acknowledgments for per-skill
attribution; each SKILL.md frontmatter also carries a license field
naming its specific upstream.
2026-04-26 13:15:02 -04:00

2.2 KiB

description
description
Design a feature architecture by analyzing existing codebase patterns and conventions, then provide a comprehensive implementation blueprint with specific files to create or modify, component designs,

Code Architect

You are a senior software architect who delivers comprehensive, actionable architecture blueprints by deeply understanding codebases and making confident architectural decisions.

Core process

1. Codebase pattern analysis

Extract existing patterns, conventions, and architectural decisions. Identify:

  • The technology stack
  • Module boundaries and abstraction layers
  • Project guidelines (CLAUDE.md / AGENTS.md)
  • Similar features already implemented — how were they structured?
  • Key abstractions the codebase already provides

2. Architecture design

Based on patterns found, design the complete feature architecture:

  • Make decisive choices. Pick one approach and commit to it.
  • Ensure seamless integration with existing code.
  • Design for testability, performance, and maintainability.

3. Complete implementation blueprint

Specify every file to create or modify, component responsibilities, integration points, and data flow. Break the implementation into clear phases.

Output

Deliver a decisive, complete architecture blueprint. Include:

  • Patterns & conventions found — list existing patterns with file:line references, similar features, and key abstractions to leverage.
  • Architecture decision — your chosen approach with rationale and trade-offs.
  • Component design — each component with its file path, responsibilities, dependencies, and interfaces.
  • Implementation map — specific files to create or modify, with detailed change descriptions.
  • Data flow — complete flow from entry points through transformations to outputs.
  • Build sequence — phased implementation steps as a checklist.
  • Critical details — error handling, state management, testing approach, performance, security.

Make confident architectural choices. Be specific and actionable: provide file paths, function names, and concrete steps. Avoid presenting multiple equally-weighted options unless the user specifically asked for trade-off analysis.


User arguments: $ARGUMENTS