/system-design
System design patterns and architectural decision frameworks for web applications and iOS native apps. Use when making technology choices, selecting architecture patterns, designing APIs, choosing databases, planning authentication, or architecting mobile app backends. Provides
$ npx -y skills add shahtuyakov/claude-setup --skill system-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/system-design
Context preview
The summary Claude sees to decide when to auto-load this skill.
System design patterns and architectural decision frameworks for web applications and iOS native apps. Use when making technology choices, selecting architecture patterns, designing APIs, choosing databases, planning authentication, or architecting mobile app backends. Provides
SKILL.md
system-design.SKILL.mdname: system-design
description: System design patterns and architectural decision frameworks for web applications and iOS native apps. Use when making technology choices, selecting architecture patterns, designing APIs, choosing databases, planning authentication, or architecting mobile app backends. Provides comparison matrices for informed decision-making.
System Design
Architectural decision framework for web apps and iOS native applications with custom backends.
Decision Process
1. Identify requirements (scale, platform, constraints) 2. Load relevant reference file (see table below) 3. Use comparison matrix to evaluate options 4. Verify compatibility using MCP context7 for latest docs 5. Document decision with rationale
Reference Navigation
| Decision Type | Load | Use When | |---------------|------|----------| | API style | `references/api-patterns.md` | Choosing REST vs GraphQL vs gRPC | | Database | `references/database-patterns.md` | Selecting primary database, caching layer | | Authentication | `references/auth-patterns.md` | Designing auth flow, token strategy | | Real-time | `references/realtime-patterns.md` | Adding live updates, push notifications | | iOS architecture | `references/ios-patterns.md` | Native iOS app structure, offline-first | | Backend architecture | `references/architecture-patterns.md` | Monolith vs microservices, serverless | | File storage | `references/storage-patterns.md` | Media uploads, CDN, cloud storage |
Decision Documentation
Record each decision in `.agents/architect/decisions.md`:
## [date] - [decision title]
Context: [what prompted this decision]
Options: [what was considered]
Decision: [what was chosen]
Rationale: [why]
Platform Considerations
Web + iOS Projects
- Design API with mobile constraints in mind (bandwidth, battery)
- Plan for offline-first on iOS with backend sync
- Consider BFF (Backend for Frontend) if needs diverge significantly
iOS-Specific
- Always check `references/ios-patterns.md` for native patterns
- Auth must include Keychain storage and biometrics
- Push notifications require APNs backend integration
Read more
name: system-design description: System design patterns and architectural decision frameworks for web applications and iOS native apps. Use when making technology choices, selecting architecture patterns, designing APIs, choosing databases, planning authentication, or architecting mobile app backends. Provides comparison matrices for informed decision-making.
System Design
Architectural decision framework for web apps and iOS native applications with custom backends.
Decision Process
1. Identify requirements (scale, platform, constraints) 2. Load relevant reference file (see table below) 3. Use comparison matrix to evaluate options 4. Verify compatibility using MCP context7 for latest docs 5. Document decision with rationale
Reference Navigation
| Decision Type | Load | Use When | |---------------|------|----------| | API style | `references/api-patterns.md` | Choosing REST vs GraphQL vs gRPC | | Database | `references/database-patterns.md` | Selecting primary database, caching layer | | Authentication | `references/auth-patterns.md` | Designing auth flow, token strategy | | Real-time | `references/realtime-patterns.md` | Adding live updates, push notifications | | iOS architecture | `references/ios-patterns.md` | Native iOS app structure, offline-first | | Backend architecture | `references/architecture-patterns.md` | Monolith vs microservices, serverless | | File storage | `references/storage-patterns.md` | Media uploads, CDN, cloud storage |
Decision Documentation
Record each decision in `.agents/architect/decisions.md`:
## [date] - [decision title] Context: [what prompted this decision] Options: [what was considered] Decision: [what was chosen] Rationale: [why]
Platform Considerations
Web + iOS Projects
- Design API with mobile constraints in mind (bandwidth, battery)
- Plan for offline-first on iOS with backend sync
- Consider BFF (Backend for Frontend) if needs diverge significantly
iOS-Specific
- Always check `references/ios-patterns.md` for native patterns
- Auth must include Keychain storage and biometrics
- Push notifications require APNs backend integration
A multi-agent orchestration framework for Claude Code. Build production software with 7 specialized AI agents that coordinate automatically through a Hub Architecture.
Repo: shahtuyakov/claude-setup
Other skills on claude-setup.
- /agent-orchestration
Hub orchestration patterns for multi-agent workflows. Use when processing delegation requests from agents, coordinating sequential/parallel agent execution, and aggregating results. Provides the protocol for agent-to-agent communication through the hub.
Open skill - /api-design-reviewer
Expert API design reviewer for REST, GraphQL, and gRPC APIs. Analyzes API designs for security, performance, consistency, scalability, and maintainability. Use when designing new APIs, reviewing API proposals, auditing existing endpoints, or before major API releases. Covers
Open skill - /brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Open skill - /canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright
Open skill - /database-patterns
Database design and implementation patterns for modern applications. Use when designing schemas, writing migrations, optimizing queries, and configuring ORMs. Covers PostgreSQL, MongoDB, Prisma, Drizzle, indexing strategies, and security best practices.
Open skill - /design-patterns
Modern design system patterns for 2025. Covers design tokens, OKLCH color systems, fluid typography, animations, dark mode, shadcn/ui components, and Figma handoff. Use when implementing UI styles, theming, accessibility, and visual polish.
Open skill