Skill

ark-architecture

From ark

Designs architecture for Ark features reusing existing patterns and principles. Use for planning new features, extending components, or evaluating technical approaches.

design

api-development

Install

npx claudepluginhub mckinsey/agents-at-scale-ark --plugin ark

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Design architecture for Ark features following existing patterns and principles.

SKILL.md

Similar Skills

applying-brand-guidelines

3 files

Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.

anthropics-claude-cookbooks

41.6k

creating-financial-models

2 files

Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.

anthropics-claude-cookbooks

41.6k

analyzing-financial-statements

2 files

Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.

anthropics-claude-cookbooks

41.6k

Stats

Parent Repo Stars364

Parent Repo Forks80

Last CommitJan 7, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

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=true query 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