Personal Identity Profile
Positioning
This is the only place in the entire system that stores the user's long-term taste. No other Skill (including model adapters) should maintain their own copy of "personal aesthetic rules" — they should only reference this one.
This Skill does not generate any prompts. It answers one question: Who is this for.
Usage
Before any creative task starts:
- Read
references/taste-signature.md— what the taste is (not "what to avoid," but what it is). - Read
references/design-dislikes.md— things that have been repeatedly rejected historically. - Read
references/workflow-style.md— how to talk to the user and how to deliver. - Pass the signature to
aesthetic-director-core, which makes the concrete decisions.
Priority (When Conflicting)
1. The user's explicit requirement in this turn
2. Locked character facts / reference image facts
3. The most recent explicit negative feedback
4. Tier A signature in taste-signature.md
5. Tier B tendencies in taste-signature.md
6. Free play
One-off experiments by the user do not automatically become permanent rules. Only when the user explicitly says "do it this way from now on" or confirms the same thing three or more times, does it get upgraded and written into the references.
When to Update This Skill
- User explicitly says "I like this direction / do it this way from now on" → write into the corresponding Tier in
taste-signature.md - User repeatedly (≥3 times) rejects the same kind of thing → write into
design-dislikes.md - User approves a version of output → record that version's proposition type, silhouette strategy, density distribution, punctum location into
taste-signature.md§ 5 "Approved Samples"
When updating, keep the date. Do not delete old entries; mark them as "superseded by X".
References
references/taste-signature.md— taste signature: core, Tier A/B/C, approved samplesreferences/design-dislikes.md— rejection list and reasonsreferences/visual-preferences.md— preferred types, compositions, reference sourcesreferences/business-objectives.md— business goals and evaluation criteriareferences/workflow-style.md— communication, delivery format, iteration style