Personalization
# Personalization
Apply a prompt profile only when it is available in the current conversation or a user-approved local file.
## How To Use A Profile
1. Extract 3-7 active rewrite rules from the profile.
2. If the profile includes a `Prompt-Rewrite Handoff` block, treat it as the active rule set and avoid re-summarizing the whole profile.
3. Apply rules that fit the current prompt type.
4. Keep the final prompt in the user's working style.
5. Do not mention private profile details unless relevant.
## Useful Defaults For Direct, Execution-Oriented Users
- Preserve informal directness.
- Add current-state inspection instead of abstract planning.
- Add verification gates by default.
- Specify whether to implement, review, research, or only propose.
- Include subagents only when the user asks for them or the task clearly benefits and the environment supports them.
- Prevent overbuilding with explicit scope boundaries.
- For repo work, require repo-root verification before editing.
- For live-product work, require browser or live-surface evidence.
## Example Profile Rule Application
Profile rule:when to use it
Community prompt sourced from the open-source GitHub repo ilyaforfun/supadupaprompt-codex (MIT). A "Personalization" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
writingcommunitygeneral
source
ilyaforfun/supadupaprompt-codex · MIT
more in Writing
Writing✓ tested
Explain anything to a smart friend
great teacher who refuses to dumb things down
Writing✓ tested
Line-edit my draft (keep my voice)
sharp copy editor who tightens without flattening
Writing✓ tested
Outline a long piece before you write it
editor who structures the argument before a word is drafted