infrastructure-guidelines

Automate idempotent Supabase SQL migrations, RLS policies, and Kubernetes deployments for Temporal workers.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/Analytics4Change/A4C-AppSuite --skill infrastructure-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infrastructure-guidelines
Source: https://github.com/Analytics4Change/A4C-AppSuite/tree/main/.claude/skills/infrastructure-guidelines
Command: npx skills add https://github.com/Analytics4Change/A4C-AppSuite --skill infrastructure-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill manages complex, multi-component infrastructure (database, Kubernetes, eventing) with a focus on safety, idempotency, and compliance. It streamlines the creation and evolution of database schemas, event contracts, and service deployments, reducing manual errors and ensuring consistency across environments.

Core Features & Use Cases

  • Idempotent Supabase SQL Migrations: Safely evolve your PostgreSQL schema with RLS policies and event triggers, ensuring changes are reversible and repeatable.
  • Kubernetes Deployments for Temporal Workers: Deploy and manage Temporal.io workers with best practices for resource limits, health checks, and rolling updates.
  • CQRS Projections & AsyncAPI Contracts: Implement event-driven read models and define robust, versioned event schemas for a scalable, auditable architecture.
  • Use Case: Automatically provision a new multi-tenant environment, including database schema, RLS policies, and eventing infrastructure, ensuring every step is auditable and recoverable.

Quick Start

Use the infrastructure-guidelines skill to create a new idempotent Supabase SQL migration for a 'patients' table, including RLS for tenant isolation.

Frequently Asked Questions about infrastructure-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create idempotent Supabase SQL migrations with RLS policies?

Idempotent Supabase migrations use CREATE TABLE IF NOT EXISTS and conditional logic to ensure schema changes are safely repeatable across environments. This Skill provides patterns for evolving PostgreSQL schemas with Row-Level Security policies and event triggers that remain consistent during rollbacks and re-runs, eliminating manual errors in multi-tenant setups.

Can I automate Kubernetes deployments for Temporal workers with infrastructure guidelines?

Yes. This Skill automates Temporal worker deployments on Kubernetes with built-in best practices for resource limits, health checks, and rolling updates. It ensures your event-driven workers scale safely and maintain compliance across CI/CD pipelines without manual intervention.

What's the best way to implement event-driven CQRS projections with AsyncAPI contracts?

Contract-first event design with AsyncAPI schemas ensures your CQRS read models stay synchronized and auditable. This Skill defines versioned event contracts and projection maintenance patterns that scale across multi-component infrastructure while preserving data consistency and auditability.

How do I provision a multi-tenant environment with database schema, RLS, and eventing automatically?

This Skill automates multi-tenant environment provisioning by combining idempotent Supabase migrations for schema and RLS policies, event trigger setup, and Kubernetes deployments into a single auditable workflow. Every step is recoverable and repeatable across staging and production.

Does this approach work for event-driven architectures with PostgreSQL and Kubernetes?

Yes. This Skill is purpose-built for PostgreSQL-backed Supabase with Kubernetes-hosted Temporal workers and event-driven CQRS patterns. It bridges database schema evolution, event contracts, and service deployments into one cohesive, safety-first framework.

What happens if a Supabase migration or Kubernetes deployment fails midway?

Idempotent patterns ensure failed steps are recoverable without manual cleanup. Migrations can re-run safely, and Kubernetes deployments roll back automatically via health checks. This Skill eliminates stuck states and ensures your infrastructure remains consistent even after errors.