Copilot Instructions - ACF Service Management Suite

Project Identity

Plugin Name: ACF Service Management Suite
Purpose: Complete service business management for WordPress - locations, service areas, and team members
Author: Falls Technology Group, LLC
Developer: Ryan T. M. Reiffenberger (github.com/ReclaimerGold)
License: GPL v2 or later
Support: https://github.com/ReclaimerGold/acf-service-management-suite
Current Version: 2.2.0

Core Principles

1. NO FLUFF DOCUMENTATION

Every doc file must serve a specific, essential purpose
Combine related content - no fragmentation across multiple files
Use inline PHPDoc comments for code documentation
README.md is the primary user-facing doc (setup, usage, examples)
DEVELOP.md for extension/contribution only
CHANGELOG.md for version history only
No PLAN.md, USAGE.md, ROADMAP.md, or other redundant docs

2. NEVER CREATE BACKUP FILES

FORBIDDEN: Do NOT create files like

filename.old

filename.bak

filename-backup.extension

FORBIDDEN: Do NOT rename files to
```
filename.extension.old
```
before modifying
CORRECT: Use the
```
/workspace/
```
directory for temporary files, drafts, and experiments
CORRECT: Rely on Git history for file recovery
Delete obsolete files directly - Git maintains history
If you need to preserve something temporarily, put it in
```
/workspace/
```
(gitignored)

3. CONVENTIONAL COMMITS - STRICTLY ENFORCED

⚠️ CRITICAL: ALL code changes MUST include proper version management following Conventional Commits.

Version Management Rules

BEFORE making ANY code changes:

Determine the commit type and version impact
Update version in ALL required files TOGETHER
Add CHANGELOG entry for the new version
NEVER commit code changes without updating versions

Required Version Update Files (MUST ALL BE UPDATED TOGETHER):

acf-location-shortcodes.php

- Plugin header

Version:

AND

ACF_LS_VERSION

constant

```
README.md
```
- Version badge
```
DEVELOP.md
```
- Version and Last Updated date
```
copilot-instructions.md
```
- Current Version
```
CHANGELOG.md
```
- New version entry with changes

Version Determination:

feat:      → MINOR version bump (2.0.0 → 2.1.0)
feat!:     → MAJOR version bump (2.0.0 → 3.0.0)
fix:       → PATCH version bump (2.0.0 → 2.0.1)
docs:      → NO version bump (documentation only)
style:     → NO version bump (formatting only)
refactor:  → NO version bump (unless behavior changes)
perf:      → PATCH version bump (2.0.0 → 2.0.1)
test:      → NO version bump (tests only)
chore:     → NO version bump (unless dependencies change)

Example Version Update Workflow:

# 1. User requests: "Add team member filtering to Elementor"
# 2. Determine: feat: (new feature) → MINOR bump (2.1.0 → 2.2.0)

# 3. Update ALL version files:
#    - acf-location-shortcodes.php: Version: 2.2.0 + ACF_LS_VERSION = '2.2.0'
#    - README.md: Version-2.2.0-green
#    - DEVELOP.md: Version: 2.2.0, Last Updated: [current date]
#    - copilot-instructions.md: Current Version: 2.2.0
#    - CHANGELOG.md: Add [2.2.0] - [date] section

# 4. Make code changes
# 5. Commit: "feat: add hierarchical location support for Elementor filters"

CHANGELOG.md Format:

## [2.2.0] - 2025-10-31

### Added
- Hierarchical location support in Elementor filters
- Team member filtering by parent location for service areas

### Changed
- Filter dropdown now shows only physical locations
- Automatic parent detection for service area pages

### Fixed
- Team member queries on service area pages

Conventional Commits Specification

All commit messages MUST follow the Conventional Commits specification:

Format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types:

```
feat:
```
- New feature for the user (MINOR version bump)
```
fix:
```
- Bug fix for the user (PATCH version bump)
```
docs:
```
- Documentation only changes (NO version bump)
```
style:
```
- Code style changes (formatting, missing semi-colons, etc.) (NO version bump)
```
refactor:
```
- Code change that neither fixes a bug nor adds a feature (NO version bump)
```
perf:
```
- Performance improvement (PATCH version bump)
```
test:
```
- Adding or updating tests (NO version bump)
```
build:
```
- Changes to build system or dependencies (NO version bump)
```
ci:
```
- Changes to CI configuration files and scripts (NO version bump)
```
chore:
```
- Other changes that don't modify src or test files (NO version bump)
```
revert:
```
- Reverts a previous commit (depends on reverted change)

Scopes (optional but recommended):

feat(shortcodes): add location_address shortcode
fix(elementor): correct query filter for service areas
docs(readme): update installation instructions
perf(cache): implement object caching for communities

Examples:

# MINOR version bump (2.0.0 → 2.1.0)
feat: add automatic parent location detection
feat(elementor): add team member filtering by location

# PATCH version bump (2.0.0 → 2.0.1)
fix: resolve cache invalidation on post update
fix(shortcodes): handle missing ACF fields gracefully
perf(queries): optimize location hierarchy lookups

# NO version bump
docs: update README with Elementor usage examples
docs(develop): add contribution guidelines
style: format code to WordPress standards
refactor: extract validation into helper method
test: add unit tests for ACF helpers
chore: update .gitignore patterns

Breaking Changes (MAJOR version bump): Use

after type or add

BREAKING CHANGE:

in footer:

# MAJOR version bump (2.0.0 → 3.0.0)
feat!: rebrand to ACF Service Management Suite
refactor!: change text domain from acf-location-shortcodes to acf-sms

BREAKING CHANGE: Text domain changed, existing translations need update

AI Assistant Version Management Behavior

When user requests code changes:

ALWAYS ask yourself: "What type of change is this?" (feat/fix/docs/etc.)
ALWAYS determine version impact: Major/Minor/Patch/None
ALWAYS update ALL version files together before completing the task
ALWAYS add CHANGELOG entry with the new version
ALWAYS mention version bump in your response to user

Version Consistency Check: Before completing any task, verify ALL these match:

Plugin header
```
Version:
```
```
ACF_LS_VERSION
```
constant
README.md badge
DEVELOP.md version + date
copilot-instructions.md current version
CHANGELOG.md latest entry

If versions are inconsistent: Stop and fix ALL files before proceeding.

Release Process

Creating a release:

# After committing changes with proper version bumps:
git tag v2.1.0
git push origin v2.1.0

# GitHub Actions will automatically:
# - Run tests
# - Build release ZIP
# - Create GitHub Release
# - Generate release notes from CHANGELOG

Tag Format:

vMAJOR.MINOR.PATCH

(e.g.,

v2.1.0

) NEVER create tags without updating versions first.

4. MODERN PHP WORDPRESS PLUGIN STANDARDS

WordPress 5.8+ / PHP 7.4+ minimum
Follow WordPress Coding Standards (WPCS) strictly
Singleton pattern for main plugin class
Namespacing not required but class prefixing mandatory
PSR-4-style autoloading structure (manual requires acceptable)
Proper sanitization, escaping, and nonce verification
i18n ready with proper text domain
Object caching with reasonable expiration (1 hour default)

5. SECURITY FIRST

// ALWAYS check capabilities before sensitive operations
if ( ! current_user_can( 'manage_options' ) ) {
    wp_die( __( 'Insufficient permissions', 'acf-sms' ) );
}

// ALWAYS sanitize input
$location_id = absint( $_POST['location_id'] );
$field_name = sanitize_text_field( $_POST['field'] );

// ALWAYS escape output
echo esc_html( $title );
echo esc_attr( $class );
echo esc_url( $link );

// ALWAYS verify nonces for forms/AJAX
check_ajax_referer( 'acf_sms_action', 'nonce' );

5. PERFORMANCE OPTIMIZATION

// Use WordPress object cache
$cached = wp_cache_get( $key, 'acf_sms_locations' );
if ( false === $cached ) {
    $cached = expensive_operation();
    wp_cache_set( $key, $cached, 'acf_sms_locations', HOUR_IN_SECONDS );
}

// Lazy load integrations
if ( did_action( 'elementor/loaded' ) ) {
    // Only load Elementor integration if needed
}

// Minimize database queries
// Cache ACF field checks
// Use transients for expensive admin checks

6. ERROR HANDLING PHILOSOPHY

Errors must be actionable - tell user how to fix it
Include context - what was attempted, what was found
Provide debug data when ACF_LS_DEBUG enabled
Only show debug to users with
```
edit_posts
```
capability
Log important events to error_log when debug enabled

Technical Stack

Required:

WordPress 5.8+
PHP 7.4+
ACF 5.0+ (Free or Pro)

Optional:

Elementor 3.0+ (for query filtering)

Included:

Complete post type structure (
```
location
```
,
```
team-member
```
)
Pre-configured ACF field groups (15 total fields)
Team Member Type taxonomy

File Structure

acf-service-management-suite/
├── acf-service-management-suite.php     # Bootstrap (constants, singleton, hooks)
├── includes/
│   ├── class-acf-helpers.php            # ACF data retrieval + caching
│   ├── class-shortcodes.php             # All shortcode handlers
│   └── class-elementor-integration.php  # Elementor query filters
├── assets/
│   ├── css/shortcodes.css               # Minimal frontend styles
│   └── js/elementor-controls.js         # Elementor editor controls
├── .github/
│   └── workflows/
│       ├── test.yml                     # Automated testing (on push)
│       └── release.yml                  # Automated releases (on tag)
├── workspace/                           # GITIGNORED - temp files, drafts, notes
│   └── README.md                        # Explains workspace usage
├── acf-export-2025-10-28.json           # Field structure (import ready)
├── README.md                            # PRIMARY documentation (setup + usage)
├── DEVELOP.md                           # Extension/contribution guide
├── CHANGELOG.md                         # Version history
├── copilot-instructions.md              # This file
├── .gitignore                           # Excludes workspace/, *.old, *.bak
└── .gitattributes                       # Export exclusions (dev files)

NO OTHER .md FILES ALLOWED - Consolidate or delete. NO BACKUP FILES (.old, .bak, -copy) ALLOWED - Use workspace/ or Git history.

GitHub Actions Workflows

.github/workflows/test.yml

- Runs on every push/PR:

PHP syntax validation (7.4-8.3)
WordPress Coding Standards (PHPCS)
Plugin structure validation
Security scanning
Asset validation (CSS/JS)

.github/workflows/release.yml

- Runs on version tag push:

Validates tag format (vX.Y.Z)
Checks version consistency
Builds release package
Removes dev files (.github/, workspace/, DEVELOP.md)
Creates WordPress.org compatible readme.txt
Generates ZIP with checksums
Publishes GitHub Release

Class Architecture

Main Plugin Class:

ACF_Location_Shortcodes

class ACF_Location_Shortcodes {
    private static $instance = null;
    public $shortcodes;
    public $acf_helpers;
    public $elementor;
    
    public static function instance() { }
    private function __construct() { }
    private function init_hooks() { }
    public function check_dependencies() { }
    public function init() { }
    private function includes() { }
    public static function log( $message, $data = array(), $level = 'info' ) { }
}

ACF Helpers:

ACF_Location_Shortcodes_ACF_Helpers

```
get_surrounding_communities( $post_id )
```
- Get + cache communities
```
parse_comma_list( $string )
```
- Parse CSV to array
```
is_physical_location( $post_id )
```
- Check if has address
```
get_servicing_location( $post_id )
```
- Get parent location

get_location_field( $field, $post_id, $default )

- Generic getter

```
field_exists( $field_name, $post_id )
```
- Validation (v1.1.0+)
```
get_field_names( $post_id )
```
- List all fields (v1.1.0+)
```
clear_cache( $post_id )
```
- Manual cache clear

Shortcodes:

ACF_Location_Shortcodes_Shortcodes

```
[location_communities]
```
- Display surrounding communities
```
[location_info field="..."]
```
- Display any ACF field
```
[location_list]
```
- Location directory (two modes)
```
[location_address]
```
- Physical address (auto parent lookup)

render_error( $message, $debug_data = array() )

- Error display

Elementor:

ACF_Location_Shortcodes_Elementor

Hooks:
```
elementor/element/before_section_end
```
(add controls)
Hooks:
```
elementor/query/query_args
```
(filter queries)
Controls: Filter toggle, location selector, AND/OR mode
Query modification for relationship field filtering

ACF Field Reference

⚠️ CRITICAL: Always reference the master ACF template file for field structure.

Master Reference:

/acf-import-templates/acf-template.json

This file contains the complete, authoritative definition of:

All post types (location, team-member)
All custom fields with exact field names, types, and configurations
All taxonomies (team-member-type)
Field groups and their attachment rules
Conditional logic and field relationships

When working with ACF fields:

ALWAYS check
```
acf-template.json
```
for the exact field name
NEVER assume field names - verify against the template
ALWAYS use the correct field type (text, post_object, relationship, etc.)
ALWAYS respect field return formats (object vs ID vs array)
UPDATE the template file when adding new fields

Field Name Verification:

# Example: Finding a field in the template
grep -A 5 '"name": "field_name"' acf-import-templates/acf-template.json

Location Post Type Fields (11)

Defined in:

acf-import-templates/acf-template.json

→ Field Group: "Location Details"

```
service_area_shorthand
```
(Text) - "Sioux Falls, SD"
```
address
```
(Text) - Physical address (empty = service area)
```
phone_number
```
(Text) - Contact number
```
location_site_url
```
(URL) - Dedicated site
```
servicing_physical_location
```
(Post Object) - Parent location
```
full_service_area_name
```
(Text) - "Greater Sioux Falls"
```
located_near
```
(Text) - "Near Falls Park"
```
metro_area_name
```
(Text) - "Sioux Falls Metro"
```
county_name
```
(Text) - "Minnehaha County"
```
surrounding_community_list
```
(Text) - CSV communities
```
team_members_assigned
```
(Relationship) - Team members

Team Member Post Type Fields (4)

Defined in:

acf-import-templates/acf-template.json

→ Field Group: "Team Member Details"

```
profile_picture
```
(Image) - Photo (return format: array)
```
title
```
(Text) - Job title
```
location
```
(Post Object, Multiple) - Assigned locations (return format: object)
```
full_profile_url
```
(URL) - Full bio link

Location Type Logic:

WITH
```
address
```
= Physical Location
WITHOUT
```
address
```
= Service Area

Coding Patterns

Shortcode Handler Template

public function render_shortcode_name( $atts ) {
    // Parse attributes with defaults
    $atts = shortcode_atts( array(
        'location_id' => get_the_ID(),
        'field'       => '',
        'default'     => '',
        'class'       => '',
    ), $atts, 'shortcode_name' );
    
    // Sanitize inputs
    $location_id = absint( $atts['location_id'] );
    $field       = sanitize_text_field( $atts['field'] );
    $class       = sanitize_html_class( $atts['class'] );
    
    // Validate
    if ( empty( $location_id ) || 'location' !== get_post_type( $location_id ) ) {
        return $this->render_error(
            sprintf( __( 'Invalid location ID: %d', 'acf-sms' ), $location_id )
        );
    }
    
    // Get data with error handling
    $result = $this->acf_helpers->get_location_field_validated( $field, $location_id );
    if ( ! $result['success'] ) {
        return $this->render_error( $result['error'], $result['debug'] );
    }
    
    // Build output
    ob_start();
    ?>
    <div class="acf-sms-<?php echo esc_attr( $class ); ?>">
        <?php echo esc_html( $result['data'] ); ?>
    </div>
    <?php
    return ob_get_clean();
}

Error Rendering Pattern (v1.1.0+)

private function render_error( $message, $debug_data = array() ) {
    // Basic error for all users
    $output = sprintf(
        '<div class="acf-sms-error"><p>%s</p></div>',
        esc_html( $message )
    );
    
    // Debug data only for editors when debug enabled
    if ( defined( 'ACF_LS_DEBUG' ) && ACF_LS_DEBUG && current_user_can( 'edit_posts' ) && ! empty( $debug_data ) ) {
        $output .= sprintf(
            '<details class="acf-sms-debug"><summary>Debug Info</summary><pre>%s</pre></details>',
            esc_html( print_r( $debug_data, true ) )
        );
    }
    
    return $output;
}

Logging Pattern (v1.1.0+)

ACF_Location_Shortcodes::log(
    'Field validation failed',
    array(
        'field' => $field_name,
        'post_id' => $post_id,
        'available_fields' => $available,
    ),
    'warning' // or 'info', 'error'
);

Caching Pattern

$cache_key = 'communities_' . $post_id;
$cached = wp_cache_get( $cache_key, 'acf_sms_locations' );

if ( false !== $cached ) {
    ACF_Location_Shortcodes::log( 'Cache hit', array( 'key' => $cache_key ), 'info' );
    return $cached;
}

// Expensive operation
$data = $this->get_expensive_data( $post_id );

wp_cache_set( $cache_key, $data, 'acf_sms_locations', HOUR_IN_SECONDS );
ACF_Location_Shortcodes::log( 'Cache miss', array( 'key' => $cache_key ), 'info' );

return $data;

Version Management & Git Workflow

CRITICAL: Version Synchronization Rules

When bumping versions, update in this exact order:

CHANGELOG.md - Add new version section FIRST

## [2.0.0] - 2025-10-28
### Added
- Complete post type structure included
### Changed
- Rebranded to ACF Service Management Suite

acf-service-management-suite.php - Plugin header + constant

* Version: 2.2.0
define( 'ACF_LS_VERSION', '2.2.0' );

README.md - Badge + Credits section

[![Version](https://img.shields.io/badge/Version-2.2.0-green)]
**Version:** 2.2.0
**Last Updated:** October 31, 2025

copilot-instructions.md - Current Version field

**Current Version:** 2.2.0

Conventional Commits for Versioning

Version bumps trigger based on commit types:

```
feat:
```
commits → Increment MINOR version (2.1.0 → 2.2.0)
```
fix:
```
commits → Increment PATCH version (2.1.0 → 2.1.1)
```
feat!:
```
or
```
BREAKING CHANGE:
```
→ Increment MAJOR version (2.0.0 → 3.0.0)
```
docs:
```
,
```
style:
```
,
```
refactor:
```
,
```
perf:
```
,
```
test:
```
,
```
chore:
```
→ No version bump (unless bundled with feat/fix)

Example Version Flow:

# Current: 2.2.0
git commit -m "fix: resolve cache invalidation bug"
# Triggers: 2.1.0 → 2.1.1

git commit -m "feat: add location_distance shortcode"
# Triggers: 2.1.1 → 2.2.0

git commit -m "feat!: change shortcode attribute names for consistency"
# Triggers: 2.1.0 → 3.0.0

Pre-Release Checklist:

All commits since last release follow Conventional Commits format
CHANGELOG has new version section with categorized changes
All 4 files have matching version numbers
All dates are current date

Git tag created:

git tag -a v2.0.0 -m "chore: release v2.0.0"

Tag follows conventional commits:

git tag -a v2.0.0 -m "chore(release): version 2.0.0"

Semantic Versioning:

MAJOR (X.0.0) - Breaking changes (feat!, refactor! with BREAKING CHANGE)
MINOR (2.X.0) - New features, backwards compatible (feat:)
PATCH (2.0.X) - Bug fixes, security patches (fix:)

Commit Message for Version Bumps:

# When releasing a new version
git commit -m "chore(release): bump version to 2.1.0

- Updated version in plugin header
- Updated ACF_LS_VERSION constant
- Updated README.md version badge
- Updated copilot-instructions.md"

git tag -a v2.1.0 -m "chore(release): version 2.1.0"

Rebranded to ACF Service Management Suite


2. **acf-service-management-suite.php** - Plugin header + constant
```php
* Version: 2.2.0
define( 'ACF_LS_VERSION', '2.2.0' );

README.md - Badge + Credits section

[![Version](https://img.shields.io/badge/Version-2.2.0-green)]
**Version:** 2.2.0
**Last Updated:** October 31, 2025

copilot-instructions.md - Current Version field

**Current Version:** 2.2.0

Pre-Release Checklist:

All 4 files have matching version numbers
CHANGELOG has complete list of changes
All dates are current date
Git tag created:
```
git tag -a v2.2.0 -m "Version 2.2.0"
```
README credits updated with correct version

Semantic Versioning:

MAJOR (X.0.0) - Breaking changes, renamed plugin, architecture overhaul
MINOR (2.X.0) - New features, new shortcodes, backwards compatible
PATCH (2.0.X) - Bug fixes, security patches, performance tweaks

Development Workflow

File Handling Rules

FORBIDDEN - Never Create Backup Files:

# ❌ WRONG - Do not do this
mv file.php file.php.old
cp file.php file.php.backup
mv file.php file-old.php

CORRECT - Use Workspace or Git:

# ✅ CORRECT - For temporary preservation
cp file.php workspace/file-draft.php
mv draft.md workspace/planning-notes.md

# ✅ CORRECT - For file history
git log file.php
git show HEAD~1:file.php
git diff HEAD~1 file.php

# ✅ CORRECT - For complete removal
rm obsolete-file.md  # Git history preserves it

Workspace Directory Usage:

```
/workspace/
```
is gitignored - safe for local files
Use for drafts, experiments, planning notes
Use for temporary code before committing
Never commit workspace contents
Workspace/README.md explains its purpose

Before Writing Code

Check if ACF function exists:
```
if ( ! function_exists( 'get_field' ) )
```
Validate post ID and post type
Check field exists before calling
```
get_field()
```
Plan error messages - what will user see?
Consider debug output - what helps troubleshooting?
Plan conventional commit message - determines version impact

During Development

Follow WPCS (WordPress Coding Standards)
Add PHPDoc comments to all methods
Use i18n functions:
```
__()
```
,
```
_e()
```
,
```
esc_html__()
```
, etc.
Test with ACF Free AND Pro
Test with Elementor Free AND Pro
Test on mobile devices
Keep commits atomic - one logical change per commit
Write commit message first - clarifies what you're building

After Code Complete

Run PHP syntax check:
```
php -l filename.php
```
Check for errors: WP_DEBUG enabled
Test all shortcodes with various attributes
Test Elementor integration with real data
Verify caching works correctly
Write conventional commit message
Update CHANGELOG.md if version bump needed
Bump version numbers (all 4 files) if releasing

Commit Workflow

# 1. Write code for one feature/fix
# 2. Test thoroughly
# 3. Stage changes
git add includes/class-shortcodes.php

# 4. Commit with conventional format
git commit -m "feat(shortcodes): add location_distance shortcode

- Calculate distance between two locations
- Support multiple distance units (miles/km)
- Add caching for distance calculations"

# 5. If this triggers version bump (feat/fix/breaking)
# Update CHANGELOG.md, version numbers, then:
git add CHANGELOG.md acf-service-management-suite.php README.md copilot-instructions.md
git commit -m "chore(release): bump version to 2.1.0"
git tag -a v2.1.0 -m "chore(release): version 2.1.0"

Documentation Standards

README.md Structure (PRIMARY DOCS)

# Plugin Name
Badges, brief description

## Why Use This Plugin?
Bullet points only

## Features
Concise feature list with code examples

## Requirements
Min/recommended versions

## Installation
3 methods max (WordPress Admin, FTP, Git)

## Quick Start Guide
5 steps to first working shortcode

## Documentation
Shortcode reference tables inline (no separate files)

## Usage Examples
Real-world scenarios with code

## ACF Field Schema
Complete field reference + import instructions

## Troubleshooting
Common issues with solutions (no fluff)

## Support
GitHub issues link only

## License
Full GPL v2 text

## Credits
Author, company, version, date

What NOT to Include in Docs

❌ Redundant "About" or "Overview" sections
❌ Separate USAGE.md file (integrate into README)
❌ Separate PLAN.md file (architecture goes in DEVELOP.md)
❌ ROADMAP.md (future features go in GitHub Issues/Projects)
❌ Multiple "Getting Started" sections
❌ Excessive screenshots (code examples better)
❌ Marketing copy or sales language
❌ Repeated content across multiple files

DEVELOP.md Structure (DEVELOPERS ONLY)

# Development Guide
- Local environment setup
- Plugin architecture
- Coding standards
- Extension patterns (how to add shortcodes, fields, integrations)
- Testing procedures
- Contribution workflow
- Release process

CHANGELOG.md Structure (VERSION HISTORY ONLY)

# Changelog
## [Unreleased]
## [2.0.0] - 2025-10-28
### Added
### Changed
### Fixed
### Security

CSS Standards

BEM Methodology

/* Block */
.acf-sms-communities { }

/* Element */
.acf-sms-communities__item { }
.acf-sms-communities__emoji { }
.acf-sms-communities__text { }

/* Modifier */
.acf-sms-communities--vertical { }
.acf-sms-communities--grid { }

Minimal CSS Philosophy

Ship only essential styles
Use flexbox/grid for layouts
Mobile-first responsive
No
```
!important
```
unless absolutely necessary
Theme compatibility - use specificity wisely

Security Checklist

Input Validation

All
```
$_GET
```
,
```
$_POST
```
,
```
$_REQUEST
```
sanitized
ACF field data sanitized (it comes from DB, could be tampered)
Shortcode attributes parsed with
```
shortcode_atts()
```
Post IDs validated with
```
absint()
```
and post type check

Output Escaping

All echo/print statements escaped
Use
```
esc_html()
```
for text
Use
```
esc_attr()
```
for attributes
Use
```
esc_url()
```
for URLs
Use
```
wp_kses_post()
```
for HTML content

Capability Checks

Admin actions check
```
manage_options
```
or similar
Plugin install checks
```
install_plugins
```
+
```
activate_plugins
```
Debug output checks
```
edit_posts
```
minimum

Nonce Verification

All forms include nonce field
AJAX requests verify nonce
Use
```
wp_create_nonce()
```
and
```
check_ajax_referer()
```

Unit Testing Standards

Testing Framework

Required Stack:

PHPUnit 9.5+ for test execution
Brain Monkey for WordPress function mocking
Mockery for class mocking
Code coverage target: 80%+ for critical paths

Test Structure:

tests/
├── bootstrap.php              # Test suite bootstrap
├── TestCase.php               # Base test case with helpers
├── README.md                  # Complete testing documentation
├── mocks/
│   └── wordpress-functions.php # WordPress function mocks
├── Unit/
│   └── [ClassName]Test.php    # One test file per class
└── Integration/
    └── [Feature]Test.php      # Integration tests

Test Naming Conventions

Files:

[ClassName]Test.php

Examples:

ACFHelpersTest.php

ShortcodesTest.php

MultisiteSyncTest.php

Classes:

[ClassName]Test extends TestCase

Namespace:

ACF_SMS\Tests\Unit

ACF_SMS\Tests\Integration

Methods:

test_[method]_[scenario]_[expected]

Examples:

test_parse_comma_list_with_valid_input()

test_get_location_field_returns_default_when_empty()

test_shortcode_renders_error_for_invalid_post_type()

Writing Tests - The TDD Cycle

CRITICAL: Follow Test-Driven Development for ALL new features and bug fixes.

Step 1: Write Failing Test First

public function test_new_shortcode_renders_phone_number() {
    // Arrange
    $this->acf_helpers->shouldReceive( 'get_location_field' )
        ->with( 'phone_number', 123, '' )
        ->andReturn( '(605) 555-1234' );
    
    // Act
    $result = $this->shortcodes->location_phone( array() );
    
    // Assert
    $this->assertStringContainsString( '(605) 555-1234', $result );
    $this->assertNotContainsError( $result );
}

Step 2: Run Test - Verify It Fails

./vendor/bin/phpunit --filter test_new_shortcode
# Expected: FAIL (method doesn't exist)

Step 3: Implement Minimum Code

public function location_phone( $atts ) {
    $phone = $this->acf_helpers->get_location_field( 'phone_number', 123, '' );
    return sprintf( '<span>%s</span>', esc_html( $phone ) );
}

Step 4: Run Test - Verify It Passes

./vendor/bin/phpunit --filter test_new_shortcode
# Expected: PASS

Step 5: Add Edge Case Tests

public function test_new_shortcode_shows_error_when_no_phone() { }
public function test_new_shortcode_uses_custom_class() { }
public function test_new_shortcode_handles_invalid_location_id() { }

Unit Test Requirements

Every public method MUST have tests for:

✅ Normal/happy path (valid input, expected output)
✅ Edge cases (empty string, null, zero, large numbers)
✅ Error conditions (invalid input, missing data)
✅ Return types (string, array, bool, object)
✅ Side effects (cache operations, hooks fired)

Example: Comprehensive Method Testing

// Test suite for parse_comma_list()
public function test_parse_comma_list_with_valid_input() { }
public function test_parse_comma_list_with_extra_spaces() { }
public function test_parse_comma_list_with_empty_string() { }
public function test_parse_comma_list_with_single_item() { }
public function test_parse_comma_list_filters_empty_values() { }
public function test_parse_comma_list_with_null_input() { }

Code Coverage Requirements

Critical Classes (90%+ coverage required):

```
ACF_Location_Shortcodes_ACF_Helpers
```
- Core data layer
```
ACF_Location_Shortcodes_Shortcodes
```
- All shortcodes
```
ACF_Location_Shortcodes_Multisite_Sync
```
- Sync logic + media

Important Classes (75%+ coverage required):

```
ACF_Location_Shortcodes_Elementor
```
- Query filtering
```
ACF_Location_Shortcodes_Admin
```
- Admin interface
```
ACF_Location_Shortcodes_Network_Admin
```
- Network settings

Run coverage report:

composer test:coverage
# Generates coverage/index.html

Mocking Patterns

WordPress Functions (Brain Monkey):

use Brain\Monkey\Functions;

// Simple return
Functions\when( 'get_option' )->justReturn( 'value' );

// Return argument unchanged (escaping functions)
Functions\when( 'esc_html' )->returnArg();

// Expect exact call
Functions\expect( 'update_option' )
    ->once()
    ->with( 'key', 'value' )
    ->andReturn( true );

// Conditional logic
Functions\when( 'get_post_type' )->alias( function( $id ) {
    return $id === 123 ? 'location' : 'post';
} );

ACF Functions:

// Mock ACF helpers class
$this->acf_helpers = Mockery::mock( 'ACF_Location_Shortcodes_ACF_Helpers' );

$this->acf_helpers->shouldReceive( 'get_location_field' )
    ->once()
    ->with( 'phone_number', 123, '' )
    ->andReturn( '555-1234' );

Custom Assertions

Provided by base TestCase:

// Check HTML content
$this->assertStringContainsHTML( '<div class="test">', $output );

// Check for error display
$this->assertContainsError( $output );
$this->assertNotContainsError( $output );

// Mock post objects
$post = $this->createMockPost( array(
    'ID' => 123,
    'post_type' => 'location',
) );

// Mock ACF fields
$field = $this->createMockACFField( 'phone', 'text', '555-1234' );

Running Tests

All tests:

composer test
# or
./vendor/bin/phpunit

Unit tests only:

composer test:unit

Integration tests only:

composer test:integration

Specific test file:

./vendor/bin/phpunit tests/Unit/ACFHelpersTest.php

Specific test method:

./vendor/bin/phpunit --filter test_parse_comma_list

With coverage:

composer test:coverage

Pre-Commit Test Checklist

Before ANY commit with code changes:

Run full test suite:
```
composer test
```
All tests passing (100% success rate)
No warnings or deprecation notices
Code coverage ≥ 80% for changed files
New methods have corresponding tests
Bug fixes include regression tests

Conventional Commits for Tests

Test-related commits:

# Adding new tests (NO version bump)
git commit -m "test: add unit tests for media sync functionality"

# Updating tests (NO version bump)
git commit -m "test: update ACF helpers tests for new validation"

# Fixing tests (NO version bump)
git commit -m "test: fix failing integration test for multisite sync"

Version Impact:

test:

commits do NOT trigger version bumps.

Testing Best Practices

DO ✅

Write tests BEFORE implementing features (TDD)
Test one behavior per test method
Use descriptive test names (read like documentation)
Mock ALL external dependencies (WordPress, ACF, database)
Test edge cases (null, empty, invalid types)
Keep tests fast (< 100ms per test)
Use setup/teardown for common initialization
Test error handling explicitly
Verify security checks (capabilities, nonces)

DON'T ❌

Skip tests because "it's simple code"
Test WordPress core functionality
Write slow tests (file I/O, database queries in unit tests)
Share state between tests
Commit failing tests
Ignore coverage drops
Test implementation details (test behavior, not internals)
Copy-paste test code (use helpers/fixtures)

AI Assistant Testing Behavior

When adding a new feature:

FIRST: Write failing test
SECOND: Run test to verify failure
THIRD: Implement minimum code to pass
FOURTH: Run test to verify pass
FIFTH: Add edge case tests
SIXTH: Run full test suite
SEVENTH: Check code coverage
FINALLY: Provide test run output to user

When fixing a bug:

FIRST: Write regression test that reproduces bug
SECOND: Verify test fails
THIRD: Fix the bug
FOURTH: Verify test passes
FIFTH: Run full test suite

When updating existing code:

FIRST: Run existing tests
SECOND: Update tests for new behavior
THIRD: Update implementation
FOURTH: Verify all tests pass
FIFTH: Check coverage maintained

Response Format:

I'll add tests for [feature] following TDD:

1. Created failing test: tests/Unit/ClassTest.php::test_method_scenario()
2. Test output: FAIL (expected)
3. Implemented: includes/class-name.php::method()
4. Test output: PASS
5. Added edge cases: test_method_with_null(), test_method_with_empty()
6. Full test suite: 124 tests, 124 passed ✓
7. Code coverage: 87% (↑ from 85%)

Ready to commit with: test: add comprehensive tests for [feature]

Test Documentation

Complete testing guide:

tests/README.md

Installation instructions
Running tests (all scenarios)
Writing test guidelines
Mocking patterns
Debugging tests
CI/CD integration
Troubleshooting

Common Mistakes to Avoid

Don't echo in shortcodes - Always return string
Don't assume ACF exists - Check
```
function_exists('get_field')
```
Don't skip validation - Verify post type before using post ID
Don't hardcode IDs - Make configurable via attributes
Don't create separate doc files - Consolidate into README/DEVELOP
Don't write vague errors - Be specific and actionable
Don't forget mobile - Test responsive layouts
Don't skip version sync - Update all 4 files
NEVER create .old, .bak, or -backup files - Use workspace/ or Git
NEVER rename files to .old before editing - Edit in place, Git tracks history
ALWAYS use Conventional Commits - Determines version bumps
Don't mix commit types - One feat/fix/docs per commit
NEVER commit code without tests - TDD is mandatory
NEVER skip test runs - Run tests before every commit
NEVER ignore failing tests - Fix or update immediately

Testing Checklist

Manual Testing

Install on fresh WordPress install
Import ACF fields from JSON
Create test locations (physical + service areas)
Test all shortcodes with various attributes
Test Elementor query filtering
Test with WP_DEBUG enabled (no errors)
Test on mobile device/responsive view
Test with ACF Free and Pro
Test with Elementor Free and Pro

Error Testing

Invalid location ID shows clear error
Missing ACF field shows helpful error
Empty data shows appropriate message
Debug mode shows collapsible debug info
Non-editors don't see debug info

AI Assistant Behavior

When Asked to "Add a Feature"

Determine if it fits plugin scope
Draft conventional commit message (determines version impact)
Plan class/method structure
Write code following all standards above
Add error handling with actionable messages
Add logging if debug-worthy
Test thoroughly
Provide conventional commit message
Update CHANGELOG.md if version bump needed
Explain usage with example
NO separate planning doc - explain inline

When Asked to "Fix a Bug"

Ask for error details and context
Review relevant code section
Identify root cause
Implement fix with tests
Write conventional commit message (fix: ...)
Add entry to CHANGELOG.md (### Fixed)
Bump PATCH version if releasing
Explain what was wrong and how it's fixed

When Asked to "Update Documentation"

Determine which file (README, DEVELOP, or CHANGELOG)
Update inline - no new files
Keep language concise and technical
Remove fluff/marketing language
Use conventional commit (docs: or docs(readme):)
Ensure version numbers match across files
NO version bump for docs-only changes

When Asked to "Create Documentation"

STOP - Ask which existing file to update
Consolidate into README.md or DEVELOP.md
NO new .md files without explicit approval
Inline code documentation via PHPDoc only
Use conventional commit (docs: ...)

When Asked to "Save/Backup a File"

STOP - Never create .old, .bak, or backup files
Suggest: "I'll save a copy to workspace/ directory"

Execute:

cp file.php workspace/file-backup-YYYY-MM-DD.php

Explain: "Git history preserves all versions"
If file is obsolete: Delete it directly

When Making Any Changes

Always stage a conventional commit message
Determine version impact (major/minor/patch/none)
Make changes atomically (one logical change)
Update CHANGELOG.md if needed
Provide complete commit message in output
Provide usage example
NO separate planning doc - explain inline

When Asked to "Fix a Bug"

Ask for error details and context
Review relevant code section
Identify root cause
Implement fix with tests
Add entry to CHANGELOG.md (### Fixed)
Explain what was wrong and how it's fixed

When Asked to "Update Documentation"

Determine which file (README, DEVELOP, or CHANGELOG)
Update inline - no new files
Keep language concise and technical
Remove fluff/marketing language
Ensure version numbers match across files

When Asked to "Create Documentation"

STOP - Ask which existing file to update
Consolidate into README.md or DEVELOP.md
NO new .md files without explicit approval
Inline code documentation via PHPDoc only

Last Updated: October 28, 2025
Current Version: 2.0.0
Primary Developer: Ryan T. M. Reiffenberger
Company: Falls Technology Group, LLC

Copilot Instructions - ACF Service Management Suite

Project Identity

Core Principles

1. NO FLUFF DOCUMENTATION

Every doc file must serve a specific, essential purpose
Combine related content - no fragmentation across multiple files
Use inline PHPDoc comments for code documentation
README.md is the primary user-facing doc (setup, usage, examples)
DEVELOP.md for extension/contribution only
CHANGELOG.md for version history only
No PLAN.md, USAGE.md, ROADMAP.md, or other redundant docs

2. NEVER CREATE BACKUP FILES

FORBIDDEN: Do NOT create files like

filename.old

filename.bak

filename-backup.extension

FORBIDDEN: Do NOT rename files to
```
filename.extension.old
```
before modifying
CORRECT: Use the
```
/workspace/
```
directory for temporary files, drafts, and experiments
CORRECT: Rely on Git history for file recovery
Delete obsolete files directly - Git maintains history
If you need to preserve something temporarily, put it in
```
/workspace/
```
(gitignored)

3. CONVENTIONAL COMMITS - STRICTLY ENFORCED

⚠️ CRITICAL: ALL code changes MUST include proper version management following Conventional Commits.

Version Management Rules

BEFORE making ANY code changes:

Determine the commit type and version impact
Update version in ALL required files TOGETHER
Add CHANGELOG entry for the new version
NEVER commit code changes without updating versions

Required Version Update Files (MUST ALL BE UPDATED TOGETHER):

acf-location-shortcodes.php

- Plugin header

Version:

AND

ACF_LS_VERSION

constant

```
README.md
```
- Version badge
```
DEVELOP.md
```
- Version and Last Updated date
```
copilot-instructions.md
```
- Current Version
```
CHANGELOG.md
```
- New version entry with changes

Version Determination:

feat:      → MINOR version bump (2.0.0 → 2.1.0)
feat!:     → MAJOR version bump (2.0.0 → 3.0.0)
fix:       → PATCH version bump (2.0.0 → 2.0.1)
docs:      → NO version bump (documentation only)
style:     → NO version bump (formatting only)
refactor:  → NO version bump (unless behavior changes)
perf:      → PATCH version bump (2.0.0 → 2.0.1)
test:      → NO version bump (tests only)
chore:     → NO version bump (unless dependencies change)

Example Version Update Workflow:

# 1. User requests: "Add team member filtering to Elementor"
# 2. Determine: feat: (new feature) → MINOR bump (2.1.0 → 2.2.0)

# 3. Update ALL version files:
#    - acf-location-shortcodes.php: Version: 2.2.0 + ACF_LS_VERSION = '2.2.0'
#    - README.md: Version-2.2.0-green
#    - DEVELOP.md: Version: 2.2.0, Last Updated: [current date]
#    - copilot-instructions.md: Current Version: 2.2.0
#    - CHANGELOG.md: Add [2.2.0] - [date] section

# 4. Make code changes
# 5. Commit: "feat: add hierarchical location support for Elementor filters"

CHANGELOG.md Format:

## [2.2.0] - 2025-10-31

### Added
- Hierarchical location support in Elementor filters
- Team member filtering by parent location for service areas

### Changed
- Filter dropdown now shows only physical locations
- Automatic parent detection for service area pages

### Fixed
- Team member queries on service area pages

Conventional Commits Specification

All commit messages MUST follow the Conventional Commits specification:

Format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types:

```
feat:
```
- New feature for the user (MINOR version bump)
```
fix:
```
- Bug fix for the user (PATCH version bump)
```
docs:
```
- Documentation only changes (NO version bump)
```
style:
```
- Code style changes (formatting, missing semi-colons, etc.) (NO version bump)
```
refactor:
```
- Code change that neither fixes a bug nor adds a feature (NO version bump)
```
perf:
```
- Performance improvement (PATCH version bump)
```
test:
```
- Adding or updating tests (NO version bump)
```
build:
```
- Changes to build system or dependencies (NO version bump)
```
ci:
```
- Changes to CI configuration files and scripts (NO version bump)
```
chore:
```
- Other changes that don't modify src or test files (NO version bump)
```
revert:
```
- Reverts a previous commit (depends on reverted change)

Scopes (optional but recommended):

feat(shortcodes): add location_address shortcode
fix(elementor): correct query filter for service areas
docs(readme): update installation instructions
perf(cache): implement object caching for communities

Examples:

# MINOR version bump (2.0.0 → 2.1.0)
feat: add automatic parent location detection
feat(elementor): add team member filtering by location

# PATCH version bump (2.0.0 → 2.0.1)
fix: resolve cache invalidation on post update
fix(shortcodes): handle missing ACF fields gracefully
perf(queries): optimize location hierarchy lookups

# NO version bump
docs: update README with Elementor usage examples
docs(develop): add contribution guidelines
style: format code to WordPress standards
refactor: extract validation into helper method
test: add unit tests for ACF helpers
chore: update .gitignore patterns

Breaking Changes (MAJOR version bump): Use

after type or add

BREAKING CHANGE:

in footer:

# MAJOR version bump (2.0.0 → 3.0.0)
feat!: rebrand to ACF Service Management Suite
refactor!: change text domain from acf-location-shortcodes to acf-sms

BREAKING CHANGE: Text domain changed, existing translations need update

AI Assistant Version Management Behavior

When user requests code changes:

ALWAYS ask yourself: "What type of change is this?" (feat/fix/docs/etc.)
ALWAYS determine version impact: Major/Minor/Patch/None
ALWAYS update ALL version files together before completing the task
ALWAYS add CHANGELOG entry with the new version
ALWAYS mention version bump in your response to user

Version Consistency Check: Before completing any task, verify ALL these match:

Plugin header
```
Version:
```
```
ACF_LS_VERSION
```
constant
README.md badge
DEVELOP.md version + date
copilot-instructions.md current version
CHANGELOG.md latest entry

If versions are inconsistent: Stop and fix ALL files before proceeding.

Release Process

Creating a release:

# After committing changes with proper version bumps:
git tag v2.1.0
git push origin v2.1.0

# GitHub Actions will automatically:
# - Run tests
# - Build release ZIP
# - Create GitHub Release
# - Generate release notes from CHANGELOG

Tag Format:

vMAJOR.MINOR.PATCH

(e.g.,

v2.1.0

) NEVER create tags without updating versions first.

4. MODERN PHP WORDPRESS PLUGIN STANDARDS

WordPress 5.8+ / PHP 7.4+ minimum
Follow WordPress Coding Standards (WPCS) strictly
Singleton pattern for main plugin class
Namespacing not required but class prefixing mandatory
PSR-4-style autoloading structure (manual requires acceptable)
Proper sanitization, escaping, and nonce verification
i18n ready with proper text domain
Object caching with reasonable expiration (1 hour default)

5. SECURITY FIRST

// ALWAYS check capabilities before sensitive operations
if ( ! current_user_can( 'manage_options' ) ) {
    wp_die( __( 'Insufficient permissions', 'acf-sms' ) );
}

// ALWAYS sanitize input
$location_id = absint( $_POST['location_id'] );
$field_name = sanitize_text_field( $_POST['field'] );

// ALWAYS escape output
echo esc_html( $title );
echo esc_attr( $class );
echo esc_url( $link );

// ALWAYS verify nonces for forms/AJAX
check_ajax_referer( 'acf_sms_action', 'nonce' );

5. PERFORMANCE OPTIMIZATION

// Use WordPress object cache
$cached = wp_cache_get( $key, 'acf_sms_locations' );
if ( false === $cached ) {
    $cached = expensive_operation();
    wp_cache_set( $key, $cached, 'acf_sms_locations', HOUR_IN_SECONDS );
}

// Lazy load integrations
if ( did_action( 'elementor/loaded' ) ) {
    // Only load Elementor integration if needed
}

// Minimize database queries
// Cache ACF field checks
// Use transients for expensive admin checks

6. ERROR HANDLING PHILOSOPHY

Errors must be actionable - tell user how to fix it
Include context - what was attempted, what was found
Provide debug data when ACF_LS_DEBUG enabled
Only show debug to users with
```
edit_posts
```
capability
Log important events to error_log when debug enabled

Technical Stack

Required:

WordPress 5.8+
PHP 7.4+
ACF 5.0+ (Free or Pro)

Optional:

Elementor 3.0+ (for query filtering)

Included:

Complete post type structure (
```
location
```
,
```
team-member
```
)
Pre-configured ACF field groups (15 total fields)
Team Member Type taxonomy

File Structure

acf-service-management-suite/
├── acf-service-management-suite.php     # Bootstrap (constants, singleton, hooks)
├── includes/
│   ├── class-acf-helpers.php            # ACF data retrieval + caching
│   ├── class-shortcodes.php             # All shortcode handlers
│   └── class-elementor-integration.php  # Elementor query filters
├── assets/
│   ├── css/shortcodes.css               # Minimal frontend styles
│   └── js/elementor-controls.js         # Elementor editor controls
├── .github/
│   └── workflows/
│       ├── test.yml                     # Automated testing (on push)
│       └── release.yml                  # Automated releases (on tag)
├── workspace/                           # GITIGNORED - temp files, drafts, notes
│   └── README.md                        # Explains workspace usage
├── acf-export-2025-10-28.json           # Field structure (import ready)
├── README.md                            # PRIMARY documentation (setup + usage)
├── DEVELOP.md                           # Extension/contribution guide
├── CHANGELOG.md                         # Version history
├── copilot-instructions.md              # This file
├── .gitignore                           # Excludes workspace/, *.old, *.bak
└── .gitattributes                       # Export exclusions (dev files)

NO OTHER .md FILES ALLOWED - Consolidate or delete. NO BACKUP FILES (.old, .bak, -copy) ALLOWED - Use workspace/ or Git history.

GitHub Actions Workflows

.github/workflows/test.yml

- Runs on every push/PR:

PHP syntax validation (7.4-8.3)
WordPress Coding Standards (PHPCS)
Plugin structure validation
Security scanning
Asset validation (CSS/JS)

.github/workflows/release.yml

- Runs on version tag push:

Validates tag format (vX.Y.Z)
Checks version consistency
Builds release package
Removes dev files (.github/, workspace/, DEVELOP.md)
Creates WordPress.org compatible readme.txt
Generates ZIP with checksums
Publishes GitHub Release

Class Architecture

Main Plugin Class:

ACF_Location_Shortcodes

class ACF_Location_Shortcodes {
    private static $instance = null;
    public $shortcodes;
    public $acf_helpers;
    public $elementor;
    
    public static function instance() { }
    private function __construct() { }
    private function init_hooks() { }
    public function check_dependencies() { }
    public function init() { }
    private function includes() { }
    public static function log( $message, $data = array(), $level = 'info' ) { }
}

ACF Helpers:

ACF_Location_Shortcodes_ACF_Helpers

```
get_surrounding_communities( $post_id )
```
- Get + cache communities
```
parse_comma_list( $string )
```
- Parse CSV to array
```
is_physical_location( $post_id )
```
- Check if has address
```
get_servicing_location( $post_id )
```
- Get parent location

get_location_field( $field, $post_id, $default )

- Generic getter

```
field_exists( $field_name, $post_id )
```
- Validation (v1.1.0+)
```
get_field_names( $post_id )
```
- List all fields (v1.1.0+)
```
clear_cache( $post_id )
```
- Manual cache clear

Shortcodes:

ACF_Location_Shortcodes_Shortcodes

```
[location_communities]
```
- Display surrounding communities
```
[location_info field="..."]
```
- Display any ACF field
```
[location_list]
```
- Location directory (two modes)
```
[location_address]
```
- Physical address (auto parent lookup)

render_error( $message, $debug_data = array() )

- Error display

Elementor:

ACF_Location_Shortcodes_Elementor

Hooks:
```
elementor/element/before_section_end
```
(add controls)
Hooks:
```
elementor/query/query_args
```
(filter queries)
Controls: Filter toggle, location selector, AND/OR mode
Query modification for relationship field filtering

ACF Field Reference

⚠️ CRITICAL: Always reference the master ACF template file for field structure.

Master Reference:

/acf-import-templates/acf-template.json

This file contains the complete, authoritative definition of:

All post types (location, team-member)
All custom fields with exact field names, types, and configurations
All taxonomies (team-member-type)
Field groups and their attachment rules
Conditional logic and field relationships

When working with ACF fields:

ALWAYS check
```
acf-template.json
```
for the exact field name
NEVER assume field names - verify against the template
ALWAYS use the correct field type (text, post_object, relationship, etc.)
ALWAYS respect field return formats (object vs ID vs array)
UPDATE the template file when adding new fields

Field Name Verification:

# Example: Finding a field in the template
grep -A 5 '"name": "field_name"' acf-import-templates/acf-template.json

Location Post Type Fields (11)

Defined in:

acf-import-templates/acf-template.json

→ Field Group: "Location Details"

```
service_area_shorthand
```
(Text) - "Sioux Falls, SD"
```
address
```
(Text) - Physical address (empty = service area)
```
phone_number
```
(Text) - Contact number
```
location_site_url
```
(URL) - Dedicated site
```
servicing_physical_location
```
(Post Object) - Parent location
```
full_service_area_name
```
(Text) - "Greater Sioux Falls"
```
located_near
```
(Text) - "Near Falls Park"
```
metro_area_name
```
(Text) - "Sioux Falls Metro"
```
county_name
```
(Text) - "Minnehaha County"
```
surrounding_community_list
```
(Text) - CSV communities
```
team_members_assigned
```
(Relationship) - Team members

Team Member Post Type Fields (4)

Defined in:

acf-import-templates/acf-template.json

→ Field Group: "Team Member Details"

```
profile_picture
```
(Image) - Photo (return format: array)
```
title
```
(Text) - Job title
```
location
```
(Post Object, Multiple) - Assigned locations (return format: object)
```
full_profile_url
```
(URL) - Full bio link

Location Type Logic:

WITH
```
address
```
= Physical Location
WITHOUT
```
address
```
= Service Area

Coding Patterns

Shortcode Handler Template

public function render_shortcode_name( $atts ) {
    // Parse attributes with defaults
    $atts = shortcode_atts( array(
        'location_id' => get_the_ID(),
        'field'       => '',
        'default'     => '',
        'class'       => '',
    ), $atts, 'shortcode_name' );
    
    // Sanitize inputs
    $location_id = absint( $atts['location_id'] );
    $field       = sanitize_text_field( $atts['field'] );
    $class       = sanitize_html_class( $atts['class'] );
    
    // Validate
    if ( empty( $location_id ) || 'location' !== get_post_type( $location_id ) ) {
        return $this->render_error(
            sprintf( __( 'Invalid location ID: %d', 'acf-sms' ), $location_id )
        );
    }
    
    // Get data with error handling
    $result = $this->acf_helpers->get_location_field_validated( $field, $location_id );
    if ( ! $result['success'] ) {
        return $this->render_error( $result['error'], $result['debug'] );
    }
    
    // Build output
    ob_start();
    ?>
    <div class="acf-sms-<?php echo esc_attr( $class ); ?>">
        <?php echo esc_html( $result['data'] ); ?>
    </div>
    <?php
    return ob_get_clean();
}

Error Rendering Pattern (v1.1.0+)

private function render_error( $message, $debug_data = array() ) {
    // Basic error for all users
    $output = sprintf(
        '<div class="acf-sms-error"><p>%s</p></div>',
        esc_html( $message )
    );
    
    // Debug data only for editors when debug enabled
    if ( defined( 'ACF_LS_DEBUG' ) && ACF_LS_DEBUG && current_user_can( 'edit_posts' ) && ! empty( $debug_data ) ) {
        $output .= sprintf(
            '<details class="acf-sms-debug"><summary>Debug Info</summary><pre>%s</pre></details>',
            esc_html( print_r( $debug_data, true ) )
        );
    }
    
    return $output;
}

Logging Pattern (v1.1.0+)

ACF_Location_Shortcodes::log(
    'Field validation failed',
    array(
        'field' => $field_name,
        'post_id' => $post_id,
        'available_fields' => $available,
    ),
    'warning' // or 'info', 'error'
);

Caching Pattern

$cache_key = 'communities_' . $post_id;
$cached = wp_cache_get( $cache_key, 'acf_sms_locations' );

if ( false !== $cached ) {
    ACF_Location_Shortcodes::log( 'Cache hit', array( 'key' => $cache_key ), 'info' );
    return $cached;
}

// Expensive operation
$data = $this->get_expensive_data( $post_id );

wp_cache_set( $cache_key, $data, 'acf_sms_locations', HOUR_IN_SECONDS );
ACF_Location_Shortcodes::log( 'Cache miss', array( 'key' => $cache_key ), 'info' );

return $data;

Version Management & Git Workflow

CRITICAL: Version Synchronization Rules

When bumping versions, update in this exact order:

CHANGELOG.md - Add new version section FIRST

## [2.0.0] - 2025-10-28
### Added
- Complete post type structure included
### Changed
- Rebranded to ACF Service Management Suite

acf-service-management-suite.php - Plugin header + constant

* Version: 2.2.0
define( 'ACF_LS_VERSION', '2.2.0' );

README.md - Badge + Credits section

[![Version](https://img.shields.io/badge/Version-2.2.0-green)]
**Version:** 2.2.0
**Last Updated:** October 31, 2025

copilot-instructions.md - Current Version field

**Current Version:** 2.2.0

Conventional Commits for Versioning

Version bumps trigger based on commit types:

```
feat:
```
commits → Increment MINOR version (2.1.0 → 2.2.0)
```
fix:
```
commits → Increment PATCH version (2.1.0 → 2.1.1)
```
feat!:
```
or
```
BREAKING CHANGE:
```
→ Increment MAJOR version (2.0.0 → 3.0.0)
```
docs:
```
,
```
style:
```
,
```
refactor:
```
,
```
perf:
```
,
```
test:
```
,
```
chore:
```
→ No version bump (unless bundled with feat/fix)

Example Version Flow:

# Current: 2.2.0
git commit -m "fix: resolve cache invalidation bug"
# Triggers: 2.1.0 → 2.1.1

git commit -m "feat: add location_distance shortcode"
# Triggers: 2.1.1 → 2.2.0

git commit -m "feat!: change shortcode attribute names for consistency"
# Triggers: 2.1.0 → 3.0.0

Pre-Release Checklist:

All commits since last release follow Conventional Commits format
CHANGELOG has new version section with categorized changes
All 4 files have matching version numbers
All dates are current date

Git tag created:

git tag -a v2.0.0 -m "chore: release v2.0.0"

Tag follows conventional commits:

git tag -a v2.0.0 -m "chore(release): version 2.0.0"

Semantic Versioning:

MAJOR (X.0.0) - Breaking changes (feat!, refactor! with BREAKING CHANGE)
MINOR (2.X.0) - New features, backwards compatible (feat:)
PATCH (2.0.X) - Bug fixes, security patches (fix:)

Commit Message for Version Bumps:

# When releasing a new version
git commit -m "chore(release): bump version to 2.1.0

- Updated version in plugin header
- Updated ACF_LS_VERSION constant
- Updated README.md version badge
- Updated copilot-instructions.md"

git tag -a v2.1.0 -m "chore(release): version 2.1.0"

Rebranded to ACF Service Management Suite


2. **acf-service-management-suite.php** - Plugin header + constant
```php
* Version: 2.2.0
define( 'ACF_LS_VERSION', '2.2.0' );

README.md - Badge + Credits section

[![Version](https://img.shields.io/badge/Version-2.2.0-green)]
**Version:** 2.2.0
**Last Updated:** October 31, 2025

copilot-instructions.md - Current Version field

**Current Version:** 2.2.0

Pre-Release Checklist:

All 4 files have matching version numbers
CHANGELOG has complete list of changes
All dates are current date
Git tag created:
```
git tag -a v2.2.0 -m "Version 2.2.0"
```
README credits updated with correct version

Semantic Versioning:

MAJOR (X.0.0) - Breaking changes, renamed plugin, architecture overhaul
MINOR (2.X.0) - New features, new shortcodes, backwards compatible
PATCH (2.0.X) - Bug fixes, security patches, performance tweaks

Development Workflow

File Handling Rules

FORBIDDEN - Never Create Backup Files:

# ❌ WRONG - Do not do this
mv file.php file.php.old
cp file.php file.php.backup
mv file.php file-old.php

CORRECT - Use Workspace or Git:

# ✅ CORRECT - For temporary preservation
cp file.php workspace/file-draft.php
mv draft.md workspace/planning-notes.md

# ✅ CORRECT - For file history
git log file.php
git show HEAD~1:file.php
git diff HEAD~1 file.php

# ✅ CORRECT - For complete removal
rm obsolete-file.md  # Git history preserves it

Workspace Directory Usage:

```
/workspace/
```
is gitignored - safe for local files
Use for drafts, experiments, planning notes
Use for temporary code before committing
Never commit workspace contents
Workspace/README.md explains its purpose

Before Writing Code

Check if ACF function exists:
```
if ( ! function_exists( 'get_field' ) )
```
Validate post ID and post type
Check field exists before calling
```
get_field()
```
Plan error messages - what will user see?
Consider debug output - what helps troubleshooting?
Plan conventional commit message - determines version impact

During Development

Follow WPCS (WordPress Coding Standards)
Add PHPDoc comments to all methods
Use i18n functions:
```
__()
```
,
```
_e()
```
,
```
esc_html__()
```
, etc.
Test with ACF Free AND Pro
Test with Elementor Free AND Pro
Test on mobile devices
Keep commits atomic - one logical change per commit
Write commit message first - clarifies what you're building

After Code Complete

Run PHP syntax check:
```
php -l filename.php
```
Check for errors: WP_DEBUG enabled
Test all shortcodes with various attributes
Test Elementor integration with real data
Verify caching works correctly
Write conventional commit message
Update CHANGELOG.md if version bump needed
Bump version numbers (all 4 files) if releasing

Commit Workflow

# 1. Write code for one feature/fix
# 2. Test thoroughly
# 3. Stage changes
git add includes/class-shortcodes.php

# 4. Commit with conventional format
git commit -m "feat(shortcodes): add location_distance shortcode

- Calculate distance between two locations
- Support multiple distance units (miles/km)
- Add caching for distance calculations"

# 5. If this triggers version bump (feat/fix/breaking)
# Update CHANGELOG.md, version numbers, then:
git add CHANGELOG.md acf-service-management-suite.php README.md copilot-instructions.md
git commit -m "chore(release): bump version to 2.1.0"
git tag -a v2.1.0 -m "chore(release): version 2.1.0"

Documentation Standards

README.md Structure (PRIMARY DOCS)

# Plugin Name
Badges, brief description

## Why Use This Plugin?
Bullet points only

## Features
Concise feature list with code examples

## Requirements
Min/recommended versions

## Installation
3 methods max (WordPress Admin, FTP, Git)

## Quick Start Guide
5 steps to first working shortcode

## Documentation
Shortcode reference tables inline (no separate files)

## Usage Examples
Real-world scenarios with code

## ACF Field Schema
Complete field reference + import instructions

## Troubleshooting
Common issues with solutions (no fluff)

## Support
GitHub issues link only

## License
Full GPL v2 text

## Credits
Author, company, version, date

What NOT to Include in Docs

❌ Redundant "About" or "Overview" sections
❌ Separate USAGE.md file (integrate into README)
❌ Separate PLAN.md file (architecture goes in DEVELOP.md)
❌ ROADMAP.md (future features go in GitHub Issues/Projects)
❌ Multiple "Getting Started" sections
❌ Excessive screenshots (code examples better)
❌ Marketing copy or sales language
❌ Repeated content across multiple files

DEVELOP.md Structure (DEVELOPERS ONLY)

# Development Guide
- Local environment setup
- Plugin architecture
- Coding standards
- Extension patterns (how to add shortcodes, fields, integrations)
- Testing procedures
- Contribution workflow
- Release process

CHANGELOG.md Structure (VERSION HISTORY ONLY)

# Changelog
## [Unreleased]
## [2.0.0] - 2025-10-28
### Added
### Changed
### Fixed
### Security

CSS Standards

BEM Methodology

/* Block */
.acf-sms-communities { }

/* Element */
.acf-sms-communities__item { }
.acf-sms-communities__emoji { }
.acf-sms-communities__text { }

/* Modifier */
.acf-sms-communities--vertical { }
.acf-sms-communities--grid { }

Minimal CSS Philosophy

Ship only essential styles
Use flexbox/grid for layouts
Mobile-first responsive
No
```
!important
```
unless absolutely necessary
Theme compatibility - use specificity wisely

Security Checklist

Input Validation

All
```
$_GET
```
,
```
$_POST
```
,
```
$_REQUEST
```
sanitized
ACF field data sanitized (it comes from DB, could be tampered)
Shortcode attributes parsed with
```
shortcode_atts()
```
Post IDs validated with
```
absint()
```
and post type check

Output Escaping

All echo/print statements escaped
Use
```
esc_html()
```
for text
Use
```
esc_attr()
```
for attributes
Use
```
esc_url()
```
for URLs
Use
```
wp_kses_post()
```
for HTML content

Capability Checks

Admin actions check
```
manage_options
```
or similar
Plugin install checks
```
install_plugins
```
+
```
activate_plugins
```
Debug output checks
```
edit_posts
```
minimum

Nonce Verification

All forms include nonce field
AJAX requests verify nonce
Use
```
wp_create_nonce()
```
and
```
check_ajax_referer()
```

Unit Testing Standards

Testing Framework

Required Stack:

PHPUnit 9.5+ for test execution
Brain Monkey for WordPress function mocking
Mockery for class mocking
Code coverage target: 80%+ for critical paths

Test Structure:

tests/
├── bootstrap.php              # Test suite bootstrap
├── TestCase.php               # Base test case with helpers
├── README.md                  # Complete testing documentation
├── mocks/
│   └── wordpress-functions.php # WordPress function mocks
├── Unit/
│   └── [ClassName]Test.php    # One test file per class
└── Integration/
    └── [Feature]Test.php      # Integration tests

Test Naming Conventions

Files:

[ClassName]Test.php

Examples:

ACFHelpersTest.php

ShortcodesTest.php

MultisiteSyncTest.php

Classes:

[ClassName]Test extends TestCase

Namespace:

ACF_SMS\Tests\Unit

ACF_SMS\Tests\Integration

Methods:

test_[method]_[scenario]_[expected]

Examples:

test_parse_comma_list_with_valid_input()

test_get_location_field_returns_default_when_empty()

test_shortcode_renders_error_for_invalid_post_type()

Writing Tests - The TDD Cycle

CRITICAL: Follow Test-Driven Development for ALL new features and bug fixes.

Step 1: Write Failing Test First

public function test_new_shortcode_renders_phone_number() {
    // Arrange
    $this->acf_helpers->shouldReceive( 'get_location_field' )
        ->with( 'phone_number', 123, '' )
        ->andReturn( '(605) 555-1234' );
    
    // Act
    $result = $this->shortcodes->location_phone( array() );
    
    // Assert
    $this->assertStringContainsString( '(605) 555-1234', $result );
    $this->assertNotContainsError( $result );
}

Step 2: Run Test - Verify It Fails

./vendor/bin/phpunit --filter test_new_shortcode
# Expected: FAIL (method doesn't exist)

Step 3: Implement Minimum Code

public function location_phone( $atts ) {
    $phone = $this->acf_helpers->get_location_field( 'phone_number', 123, '' );
    return sprintf( '<span>%s</span>', esc_html( $phone ) );
}

Step 4: Run Test - Verify It Passes

./vendor/bin/phpunit --filter test_new_shortcode
# Expected: PASS

Step 5: Add Edge Case Tests

public function test_new_shortcode_shows_error_when_no_phone() { }
public function test_new_shortcode_uses_custom_class() { }
public function test_new_shortcode_handles_invalid_location_id() { }

Unit Test Requirements

Every public method MUST have tests for:

✅ Normal/happy path (valid input, expected output)
✅ Edge cases (empty string, null, zero, large numbers)
✅ Error conditions (invalid input, missing data)
✅ Return types (string, array, bool, object)
✅ Side effects (cache operations, hooks fired)

Example: Comprehensive Method Testing

// Test suite for parse_comma_list()
public function test_parse_comma_list_with_valid_input() { }
public function test_parse_comma_list_with_extra_spaces() { }
public function test_parse_comma_list_with_empty_string() { }
public function test_parse_comma_list_with_single_item() { }
public function test_parse_comma_list_filters_empty_values() { }
public function test_parse_comma_list_with_null_input() { }

Code Coverage Requirements

Critical Classes (90%+ coverage required):

```
ACF_Location_Shortcodes_ACF_Helpers
```
- Core data layer
```
ACF_Location_Shortcodes_Shortcodes
```
- All shortcodes
```
ACF_Location_Shortcodes_Multisite_Sync
```
- Sync logic + media

Important Classes (75%+ coverage required):

```
ACF_Location_Shortcodes_Elementor
```
- Query filtering
```
ACF_Location_Shortcodes_Admin
```
- Admin interface
```
ACF_Location_Shortcodes_Network_Admin
```
- Network settings

Run coverage report:

composer test:coverage
# Generates coverage/index.html

Mocking Patterns

WordPress Functions (Brain Monkey):

use Brain\Monkey\Functions;

// Simple return
Functions\when( 'get_option' )->justReturn( 'value' );

// Return argument unchanged (escaping functions)
Functions\when( 'esc_html' )->returnArg();

// Expect exact call
Functions\expect( 'update_option' )
    ->once()
    ->with( 'key', 'value' )
    ->andReturn( true );

// Conditional logic
Functions\when( 'get_post_type' )->alias( function( $id ) {
    return $id === 123 ? 'location' : 'post';
} );

ACF Functions:

// Mock ACF helpers class
$this->acf_helpers = Mockery::mock( 'ACF_Location_Shortcodes_ACF_Helpers' );

$this->acf_helpers->shouldReceive( 'get_location_field' )
    ->once()
    ->with( 'phone_number', 123, '' )
    ->andReturn( '555-1234' );

Custom Assertions

Provided by base TestCase:

// Check HTML content
$this->assertStringContainsHTML( '<div class="test">', $output );

// Check for error display
$this->assertContainsError( $output );
$this->assertNotContainsError( $output );

// Mock post objects
$post = $this->createMockPost( array(
    'ID' => 123,
    'post_type' => 'location',
) );

// Mock ACF fields
$field = $this->createMockACFField( 'phone', 'text', '555-1234' );

Running Tests

All tests:

composer test
# or
./vendor/bin/phpunit

Unit tests only:

composer test:unit

Integration tests only:

composer test:integration

Specific test file:

./vendor/bin/phpunit tests/Unit/ACFHelpersTest.php

Specific test method:

./vendor/bin/phpunit --filter test_parse_comma_list

With coverage:

composer test:coverage

Pre-Commit Test Checklist

Before ANY commit with code changes:

Run full test suite:
```
composer test
```
All tests passing (100% success rate)
No warnings or deprecation notices
Code coverage ≥ 80% for changed files
New methods have corresponding tests
Bug fixes include regression tests

Conventional Commits for Tests

Test-related commits:

# Adding new tests (NO version bump)
git commit -m "test: add unit tests for media sync functionality"

# Updating tests (NO version bump)
git commit -m "test: update ACF helpers tests for new validation"

# Fixing tests (NO version bump)
git commit -m "test: fix failing integration test for multisite sync"

Version Impact:

test:

commits do NOT trigger version bumps.

Testing Best Practices

DO ✅

Write tests BEFORE implementing features (TDD)
Test one behavior per test method
Use descriptive test names (read like documentation)
Mock ALL external dependencies (WordPress, ACF, database)
Test edge cases (null, empty, invalid types)
Keep tests fast (< 100ms per test)
Use setup/teardown for common initialization
Test error handling explicitly
Verify security checks (capabilities, nonces)

DON'T ❌

Skip tests because "it's simple code"
Test WordPress core functionality
Write slow tests (file I/O, database queries in unit tests)
Share state between tests
Commit failing tests
Ignore coverage drops
Test implementation details (test behavior, not internals)
Copy-paste test code (use helpers/fixtures)

AI Assistant Testing Behavior

When adding a new feature:

FIRST: Write failing test
SECOND: Run test to verify failure
THIRD: Implement minimum code to pass
FOURTH: Run test to verify pass
FIFTH: Add edge case tests
SIXTH: Run full test suite
SEVENTH: Check code coverage
FINALLY: Provide test run output to user

When fixing a bug:

FIRST: Write regression test that reproduces bug
SECOND: Verify test fails
THIRD: Fix the bug
FOURTH: Verify test passes
FIFTH: Run full test suite

When updating existing code:

FIRST: Run existing tests
SECOND: Update tests for new behavior
THIRD: Update implementation
FOURTH: Verify all tests pass
FIFTH: Check coverage maintained

Response Format:

I'll add tests for [feature] following TDD:

1. Created failing test: tests/Unit/ClassTest.php::test_method_scenario()
2. Test output: FAIL (expected)
3. Implemented: includes/class-name.php::method()
4. Test output: PASS
5. Added edge cases: test_method_with_null(), test_method_with_empty()
6. Full test suite: 124 tests, 124 passed ✓
7. Code coverage: 87% (↑ from 85%)

Ready to commit with: test: add comprehensive tests for [feature]

Test Documentation

Complete testing guide:

tests/README.md

Installation instructions
Running tests (all scenarios)
Writing test guidelines
Mocking patterns
Debugging tests
CI/CD integration
Troubleshooting

Common Mistakes to Avoid

Don't echo in shortcodes - Always return string
Don't assume ACF exists - Check
```
function_exists('get_field')
```
Don't skip validation - Verify post type before using post ID
Don't hardcode IDs - Make configurable via attributes
Don't create separate doc files - Consolidate into README/DEVELOP
Don't write vague errors - Be specific and actionable
Don't forget mobile - Test responsive layouts
Don't skip version sync - Update all 4 files
NEVER create .old, .bak, or -backup files - Use workspace/ or Git
NEVER rename files to .old before editing - Edit in place, Git tracks history
ALWAYS use Conventional Commits - Determines version bumps
Don't mix commit types - One feat/fix/docs per commit
NEVER commit code without tests - TDD is mandatory
NEVER skip test runs - Run tests before every commit
NEVER ignore failing tests - Fix or update immediately

Testing Checklist

Manual Testing

Install on fresh WordPress install
Import ACF fields from JSON
Create test locations (physical + service areas)
Test all shortcodes with various attributes
Test Elementor query filtering
Test with WP_DEBUG enabled (no errors)
Test on mobile device/responsive view
Test with ACF Free and Pro
Test with Elementor Free and Pro

Error Testing

Invalid location ID shows clear error
Missing ACF field shows helpful error
Empty data shows appropriate message
Debug mode shows collapsible debug info
Non-editors don't see debug info

AI Assistant Behavior

When Asked to "Add a Feature"

Determine if it fits plugin scope
Draft conventional commit message (determines version impact)
Plan class/method structure
Write code following all standards above
Add error handling with actionable messages
Add logging if debug-worthy
Test thoroughly
Provide conventional commit message
Update CHANGELOG.md if version bump needed
Explain usage with example
NO separate planning doc - explain inline

When Asked to "Fix a Bug"

Ask for error details and context
Review relevant code section
Identify root cause
Implement fix with tests
Write conventional commit message (fix: ...)
Add entry to CHANGELOG.md (### Fixed)
Bump PATCH version if releasing
Explain what was wrong and how it's fixed

When Asked to "Update Documentation"

Determine which file (README, DEVELOP, or CHANGELOG)
Update inline - no new files
Keep language concise and technical
Remove fluff/marketing language
Use conventional commit (docs: or docs(readme):)
Ensure version numbers match across files
NO version bump for docs-only changes

When Asked to "Create Documentation"

STOP - Ask which existing file to update
Consolidate into README.md or DEVELOP.md
NO new .md files without explicit approval
Inline code documentation via PHPDoc only
Use conventional commit (docs: ...)

When Asked to "Save/Backup a File"

STOP - Never create .old, .bak, or backup files
Suggest: "I'll save a copy to workspace/ directory"

Execute:

cp file.php workspace/file-backup-YYYY-MM-DD.php

Explain: "Git history preserves all versions"
If file is obsolete: Delete it directly

When Making Any Changes

Always stage a conventional commit message
Determine version impact (major/minor/patch/none)
Make changes atomically (one logical change)
Update CHANGELOG.md if needed
Provide complete commit message in output
Provide usage example
NO separate planning doc - explain inline

When Asked to "Fix a Bug"

Ask for error details and context
Review relevant code section
Identify root cause
Implement fix with tests
Add entry to CHANGELOG.md (### Fixed)
Explain what was wrong and how it's fixed

When Asked to "Update Documentation"

Determine which file (README, DEVELOP, or CHANGELOG)
Update inline - no new files
Keep language concise and technical
Remove fluff/marketing language
Ensure version numbers match across files

When Asked to "Create Documentation"

STOP - Ask which existing file to update
Consolidate into README.md or DEVELOP.md
NO new .md files without explicit approval
Inline code documentation via PHPDoc only

Last Updated: October 28, 2025
Current Version: 2.0.0
Primary Developer: Ryan T. M. Reiffenberger
Company: Falls Technology Group, LLC

Copilot Instructions - ACF Service Management Suite

Related Skills

Markdown Converter

Nano Banana Pro

1password