Comprehensive validation methodology for multi-component applications including backend, frontend, database, and infrastructure
Validates full-stack applications by detecting backend, frontend, database, and infrastructure components, then running parallel checks for dependencies, type safety, API contracts, and environment consistency. Automatically triggers on multi-component projects or when you mention "full-stack" to catch integration issues before deployment.
/plugin marketplace add bejranonda/LLM-Autonomous-Agent-Plugin-for-Claude/plugin install bejranonda-autonomous-agent@bejranonda/LLM-Autonomous-Agent-Plugin-for-ClaudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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.
Monorepo Indicators:
package.json with workspaceslerna.json or nx.json presentpackage.json files in subdirectoriespnpm-workspace.yaml presentSeparate Repos Indicators:
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
Python/FastAPI Projects:
Dependency validation
Type checking
Test validation
API schema validation
Database migration validation
Node.js/Express Projects:
React + TypeScript Projects:
TypeScript validation
Dependency validation
Build validation
Code quality
API client validation
Vue/Angular Projects: Similar checklist adapted to framework specifics
Schema validation
Test isolation validation
Query validation
Docker Compose Projects:
Service health checks
Port conflict detection
Volume validation
Environment variable validation
Process:
Extract backend API schema
Extract frontend API client calls
Cross-validate
Auto-fix capabilities:
Process:
Collect all env var references
Cross-validate
Process:
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)
├─ Environment variable validation
└─ Authentication flow validation
Phase 4: Reporting (Sequential)
├─ Aggregate results
├─ Prioritize issues
└─ Generate recommendations
Critical (🔴): Blocks deployment, requires immediate fix
Warning (🟡): Should be fixed, doesn't block deployment
Info (🟢): Nice to have, improves quality
TypeScript:
Python:
Configuration:
TypeScript:
Python:
Database:
Project Structure Patterns:
{
"project_type": "fullstack-monorepo",
"backend": "fastapi",
"frontend": "react-typescript",
"database": "postgresql",
"infrastructure": "docker-compose",
"patterns_detected": {
"api_versioning": "/api/v1",
"auth_method": "jwt",
"orm": "sqlalchemy",
"state_management": "react-query"
}
}
Common Issue Patterns:
{
"typescript_unused_imports": {
"frequency": 12,
"auto_fix_success_rate": 1.0,
"common_files": ["src/components/*.tsx"]
},
"sqlalchemy_raw_sql": {
"frequency": 5,
"auto_fix_success_rate": 1.0,
"pattern": "execute('SELECT ...') → execute(text('SELECT ...'))"
},
"react_query_v4_syntax": {
"frequency": 3,
"auto_fix_success_rate": 0.9,
"pattern": "useQuery(['key'], fn) → useQuery({queryKey: ['key'], queryFn: fn})"
}
}
Validation Performance Patterns:
{
"backend_validation_time": "15s",
"frontend_validation_time": "45s",
"bottlenecks": ["TypeScript compilation", "npm install"],
"optimization_opportunities": ["Use turbo for builds", "Cache dependencies"]
}
Automatic triggers:
/validate-fullstack commandManual triggers:
Combines with:
code-analysis: For structural analysis of each componentquality-standards: For quality benchmarkstesting-strategies: For test coverage validationpattern-learning: For capturing project-specific patternsvalidation-standards: For tool usage validationDelegates to agents:
frontend-analyzer: For detailed TypeScript/React validationapi-contract-validator: For API synchronizationbuild-validator: For build configuration issuestest-engineer: For test infrastructure fixesquality-controller: For comprehensive quality assessmentValidation effectiveness:
Quality improvements:
✅ Full-Stack Validation Complete (2m 34s)
📊 Component Status:
├─ Backend (FastAPI + PostgreSQL)
│ ├─ ✅ Dependencies: 42 packages, 0 conflicts
│ ├─ ✅ Type hints: 98% coverage
│ ├─ ⚠️ Tests: 45 passing, 42% coverage (target: 70%)
│ └─ ✅ API schema: 23 endpoints documented
│
├─ Frontend (React + TypeScript)
│ ├─ ✅ Type check: 0 errors (auto-fixed 16)
│ ├─ ✅ Build: 882KB bundle (optimized)
│ ├─ ✅ Dependencies: 124 packages, 0 peer warnings
│ └─ ✅ Unused imports: 0 (auto-removed 5)
│
└─ Integration
├─ ✅ API contract: 23/23 endpoints matched
├─ ✅ Environment vars: 15/15 documented
└─ ✅ Auth flow: JWT tokens validated
🔧 Auto-Fixed Issues (11):
✓ Removed 5 unused TypeScript imports
✓ Generated vite-env.d.ts
✓ Added text() wrapper to 3 SQL queries
✓ Fixed 2 React Query v5 syntax issues
⚠️ Recommended Actions (2):
1. Increase test coverage to 70% (currently 42%)
2. Add indexes to users.email and projects.created_at
🎯 Overall Score: 87/100 (Production Ready)
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.