property-building-guard

To enforce RLS guardrails, apply this skill when modifying property or building code. It mandates using user_profile_id() instead of auth.uid() and validates consistent admin and tenant access controls to prevent security regressions.

The best way to enforce strict type safety is by applying this guard during development. It mandates zero-use of any types and validates Zod-based schemas across property and building-related code to ensure structural integrity.

To add rate limiting on property mutation routes, activate this architectural guard. It enforces rate-limiting rules on API mutations, uses structured logging, and validates correct API route patterns to ensure safe operations.

You need architectural guardrails when creating or modifying properties, buildings, building_units, or related APIs and migrations. They prevent regressions by validating patterns, wizard store stability, and database type configurations.

Yes, this guardrail integrates with your existing setup by validating code in app/api/properties/, app/api/buildings/, features/properties/, and the wizard store. It ensures stability and enforces correct API route patterns during modifications.

Property building code fails review without strict type safety because architectural rules require zero-any typing and Zod validation. Activate this guard during reviews to validate configurations and prevent structural regressions.