smithery.ai

ark-architecture

Design architecture for Ark features following existing patterns and principles. Use when planning new features, extending components, or evaluating technical approaches.

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,593 B
  • docs SUMMARY.md 194 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Ark Architecture Skill

Design architecture for Ark features following existing patterns and principles.

Process

  1. Analyze Current Solution - Use the ark-analysis skill to examine relevant parts of the codebase
  2. Identify Patterns - Find existing idioms, data models, and service structures to reuse
  3. Design for Reuse - Extend existing components rather than creating new ones
  4. Enable Incremental Updates - Break changes into small, independent pieces
  5. 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