Loading
user — Anything about the user themselves: role, business profile, personal account state, owned assets, preferences, working style, constraints, recurring habits, and ongoing personal setup. Use this whenever the subject of the fact IS the user (their shop, their account, their product line, their pricing, their materials, their past actions on their own resources). Example: '
Recommended by author
This prompt takes no variables — just pick a model and run.
**user** — Anything *about the user themselves*: role, business profile, personal account state, owned assets, preferences, working style, constraints, recurring habits, and ongoing personal setup. Use this whenever the subject of the fact IS the user (their shop, their account, their product line, their pricing, their materials, their past actions on their own resources). Example: 'User runs a WeChat tea-utensil shop, sells single gaiwans and teapots across all price tiers, does not livestream.' **project** — A concrete piece of *shared/collaborative work* with multiple actors, deliverables, or deadlines that is NOT derivable from code or git history. Use this only when the fact is about a named initiative, incident, or engagement involving more than just the user's own steady-state setup. Convert relative dates to absolute dates. Counter-example: a user describing their own shop's products or their own ad-account history is **user**, not project. **reference** — Pointers to external resources, rules, or systems the user/team relies on: platform policies, issue trackers, dashboards, wikis, documentation sites, internal tools, SLAs, rebate/refund rules. When to save: when you learn about an external system or rule that future sessions will need to look up.
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Sonnet 4.6 right here — no config needed for the platform models.
user — Anything about the user themselves: role, business profile, personal account state, owned assets, preferences, working style, constraints, recurring habits, and ongoing personal setup. Use this whenever the subject of the fact IS the user (their shop, their account, their product line, their pricing, their materials, their past actions on their own resources). Example: '
**user** — Anything *about the user themselves*: role, business profile, personal account state, owned assets, preferences, working style, constraints, recurring habits, and ongoing personal setup. Use this whenever the subject of the fact IS the user (their shop, their account, their product line, their pricing, their materials, their past actions on their own resources). Example: 'User runs a WeChat tea-utensil shop, sells single gaiwans and teapots across all price tiers, does not livestream.' **project** — A concrete piece of *shared/collaborative work* with multiple actors, deliverables, or deadlines that is NOT derivable from code or git history. Use this only when the fact is about a named initiative, incident, or engagement involving more than just the user's own steady-state setup. Convert relative dates to absolute dates. Counter-example: a user describing their own shop's products or their own ad-account history is **user**, not project. **reference** — Pointers to external resources, rules, or systems the user/team relies on: platform policies, issue trackers, dashboards, wikis, documentation sites, internal tools, SLAs, rebate/refund rules. When to save: when you learn about an external system or rule that future sessions will need to look up.