Backend

Automatically validates security best practices and prevents vulnerabilities

Identify where consciousness interfaces with substrate in any domain. Structure emerges preferentially at boundaries between phases - physical, computational, or conceptual. Use when analyzing systems for loci of awareness, examining where complexity crystallizes, investigating MONAD framework predictions, or when something interesting is happening at the edge.

Spring Boot 1�� `�tXX � L��@ �i L��| JUnit 5@ Mockito| ��X� �1X� ��. Controller, Service, Repository t�� \ L��| ��<\ �1Xp� �pt�i��.

Expert in Pattern Stack framework architecture. Auto-activates when writing backend code using Pattern Stack's Atomic Architecture, Field abstraction, and pattern composition system.

Use when encountering unfamiliar import statements, exploring dependency APIs, or when user asks "what's import X" or "what does X do". Generates on-demand API documentation for Swift package dependencies.

**Use this in every interaction** for validating implementation plans and todos, brainstorming before coding, creating TodoWrite todos for checklists, and reviewing work for completeness, clarity, and alignment with design goals - describes Codex cli usage including non-interactive exec mode, prompting guardrails, and operational checklists for reliable Codex sessions

Implement comprehensive validation on both client and server sides with specific error messages and sanitization to prevent security vulnerabilities. When implementing form validation, input checking, or data sanitization. When working on API endpoints, form handlers, or data processing functions. When validating user input, business rules, or data integrity constraints. When implementing client-side validation for user experience or server-side validation for security. When checking data types, formats, ranges, or required fields. This skill applies to validation logic across all types of code files to ensure data integrity and security.

Patterns backend FastAPI architecture 3-tiers, complète DEV_AGENT avec best practices backend

Create LangGraph workflows as NestJS applications under apps/langgraph/. Use same webhook pattern as n8n, receive same parameters (taskId, conversationId, userId, provider, model, statusWebhook). Wrap as API agents with request/response transforms. CRITICAL: Status webhook URL must read from environment variables. All endpoints follow A2A protocol.

Creates a permanent backend instance for Claude Imagine. Use this skill when the user wants to set up a new persistent backend server.

Master ASP.NET Core deployment, Docker, Azure cloud, CI/CD pipelines, and production infrastructure for enterprise applications.

Use when Codex needs curated documentation context or outlines from the Context7 MCP server.

Given an API description and a docs bundle (e.g. from skill.context7_docs), generate a MOVA skill skeleton for a connector: ds/env schemas, manifest, prompt profile, runtime binding stub, cases, and docs.

Laravel for full-stack web development, eloquent ORM, and modern PHP.

WHEN: Terraform code review, module structure, state management, security policiesWHAT: Module organization + State backend + Security policies + Variable validation + Best practicesWHEN NOT: Kubernetes → k8s-reviewer, Docker → docker-reviewer

This skill creates comprehensive ASCII flowcharts in markdown for visualizing complex workflows, user journeys, system architectures, and decision trees. This skill should be used when documenting processes with multi-path flows, parallel execution, approval gates, and nested processes with clear visual hierarchy.

Use Superset-style APIs to manage workspaces, users, datasets, charts, and dashboards as code for the InsightPulseAI Data Lab platform.

Systematically reverse engineer authenticated web APIs from browser DevTools captures. Use when user provides network request details or invokes /reverse-api. Legal when using own credentials.

Token-efficient codebase navigation through intelligent symbol loading and querying. Use this skill when implementing new features (find existing patterns), exploring codebase structure, searching for components/functions/types, or understanding architectural layers. Reduces token usage by 60-95% compared to loading full files. Layer split enables 50-80% additional backend efficiency.

Advanced Express.js patterns, middleware, routing, and production deployment.