yetong-fitness-xhs-profile

Yetong Fitness Coach Personal Core Interview

Organize the real life experiences, business situation, local client base, content assets, and expression habits of a fitness coach serving local clients in a specific city, business district, or community into a unique personal DNA profile. By default, start with a short interview that can begin real topic selection; growth stories, member cases, and more detailed writing style are supplemented when specific content needs arise. Subsequent topic selection and copywriting Skills must read this profile and not copy personal information in their own directories.

Core Output

Deliver a person-dna.md file. It is both a profile the person can review and the source of truth for personal information for downstream Skills.

The profile must distinguish:

Facts already confirmed by the person;
Inferences or gaps still awaiting confirmation;
Information that can be public, used only internally, and prohibited from use;
Real experiences, expression preferences, and content creation suggestions.
The city, actual service radius, local client base, and a pain point map supported by facts.

For the profile structure, see Personal DNA Structure。

Invariants

Do not fabricate life experiences, member cases, certificates, achievements, numbers, locations, or personal relationships.
The interview advances as a dialogue, asking only 1–3 related questions per round that would change the profile, not throwing out a long questionnaire at once. 2a. Limiting the number of questions per round does not equal limiting total cost. By default, first complete a basic usable profile and provide a confirmation summary as early as possible; do not keep asking for an hour just to fill all eight interview modules. When the user actively wants to discuss life in depth, then proceed to an in-depth interview.
When the user speaks colloquially, jumps around, or is incomplete, organize first and then restate for confirmation, without asking the user to reorganize.
Keep original words and the Agent's summaries stored separately. Summaries that have not been confirmed by the person must not be written as established facts.
Privacy permissions are as important as factual accuracy. Information prohibited from being public can inform internal judgment but must not enter public content.
Only a profile with the status active counts as having Personal DNA activated.draft and pending_confirmation can only be used to continue the interview or request confirmation.
When updating the profile, modify the same source of truth and increase the version number; do not create conflicting copies of the personal profile.
The target of this Skill is ordinary fitness coaches whose main business is local offline clients. Pure online, nationwide enrollment, or teaching peers to acquire clients does not enter this content process; if the coach has other businesses, they can be recorded as background, but the downstream target is always their local potential members.
Do not guess the client base based on city labels. Pain points must come from the coach's real consultations, deals, member cases, interviews, or clearly marked observations pending verification.
Do not force real experiences to have dramatic turns. Long-term repeated basic services, stable fulfillment, and ordinary training routines can also become distinctive story assets.
Before asking about services, pricing, or after-sales commitments, first check the rights and written rules the user has previously provided; do not ask again about content that has already been made clear. When oral statements conflict with existing rules, retain both sources and mark them as pending verification; do not directly elevate improvised wording into a public commitment.

Entry Methods

Initial Profile Creation

When the user does not yet have a person profile, or a downstream Skill cannot locate the person profile:

Use the Interview Guide 's "Default Quick Start" to first confirm the local offline business, actual service area, main members, one sourced customer problem, and one genuine service action of their own; prioritize extracting from what the user has already stated orally, and do not ask again.
From the answers, retain a passage of natural original wording as an initial expression sample; if it is insufficient to judge the writing style, mark it as "tone pending calibration," and do not force a request for old drafts because of this.
Combine the intended public scope of the current identity, city/venue, and service actions with the prohibited zones of other materials into a single summary for the person to review; do not require them to first tell their complete growth history or provide member photos or performance data.
Before the person confirms, first save draft or pending_confirmation; once the basic conditions are met and explicit confirmation is given, it can be activated. Modules not yet interviewed should be marked "not yet provided" in the same profile and filled in later as needed.

If the user's business mainly targets a nationwide online customer base, explain that this Skill's local business assumption does not hold and stop; do not forcibly rewrite nationwide users as a local customer base.

Continue Interview

When draft already exists:

Read the existing content;
Identify key gaps that would hinder subsequent content work;
Continue from where it stopped last time, and do not repeat questions that have already been confirmed.

Confirmation and Activation

When the core information is already sufficient:

Once the "basically usable" conditions are met, output a summary that is easy for the person to check, without waiting for all eight modules to be filled in;
List contradictory items, inferred items, sensitive items, and intended public boundaries separately;
Request the person to confirm or correct;
Only after receiving explicit confirmation, change the status to active and write in the confirmation date.active indicates that the recorded information has been confirmed; it does not mean that the life story, member cases, and tone are all complete; downstream should use only known facts, and ask specifically about whatever is missing for the current piece of content.

Update Profile

When the user adds new experiences, changes cities, changes venues, adjusts the business, or corrects old information:

Retain the time ranges of both old and new information;
Mark which old facts are no longer valid;
Update the same profile's profile_version and updated_at；
Major changes re-enter pending_confirmation。

Interview Order

The default quick start only covers items 1–3 below, plus one confirmation of public boundaries and summary. Items 4–9 are optional deep interviews; if the user has already provided them naturally, extract directly and do not ask again.

Prioritize completing the fields that will change the direction of the content:

Current identity, city, district/county, venue, and business;
Local service radius, customer base composition, and in-store conditions;
The local customer base's goals, explicit pain points, implicit pain points, real constraints, and closing obstacles;
Products, closing path, and points of difference from local peers;
Entry into the industry, growth, and key turning points;
Real member cases and verifiable evidence;
Values, stance, and content boundaries;
Speaking habits, frequently used words, and disliked expressions;
Interpersonal relationships, daily life, and sustainable filming scenarios.

For the complete modules, follow-up methods, and early stopping conditions, see Interview Guide。

Minimum Questioning Principle

Only follow up when any of the following conditions is met, and first judge whether it hindersthe topic or copy currently being worked on; gaps that do not affect the current output are left for later:

The answer would change the person's positioning, target customers, or content direction;
It is unclear which city areas the user actually covers, their commuting range, or how they get to the store;
The customer pain points are only industry common sense and are not yet supported by local inquiries, cases, or direct quotes;
The current topic must use a certain experience but the profile lacks the facts; otherwise, first choose a service scenario with sources, and do not force them to tell their life story just to build the profile;
The same information conflicts and the time range needs to be determined;
It is unclear whether the information can be made public;
It is impossible to determine whether a sentence is the user's own words, someone else's evaluation, or an Agent inference.

Low-risk formatting, titles, and ordering are handled directly by the Agent.

Person DNA Readiness

Use the following statuses:

draft: Interview in progress, information can continue to be supplemented;
pending_confirmation: The core profile has been formed, awaiting the person's review;
active: The person has explicitly confirmed the basic profile, and downstream Skills may use known facts; missing stories, cases, or writing style still cannot be inferred;
needs_review: A major change has occurred in the business, identity, or public boundaries, so personalized generation is paused.

When a downstream request occurs while the profile is not activated, use the following prompt as is:

Person DNA is not yet activated. Currently only general methods can be called, and personalized topic selection, real experience mapping, and personal expression calibration cannot be enabled. Complete the "Person Background Interview" and confirm the profile to unlock the full Ye Tong content method engine.

The user may explicitly request to skip the interview and obtain general results, but downstream output must be marked "General Version" and must not claim to match the person's experience or personal expression.

Saving Rules

Prefer the save location explicitly specified by the user.
When no location is specified, ask only once for the save location before the first write, and do not silently write to a private directory.
Use the filename person-dna.md; when building profiles for multiple people, use a separate directory for each person.
Do not write person profiles, original interview text, or private cases into this Skill directory.

After writing, run:

python3 scripts/validate_profile.py /path/to/person-dna.md

If validation fails, keep the original status, fix the structure, and then request the person's confirmation again.

Downstream Handoff

When topic selection, copywriting, and the main entry Skill connect to the person profile, read Downstream Reading Contract。

Downstream results must be able to point out:

Which confirmed person information was used;
Which creative judgments came from Person DNA;
Which facts are still missing;
Whether public boundaries were touched.

Privacy and Evidence Boundaries

Member cases are de-identified by default; before making names, photos, chat records, and health information public, require the user to confirm that authorization has been obtained.
Small cities, fixed venues, and narrow customer groups are easily reverse-identified; even if names are hidden, check whether the combination of information exposes a specific member.
Medical, rehabilitation, and training effects must not be elevated from a single story to a general guarantee.
Others' evaluations of the user must indicate their source, and self-evaluations must not be disguised as third-party endorsements.
Identity, certificates, performance, and effect figures must be marked as pending confirmation when there is no evidence.
Do not read private files, chat records, or contact information that the user has not actively provided or authorized.

Completion conditions

By default, the "basically usable" interview is complete when the following conditions are met:

person-dna.md Meets the structural requirements;
The local offline business, the real service area or in-store context, and the main customer groups have been clarified;
At least one real customer problem with a source and one service action that the person is actually doing have been recorded, sufficient to support the first round of topic selection;
The person's own words that can currently be observed have been saved; when the sample is too small, clearly mark "tone pending calibration";
The current facts intended for public disclosure, the unknown permissions for the remaining materials, contradictions, and gaps have been listed separately;
The person has explicitly confirmed the file;
The status is active；
The validation script returns success.

The absence of a growth story, authorized member cases, or complete life materials does not prevent activation of the basic file, but personalized content of the corresponding type still must not be fabricated. If the basic facts or public boundaries have not yet been confirmed, save as draft or pending_confirmation, and do not activate without authorization in order to shorten the process. If the user is willing, the in-depth interview may continue; do not make the in-depth interview a prerequisite paid time for obtaining the first usable topic.