Results for “architecture-validation”

Provides production-grade NestJS architecture patterns covering modules, controllers, providers, DTO validation, guards, interceptors, exception filters, configuration, and testing for TypeScript backends.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

Analyzes codebases to generate comprehensive architectural documentation, including technology stack detection, visual diagrams, and implementation patterns.

Validates custom dotnet new templates for correctness before publishing, catching missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes.

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Internal codebase knowledge-check assistant for maintainers. Focus on architecture understanding, implementation details, and change-risk analysis for this repository.

Validates rendered UI with browser or Playwright screenshots after implementation, redesign, responsive changes, or visual regressions.

Validates observable behavior of apps, CLIs, APIs, and generated artifacts against a prewritten contract without inspecting source code.

Quality Gates

Verifies data structures, files, YAML blocks, or agent output against their defined schema, producing a pass/fail report with actionable fix instructions.

Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.

Estructura aplicaciones Flutter en módulos independientes y reutilizables con flutter_modular, incluyendo diseño de paquetes, dependencias y configuración de Melos.

Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.

Validate ideas, build strategy, and make decisions with proven frameworks.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

Guardian of V.A.I.R.E. quality standards (Value/Agency/Identity/Resilience/Echo). Handles pre-release evaluation, scorecard assessment, and pass/fail determination. Use when UX quality gates are needed. Does not write code.

Provides grep-based patterns to verify that code artifacts are real implementations rather than stubs or placeholders, covering React components, API routes, database schemas, and hooks.

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

This skill should be used when the user asks to "validate a plugin", "optimize plugin", "check plugin quality", "review plugin structure", or "run plugin optimizer".

Organizes Flutter code by business features instead of technical layers, with self-contained folders for UI, logic, and data, plus a recommended project structure and dependencies.

Applies SOLID principles, clean architecture layers, dependency injection, and patterns like CQRS and event sourcing to design scalable, maintainable systems.

Tests approaches at extreme scales to reveal fundamental limits and strengths hidden at normal scales.

Guides architecture decisions, flow type selection, bulk safety validation, and fault handling standards for Salesforce Flow design and review.

Maximally Endowed Graph Architecture — λ-calculus over bounded n-SuperHyperGraphs with grounded uncertainty, conditional self-duality, and autopoietic refinement. Use when (1) simple graphs insufficient (η<2), (2) multi-scale reasoning required, (3) uncertainty is structured not stochastic, (4) knowledge must self-refactor. Pareto-governed: complexity added only when simpler structures fail validation.