Results for “architecture”

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md.

Designs system architecture, selects technology stack, creates ERDs and sequence diagrams, and records ADRs from BA artifacts, declaring a design freeze gate.

Produces clean, functional code that matches the architecture and checklists.

Create process and architecture diagrams using Mermaid.js syntax

Generates detailed, technology-agnostic implementation blueprints by analyzing project architecture, technology stacks, and data flow patterns.

Organizes Flutter code into domain, data, and presentation layers with unidirectional dependencies, using BLoC, use cases, and repository patterns for testable, maintainable enterprise applications.

Finds architectural friction in a codebase and proposes deep-module refactors to improve testability and AI-navigability, informed by the domain glossary and ADRs.

Internal architecture and change-impact review assistant for this repository.

Skills system architecture — progressive disclosure, frontmatter, platform filtering, self-editing

Guides developers through building Dify plugins, covering the four plugin types, Beehive architecture, runtime modes, and the full development workflow from setup to packaging.

NestJS architecture including modules, dependency injection, guards, interceptors, and microservices patterns.

Generates Mermaid architecture diagrams from a codebase, including C4 context and container diagrams, sequence diagrams for key flows, ER diagrams from database schemas, and module dependency graphs.

Comprehensive guide for developing on EspoCRM - metadata-driven CRM with service layer architecture

Applies senior Python rules for typing, async, APIs, persistence, tests, packaging, and architecture.

Applies TypeScript/JavaScript rules for types, async behavior, APIs, tooling, tests, and architecture.

Builds a local knowledge graph of a codebase using tree-sitter and graph algorithms, then answers architecture questions by querying the graph instead of reading many files, saving tokens.

Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening. Covers Node.js/Express/Fastify development, PostgreSQL optimization, API security, and backend architecture patterns.

Design multiplayer systems including networking architecture, matchmaking, social features, anti-cheat, and multiplayer game modes. Use when adding online or local multiplayer to a game. Also trigger for "multiplayer", "online play", "co-op design", "PvP design", "matchmaking", "netcode", or "multiplayer architecture".

Drive IT strategy, digital transformation, vendor management, architecture decisions, and technology governance.

Generate Excalidraw diagrams from natural language descriptions, supporting flowcharts, relationship diagrams, mind maps, architecture diagrams, and more. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

Runs an evidence-first, read-only workflow over large codebases via an external JSONL REPL server, retrieving only minimal file slices and greps to produce cited architecture and audit reports.

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

Provides foundational patterns for building type-safe frontend applications with Elm, covering The Elm Architecture, core language features, and Elm's approach to functional web development.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

The single highest-leverage decision is recognizing that most of what teams call

Builds and validates Russian Obsidian repository wikis, architecture docs, and code/docs/ADR drift reports.

Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Maps domains, ownership, dependencies, entry points, tests, services, and risks before broad changes, review, migration, or handoff.

Scan project structure and generate ARCHITECTURE.md with a Mermaid module relationship diagram. Use when user says "/map".

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

SONA self-optimizing neural architecture with ReasoningBank trajectory learning, EWC++ anti-forgetting, and reinforcement learning feedback loops.

NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.

Decomposes large modules, god files, classes, or packages in reviewable steps while preserving public APIs. Not for routine refactors.