Choose best design patterns
Helps you and your coding agent choose the best-fit software architecture for your project by analyzing needs, comparing architectural options and design patterns, and explaining trade-offs before implementation. Guides evidence-based decisions with guardrails, validated Architecture Decision Records (ADRs), coding handoffs, and conformance reviews using the user's selected AI model. More
Skills 29 in the ChatGPT listing
AI Software Architect Review a current project, suggest and compare suitable design patterns or architecture styles, explain patterns with stored examples, obtain approval, create ADRs and an architecture contract, prepare coding handoffs, or review conformance. Adr design docs Write architecture documentation: architecture decision records (ADRs), technical design documents, RFCs, solution architecture documents, arc42 templates, runbooks and onboarding docs for engineering teams. Ai llm architecture Design AI and LLM application architecture: retrieval-augmented generation (RAG), vector databases, embeddings, AI agents and tool use, LLM gateways, prompt management, evaluation, guardrails, caching, cost and latency control, and MLOps. Api design Design APIs like an API architect: REST, GraphQL, gRPC, WebSockets and webhooks, resource modelling, OpenAPI specs, versioning, pagination, errors, idempotency, rate limits, API gateways and backend for frontend. Architect help Show everything Software Architect can do and route the user to the right skill. Architecture diagrams Create software architecture diagrams as code: C4 model (context, container, component, code), UML (sequence, class, component, deployment, state, activity), cloud and deployment diagrams, ER diagrams and data flow, in Mermaid, PlantUML, Structurizr DSL and D2, plus fixing broken diagram code. Architecture review Review an existing architecture like a senior reviewer: scorecard across quality attributes, risks, single points of failure, coupling, scalability limits, security gaps, cost issues and technical debt, with a prioritized improvement plan. Architecture styles Choose the right architecture style: monolith, modular monolith, layered, clean, hexagonal, onion, microservices, service-oriented, serverless, event-driven, micro-kernel, space-based, pipeline and CQRS, with a clear comparison and recommendation. Cloud architecture Design cloud architectures on AWS, Azure and Google Cloud: reference architectures, well-architected reviews, networking, compute choices, managed services, multi-region, hybrid and multi-cloud, and cloud cost optimization (FinOps). Creately guide Guide to turning architecture designs from this plugin into professional diagrams in Creately: software architecture, C4, UML, AWS, Azure and Google Cloud diagrams, templates, AI diagram generation, collaboration, sharing and export. Data architecture Design the data layer: choosing SQL, NoSQL, key-value, document, graph, time-series, search and vector databases; data modelling and ER diagrams; indexing, partitioning, sharding, replication, caching, consistency, data pipelines, warehouses and lakehouses. Design patterns Apply software design patterns and principles: SOLID, DRY, KISS, YAGNI, GoF patterns, enterprise integration patterns, cloud design patterns, resilience patterns and common anti-patterns, with code examples in any language. Devops platform Design delivery and platform architecture: CI/CD pipelines, infrastructure as code (Terraform, Pulumi, Bicep, CloudFormation), containers, Kubernetes, GitOps, environments, deployment strategies and internal developer platforms. Domain driven design Apply domain-driven design: ubiquitous language, subdomains (core, supporting, generic), bounded contexts, context maps, aggregates, entities, value objects, domain events and event storming workshops. Event driven architecture Design event-driven and messaging architectures: events vs commands, message brokers and streams (Kafka, RabbitMQ, SQS, SNS, Pub/Sub, Event Hubs), CQRS, event sourcing, outbox, ordering, idempotency and dead letter queues. Frontend mobile architecture Design frontend and mobile architecture: SPA, SSR, SSG and hybrid rendering, micro-frontends, state management, design systems, backend for frontend, offline-first mobile apps, sync, push notifications and performance at scale. Legacy modernization Modernize legacy systems: assess the current state, choose a strategy (retain, rehost, replatform, refactor, rearchitect, rebuild, replace), strangler fig migrations, monolith to microservices, database migration, cloud migration and reducing technical debt safely. Microservices design Design microservices properly: service boundaries, data ownership, sync and async communication, API gateway, service discovery, sagas and distributed transactions, versioning, testing and when not to use microservices. observability Design observability: structured logging, metrics, distributed tracing, OpenTelemetry, dashboards, alerting on SLOs, correlation IDs and tool choices such as Prometheus, Grafana, Datadog, New Relic, ELK and cloud-native monitoring. Recommended tools Recommend tools for designing, diagramming, documenting and sharing software architecture, with honest guidance on which fits the user's needs. Reliability resilience Design reliable, highly available systems: SLOs and error budgets, redundancy, failover, disaster recovery (RTO and RPO), backups, circuit breakers, retries, timeouts, bulkheads, graceful degradation and chaos engineering. Requirements analysis Turn ideas into architecture-ready requirements: functional and non-functional requirements, quality attributes, utility trees, SLAs and SLOs, constraints, assumptions and architecturally significant requirements. Saas architecture Design SaaS and multi-tenant architectures: tenancy models (pool, silo, bridge), tenant isolation, onboarding, subscriptions and billing, usage metering, feature flags, tenant-aware data, noisy neighbours and enterprise features like SSO and audit logs. Scalability performance Make systems fast and scalable: capacity planning, back-of-the-envelope math, horizontal and vertical scaling, load balancing, caching layers, CDNs, async processing, database scaling, rate limiting and performance bottleneck analysis. Security architecture Design secure-by-design architectures that protect your own systems and users: identity and access (OAuth 2.0, OpenID Connect, SSO, RBAC, ABAC), zero trust, secrets and key management, encryption, network segmentation, secure SDLC, privacy by design and compliance-ready design (GDPR, SOC 2, ISO 27001, PCI DSS). Software architect Always use this skill for every message while Software Architect is active, including greetings, thanks, short replies, off-topic messages and every follow-up. System design Design complete systems end to end from requirements: scale estimates, high-level design, components, data flow, APIs, storage, caching, queues, bottlenecks and trade-offs, for any product such as marketplaces, chat, streaming, feeds, booking, payments and analytics. System design interview Prepare for system design and software architect interviews: a step-by-step framework, classic questions with model answers, mock interviews with scoring and feedback, and architect role behavioural questions. Tech stack advisor Choose the right technology stack: languages, frameworks, databases, cloud services, messaging, hosting and tools, with weighted trade-off matrices, build vs buy vs open source decisions and team-fit analysis. 