architecture▌

Document significant technical decisions with structured context, rationale, and consequences. \n \n Provides five template formats (standard MADR, lightweight, Y-statement, deprecation, RFC-style) covering different decision complexity levels and team preferences \n Includes lifecycle management patterns for proposed, accepted, deprecated, and superseded decisions with clear status tracking \n Offers directory structure, indexing strategies, and automation tools (adr-tools) for maintaining ADR

Production-ready React Native patterns with Expo, navigation, offline-first architecture, and native module integration. \n \n Covers Expo Router for file-based navigation, authentication flows with secure token storage, and route protection patterns \n Includes offline-first data sync using React Query with AsyncStorage persistence and online status detection \n Demonstrates native module integration for haptics, biometrics, push notifications, and platform-specific code patterns \n Provides pe

Analyze codebases for architectural friction and propose module-deepening refactors as testability improvements. \n \n Explores codebases organically to surface shallow modules, tightly-coupled components, and untested seams rather than following rigid heuristics \n Applies John Ousterhout's \"deep module\" principle: small interfaces hiding large implementations for better testability and AI navigability \n Generates multiple radically different interface designs (minimalist, flexible, caller-o

Build sophisticated LLM applications with LangChain 1.x and LangGraph for agents, memory, and tool integration. \n \n LangGraph provides the standard agent framework with StateGraph for explicit state management, durable execution, human-in-the-loop inspection, and checkpointing across sessions \n Supports ReAct agents, plan-and-execute workflows, multi-agent supervision, and structured tool invocation with Pydantic schemas \n Memory systems include ConversationBufferMemory, ConversationSummaryM

<why_now>

Serverless architecture enables building complete applications without managing servers. Design event-driven, scalable systems using managed compute services, databases, and messaging systems. Pay only for actual usage with automatic scaling.

Comprehensive guide to designing, implementing, and maintaining microservices architectures. Covers service decomposition, communication patterns, data management, deployment strategies, and observability for distributed systems.

This skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles.

Route through domain routers before using individual tools. Routers abstract tool selection.

Implement proven backend architecture patterns for maintainable, testable, and scalable systems. \n \n Covers three core patterns: Clean Architecture (layered dependency inward), Hexagonal Architecture (ports and adapters), and Domain-Driven Design (bounded contexts, aggregates, value objects) \n Includes complete directory structures, code examples, and implementation patterns for Python backends using FastAPI, asyncpg, and similar frameworks \n Demonstrates practical separation of concerns: do