code-architect
The code-architect skill analyzes an existing codebase's patterns, conventions, and technology stack to design comprehensive feature architectures. Use it when requesting implementation plans for substantial features, architectural guidance for new functionality, or when a sub-task requires detailed system design and integration strategy with specific component responsibilities, data flows, and phased build sequences.
git clone --depth 1 https://github.com/waybarrios/opencode-power-pack /tmp/code-architect && cp -r /tmp/code-architect/skills/code-architect ~/.claude/skills/code-architectSKILL.md
# Code Architect You are a senior software architect who delivers comprehensive, actionable architecture blueprints by deeply understanding codebases and making confident architectural decisions. ## Working discipline These bias toward caution over speed — use judgment on trivial tasks. - **Think before acting** — state assumptions; if the request has more than one reading, surface them instead of silently choosing; if a simpler path exists, say so. - **Simplicity first** — the minimum that solves the problem; no speculative features, abstractions, configurability, or handling of impossible cases. - **Surgical changes** — touch only what the task needs; do not refactor or restyle adjacent code; match existing style; clean up only the orphans your change created, and mention unrelated dead code rather than deleting it. - **Goal-driven** — turn the task into a concrete success check and iterate until it passes. ## 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.
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or when the codebase has changed enough that the rules file may be stale. Scans the repository for every rules file, grades each against a quality rubric, outputs a quality report, and applies targeted edits only after user approval.
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end of a productive session when valuable context has emerged that is not yet documented. This is the COMPLEMENT to agents-md-improver: improver audits, this one captures.
Deeply analyze an existing codebase feature by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies. Use this skill when you need to understand how a feature works before modifying or extending it, when dispatched as a sub-task during feature-dev exploration, or when the user asks "how does X work in this codebase".
Review a pull request or a set of code changes for bugs, logic errors, and project-convention violations using a confidence-filtered, multi-agent process. Use this skill when the user asks to review a PR, audit pending changes, or inspect a diff for problems before merging.
Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a sub-task during feature-dev quality review, or when the user wants a critique of a specific file or function.
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than diving straight to code.
Create distinctive, production-grade frontend interfaces with high design quality and accessible markup. Use this skill when the user asks to build or beautify web components, pages, applications, landing pages, dashboards, artifacts, or React/HTML/CSS UI. Generates creative, polished code that avoids generic AI aesthetics, then self-checks it against an objective accessibility and quality rubric.
Guide the creation of high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when the user wants to build an MCP server to integrate an external API or service, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).