fullstack-validation
Comprehensive validation methodology for multi-component applications including backend, frontend, database, and infrastructure
What this skill does
## Overview This skill provides systematic approaches for validating full-stack applications with multiple interconnected components. It enables automatic detection of project structure, parallel validation workflows, cross-component verification, and identification of integration issues. **When to use**: Full-stack projects with backend + frontend, microservices, monorepos, Docker Compose setups, or any multi-technology application. **Key innovation**: Parallel validation with cross-component awareness - validates each layer independently while ensuring they work together correctly. ## Project Structure Detection ### Detection Patterns **Monorepo Indicators**: - Root `package.json` with workspaces - `lerna.json` or `nx.json` present - Multiple `package.json` files in subdirectories - `pnpm-workspace.yaml` present **Separate Repos Indicators**: - Single technology stack per repository - Docker Compose references external services - Git submodules present **Technology Stack Detection**: ``` Backend: - FastAPI: requirements.txt with 'fastapi', main.py with FastAPI app - Django: manage.py, settings.py present - Express: package.json with 'express', app.js/index.js - Spring Boot: pom.xml or build.gradle with spring-boot Frontend: - React: package.json with 'react', src/App.tsx or src/App.jsx - Vue: package.json with 'vue', src/App.vue - Angular: package.json with '@angular/core', angular.json - Svelte: package.json with 'svelte', src/App.svelte Database: - PostgreSQL: requirements.txt with 'psycopg2', docker-compose.yml with postgres - MySQL: package.json with 'mysql2', docker-compose.yml with mysql - MongoDB: package.json with 'mongoose', docker-compose.yml with mongo - Redis: docker-compose.yml with redis, requirements.txt with 'redis' Infrastructure: - Docker: Dockerfile, docker-compose.yml present - Kubernetes: k8s/ or kubernetes/ directory with .yaml files - Terraform: .tf files present - Nginx: nginx.conf present ``` ## Validation Workflows ### Backend Validation Checklist **Python/FastAPI Projects**: 1. Dependency validation - Check requirements.txt exists and is parseable - Verify all imports can be resolved - Check for version conflicts - Validate Python version compatibility 2. Type checking - Run mypy on all source files - Check for missing type hints - Validate Pydantic model definitions - Verify return type annotations 3. Test validation - Run pytest with coverage - Check test isolation (database cleanup) - Validate fixture dependencies - Ensure no test data pollution - Check for views/triggers blocking teardown 4. API schema validation - Extract OpenAPI/Swagger schema - Validate all endpoints have docstrings - Check request/response models - Verify authentication decorators 5. Database migration validation - Check Alembic migrations are sequential - Validate up/down migration pairs - Ensure migrations are reversible - Check for data loss risks **Node.js/Express Projects**: 1. Dependency validation (npm/yarn/pnpm) 2. ESLint validation 3. Jest/Mocha test execution 4. API route validation 5. Database migration validation (Knex/Sequelize) ### Frontend Validation Checklist **React + TypeScript Projects**: 1. TypeScript validation - Run tsc --noEmit for type checking - Detect unused imports (auto-fix available) - Check tsconfig.json strictness - Validate path aliases (@/ imports) - Generate missing .d.ts files (vite-env.d.ts, etc.) 2. Dependency validation - Check package.json for peer dependency warnings - Detect version mismatches (React Query vs React) - Validate ESM vs CommonJS consistency - Check for deprecated packages 3. Build validation - Run production build (npm run build / vite build) - Check bundle size (warn if > 1MB per chunk) - Validate environment variables - Check for build warnings - Validate asset optimization 4. Code quality - Run ESLint with auto-fix - Check for console.log statements in production - Validate React hooks usage - Check for deprecated React patterns - Detect old library syntax (React Query v4 → v5) 5. API client validation - Check all API calls have error handling - Validate API base URLs - Ensure loading/error states exist - Check authentication token handling **Vue/Angular Projects**: Similar checklist adapted to framework specifics ### Database Validation Checklist 1. Schema validation - Check all tables exist - Validate foreign key constraints - Check for orphaned records - Validate indexes on frequently queried columns 2. Test isolation validation - Detect views dependent on test tables - Check for triggers that prevent cleanup - Validate CASCADE deletion works - Ensure test data doesn't leak to other tests 3. Query validation - Check for N+1 query problems - Validate JOIN efficiency - Check for missing indexes - Detect raw SQL strings (SQLAlchemy 2.0 requires text() wrapper) ### Infrastructure Validation Checklist **Docker Compose Projects**: 1. Service health checks - Verify all services start successfully - Check healthcheck endpoints respond - Validate depends_on order is correct - Check restart policies 2. Port conflict detection - Ensure no duplicate port mappings - Check host ports are available - Validate internal service communication 3. Volume validation - Check mounted directories exist - Validate volume permissions - Ensure persistent data volumes are defined 4. Environment variable validation - Check .env.example matches required vars - Validate all services receive needed env vars - Check for hardcoded credentials - Ensure secrets are not committed ## Cross-Component Validation ### API Contract Validation **Process**: 1. Extract backend API schema - FastAPI: GET /docs → openapi.json - Express: Parse route definitions - Django REST: GET /schema 2. Extract frontend API client calls - Search for axios/fetch calls - Find API client service files - Parse API endpoint strings 3. Cross-validate - Check every frontend call has matching backend endpoint - Validate HTTP methods match (GET/POST/PUT/DELETE) - Check parameter names and types match - Verify response types match frontend expectations - Detect missing error handling **Auto-fix capabilities**: - Generate missing TypeScript types from OpenAPI schema - Generate missing API client methods - Update deprecated endpoint calls - Add missing error handling ### Environment Variable Consistency **Process**: 1. Collect all env var references - Backend: os.getenv(), settings.py - Frontend: import.meta.env, process.env - Docker: docker-compose.yml env sections 2. Cross-validate - Check .env.example has all referenced vars - Ensure frontend vars have VITE_ or REACT_APP_ prefix - Validate no secrets in frontend code - Check env vars are documented ### Authentication Flow Validation **Process**: 1. Identify auth mechanism (JWT, OAuth, Basic, API Key) 2. Check backend auth implementation - Token generation/validation - Password hashing - Session management 3. Check frontend auth implementation - Token storage (localStorage/sessionStorage/cookies) - Auth headers in API calls - Protected route guards - Token refresh logic 4. Cross-validate - Ensure token format matches backend expectations - Check expiration handling - Validate logout clears all auth data ## Parallel Validation Strategy ### Execution Plan ``` Phase 1: Detection (Sequential) ├─ Scan project structure ├─ Identify all components └─ Determine validation workflows Phase 2: Component Validation (Parallel) ├─ Backend validation (background) ├─ Frontend validation (background) ├─ Database validation (background) └─ Infrastructure validation (background) Phase 3: Cross-Component Validation (Sequential) ├─ API contract validation (requires Phase 2 complete) ├─ En
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.