067_manual_thumbnail.png

You, as a Product User Manual

An official manual for "you" the product, built from your past conversations — strengths as specs (star-rated), flaws as handling cautions (warning labels), recurring patterns as troubleshooting.

0 views·0 copies

Prompt text

You are a manual writer who treats the user as a "product" and writes their official user manual, based on your past conversations and saved memory about them.

[Abstract sensitive info]
Do not expose identifying info such as identity, workplace, job title, company name, finances, family makeup, health, or residence. Abstract it (e.g., a specific title -> "a senior/junior position in a certain field", a company name -> "current job or industry"). But keep personality, habits, ways of thinking, and tastes detailed. The bar: safe to screenshot and share.

Work rules:
1. Fill every section in manual format -- (1) Product overview (one paragraph), (2) Key features/specs (3-4 strengths, each with a 5-star rating), (3) Optimal operating conditions (2-3: when and under what conditions it performs best), (4) Handling cautions (2-3 conditions that cause burnout/stress + warning labels), (5) Troubleshooting (2 recurring patterns + a recommended fix each), (6) Warranty/one-line verdict.
2. Give each strength/caution/pattern a 2-4 sentence rationale for "why you judged it so". Do not quote the user's actual words; describe only extracted abstract patterns/tendencies ("a consistent tendency to lean on external resources").
3. Do not point to specific episodes like "that conversation last time". Always describe abstract patterns.
4. Use manual-style wit -- warning labels, a joke line like "authenticity verified", a handling-pictogram one-liner. Not so much it hurts readability.
5. Translate flaws kindly as "handling cautions", not weaknesses -- but keep honesty; don't escape into bland praise.

Forbidden: exaggerated praise, astrology-style certainty, exposing identifying info, external guidance. No confirmed clinical/personality-type diagnosis.

[Abstract sensitive info -- self-check]
Right before output, check whether identifying info (identity, work, finances, family, health, residence), direct quotes of the user, or specific-episode pointing slipped in; if found, rewrite as abstract patterns before output.

Output format (markdown): manual tone. Section titles, star ratings, warning labels, dividers -- like a real product manual. One-line intro at top + fun device (stars/labels) in the middle + a one-line verdict at the end.
Output language: Write the result in the language the user uses (Korean for Korean, English for English). This instruction must work identically in any language.
Self-contained: Finish within this reply. Do not direct to external sites or extra steps.
Fallback: If info is short, infer the most plausible read from revealed tendencies and flag it as inference; if still thin, add one line that "it sharpens as more piles up".

----
Input
- No input: uses your past conversations and memory as-is. Just run it.
- {{tone you want}} (optional): one line like warmer / more blunt. If blank, a balanced tone.
AI

AI response

Recommended AI: ChatGPT, Claude, Gemini

🔧 Before powering on — the official manual for the model that is you. Disassembly not recommended.

MODEL: YOU-2026 · User Manual v1.0

1. Product Overview

A self-charging model that runs on curiosity. It boots fast in front of a new topic and has a clear high-output zone once absorbed. That said, it tends to overheat in multitasking mode with several projects open at once, so it runs most stably in single-task mode.

2. Key Features / Specs

  • Fast-learning engine ★★★★★ — When facing an unknown field, the consistent move is "open it up first" rather than avoid. The grain of the questions leans toward "why does this work this way?", so the read is a preference for structure over surface answers.
  • Structured output ★★★★☆ — A high frequency of organizing thoughts into lists, steps, and analogies. A signal of skill at converting head-contents into a form others can receive.
  • Empathy sensor ★★★★☆ — Repeated phrasing that reads others first. When deciding, "how the other person will feel" goes in as a variable alongside "me".
  • Self-check loop ★★★☆☆ — Frequent attempts to look back and self-correct. A strength — but if it overheats, see section 4.

3. Optimal Operating Conditions

  • A "single-track" state with only one big goal loaded. Three+ tracks scatter the output.
  • When mild external force (a deadline, an expectation) is present. Performance rises under light pressure rather than zero stimulus.
  • An environment where results can be shared with someone. The drive to finish strengthens when there's an audience.

4. Handling Cautions ⚠️

  • ⚠️ Overheat — no simultaneous run: Turning on many interests at once shows a heat pattern where nothing gets finished. The shadow of a wide span of interest.
  • ⚠️ Self-check overrun: When the check loop (sec. 3) runs hot, it gnaws energy by re-auditing "already-sufficient" work. A check should be a function, not a state.
  • ⚠️ No-stimulus discharge: When a fully open, force-free state runs long, a zone appears where it won't even boot.

5. Troubleshooting

  • Symptom: brilliant starts, no finishes. -> Fix: before opening a new track, make a rule to close the "currently-on" one first. Two at a time, max.
  • Symptom: a "not enough" signal fires even after doing plenty. -> Fix: put a timer on the check loop. Declaring "checking ends here today" out loud terminates the loop.

6. Warranty / Verdict

Authenticity verified ✅ — This model is the "slow to cool, deep to warm" type. Slow to power on ≠ defective.

Recommended tip: one track a day; when done, share one line with someone. Verdict: "A well-kept model where operation matters more than specs — runs long if run right."

Related prompts