What problem does it solve?
ChurchCRM teams often lack a unified, project-specific playbook that ties architecture guidance, API design patterns, database practices, frontend migration steps, security guidelines, plugin workflows, testing strategies, and development workflows into a single, actionable reference.
Core Features & Use Cases
- Guides for architecture and API development, including routing structures, service layer extraction, and migration patterns tailored to ChurchCRM.
- Frontend and UI migration guidance (Bootstrap 5/Tabler) with asset/tooling recommendations (Webpack, React, i18n) and consistency rules.
- Security, testing, and development workflows (InputUtils, SlimUtils, Cypress, Git workflows) with example implementations and references.
Quick Start
Describe your ChurchCRM feature or migration task using this skill to apply project-specific engineering standards and recommended workflows.