Results for “config-validation”

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

Run pre-deployment validation checks for Azure readiness, including configuration, infrastructure (Bicep or Terraform), RBAC role assignments, and managed identity permissions.

Provides step-by-step guidance and generates configurations for creating surveys, following industry best practices and validation standards.

Python dataclass best practices: slots, frozen, validation. Trigger when optimizing dataclasses or creating config classes.

Use this when the system needs explicit runtime validation for API inputs, config, queue messages, webhook payloads, file metadata, or external provider responses in TypeScript, JavaScript, Python, or mixed systems.

Build production Rust CLIs with Clap: subcommands, config layering, validation, exit codes, shell completions, and testable command surfaces

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

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

Validates CircleCI configuration files and custom Orbs using the CircleCI CLI and Orb Development Kit, checking for deprecated images, inefficient caching, and security anti-patterns.

You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.

Configure MCP servers in .claude/.mcp.json with examples for memory, filesystem, search, and browser automation, plus environment variable handling and validation rules.

Validates NVIDIA TAO DAFT datasets for structure, schema, and cross-reference errors using the `tao-daft validate` CLI tool.

Use when developing or reviewing a third-party payment provider module for Weline_Payment, including ProviderInterface implementation, checkout phtml, SystemConfig config phtml, PayableResolver boundaries, payment/refund idempotency, scope-aware configuration, currency/country support, and fake-mode validation.

Use this when reviewing how a codebase organizes configuration files, env vars, runtime options, feature flags, and per-environment settings. Trigger on requests to clean up or validate config structure.

Validates Claude Ads contracts, bundles, scores, runs, capabilities, repositories, and releases with deterministic checks and recovery steps.

Validates the integrity of a project's .planning/ directory, reporting missing files, invalid configurations, and inconsistent state, with optional auto-repair of safe issues.

Periodically scans Claude Code configuration for redundant, stale, or orphaned items and walks the user through a confirm-each-deletion cleanup.

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

A comprehensive verification system for Claude Code sessions.

Use in TURBO mode before finalizing implementation, architecture, UI/UX, 3D web, mobile, SEO/PPC/growth, or programming work.

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

Reviews secrets, config defaults, environment variables, logs, credentials, CI secrets, and unsafe settings.

Define and enforce data schemas and quality checks using pandera, Great Expectations, or manual assertions, with clear error handling and documentation.

Probe the forms on a page for validation gaps — missing required-field enforcement, no client-side validation, accepts malformed input, and absent error messaging. Reports per-field findings. Playwright MCP only, no signup.

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

Verifies suspected security bugs to eliminate false positives, producing a TRUE POSITIVE or FALSE POSITIVE verdict with documented evidence for each.

This skill should be used when the user asks to "validate plugin structure", "review manifest files", "check frontmatter compliance", "verify tool invocation patterns", "explain plugin component types", or needs Claude Code plugin architectural guidance.

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

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.

Validate current branch follows feature branch naming conventions