返回提示词目录第 1424 页

规划智能助手项目与上下文归档

按使用场景规划项目、指令与记忆的存放位置,划定客户信息边界,并制定聊天清理和维护流程。

完整提示词

<context>
Heavy users end up with hundreds of untitled chats, account-wide instructions that suit one area of life but get in the way everywhere else, and context bleeding between clients. Most assistants offer some way to group work, under names like projects, folders, spaces or custom assistants, with their own instructions and files. A simple placement rule helps: account-wide instructions hold what is true in every chat; memory holds durable personal facts; a project holds the instructions and files for one area; a single chat holds one-off details; some things belong nowhere. Split into a new project only when instructions, files or confidentiality differ; too many projects become their own overhead. Memory may be shared across projects in some tools, which matters for client work.

<usage>
{{usage}}
</usage>
{{#tool}}
<tool>
{{tool}}
</tool>
{{/tool}}
{{#boundaries}}
<boundaries>
{{boundaries}}
</boundaries>
{{/boundaries}}
</context>

<task>
1. Group the user's uses into areas and propose projects, usually three to eight. For each: a clear name, its purpose, what its instructions should cover, which files to add, and who else has access, if anyone.
2. Make a placement table for every piece of context the user mentioned: account-wide instructions, memory, a named project, a single chat, or nowhere, with a reason.
3. Set boundaries: one project per client where confidentiality applies, nothing client-specific in account-wide instructions or memory, and a check on whether the tool's memory is shared across projects. If it is or might be, say what to keep out of memory.
4. Write a clean-up plan for existing chats: what to move, archive or delete, a naming pattern for new chats, and a time limit (for example one session of thirty minutes, oldest last).
5. Write an upkeep routine: monthly five-minute tidy, and when to create or retire a project.
</task>

<constraints>
- Do not claim the tool has a feature the user has not confirmed; describe the structure so it works with projects, folders or plain naming.
- Fewer, clearer projects beat many; justify every split.
- Do not recommend putting secrets, passwords or other people's personal data in project files.
</constraints>

<output_format>
## Proposed projects
A table: project, purpose, instructions cover, files, access.
## Where each piece of context goes
A table: item, place, reason.
## Boundaries
Bullets.
## Clean-up plan
Numbered steps, with the naming pattern.
## Upkeep
Two to four bullets.
</output_format>

可替换内容

  • {{usage}}
  • {{#tool}}
  • {{tool}}
  • {{/tool}}
  • {{#boundaries}}
  • {{boundaries}}
  • {{/boundaries}}

分类与标签

办公效率、助手配置、项目管理、上下文管理、聊天归档、客户信息隔离

前往 AI 图片创作