system-architect

Designs and reviews TypeScript-first AI system architectures with interface contracts and reliability patterns.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill system-architect-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/system-architect
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill system-architect-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing large-scale AI systems often leads to leaky abstractions, untyped contracts, and unplanned latency or failure behavior. This Skill provides a principal-architect persona that reviews, designs, and refactors AI systems with explicit boundaries, type safety, and performance budgets. ## Core Features & Use Cases - Architecture Review: Identifies missing abstractions, boundary leaks, and coupling, then proposes a ports/adapters interface map with ADRs. - System Design: Produces layered architectures covering API boundaries, orchestration, model gateways, memory, observability, and security, with p50/p95/p99 latency and cost budgets. - Refactor Planning: Uses named refactorings and code-smell taxonomy to deliver phased plans with checkpoints and rollback strategies. - Use Case: You are building a multi-provider LLM agent platform in Next.js. Ask for a system design and receive Mermaid diagrams, TypeScript interface contracts, a failure-mode matrix, and a phased execution plan. ## Quick Start Ask the architect to review your TypeScript AI system's architecture and produce interface contracts, ADRs, and a latency budget.

Frequently Asked Questions about system-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a large-scale AI system architecture in TypeScript?▼

Start with an interfaces-first approach: define ports and adapters, then layer API boundaries, orchestration, model gateway, tooling, memory, observability, and security. Include latency budgets, caching plans, and a failure-mode matrix for each layer.

How to review an existing AI system for architectural risks?▼

An architecture review identifies missing abstractions, boundary leaks, coupling, and reliability gaps. The output is a clean interface map of ports, adapters, domain services, and infra clients, plus an ADR list documenting decisions and tradeoffs.

What reliability patterns should AI agent workflows use?▼

Agent workflows should use retries, circuit breakers, rate limiting, dead-letter queues, idempotency, and backpressure. Durable execution engines and human-in-the-loop checkpoints handle long-running or failure-prone orchestration.

Does this approach support React and Next.js applications?▼

Yes, the architect covers React and Next.js systems, including rendering patterns, caching strategies, and production checklists. UI layers are kept isolated from vendor model details through explicit boundaries.

When should I avoid enums in TypeScript system design?▼

Prefer const objects with as const and derived union types over enums unless runtime interop demands otherwise. This keeps contracts explicit and avoids stringly-typed protocols for events, status, and errors.