churchcrm

Plan and implement ChurchCRM development using Slim 4, Perpl ORM, and Bootstrap 5/Tabler patterns.

933|557|Updated Feb 16, 2015
One-click install
npx skills add https://github.com/ChurchCRM/CRM --skill churchcrm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churchcrm
Source: https://github.com/ChurchCRM/CRM/tree/main/.agents/skills/churchcrm
Command: npx skills add https://github.com/ChurchCRM/CRM --skill churchcrm

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about churchcrm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and implement ChurchCRM feature work using Slim 4 and Propel ORM?

To implement ChurchCRM features, apply project-specific patterns to routing, service layer extraction, and database migrations using Slim 4 and Propel ORM. This ensures architecture consistency and adherence to project engineering standards.

What is the recommended workflow for migrating ChurchCRM frontend components to Bootstrap 5 and Tabler?

Frontend migration to Bootstrap 5 and Tabler requires following specific UI consistency rules and asset tooling recommendations. This includes configuring Webpack, integrating React, and implementing i18n for localized interface components.

How do I enforce security and testing standards during ChurchCRM API development?

Security and testing standards are enforced by applying InputUtils and SlimUtils for validation, running Cypress for end-to-end testing, and documenting endpoints with OpenAPI to secure ChurchCRM API routing and service layers.

Does ChurchCRM development require specific Git workflows for release management?

ChurchCRM development requires specific release workflows and Git strategies to maintain code stability. Following these project-specific development workflows ensures proper version control and standardized feature deployment.

Can I use this skill to extract service layers and write database migrations for ChurchCRM?

Yes, you can extract service layers and write database migrations using tailored ChurchCRM patterns. The skill provides actionable references and examples for structuring Propel ORM database practices and service architecture.

What are the limitations when applying ChurchCRM-specific patterns to plugin development?

The ChurchCRM patterns focus specifically on the core stack of Slim 4, Propel ORM, and Bootstrap 5/Tabler. Plugin development must adhere strictly to these established security, testing, and architecture guidelines to avoid compatibility limitations.