rudder-iac

Enforce a disciplined TDD workflow with CRAP score monitoring. Use after writing or modifying Go code to ensure tests are written first (Red-Green-Refactor) and complexity stays low (CRAP < 8). Triggers on every code change cycle.

Guide for creating new providers in the rudder-iac project using the latest BaseProvider and BaseHandler framework. Use when building providers for new RudderStack services (data-graph, profiles, etc.) or creating providers from scratch with custom resources. Implements type-safe handlers with generics, resource lifecycle management (CRUD), remote state sync, and import/export functionality.

Apply repository-specific Go code structure and quality conventions for rudder-iac. Use when writing, refactoring, or reviewing Go code to make consistent choices about package design, interfaces, context usage, error handling, concurrency, naming, and tests. Prioritize this skill whenever multiple valid Go implementations exist and you need the most idiomatic, maintainable option for this repository.