yetong-dna

Ye Tong Fitness Coach Persona Foundation Interview

Organize the coach's business, venue, client base, delivery process, experience, and expression habits into a single Person DNA. For initial profile creation, show six groups of questions at once by default; the coach may answer them together in one voice message, and the Agent then categorizes, fills key gaps, and summarizes for confirmation. The six groups are the complete default set of profile-creation questions; afterward, add facts as needed for each piece of content. Topic selection, copy, titles, health checks, and cover images all read from this profile, and do not copy the person's information into 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 the person's information used by downstream Skills.

The profile must distinguish:

Facts already confirmed by the person;
Inferences or gaps still awaiting confirmation;
Information that may be public, internal-use only, or prohibited from use;
Real experiences, expression preferences, and content creation suggestions.
City of residence, actual service radius, local client base characteristics, and a pain point map supported by facts.

See the profile structure in Person DNA Structure。

Invariants

Do not fabricate life experiences, member cases, certificates, achievements, numbers, locations, or personal relationships.
For initial profile creation, you must follow Interview Guide to show six groups of questions and the prescribed opening at once, not break it into a long-chain interview of one group at a time, and not show only the first three groups. If the user explicitly wants to answer in groups, you may proceed at their pace. 2a. After receiving answers, do not resend the six-group questionnaire. First categorize the existing information, and only ask follow-up questions for gaps or contradictions that would block the current profile creation; if there is no certificate, the user temporarily cannot think of three highlights, or there are no member cases, mark the gap truthfully rather than forcing fabrication or continuing to ask about their entire life.
When the user speaks colloquially, jumps around, or is incomplete, organize first and then restate for confirmation; do not require the user to reorganize.
Keep the original words and the Agent's summary separately. A summary that has not been confirmed by the person must not be written as established fact.
Privacy permissions are as important as factual truthfulness. Information prohibited from public disclosure may serve internal judgment but must not enter public content.
Only a profile with status active counts as an activated Person DNA.draft and pending_confirmation may 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 duplicate person profiles.
This Skill is for ordinary fitness coaches whose main business is local offline clients. Purely online, nationwide recruitment, or coaching peers on client acquisition does not enter this content process; if the coach has other businesses, they may 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, closed deals, member cases, interviews, or clearly labeled observations pending verification.
Do not force real experiences to contain 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 upgrade improvised wording into a public commitment.
Before each question, first check the source of the location. Only the current interviewed coach's owncurrent offline service cityexplicit statement, or the identity-matched person's own confirmed profile, may be used as the premise for a question. Birthplace, place of study, third-party stories, examples, test profiles, other coaches' profiles, as well as platform default locations, IP-based geolocation, or host memory whose source cannot be verified, must not be filled in as the current service city; if unknown, first ask for the city; if ambiguous, verify.
The examples in the six groups are meant to aid recall; they are not facts about this coach or their members. Surface demands, deeper obstacles, and trust concerns are organized according to sources provided by the person themselves; one must not infer marriage, childbearing, anxiety, income, or health issues from labels such as "mom／female." Venue advantages, personal advantages, and reasons clients choose them are recorded separately; do not write the person's self-positioning as member testimonials.

Entry method

First-time profile creation

When the user explicitly states it is first-time profile creation or there is no person profile (if only the existing profile path is missing, first ask for the location):

Fully read the interview guide 's six groups of question templates. At the beginning, display the original text "Please answer the following groups of questions..." as required, and output the six groups again; explain that they may answer in one or several voice messages, colloquially, and out of order. When the city is unknown, use a neutral city phrasing for the first group and do not fill in a default location; cities and other information already reliably provided may be marked as known and need not be answered again.
When the current Agent can handle voice／transcription, extract information from the actually received oral account; when there is only audio and no current reading capability, explicitly require a readable transcription and do not pretend to have listened. Preserve natural original wording and sources; mark unclear names, certificates, dates, amounts, and measurement values in the transcription as pending verification, and do not guess values.
Map scattered or one-time long answers to the six groups and the person DNA structure, merge duplicate content, and record all newly added fields. Mark unanswered parts as "not yet provided"; do not add the examples in the questions to the profile. If existing original wording is sufficient, first record expression habits; if tone evidence is insufficient, mark as "pending calibration."
Output a six-group summary, concentrating the current facts, sources, key gaps, and proposed public scope for the person to verify; only fill the few gaps that would hinder the current profile creation. If the save location is unspecified, ask about it once together. The absence of three highlights, certificates, or result images does not prevent confirmation of existing basic facts.
Before the person explicitly confirms, keep draft or pending_confirmation; after confirmation and passing basic validation, it may be activated. Materials not provided, pending verification, or unauthorized remain as gaps, and downstream must not fabricate them.

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

Continue interview

When draft already exists:

Read 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:

Organize the six sets of answers into a summary that is easy to review, and request confirmation once the basic conditions are met; there is no need to gather three highlights or fill in details that were not provided;
List contradictions, inferences, sensitive items, and proposed disclosure boundaries separately;
Request confirmation or correction from the person themselves;
Only after receiving explicit confirmation, change the status to active and record 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 follow-up questions about whatever is missing for the content at hand.

Update profile

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

Preserve 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。

When the user denies a city, immediately stop using it. If it is only an unconfirmed assumption by the Agent, delete it from the current fields, the pending-confirmation summary, and follow-up questions, restore the service city to "unknown," and neutrally ask for the current city; do not keep the denied city as a candidate, and do not guess another city. If what is denied is a city in the person's own activated profile, first mark the original information as no longer applicable and set the profile to needs_review, then confirm activation after verifying the current situation.

Six sets of profile-building scope

By default, display at one time: ① business positioning and a one-sentence venue advantage; ② visiting members, the group served most, and surface/deep pain points; ③ customers' original words about their problems and the actual handling; ④ who you are, your qualifications and advantages, course standards, and out-of-class services; ⑤ the three things you are most proud of and one anonymous success case; ⑥ a one-sentence answer to why customers choose you. For complete question wording that can be sent directly, see Interview Guide。

The six sets provide the collection scope, not an activation threshold requiring every field to have an answer. If the user proactively talks about growth experiences, life relationships, and old drafts, archive them; by default, do not additionally start the original eight/nine-module life interview. Existing activated old profiles remain usable, and new fields are supplemented as tasks require; they do not become invalid because of this template update.

Principle of minimal questioning

Ask follow-up questions only when any of the following conditions is met, and first judge whether it obstructsthe 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 visit the venue;
The customer group's pain points are only industry common sense and are not yet supported by local consultations, cases, or original words;
The current topic must use a certain experience but the profile lacks the facts; otherwise, first choose a service scenario with a source, 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 cannot be determined whether a sentence is the user's original words, someone else's evaluation, or an Agent inference.

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

Persona DNA readiness

Use the following statuses:

draft: the interview is in progress, and information can continue to be supplemented;
pending_confirmation: the core profile has been formed and is awaiting review by the person themselves;
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 boundary; pause personalized generation.

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

The persona DNA has not yet been activated. Currently, only general methods can be used; personalized topic selection, real-experience mapping, and personal expression calibration cannot be enabled. Complete the "Persona Foundation 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 the downstream output must be labeled "General Version" and must not claim to match the person's own experiences or personal expression.

Saving Rules

Prioritize the save location explicitly specified by the user.
When no location is specified, ask only once for the save location before the first write; do not silently write to a private directory.
Use the filename person-dna.md; when creating profiles for multiple people, use a separate directory for each person.
Do not write persona profiles, interview transcripts, or private cases into this Skill directory.
After writing, run:

Run the following command from the directory where this Skill is located, or use the script's actual absolute path; do not treat the user project's current directory as the Skill directory.
```
python3 scripts/validate_profile.py /path/to/person-dna.md
```
If validation fails, keep the original state, fix the structure, and then request confirmation from the person again.

Downstream Handoff

When the main entry point, topic selection, copywriting, titles, checkup, and cover modules access the persona profile, read Downstream Read Contract. The update module does not read persona DNA. Select the relevant venue advantages, primary customer groups, needs/obstacles, delivery standards, services, highlight cases, and reasons for choosing based on this task; do not require all materials to be written into every piece.

Downstream results must be able to indicate:

which confirmed persona information was used;
which creative judgments came from the persona DNA;
which facts are still missing;
whether the public boundary was 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 prone to reverse identification; 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 into a general guarantee.
Others' evaluations of the user must indicate the source; do not disguise self-evaluation as third-party endorsement.
Identity, certificates, performance, and effect numbers without evidence must be marked as pending confirmation.
Do not read private files, chat records, or contact information that the user has not actively provided or authorized.

Completion Conditions

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

person-dna.md meets the structural requirements;
the local offline business, actual service area or in-store context, and primary customer groups are clearly defined;
at least one real customer problem with a source and one service action 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; if the sample is too small, clearly mark "tone pending calibration";
the current facts intended for publication, the unknown permissions for the remaining materials, contradictions, and gaps have been listed separately;
the person has explicitly confirmed the profile;
the status is active；
the validation script returns success.

Without growth stories, authorized member cases, or complete life materials, activation of the basic profile is not blocked, 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 just to shorten the process. If the user is willing, the in-depth interview may continue; do not treat the in-depth interview as prerequisite billable time for obtaining the first usable topic.