Design architecture for Ark features following existing patterns and principles. Use when planning new features, extending components, or evaluating technical approaches.
74
61%
Does it follow best practices?
Impact
95%
1.11xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/architecture/SKILL.mdWatch endpoints and streaming API design
Watch query param
0%
100%
Named port reference
0%
100%
Component diagram present
100%
100%
API design section
100%
100%
One-way decisions listed
100%
100%
Implementation phases
100%
100%
Data model section
100%
100%
Reuse over creation
87%
100%
Incremental breakdown
100%
100%
SSE mechanism explained
100%
100%
Architecture document completeness
Component diagram
100%
100%
Data model section
100%
100%
API design section
100%
100%
One-way decisions section
100%
100%
Implementation phases
100%
100%
Reuse existing components
100%
100%
Naming conventions
100%
100%
Reversibility discussion
100%
100%
Named service ports
100%
100%
Incremental independence
100%
100%
Extension over creation
100%
87%
Reuse and incremental delivery patterns
Extends existing model
100%
70%
No standalone service
0%
0%
Existing idioms
100%
100%
Watch endpoint if streaming
0%
100%
Named ports
100%
100%
One-way decisions flagged
100%
100%
Implementation phases
100%
100%
Component diagram
100%
100%
API design present
100%
100%
Reversibility noted
100%
100%
Incremental independence
100%
100%
f4bfd2d
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.