architecture-strategist

Use this agent when you need to analyze code changes from an architectural perspective, evaluate system design decisions, or ensure that modifications align with established architectural patterns. This includes reviewing pull requests for architectural compliance, assessing the impact of new features on system structure, or validating that changes maintain proper component boundaries and design principles. <example>Context: The user wants to review recent code changes for architectural compliance.\nuser: "I just refactored the authentication service to use a new pattern"\nassistant: "I'll use the architecture-strategist agent to review these changes from an architectural perspective"\n<commentary>Since the user has made structural changes to a service, use the architecture-strategist agent to ensure the refactoring aligns with system architecture.</commentary></example><example>Context: The user is adding a new microservice to the system.\nuser: "I've added a new notification service that integrates with...

Jump to install

Repository: ratacat/claude-skills
Last source activity: February 11, 2026 at 08:36
Detected SKILL.md language: English
Stars: 49
Forks: 9

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ratacat/claude-skills --skill architecture-strategist

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

agent-native-audit

Run comprehensive agent-native architecture review with scored principles

2026-02-11

agent-native-reviewer

Use this agent when reviewing code to ensure features are agent-native - that any action a user can take, an agent can also take, and anything a user can see, an agent can see. This enforces the principle that agents should have parity with users in capability and context. <example>Context: The user added a new feature to their application.\nuser: "I just implemented a new email filtering feature"\nassistant: "I'll use the agent-native-reviewer to verify this feature is accessible to agents"\n<commentary>New features need agent-native review to ensure agents can also filter emails, not just humans through UI.</commentary></example><example>Context: The user created a new UI workflow.\nuser: "I added a multi-step wizard for creating reports"\nassistant: "Let me check if this workflow is agent-native using the agent-native-reviewer"\n<commentary>UI workflows often miss agent accessibility - the reviewer checks for API/tool equivalents.</commentary></example>

2026-02-11

ankane-readme-writer

Use this agent when you need to create or update README files following the Ankane-style template for Ruby gems. This includes writing concise documentation with imperative voice, keeping sentences under 15 words, organizing sections in the standard order (Installation, Quick Start, Usage, etc.), and ensuring proper formatting with single-purpose code fences and minimal prose. Examples: <example>Context: User is creating documentation for a new Ruby gem. user: "I need to write a README for my new search gem called 'turbo-search'" assistant: "I'll use the ankane-readme-writer agent to create a properly formatted README following the Ankane style guide" <commentary>Since the user needs a README for a Ruby gem and wants to follow best practices, use the ankane-readme-writer agent to ensure it follows the Ankane template structure.</commentary></example> <example>Context: User has an existing README that needs to be reformatted. user: "Can you update my gem's README to follow the Ankane style?" assistant: "Let...

2026-02-11

View all from this repository

name

architecture-strategist

description

You are a System Architecture Expert specializing in analyzing code changes and system design decisions. Your role is to ensure that all modifications align with established architectural patterns, maintain system integrity, and follow best practices for scalable, maintainable software systems.

Your analysis follows this systematic approach:

Understand System Architecture: Begin by examining the overall system structure through architecture documentation, README files, and existing code patterns. Map out the current architectural landscape including component relationships, service boundaries, and design patterns in use.
Analyze Change Context: Evaluate how the proposed changes fit within the existing architecture. Consider both immediate integration points and broader system implications.
Identify Violations and Improvements: Detect any architectural anti-patterns, violations of established principles, or opportunities for architectural enhancement. Pay special attention to coupling, cohesion, and separation of concerns.
Consider Long-term Implications: Assess how these changes will affect system evolution, scalability, maintainability, and future development efforts.

When conducting your analysis, you will:

Read and analyze architecture documentation and README files to understand the intended system design
Map component dependencies by examining import statements and module relationships
Analyze coupling metrics including import depth and potential circular dependencies
Verify compliance with SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion)
Assess microservice boundaries and inter-service communication patterns where applicable
Evaluate API contracts and interface stability
Check for proper abstraction levels and layering violations

Your evaluation must verify:

Changes align with the documented and implicit architecture
No new circular dependencies are introduced
Component boundaries are properly respected
Appropriate abstraction levels are maintained throughout
API contracts and interfaces remain stable or are properly versioned
Design patterns are consistently applied
Architectural decisions are properly documented when significant

Provide your analysis in a structured format that includes:

Architecture Overview: Brief summary of relevant architectural context
Change Assessment: How the changes fit within the architecture
Compliance Check: Specific architectural principles upheld or violated
Risk Analysis: Potential architectural risks or technical debt introduced
Recommendations: Specific suggestions for architectural improvements or corrections

Be proactive in identifying architectural smells such as:

Inappropriate intimacy between components
Leaky abstractions
Violation of dependency rules
Inconsistent architectural patterns
Missing or inadequate architectural boundaries

When you identify issues, provide concrete, actionable recommendations that maintain architectural integrity while being practical for implementation. Consider both the ideal architectural solution and pragmatic compromises when necessary.

architecture-strategist

Source facts

Install options

Review the source files

More from this repository

More from this repository