enterprise-infrastructure

Scale Kailash infrastructure from Level 0 to Level 2 with environment-driven configuration and a single code path across Postgres, MySQL, and SQLite via StoreFactory and dialect adapters.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/William189189/boss-bidding --skill enterprise-infrastructure-william189189
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-infrastructure
Source: https://github.com/William189189/boss-bidding/tree/main/.claude/skills/15-enterprise-infrastructure
Command: npx skills add https://github.com/William189189/boss-bidding --skill enterprise-infrastructure-william189189

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kailash's progressive infrastructure model solves the challenge of scaling from single-process SQLite to multi-worker deployments with minimal code changes, by guiding architecture and configuration for Level 0 through Level 2.

Core Features & Use Cases

  • Progressive Infrastructure Model (Level 0/1/2) with environment-driven configuration and a single code path for all levels.
  • Dialect-portable SQL patterns, shared ConnectionManager, and StoreFactory for cross-dialect stores.
  • Task queues, worker registry, and idempotency patterns to enable reliable, scalable workflows.

Quick Start

Set the environment variables (KAILASH_DATABASE_URL and optionally KAILASH_QUEUE_URL) and initialize the StoreFactory to spin up the appropriate infrastructure stores.

Frequently Asked Questions about enterprise-infrastructure

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

FAQPage Schema
How do I scale infrastructure from SQLite to multi-worker Postgres without rewriting code?

Progressive infrastructure scales from SQLite to multi-worker Postgres using environment-driven configuration and a single code path. Set the KAILASH_DATABASE_URL environment variable and initialize StoreFactory to automatically provision the appropriate infrastructure stores.

What is dialect-portable SQL and how does it work across multiple databases?

Dialect-portable SQL enables cross-database compatibility across Postgres, MySQL, and SQLite using shared ConnectionManager and StoreFactory with dialect adapters. This allows applications to switch database backends through environment variables without modifying application logic.

How do I set up task queues and worker registry for reliable distributed workflows?

Task queues and worker registry enable reliable distributed workflows by managing multi-worker queue processing and idempotency patterns. Configure KAILASH_QUEUE_URL to activate queue infrastructure alongside environment-driven database stores for scalable task execution.

Can I use environment-driven configuration to manage progressive deployment levels?

Environment-driven configuration manages progressive deployment across Level 0 through Level 2 infrastructure levels. A single code path handles all deployment stages, applying lazy imports and schema-versioning via StoreFactory and dialect adapters for minimal code changes during scaling.

What are the limitations of progressive infrastructure patterns for multi-worker deployments?

Progressive infrastructure requires careful environment variable management (KAILASH_DATABASE_URL, KAILASH_QUEUE_URL) and relies on dialect adapters for portable SQL. Complex multi-worker setups need proper idempotency pattern implementation to ensure reliable task queue processing across workers.

When do I need idempotency patterns in task queue infrastructure?

Idempotency patterns are needed in task queue infrastructure when running multi-worker deployments to prevent duplicate task execution. They ensure reliable, scalable workflows by guaranteeing tasks produce consistent results even if processed multiple times across distributed workers.