What problem does it solve?
Manually removing built-in Atomic CRM resources (contacts, companies, deals, tags, tasks) from the codebase is extremely error-prone, as these resources are woven into TypeScript types, shared subsystems, configuration props, frontend components, and Supabase backend database schemas. Missing even a single reference leads to broken builds, runtime errors, or orphaned database objects.
Core Features & Use Cases
- Automated core deletion: Runs a script to delete the selected resource's core component folder and prints a merged, de-duplicated list of all dependent files that require cleanup.
- Per-resource edge case guidance: Includes detailed guides for each of the five built-in resources covering shared subsystem adjustments (notes, activity log), aggregated field removal, i18n key cleanup, and backend schema migration steps.
- Use Case: You are customizing Atomic CRM for a use case that does not require the deals or tags features. Use this skill to fully remove the selected resource, then follow the provided guidance to clean up all related references without breaking the rest of the application.
Quick Start
Use the delete-initial-resource skill to remove the tags resource from your Atomic CRM codebase, then follow the printed dependent file list and per-resource guide to clean up all remaining references and pass typecheck and lint validation.
