Deploying Person Account Fields via Contact

What this skill is for

Person Accounts are a single logical record stored as two rows: an Account row and a matched Contact (PersonContactId) row. This split is the source of the #1 Person Account custom-field mistake: creating a member/person attribute directly on Account when it belongs on the person.

The rule: for a person-level custom field, create it on Contact. Salesforce automatically mirrors it onto the Account object for Person Accounts under a __pc-suffixed API name. You never author the Account-side field — the platform materializes it, and it's immediately available via SOQL, REST/Bulk API, and Flow.

Create custom field on Contact:            Member_Status__c
        │  (Person Accounts enabled)
        ▼  platform auto-mirrors
Account (Person Account) gains:            Member_Status__pc      ← queryable, API-accessible, Flow-referenceable
                                                                    (you did NOT create this — it's automatic)

Verified end-to-end on the OMERS pension demo (org CommericalDemos): 8 member fields authored on Contact all surfaced as __pc on Account, queried via SOQL and read in system-mode Flows — see the worked example at the bottom.