use for cross-cutting engineering rules that are language/framework-agnostic, including communication, verification, validation, dependency choices, documentation quality, and feature lifecycle discipline.
Provide a single source-of-truth for reusable engineering guidance that applies across projects.
references/communication.md and references/coding-style-core.md for baseline execution quality.references/verification-core.md and references/validation-core.md when changing behavior.references/dependencies-core.md when adding/updating third-party tooling.references/documentation-core.md when producing or updating documentation.references/error-handling-core.md when defining or revising failure behavior.references/feature-implementation-core.mdreferences/feature-iteration-core.mdreferences/feature-removal.mdreferences/analytics-monitoring-core.md only when telemetry/observability is touched.references/tenant-isolation-conditional.md only when tenant guidance is enabled.references/compliance-conditional.md only when compliance guidance is enabled.../supabase-postgres-best-practices/SKILL.md before finalizing implementation decisions.Treat multi-tenant as enabled only with concrete evidence, such as:
tenant_id, account_id, org_id, similar)