ark-architecture
Provides architectural patterns and design principles for the Ark codebase.
Install
mkdir -p .claude/skills/ark-architecture && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2909" && unzip -o skill.zip -d .claude/skills/ark-architecture && rm skill.zipInstalls to .claude/skills/ark-architecture
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Design architecture for Ark features following existing patterns and principles. Use when planning new features, extending components, or evaluating technical approaches.Key capabilities
- →Identify service patterns for component reuse
- →Map component relationships in architecture diagrams
- →Flag one-way technical decisions
- →Generate incremental implementation phases
How it works
It parses the existing codebase to identify idioms and models, then applies a structural checklist to ensure new features align with established service patterns.
Inputs & outputs
When to use ark-architecture
- →Plan new Ark features
- →Extend existing service components
- →Evaluate technical approaches
About this skill
Ark Architecture Skill
Design architecture for Ark features following existing patterns and principles.
Process
- Analyze Current Solution - Use the ark-analysis skill to examine relevant parts of the codebase
- Identify Patterns - Find existing idioms, data models, and service structures to reuse
- Design for Reuse - Extend existing components rather than creating new ones
- Enable Incremental Updates - Break changes into small, independent pieces
- Flag One-Way Decisions - Raise questions on choices that are hard to reverse
Principles
- Reuse over creation - Extend existing services, models, and patterns
- Follow existing idioms - Match current code style, naming, and structure
- Incremental delivery - Design so features can be shipped in stages
- Reversibility - Identify and question decisions that lock in future options
Conventions
- Watch endpoints: Use
?watch=truequery param for SSE streaming (Kubernetes-style) - Service ports: Use named ports (e.g.,
port: mcp) rather than port numbers
Output
Architecture documents should include:
- Component diagram showing how new pieces fit with existing ones
- Data model extending current schemas
- API design following existing conventions
- List of one-way decisions requiring team input
- Implementation phases for incremental delivery
When not to use it
- →When working on projects outside the Ark architecture ecosystem
- →For greenfield projects requiring entirely new architecture
Limitations
- →Requires access to the full Ark codebase for analysis
- →Limited by existing architectural constraints
How it compares
It strictly enforces specific project conventions like SSE streaming and port naming rather than applying general software design patterns.
Compared to similar skills
ark-architecture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ark-architecture (this skill) | 1 | 7mo | No flags | Intermediate |
| software-architecture | 333 | 6mo | No flags | Intermediate |
| architect-review | 109 | 4mo | No flags | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mckinsey
View all by mckinsey →You might also like
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
architect-review
sickn33
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
mcp-builder
anthropics
Guide 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).
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.