DevOps

Master backend frameworks and languages including Node.js, Python, Java, Go, GraphQL, and RESTful API design. Use when building server applications, APIs, or backend services.

WebUI server-rendered frontend application

Writing style guidelines for clear, human-centered communication. Use when writing blog posts, documentation, README files, marketing copy, emails, or any external-facing content. Apply these rules to produce direct, specific, jargon-free writing.

Infrastructure guidelines for A4C-AppSuite. Covers idempotent Supabase SQL migrations with RLS policies, Kubernetes deployments for Temporal workers, CQRS projections with PostgreSQL triggers, and AsyncAPI contract-first event design. Emphasizes safety, idempotency, and SQL-first development.

Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"

Generates LinkedIn and X posts to promote published blog content with personal storytelling

AWS cloud infrastructure patterns and best practices. Use when designing or implementing AWS solutions including EC2, Lambda, S3, RDS, and infrastructure as code with Terraform or CloudFormation.

Newman/Postman collection testing patterns for API testing with environment variables, test assertions, and reporting. Use when building API tests, running Newman collections, testing REST APIs, validating HTTP responses, creating Postman collections, configuring API test environments, generating test reports, or when user mentions Newman, Postman, API testing, collection runner, integration tests, API validation, test automation, or CI/CD API testing.

Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.

Validates TRUST 5-principles (Test 85%+, Readable, Unified, Secured, Trackable). Use when aligning with TRUST governance.

Use when implementing features in Atomic CRM - enforces Engineering Constitution principles including fail-fast error handling, single composable entry point for data access, form state from Zod schemas, and pre-launch velocity over resilience

SPARC Pseudocode phase specialist for algorithm design, data structure selection, complexity analysis, and design pattern identification

Create and modify React components following project patterns. Use when building UI components, forms, layouts, navigation, or implementing React hooks. Includes DaisyUI, Tailwind CSS, and lucide-react icons.

Master advanced machine learning. Learn scikit-learn, model selection, hyperparameter tuning, ensemble methods, and model evaluation.

Master error handling and recovery patterns for robust agent workflows. Learn retry strategies, timeout handling, optimistic updates with rollback, circuit breakers, and graceful degradation. Essential for production-ready agents.

Tracks untrusted input propagation from sources to sinks in binary code to identify injection vulnerabilities. Use when analyzing data flow, tracing user input to dangerous functions, or detecting command/SQL injection.

Implement cost-optimized LLM routing with NO OpenAI. Use tiered model selection (DeepSeek, Haiku, Sonnet) to achieve 70-90% cost savings. Triggers on "LLM costs", "model selection", "cost optimization", "which model", "DeepSeek", "Claude pricing", "reduce AI costs".

Deploy and operate the vehicle insurance data analysis platform. Use when user asks about local development setup, production deployment, server configuration, build process, service management, or troubleshooting deployment issues. Focuses on the project's actual simple deployment model using start_server.sh, not complex enterprise setups.

Expert knowledge for implementing event sourcing in Composable Rust. Use when implementing event-sourced aggregates, working with EventStore trait or PostgreSQL, designing event schemas, implementing state reconstruction, dealing with optimistic concurrency and version tracking, or questions about event sourcing, CQRS, and persistence patterns.

Spec-First, Agent-Implemented Software Development Lifecycle. Use when: (1) Starting a new software project that needs structured design-before-code approach, (2) User mentions "SDLC", "spec-first", "design docs", or "implementation spec", (3) User wants to go from requirements/intent to working code with traceability, (4) Project requires documented architectural decisions and review checkpoints, (5) User has existing design artifacts and wants to continue from a specific phase. Produces: Intent doc → HLD → ADR-Lite → EIS → Code → Validation tests.