AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Architecture Kata

skill-sethdford-claude-skills-architecture-kata · by sethdford

Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.

↗ Repository
— No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-sethdford-claude-skills-architecture-kata

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Architecture Kata? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Architecture Kata

Practice architectural design through structured, time-limited design challenges.

Context

You are working on architecture kata. Design a system within constraints (time, technology, team). Iterate on design, gather feedback, refine. Read problem statement and constraints carefully.

Domain Context

Based on architecture kata format (similar to code kata, but for design):

  • Problem Statement: Requirements, constraints, scale, non-functional requirements
  • Time Box: 30 minutes to 2 hours. Forces focus and trade-off decisions.
  • Constraints: Limited technology choices, team size, deployment options. Realistic constraints teach design skill.
  • Feedback: After kata, discuss solution with peers/mentor. Learn from different approaches.

Instructions

  1. Read Problem: Understand requirements. What's the core business problem? What's the scale? What's non-negotiable?
  1. Identify Constraints: Technology choices? Team size? Deployment platform? Time-to-market? These shape design.
  1. Quick Design (15-30 min):
  • Sketch components/services
  • Identify data model
  • Show communication patterns
  • Call out risks/trade-offs
  1. Document Decisions: Why this architecture? What trade-offs made? What would you do differently at 10x scale?
  1. Discuss & Refine: Present to peer or mentor. What would they do differently? Why? Learn from different perspectives.

Anti-Patterns

  • Analysis Paralysis: Spend 30 minutes debating one decision. Result: no design in time box. Guard: Make quick decisions; iterate after.
  • Overengineering: Design for 100x scale when problem is tiny. Result: complex, doesn't teach. Guard: Design for stated requirements; note what changes at 10x.
  • No Constraints: Assume unlimited budget/time/team. Result: not realistic. Guard: Use constraints to learn prioritization.
  • No Discussion: Design alone, never discuss. Result: miss learning. Guard: Share, discuss, learn from others' approaches.

Further Reading

  • Architecture Kata by Neal Ford and Mark Richards — structured design exercises
  • Building Microservices by Sam Newman — design patterns through examples
  • Growing Object-Oriented Software, Guided by Tests — iterative design practice

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML