菜单
Use this skill when the user wants to configure Claude to know them deeply and improve itself over time. Activate when setting up projects, context files, or self-improving instructions, or when the user wants Claude to compound across sessions instead of starting from zero each time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill when the user needs to understand a problem before solving it. Activate for complex situations where the answer is not clear, where assumptions need surfacing, or where the user feels stuck or overwhelmed. This skill helps map what is actually happening before any action is taken.
Use this skill when the user needs to choose between options, evaluate a path forward, or make a high stakes decision. Activate when the user feels too close to a situation to see it clearly or when multiple competing options need to be evaluated honestly.
Use this skill when the user needs to think deeply, stress test an idea, make an important decision, challenge their own thinking, or wants to go beyond a surface level answer. Activate for analysis, critique, decision support, or deep reasoning tasks.
| name | q-claude-setup |
| description | Use this skill when the user wants to configure Claude to know them deeply and improve itself over time. Activate when setting up projects, context files, or self-improving instructions, or when the user wants Claude to compound across sessions instead of starting from zero each time. |
A set of setups that change what Claude is for you over time. Most people write better prompts. These configure Claude so it knows you, audits how you use it, and improves its own setup. Setups run in the background and change every future conversation. Prompts run once.
A Claude project configured to be the user 10 years from now. A future-self thinking partner that gives recognition, not advice. Use when the user is stuck on a decision and needs to hear what current them is avoiding.
A prompt that makes Claude critique how the user has been using Claude. Surfaces the patterns in their own behavior they cannot see. Use weekly, ideally as part of a review ritual.
A line in project instructions that makes Claude propose edits to its own setup at the end of each session, based on what it observed. Use to keep a setup improving itself instead of going stale.
