What problem does it solve?
This Skill codifies Atomic CRM's Engineering Constitution to prevent over-engineering during pre-launch. It enforces fail-fast, a single composable entry point, and schema-driven form defaults. It guides developers to use Zod at the API boundary, maintain clear validation, and minimize complexity until user feedback justifies resilience patterns.
Core Features & Use Cases
- Fail-fast discipline: avoid retries, circuit breakers, and graceful fallbacks during pre-launch; loud failures for rapid iteration.
- Single composable entry point: consolidate data access behind a unified provider that delegates to resource modules with Zod-based API validation.
- Form defaults from schema: derive default form values from Zod schemas (e.g.,
zodSchema.partial().parse({})) to keep defaults in a single source of truth.
- Guidance on patterns: TypeScript types vs interfaces, React Admin patterns, and security/testing anti-patterns.
- Real-world use: apply these principles when implementing features, handling errors, adding validation, creating forms, and writing migrations.
Quick Start
- Start by auditing current code paths for retry logic and circuit breakers; remove resilience wrappers so failures throw to the operator.
- Ensure a unified data provider is in place and that validation happens at the API boundary using Zod schemas.
- Replace hardcoded form defaults with
zodSchema.partial().parse({}) and merge in runtime values.
- Avoid over-engineering until user feedback justifies more resilient patterns.
