Skip to content

Latest commit

 

History

History
110 lines (87 loc) · 6 KB

SKILL.md

File metadata and controls

110 lines (87 loc) · 6 KB
name description metadata
churchcrm
ChurchCRM project-specific development skills covering architecture, API, database, frontend, security, plugins, testing, and workflows. Use when working on any ChurchCRM feature, bug fix, or migration.
author version
ChurchCRM
1.0.0

ChurchCRM Development Skills

Project-specific skills for AI agents and developers working on ChurchCRM. Each skill covers a focused workflow area with ChurchCRM-specific patterns, conventions, and examples.

Architecture & API

Skill When to Use
Routing & Architecture Adding routes, organizing project file layout
Slim 4 Best Practices Building REST APIs, middleware configuration
Slim MVC Skill MVC route groups, migration guidance
API Development Creating/modifying REST API endpoints
API Compatibility & Deprecation Backward compatibility, deprecation timelines
Service Layer Creating business logic, service classes
Configuration Management Settings, SystemConfig, admin panels

Database

Skill When to Use
Database Operations ORM queries, Perpl ORM patterns, data persistence
DB Schema Migration Schema changes, migration scripts

Frontend & UI

Skill When to Use
Frontend Development UI changes, Bootstrap 4, i18n
Bootstrap 4.6.2 & AdminLTE UI components, layouts, admin pages
Webpack & TypeScript Frontend bundling, React, asset management
UI Development General UI development practices
i18n & Localization Adding UI text, translations
AI Locale Translation Translating missing terms via Claude AI before a release

Security

Skill When to Use
Authorization & Security Permission checks, authentication
Security Best Practices Security features, sensitive operations

Plugins

Skill When to Use
Plugin System Plugin architecture, hooks, PluginManager
Plugin Development Creating/modifying plugins
Plugin Migration Migrating plugins to new structure

Testing

Skill When to Use
Testing Writing tests, debugging, test suites
Cypress Testing E2E tests, CI/CD testing, API test patterns
Testing Migration & E2E Testing strategy for migrations

Before committing ANY test changes: See CLAUDE.md → Test Review & Commit Workflow for mandatory checklist

MVC Migration

Skill When to Use
Admin MVC Migration Migrating legacy pages to modern MVC
Groups MVC Guidelines Groups module MVC patterns
Refactor Refactoring legacy code to services/MVC

PHP & Performance

Skill When to Use
PHP Best Practices ChurchCRM PHP patterns, Perpl ORM
Modern PHP Frameworks Security hardening, framework features
Performance Optimization Query optimization, scaling, response times
Observability, Logging & Metrics Logging, metrics, monitoring

Development Process

Skill When to Use
Git Workflow Commits, PRs, pre-commit validation
GitHub Interaction Reviews, commits, PR management
PR Review Full PR review: fetch changes, validate standards, check docs/wiki, manual testing, address comments, capture learnings
PR Description Guidelines Ensure PR bodies are written in Markdown with required sections (Summary, Changes, Files Changed, Validation, Testing)
Development Workflows Setup, build, Docker management
Code Standards General coding, quality checks, PR reviews
Wiki Documentation Complex documentation, admin guides
Release Notes Authoring GitHub release notes for any version type
Social Media Release Generating platform posts for X, Facebook, Instagram, LinkedIn

Example Workflows

  • New API endpoint: api-development.md → service-layer.md → slim-4-best-practices.md → security-best-practices.md → cypress-testing.md → git-workflow.md
  • Migrate legacy page: routing-architecture.md → admin-mvc-migration.md → frontend-development.md → database-operations.md → git-workflow.md
  • Fix security issue: security-best-practices.md → authorization-security.md → php-best-practices.md → git-workflow.md
  • Add plugin: plugin-system.md → plugin-development.md → api-development.md → git-workflow.md
  • Optimize queries: performance-optimization.md → database-operations.md → service-layer.md
  • Add UI text: i18n-localization.md → frontend-development.md → git-workflow.md
  • Write release notes: release-notes.md → github-interaction.md
  • Publish a release: release-notes.md → social-media-release.md → github-interaction.md
  • Review a PR: pr-review.md → code-standards.md → security-best-practices.md → wiki-documentation.md
  • Address PR comments: pr-review.md → github-interaction.md → git-workflow.md