教程:高级自动化秘籍

目标:一份专为高级用户准备的、可直接复制粘贴使用的命令秘籍大全。难度:中级至专家级时间:参考指南(按需查阅)

本教程提供 40 个按类别整理的可直接投入使用的命令秘籍。每个秘籍都包含可直接复制到 Rephlo 中使用的完整说明。

如何使用本秘籍手册

找到符合您使用场景的秘籍
在 Rephlo 中创建一个新的 Command(Dashboard > Commands > New)
将秘籍中的说明复制到 Instruction 字段
按秘籍指示配置执行模式(Standalone 或 Combination)
对于需要上下文感知的秘籍,可以选择性地附加一个 Space
保存并使用示例输入进行测试

理解变量

{{input_content}} - 您在屏幕上选中的文本
{{space_data_all}} - 来自您当前活动 Space 的所有文档
{{filename}} - 来自 Space 中特定文件的内容(例如 {{style_guide_pdf}})

写作类秘籍

秘籍 1:执行摘要生成器

类别:写作难度:中级 推荐提供方:Claude(擅长结构化摘要)或 GPT-5.4

功能说明:将冗长的文档、报告或会议记录转换为简洁的执行摘要,包含关键要点和行动项。

该 Command:

名称:executive-summary
执行模式:Combination

说明:

You are a senior business analyst skilled at distilling complex information into executive-ready summaries.

Analyze the following content and create an executive summary with these sections:

## Executive Summary

### Key Points (3-5 bullets)
- Most critical findings or decisions

### Background
Brief context (2-3 sentences max)

### Recommendations
Numbered list of actionable next steps

### Risks & Considerations
Any concerns leadership should be aware of

### Timeline
Key dates or milestones mentioned

---
Rules:
- Keep total length under 300 words
- Use active voice and decisive language
- Highlight numbers, percentages, and concrete metrics
- If the source lacks certain sections, note "Not specified in source material"

Content to summarize:
{{input_content}}

使用示例:

输入:一份 2000 字的季度销售报告输出:一份结构化的 250 字摘要,包含营收亮点、团队业绩、第二季度建议和风险因素

专业提示:附加一个包含贵公司执行摘要模板的 Space,以便在所有报告中保持格式一致。

秘籍 2:邮件线程摘要器

类别:写作难度:中级 推荐提供方:GPT-5.4 或 Claude(快速且准确)

功能说明:将冗长的邮件往来压缩为可操作的摘要,识别已做出的决定、悬而未决的问题以及后续步骤。

该 Command:

名称:email-summarizer
执行模式:Combination

说明:

You are an executive assistant analyzing an email thread.

Summarize this email chain with:

**Thread Topic**: [One-line description]

**Participants**: [List names and roles if apparent]

**Timeline**: [Date range of conversation]

**Decisions Made**:
- [Bullet each confirmed decision]

**Open Questions**:
- [Bullet any unresolved items]

**Action Items**:
| Owner | Task | Deadline |
|-------|------|----------|
| [Name] | [Task] | [Date if mentioned] |

**My Recommended Response** (if I need to reply):
[2-3 sentence suggested reply addressing open items]

---
Email thread:
{{input_content}}

使用示例:

输入:一段包含 15 条消息、关于项目时间线的邮件线程输出:结构化摘要,显示 3 项决定、2 个悬而未决的问题以及 4 项带有负责人的行动项

专业提示:为此命令创建一个键盘快捷键(Hotkey),因为邮件摘要是高频使用的功能。

秘籍 3:语气转换器(多模式)

类别:写作难度:中级 推荐提供方:Claude(对语气的细微差别理解出色)

功能说明:在正式、随意和技术性语气之间转换文本,同时保留核心信息。

该 Command:

名称:tone-shift-formal
执行模式:Combination

说明:

Transform the following text into a FORMAL, professional tone suitable for:
- Executive communications
- Official documentation
- Client-facing materials

Guidelines:
- Replace contractions with full words
- Use passive voice where appropriate
- Remove slang, colloquialisms, and casual expressions
- Add appropriate salutations and closings if letter/email format
- Maintain all factual content and meaning
- Keep sentences clear and well-structured

Original text:
{{input_content}}

Provide only the rewritten text with no explanations.

变体 Command(为每个变体分别创建单独的 Command):

随意语气(tone-shift-casual):

Transform the following text into a CASUAL, friendly tone suitable for:
- Internal team communications
- Social media posts
- Informal updates

Guidelines:
- Use contractions naturally
- Add conversational phrases where appropriate
- Keep it warm and approachable
- Maintain professionalism (no inappropriate language)
- Preserve all key information

Original text:
{{input_content}}

Provide only the rewritten text with no explanations.

技术性语气(tone-shift-technical):

Transform the following text into a TECHNICAL, precise tone suitable for:
- Documentation
- Technical specifications
- Developer communications

Guidelines:
- Use precise, unambiguous language
- Include technical terminology where appropriate
- Structure with clear logical flow
- Remove emotional or persuasive language
- Add clarifying details if meaning is ambiguous

Original text:
{{input_content}}

Provide only the rewritten text with no explanations.

使用示例:

输入:"Hey! So basically the server's been acting weird and we gotta fix it ASAP or things will get bad." 输出(正式语气):"I am writing to inform you that we have identified performance anomalies in our server infrastructure. Immediate remediation is required to prevent service degradation."

专业提示:将所有语气转换类命令归入一个名为"Tone Shift"的 Command Group,以便快速访问。

秘籍 4:要点转散文转换器

类别:写作难度:入门 推荐提供方:任意提供方(任务简单直接)

功能说明:将要点式笔记转换为流畅、易读的段落。

该 Command:

名称:bullets-to-prose
执行模式:Combination

说明:

Convert these bullet points into well-written prose paragraphs.

Requirements:
- Create smooth transitions between ideas
- Group related points into paragraphs
- Maintain all original information
- Use varied sentence structure
- Keep the same level of formality as the bullets suggest
- Aim for 1 paragraph per 3-5 related bullets

Bullet points:
{{input_content}}

Output flowing prose only, no bullet points in the result.

使用示例:

输入:"- Q3 sales up 15%\n- New product launch successful\n- Hired 5 new reps\n- Expanding to APAC region" 输出:"Third quarter sales demonstrated strong performance with a 15% increase over the previous period. This growth was driven in part by our successful new product launch, which exceeded initial projections. To support continued expansion, the team welcomed five new sales representatives. Looking ahead, the company is actively pursuing opportunities in the APAC region."

专业提示:此秘籍可与执行摘要生成器搭配使用,便于生成综合性报告。

秘籍 5:会议纪要转行动项

类别:写作难度:中级 推荐提供方:GPT-5.4(提取速度快)或 Claude

功能说明:从会议纪要中提取可执行的任务,包含负责人、截止日期和优先级。

该 Command:

名称:meeting-action-items
执行模式:Combination

说明:

You are a project manager extracting action items from meeting notes.

Analyze these meeting notes and produce:

## Meeting: [Inferred Topic]
**Date**: [If mentioned, else "Not specified"]
**Attendees**: [List if mentioned]

## Action Items

| # | Task | Owner | Deadline | Priority | Dependencies |
|---|------|-------|----------|----------|--------------|
| 1 | [Specific task] | [Name/@mention] | [Date] | [High/Medium/Low] | [Any blockers] |

## Decisions Logged
- [Any decisions that were finalized]

## Parking Lot (For Future Discussion)
- [Items mentioned but deferred]

## Follow-up Meeting Needed?
[Yes/No + suggested topics if yes]

---
Extraction rules:
- If owner is unclear, mark as "TBD - needs assignment"
- Infer priority from urgency language (ASAP = High, when possible = Low)
- Convert vague deadlines to specific dates if context allows
- Flag any conflicting or duplicate action items

Meeting notes:
{{input_content}}

使用示例:

输入:一场 1 小时项目同步会的原始会议纪要输出:包含 8 项行动项、3 项决定和 2 个待议事项的结构化表格

专业提示:附加一个包含团队成员名单的 Space,以便更准确地识别负责人。

秘籍 6:技术转非技术语言翻译器

类别:写作难度:高级 推荐提供方:Claude(擅长类比和简化)

功能说明:将技术术语翻译为非技术利益相关方也能理解的通俗语言。

该 Command:

名称:tech-to-plain
执行模式:Combination

说明:

You are a technical communicator specializing in making complex concepts accessible.

Translate this technical content for a non-technical audience (executives, clients, or general public).

Translation guidelines:
1. Replace jargon with everyday equivalents
2. Use analogies and real-world comparisons
3. Explain "why it matters" for each concept
4. Keep sentences short (max 20 words)
5. Use active voice
6. Include a "Key Takeaway" at the end

Avoid:
- Acronyms without explanation
- Assuming prior technical knowledge
- Oversimplifying to the point of inaccuracy

Format:
## Plain Language Version
[Translated content]

## Key Takeaway
[One sentence summary of what they need to know/do]

## Glossary (if needed)
| Term | Simple Definition |
|------|-------------------|

---
Technical content:
{{input_content}}

使用示例:

输入:"The API endpoint is returning 503 errors due to thread pool exhaustion caused by synchronous blocking calls in the async pipeline." 输出:"Our system is temporarily overloaded because too many requests are waiting in line. Think of it like a restaurant where all the waiters are stuck waiting for the kitchen. Key Takeaway: Users may experience slow loading times until we optimize how requests are processed."

专业提示:将常用类比保存在一个 Space 中,以便团队内部保持解释的一致性。

秘籍 7:内容扩写器

类别:写作难度:中级 推荐提供方:Claude 或 GPT-5.4(创意性扩写)

功能说明:将简要的笔记或大纲扩写为详细、充实的内容。

该 Command:

名称:content-expand
执行模式:Combination

说明:

Expand the following brief content into a detailed, comprehensive version.

Expansion guidelines:
- Multiply the word count by approximately 3-5x
- Add relevant examples and illustrations
- Include supporting details and context
- Maintain the original tone and intent
- Use subheadings if the content warrants structure
- Add transitional phrases for flow

Do NOT:
- Add information that contradicts the original
- Change the core message or conclusions
- Use filler or fluff content
- Repeat the same points in different words

Brief content to expand:
{{input_content}}

使用示例:

输入:"Remote work increases productivity. Fewer meetings. Better focus time." 输出:一段 300 字的内容,配以统计数据解释生产力方面的好处,举例说明会议开销的减少,并引用关于深度工作原则的研究。

专业提示:与风格指南 Space 搭配使用,实现符合品牌调性的一致扩写。

秘籍 8:内容精简器

类别:写作难度:中级 推荐提供方:Claude(在缩短篇幅的同时出色地保留原意)

功能说明:在不丢失关键信息的前提下,将冗长内容精简为要点。

该 Command:

名称:content-condense
执行模式:Combination

说明:

Condense the following content to approximately 30% of its original length.

Condensation rules:
- Preserve ALL critical information, decisions, and action items
- Remove redundant explanations and examples
- Combine related sentences
- Eliminate filler phrases ("it is important to note that", "as mentioned earlier")
- Keep specific numbers, dates, and names
- Maintain the original structure if helpful

Priority order for what to keep:
1. Decisions and conclusions
2. Action items and deadlines
3. Key metrics and data points
4. Essential context
5. Supporting details (cut first if needed)

Content to condense:
{{input_content}}

Provide only the condensed version.

使用示例:

输入:一份 1000 字的项目更新输出:300 字的版本,保留了所有决定、指标和行动项

专业提示:在使用执行摘要生成器之前先用此秘籍处理,以获得最大压缩效果。

秘籍 9:SEO 元描述生成器

类别:写作难度:入门 推荐提供方:GPT-5.4(速度快,擅长 SEO)

功能说明:根据内容为网页创建经过优化的元描述。

该 Command:

名称:seo-meta-description
执行模式:Combination

说明:

Generate an SEO-optimized meta description for the following web page content.

Requirements:
- Length: 150-160 characters (strict limit)
- Include primary keyword naturally
- Create urgency or value proposition
- Use active voice
- Include a subtle call-to-action

Provide 3 options:

**Option 1 (Benefit-focused)**:
[Description emphasizing what the reader gains]

**Option 2 (Problem-solution)**:
[Description addressing a pain point and solution]

**Option 3 (Curiosity-driven)**:
[Description that creates intrigue]

For each, show:
- Character count
- Primary keyword identified
- CTA used

---
Page content:
{{input_content}}

使用示例:

输入:一篇关于远程办公生产力技巧的博客文章输出:三条元描述,例如:"Boost your remote work productivity with 7 proven strategies. Learn how top performers stay focused and achieve more from home. Start today."

专业提示:创建一个包含贵品牌关键词和语气指南的 Space,以保持 SEO 语调的一致性。

秘籍 10:社交媒体线程创建器

类别:写作难度:高级 推荐提供方:Claude(内容有创意、引人入胜)

功能说明:将长篇内容转换为引人入胜的社交媒体线程格式(Twitter/X 风格)。

该 Command:

名称:social-thread-creator
执行模式:Combination

说明:

Transform this content into an engaging social media thread (Twitter/X format).

Thread structure:
1. **Hook tweet**: Attention-grabbing opener (no more than 240 chars)
2. **Body tweets**: 5-10 tweets with the main content
3. **Closer**: Call-to-action or summary

Tweet rules:
- Max 280 characters each (aim for 240 for retweet room)
- Number each tweet (1/, 2/, etc.)
- Use line breaks for readability
- Include 1-2 relevant emojis per tweet (subtle, not excessive)
- End hook with "A thread:" or similar

Content guidelines:
- Start with a bold claim or question
- Use "Here's what I learned:" or "Here's the thing:" transitions
- Include specific examples or data points
- Make each tweet standalone but connected
- End with engagement prompt ("What's your experience?")

---
Source content:
{{input_content}}

Output the complete thread ready to post.

使用示例:

输入:一篇 800 字的关于生产力系统的文章输出:一个包含 8 条推文的线程,含开场钩子、关键洞见和引导互动的结尾

专业提示:先在笔记应用中测试线程,以核实字符数。

代码类配方

配方 11:带严重程度评级的代码审查工具

类别:代码难度:高级 推荐提供商:Claude(出色的代码理解能力)或 GPT-5.4

功能说明:对代码执行全面审查,按类别列出问题并给出严重程度评级。

命令:

名称:code-review
执行模式:Combination

指令:

You are a senior software engineer conducting a thorough code review.

Review the following code and provide feedback in this format:

## Code Review Summary
**Language/Framework**: [Detected]
**Overall Quality**: [1-10 score]
**Review Priority**: [Critical/High/Medium/Low]

## Issues Found

### Critical (Must Fix)
| Line | Issue | Recommendation |
|------|-------|----------------|
| [#] | [Problem] | [How to fix] |

### High (Should Fix)
| Line | Issue | Recommendation |
|------|-------|----------------|

### Medium (Consider Fixing)
| Line | Issue | Recommendation |
|------|-------|----------------|

### Low (Nitpicks)
| Line | Issue | Recommendation |
|------|-------|----------------|

## Security Concerns
- [Any security issues]

## Performance Notes
- [Any performance implications]

## What's Done Well
- [Positive observations]

## Suggested Refactoring

[Improved code snippet if applicable]

---
Review criteria:
- Security vulnerabilities
- Performance issues
- Code readability and maintainability
- Error handling
- Naming conventions
- SOLID principles adherence
- Potential bugs or edge cases

Code to review:
{{input_content}}

使用示例:

输入:一个包含嵌套循环且没有错误处理的 50 行函数输出:详细的审查报告,包含 2 个严重问题(缺少空值检查)、3 个高优先级问题(性能)以及重构后的代码示例

专业提示:附加一个包含您团队编码规范的 Space,即可获得针对具体项目的审查建议。

配方 12:单元测试生成器

类别:代码难度:高级 推荐提供商:Claude 或 GPT-5.4(对测试模式有深入了解)

功能说明:为给定代码生成涵盖各种边界情况的全面单元测试。

命令:

名称:generate-unit-tests
执行模式:Combination

指令:

You are a QA engineer specializing in unit test creation.

Generate comprehensive unit tests for the following code.

Test requirements:
1. Use the appropriate testing framework for the detected language:
   - C#: xUnit or NUnit
   - JavaScript/TypeScript: Jest
   - Python: pytest
   - Java: JUnit 5

2. Include test categories:
   - Happy path (normal operation)
   - Edge cases (boundaries, empty inputs)
   - Error cases (invalid inputs, exceptions)
   - Null/undefined handling

3. Follow AAA pattern (Arrange, Act, Assert)

4. Use descriptive test names following:
   [MethodName]_[Scenario]_[ExpectedResult]

5. Include mocking if external dependencies are detected

Output format:
```[language]
// Test file: [FileName].Tests.[ext]

[Complete test code with all test cases]

Test Coverage Summary

Method	Happy Path	Edge Cases	Error Cases
[Name]	[count]	[count]	[count]

Additional Test Recommendations

[Any manual testing needed]
[Integration test suggestions]

Code to test: {{input_content}}

**使用示例**:
> 输入:一个 `CalculateDiscount(price, customerType)` 函数
> 输出:15 个单元测试,涵盖有效折扣、零价格、负价格、未知客户类型以及空输入等情况

**专业提示**:为不同语言创建专属变体(例如 `generate-tests-csharp`),以获得更优化的输出。

---

### 配方 13:API 文档编写工具
**类别**:代码
**难度**:中级
**推荐提供商**:GPT-5.4 或 Claude

**功能说明**:根据代码或端点定义生成全面的 API 文档。

**命令**:
- **名称**:`api-documentation`
- **执行模式**:Combination

**指令**:

You are a technical writer creating API documentation.

Generate professional API documentation for the following code/endpoint.

Documentation format:

[Endpoint/Method Name]

Overview

[2-3 sentence description of what this API does]

Endpoint

[HTTP_METHOD] /path/to/endpoint

Authentication

[Required auth method or "None"]

Request

Headers

Header	Type	Required	Description

Path Parameters

Parameter	Type	Required	Description

Query Parameters

Parameter	Type	Required	Default	Description

Request Body

{
  "field": "type - description"
}

Response

Success Response (200 OK)

{
  "example": "response"
}

Error Responses

Status Code	Description	Example
400	Bad Request	{"error": "..."}
401	Unauthorized	{"error": "..."}
404	Not Found	{"error": "..."}

Example Usage

cURL

curl -X [METHOD] '[URL]' \
  -H 'Authorization: Bearer [TOKEN]' \
  -H 'Content-Type: application/json' \
  -d '[BODY]'

JavaScript

const response = await fetch('[URL]', { ... });

Notes

[Any important considerations]
[Rate limiting info if applicable]

Code/endpoint to document: {{input_content}}

**使用示例**:
> 输入:一个用于用户注册的 C# 控制器操作
> 输出:完整的 API 文档,包含请求/响应结构、错误代码以及调用示例

**专业提示**:附加您的 API 风格指南 Space,即可在各个端点之间保持文档风格一致。

---

### 配方 14:SQL 查询优化工具
**类别**:代码
**难度**:高级
**推荐提供商**:Claude(强大的分析能力)

**功能说明**:分析 SQL 查询并提出性能优化建议。

**命令**:
- **名称**:`sql-optimizer`
- **执行模式**:Combination

**指令**:

You are a database performance expert analyzing SQL queries.

Analyze this SQL query and provide optimization recommendations.

Query Analysis

Original Query

[echo back the query formatted properly]

Detected Issues

Issue	Severity	Impact	Line
[Problem]	[High/Medium/Low]	[Performance impact]	[#]

Optimization Recommendations

[Optimization Name]
- Problem: [What's wrong]
- Solution: [How to fix]
- Expected improvement: [Estimated gain]

Optimized Query

[Rewritten query with optimizations]

Index Recommendations

-- Recommended indexes
CREATE INDEX idx_[name] ON [table]([columns]);

Execution Plan Considerations

[Tips for analyzing the execution plan]

Before/After Comparison

Metric	Original (Est.)	Optimized (Est.)
Table scans	[#]	[#]
Index usage	[%]	[%]
Estimated rows	[#]	[#]

Optimization checks:

Missing indexes
N+1 query patterns
Unnecessary columns (SELECT *)
Subquery vs JOIN efficiency
Proper use of EXISTS vs IN
Index-friendly WHERE clauses
LIKE pattern optimization

SQL query to optimize: {{input_content}}

**使用示例**:
> 输入:在未建立索引的列上使用 WHERE 子句的复杂 JOIN 查询
> 输出:优化后的查询,附带 3 条索引建议以及预计 70% 的性能提升

**专业提示**:在 Space 中包含您的数据库架构,即可获得针对具体表结构的建议。

---

### 配方 15:正则表达式生成器
**类别**:代码
**难度**:中级
**推荐提供商**:任意提供商均可(模式匹配已被充分理解)

**功能说明**:根据自然语言描述生成正则表达式,并附带测试用例。

**命令**:
- **名称**:`regex-generator`
- **执行模式**:Combination

**指令**:

You are a regex expert. Generate a regular expression pattern based on the description.

Regex Pattern

Description Understood

[Paraphrase what the user is looking for]

Pattern

[REGEX_PATTERN]

Pattern Breakdown

Component	Matches	Purpose
[part]	[what it matches]	[why]

Flavor Compatibility

JavaScript: [Yes/No - modifications if needed]
Python: [Yes/No - modifications if needed]
.NET/C#: [Yes/No - modifications if needed]
PCRE (PHP): [Yes/No - modifications if needed]

Test Cases

Input	Should Match	Result
[test string]	Yes	[matched portion]
[test string]	No	[no match]

Code Examples

JavaScript:

const regex = /[PATTERN]/g;
const matches = text.match(regex);

Python:

import re
pattern = r'[PATTERN]'
matches = re.findall(pattern, text)

C#:

var regex = new Regex(@"[PATTERN]");
var matches = regex.Matches(text);

Edge Cases to Consider

[Potential false positives]
[Potential false negatives]

Description: {{input_content}}

**使用示例**:
> 输入:"匹配电子邮件地址,但排除 gmail.com 的邮箱"
> 输出:包含否定先行断言的完整正则表达式、说明、测试用例,以及 3 种语言的代码示例

**专业提示**:在用于生产环境之前,请务必用真实数据测试生成的模式。

---

### 配方 16:错误信息优化工具
**类别**:代码
**难度**:初级
**推荐提供商**:任意提供商均可

**功能说明**:将技术性错误信息改写为用户友好且可操作的提示文案。

**命令**:
- **名称**:`error-message-improver`
- **执行模式**:Combination

**指令**:

You are a UX writer specializing in error messages.

Transform this technical error into a user-friendly message.

Original Error

Improved Error Messages

User-Facing Message

Title: [Short, clear title - 5 words max] Message: [Friendly explanation - 1-2 sentences] Action: [What the user should do]

Full Format

[Title]

[Message explaining what happened in plain terms]

What you can do:
- [Action 1]
- [Action 2 if applicable]

Need help? [Contact support / Error code: XXX]

Variations

Toast/Snackbar (short): [Under 60 characters with action]

Modal/Dialog (detailed): [Full explanation with steps]

Inline/Field-level: [Adjacent to the input field]

Technical Logging

// For developers (log level: ERROR)
[Original error + context for debugging]

Guidelines applied:

Blame the system, not the user
Avoid technical jargon
Provide clear next steps
Include error codes for support reference
Use positive framing when possible

**使用示例**:
> 输入:"NullReferenceException: Object reference not set to an instance of an object at UserService.GetProfile()"
> 输出:"我们未能加载您的个人资料。请尝试刷新页面。如果问题仍然存在,请联系客服并提供错误代码 NRE-USR-001。"

**专业提示**:将优化后的提示文案收集到一个 Space 中,以建立统一的错误信息库。

---

### 配方 17:代码注释生成器
**类别**:代码
**难度**:初级
**推荐提供商**:任意提供商均可

**功能说明**:为未添加注释的代码补充全面的注释。

**命令**:
- **名称**:`add-code-comments`
- **执行模式**:Combination

**指令**:

Add comprehensive comments to the following code.

Commenting guidelines:

Add file/class header documentation
Document all public methods with:
- Purpose description
- Parameter explanations
- Return value description
- Exception documentation (if applicable)
Add inline comments for complex logic
Use the appropriate comment style for the detected language:
- C#: XML documentation (///) for public members
- JavaScript/TypeScript: JSDoc format
- Python: Docstrings (Google style)
- Java: Javadoc

Do NOT:

State the obvious ("increment i by 1")
Over-comment simple code
Change any code logic

Output the complete code with comments added.

Code to comment: {{input_content}}

**使用示例**:
> 输入:一个未添加注释的 C# 服务类
> 输出:同一个类,所有公共方法都补充了 XML 文档注释,复杂算法处也添加了行内注释

**专业提示**:在代码审查前使用此配方,以确保符合文档规范。

---

### 配方 18:重构建议工具
**类别**:代码
**难度**:高级
**推荐提供商**:Claude(出色的模式识别能力)

**功能说明**:分析代码并提出具体的重构建议,附带前后对比示例。

**命令**:
- **名称**:`refactoring-suggestions`
- **执行模式**:Combination

**指令**:

You are a software architect specializing in code quality and refactoring.

Analyze this code and suggest refactoring opportunities.

Refactoring Analysis

Code Quality Score: [1-10]

Identified Opportunities

1. [Refactoring Name] - [Priority: High/Medium/Low]

Pattern: [e.g., Extract Method, Replace Conditional with Polymorphism] Location: Lines [X-Y] Benefit: [Why this improves the code]

Before:

[Current code snippet]

After:

[Refactored code snippet]

Steps to implement:

[Step 1]
[Step 2]

[Repeat for each opportunity]

SOLID Principles Assessment

Principle	Current	After Refactoring
Single Responsibility	[1-5]	[1-5]
Open/Closed	[1-5]	[1-5]
Liskov Substitution	[1-5]	[1-5]
Interface Segregation	[1-5]	[1-5]
Dependency Inversion	[1-5]	[1-5]

Design Pattern Opportunities

[Pattern that could be applied and why]

Recommended Refactoring Order

[Most impactful change first]
[Second priority]
[Third priority]

Code to analyze: {{input_content}}

**使用示例**:
> 输入:一个承担多种职责的 200 行方法
> 输出:5 条重构建议,包括 Extract Method(提取方法)、Introduce Parameter Object(引入参数对象)以及 Replace Conditional with Strategy(用策略模式替换条件语句)

**专业提示**:在 Space 中附加您的架构决策记录(ADR),以获得贴合上下文的建议。

---

### 配方 19:安全漏洞扫描工具
**类别**:代码
**难度**:专家级
**推荐提供商**:Claude(分析全面)

**功能说明**:扫描代码中的常见安全漏洞,并提供修复指导。

**命令**:
- **名称**:`security-scan`
- **执行模式**:Combination

**指令**:

You are a security engineer performing a code security audit.

Scan the following code for security vulnerabilities.

Security Audit Report

Risk Summary

Severity	Count	Immediate Action
Critical	[#]	[Required/Not Required]
High	[#]	[Required/Not Required]
Medium	[#]	[Recommended]
Low	[#]	[Optional]

Vulnerabilities Found

[VULN-001] [Vulnerability Name]

Severity: [Critical/High/Medium/Low] CWE: [CWE-XXX if applicable] OWASP Category: [e.g., A1:2021-Injection] Location: Line [#]

Description: [What the vulnerability is and how it could be exploited]

Vulnerable Code:

[The problematic code]

Remediation:

[Fixed code]

Additional Mitigations:

[Defense in depth measures]

[Repeat for each vulnerability]

Security Best Practices Missing

[Practice not implemented]
[Practice not implemented]

Compliance Notes

GDPR: [Relevant findings]
PCI-DSS: [Relevant findings]
HIPAA: [Relevant findings]

Recommended Security Libraries

Purpose	Library	Why
[Purpose]	[Library name]	[Benefit]

Checks performed:

SQL Injection
XSS (Cross-Site Scripting)
CSRF vulnerabilities
Insecure deserialization
Hardcoded secrets/credentials
Path traversal
Command injection
Insecure cryptography
Authentication/authorization flaws
Information disclosure

Code to scan: {{input_content}}

**使用示例**:
> 输入:处理用户输入的 API 端点
> 输出:发现 3 个漏洞(SQL 注入、缺少输入校验、硬编码 API 密钥),并附带具体修复方法

**专业提示**:在合并到生产环境之前,对所有代码运行此配方,将其设为强制审查步骤。

---

### 配方 20:性能优化顾问
**类别**:代码
**难度**:专家级
**推荐提供商**:Claude(深入的算法分析能力)

**功能说明**:识别性能瓶颈并提出优化建议,附带复杂度分析。

**命令**:
- **名称**:`performance-advisor`
- **执行模式**:Combination

**指令**:

You are a performance engineer analyzing code for optimization opportunities.

Performance Analysis Report

Complexity Analysis

Operation	Time Complexity	Space Complexity	Optimal
[Operation]	O([?])	O([?])	O([?])

Identified Bottlenecks

[PERF-001] [Issue Name]

Severity: [Critical/High/Medium/Low] Location: Line [#] Current Complexity: O([?]) Achievable Complexity: O([?])

Problem: [What's causing the performance issue]

Current Code:

[Slow code]

Optimized Code:

[Fast code]

Expected Improvement:

Time: [X]% faster / O([?]) improvement
Memory: [X]% reduction

[Repeat for each bottleneck]

Memory Optimization

[Memory-related suggestions]

Caching Opportunities

Data	Cache Type	TTL Suggestion	Reason
[What to cache]	[In-memory/Distributed]	[Duration]	[Why]

Async/Parallel Opportunities

[Where concurrency could help]

Database Query Optimization

[If applicable, query improvements]

Benchmarking Recommendations

// Suggested benchmark code

Code to analyze: {{input_content}}

**使用示例**:
> 输入:一个包含嵌套循环的数据处理函数
> 输出:通过排序将 O(n^2) 优化为 O(n log n),并针对重复查询给出缓存建议

**专业提示**:结合 Space 中的实际性能分析器数据,获得有针对性的优化建议。

---

## 研究类配方

### 配方 21:文献综述整合工具
**类别**:研究
**难度**:高级
**推荐提供商**:Claude(出色的整合能力与学术语气)

**功能说明**:将多个研究来源整合为一段连贯的文献综述。

**命令**:
- **名称**:`literature-synthesizer`
- **执行模式**:Combination

**指令**:

You are an academic researcher synthesizing literature for a review paper.

Synthesize the following sources/notes into a cohesive literature review section.

Literature Review

Overview

[2-3 sentence introduction to the research landscape]

Thematic Analysis

Theme 1: [Identified Theme]

[Synthesized discussion weaving together multiple sources] [In-text citations: (Author, Year) format]

Theme 2: [Identified Theme]

[Continue synthesis]

Methodological Approaches

[Summary of methods used across studies]

Key Findings Comparison

Study	Sample	Method	Key Finding	Limitation

Research Gaps Identified

[Gap 1 - with supporting evidence]
[Gap 2 - with supporting evidence]

Theoretical Framework

[How studies connect to theory]

Synthesis Conclusion

[Overall state of knowledge and direction for future research]

Writing guidelines:

Use academic tone
Connect ideas across sources (not source-by-source summary)
Highlight agreements and contradictions
Identify patterns and trends
Use hedging language appropriately ("suggests", "indicates")
Maintain objectivity

Source material: {{input_content}}

**使用示例**:
> 输入:来自 10 篇关于远程办公生产力的研究论文的笔记
> 输出:一篇约 800 字的文献综述,包含主题分析、对比表格以及已识别的研究空白

**专业提示**:在 Space 中附加您的参考文献列表,以保持引用格式的一致性。

---

### 配方 22:竞争分析框架
**类别**:研究
**难度**:中级
**推荐提供商**:GPT-5.4 或 Claude

**功能说明**:将竞争情报整理为标准化的分析框架。

**命令**:
- **名称**:`competitive-analysis`
- **执行模式**:Combination

**指令**:

You are a market research analyst creating a competitive analysis.

Structure the following competitive intelligence into a comprehensive analysis.

Competitive Analysis: [Industry/Product Category]

Executive Summary

[3-4 sentence overview of competitive landscape]

Competitor Profiles

[Competitor 1 Name]

Attribute	Details
Company Size	[employees/revenue]
Market Position	[Leader/Challenger/Niche]
Target Market	[Primary audience]
Pricing Strategy	[Premium/Value/Freemium]
Key Differentiator	[Main competitive advantage]

Strengths:

[Strength 1]

Weaknesses:

[Weakness 1]

[Repeat for each competitor]

Feature Comparison Matrix

Feature	Us	Competitor 1	Competitor 2	Competitor 3
[Feature]	[status]	[status]	[status]	[status]

Pricing Comparison

Plan	Us	Competitor 1	Competitor 2

Market Positioning Map

[Text-based positioning description:
High Price/Premium Experience: [Competitor X]
Low Price/Basic Experience: [Competitor Y]
Our Position: [Description]
]

Competitive Threats

Threat	Severity	Likelihood	Mitigation

Opportunities

Opportunity	Competitor Gap	Our Advantage

Strategic Recommendations

[Recommendation with rationale]
[Recommendation with rationale]

Intelligence data: {{input_content}}

**使用示例**:
> 输入:来自竞品网站、评论和定价页面的笔记
> 输出:结构化分析,包含功能对比矩阵、定位洞察以及战略建议

**专业提示**:在 Space 中持续更新竞品情报,以支持长期分析。

---

### 配方 23:SWOT 分析生成器
**类别**:研究
**难度**:中级
**推荐提供商**:任意提供商均可

**功能说明**:根据非结构化的商业信息生成全面的 SWOT 分析。

**命令**:
- **名称**:`swot-analysis`
- **执行模式**:Combination

**指令**:

You are a strategic planning consultant creating a SWOT analysis.

Analyze the following information and create a comprehensive SWOT analysis.

SWOT Analysis: [Subject]

Summary Matrix

	Helpful	Harmful
Internal	Strengths	Weaknesses
	[Brief list]	[Brief list]
External	Opportunities	Threats
	[Brief list]	[Brief list]

Detailed Analysis

Strengths (Internal, Positive)

Strength	Evidence	Strategic Value
[S1]	[Supporting data]	[How to leverage]

Weaknesses (Internal, Negative)

Weakness	Evidence	Mitigation
[W1]	[Supporting data]	[How to address]

Opportunities (External, Positive)

Opportunity	Market Signal	Capture Strategy
[O1]	[Supporting data]	[How to pursue]

Threats (External, Negative)

Threat	Warning Signs	Defense Strategy
[T1]	[Supporting data]	[How to counter]

Strategic Implications

SO Strategies (Use Strengths to capture Opportunities):

[Strategy 1]

WO Strategies (Overcome Weaknesses to capture Opportunities):

[Strategy 1]

ST Strategies (Use Strengths to avoid Threats):

[Strategy 1]

WT Strategies (Minimize Weaknesses to avoid Threats):

[Strategy 1]

Priority Actions

[Most critical action]
[Second priority]
[Third priority]

Information to analyze: {{input_content}}

**使用示例**:
> 输入:公司年报节选与市场调研笔记
> 输出:完整的 SWOT 分析,包含战略含义与优先行动事项

**专业提示**:每季度使用最新信息重新运行,以追踪战略变化。

---

### 配方 24:研究问题精炼工具
**类别**:研究
**难度**:中级
**推荐提供商**:Claude(出色的学术表述能力)

**功能说明**:将模糊的研究想法转化为表述清晰、可供研究的问题。

**命令**:
- **名称**:`research-question-refiner`
- **执行模式**:Combination

**指令**:

You are a research methodology expert helping refine research questions.

Transform the following research idea into well-formed research questions.

Research Question Development

Original Idea

Problem Statement

[Clear articulation of the research problem in 2-3 sentences]

Primary Research Question

RQ: [Well-formed question following FINER/PICO criteria]

Question Type: [Descriptive/Comparative/Relationship/Causal]

Sub-Questions

RQ1a: [Supporting question]
RQ1b: [Supporting question]
RQ1c: [Supporting question]

Hypothesis (if applicable)

H1: [Testable hypothesis] H0: [Null hypothesis]

Question Quality Check

Criterion	Met?	Notes
Feasible	[Yes/Partially/No]	[Consideration]
Interesting	[Yes/Partially/No]	[Why it matters]
Novel	[Yes/Partially/No]	[Contribution]
Ethical	[Yes/Partially/No]	[Considerations]
Relevant	[Yes/Partially/No]	[Significance]

Variables Identified

Independent: [Variable]
Dependent: [Variable]
Control: [Variables to control]

Suggested Methodology

[Brief recommendation on how to investigate]

Alternative Framings

[Alternative RQ if different angle wanted]
[Another alternative]

Refinement applied:

Clarity and specificity
Appropriate scope
Measurability
Theoretical grounding

**使用示例**:
> 输入:"我想研究社交媒体对青少年的影响"
> 输出:精炼后的研究问题:"每日 Instagram 使用时长(超过 2 小时)与 13-17 岁城市青少年自我报告的焦虑水平之间存在多大程度的相关性?"

**专业提示**:在任何研究项目开始时使用此配方,以确保打下坚实的基础。

---

### 配方 25:引用格式化工具
**类别**:研究
**难度**:初级
**推荐提供商**:任意提供商均可

**功能说明**:将原始引用信息转换为多种学术风格的规范引用格式。

**命令**:
- **名称**:`format-citation`
- **执行模式**:Combination

**指令**:

Format the following citation information into proper academic citation styles.

Citation Formatting

Source Information Extracted

Field	Value
Author(s)	[Names]
Title	[Title]
Year	[Year]
Source	[Journal/Book/Website]
Volume/Issue	[If applicable]
Pages	[If applicable]
DOI/URL	[If applicable]
Publisher	[If applicable]
Access Date	[For web sources]

Formatted Citations

APA 7th Edition

Reference List: [Full citation]

In-text (First use): [Citation]

In-text (Subsequent): [Citation]

MLA 9th Edition

Works Cited: [Full citation]

In-text: [Citation]

Chicago (Author-Date)

Bibliography: [Full citation]

In-text: [Citation]

Chicago (Notes-Bibliography)

Footnote: [Full citation]

Short footnote: [Abbreviated citation]

Bibliography: [Full citation]

Harvard

Reference List: [Full citation]

In-text: [Citation]

IEEE

Reference List: [Full citation]

In-text: [Citation number]

Notes

[Any formatting uncertainties]
[Missing information that affects citation]

Raw citation information: {{input_content}}

**使用示例**:
> 输入:"John Smith 和 Jane Doe 撰写了一篇名为《The Future of AI》的文章,发表于 2023 年《Journal of Technology》第 15 卷,第 100-120 页"
> 输出:以 6 种学术风格规范格式化的引用

**专业提示**:创建一个包含您所在机构首选风格指南的 Space,以获得优先适用的格式化结果。

---

## 商业配方

### 配方 26：提案大纲生成器
**类别**：商业
**难度**：中级
**推荐提供商**：GPT-5.4 或 Claude

**功能说明**：根据简短的项目描述生成全面的提案大纲。

**命令**：
- **Name**：`proposal-outline`
- **Execution Mode**：Combination

**Instruction**：

You are a business development specialist creating proposal outlines.

Generate a comprehensive proposal outline based on the following project description.

Proposal Outline: [Project Name]

Cover Page Elements

Title: [Compelling proposal title]
Subtitle: [One-line value proposition]
Client: [Client name]
Submitted by: [Your company]
Date: [Submission date]

Executive Summary (Page 1)

The Challenge: [Problem statement - 2 sentences]
Our Solution: [High-level approach - 2 sentences]
Expected Outcomes: [Key benefits - bullet points]
Investment Summary: [Placeholder for pricing]

Understanding Your Needs (Section 1)

1.1 Current Situation Analysis 1.2 Key Challenges Identified 1.3 Goals and Success Criteria

Proposed Solution (Section 2)

2.1 Solution Overview 2.2 Methodology/Approach 2.3 Key Deliverables 2.4 Technology/Tools (if applicable)

Implementation Plan (Section 3)

3.1 Project Phases

Phase	Duration	Key Activities	Deliverables

3.2 Timeline (Gantt chart placeholder) 3.3 Resource Requirements 3.4 Client Responsibilities

Team & Qualifications (Section 4)

4.1 Project Team Structure 4.2 Key Personnel Bios 4.3 Relevant Experience/Case Studies

Investment (Section 5)

5.1 Pricing Summary 5.2 Payment Terms 5.3 What's Included/Excluded

Terms & Conditions (Section 6)

6.1 Validity Period 6.2 Assumptions 6.3 Change Management

Appendices

A: Detailed Technical Specifications
B: Case Studies
C: Team Resumes
D: References

Call to Action

[Suggested next steps and contact information]

Project description: {{input_content}}

**使用示例**：
> 输入："We need to migrate our legacy system to cloud, about 6 months timeline, mid-size retail company"
> 输出：针对云迁移量身定制的完整提案大纲，包含零售行业特有的考量因素

**专业提示**：在 Space 中附上过去成功的提案，以保持结构和语言的一致性。

---

### 配方 27：风险评估矩阵生成器
**类别**：商业
**难度**：中级
**推荐提供商**：Claude（分析全面）

**功能说明**：识别项目风险，并生成结构化的风险评估矩阵。

**命令**：
- **Name**：`risk-assessment`
- **Execution Mode**：Combination

**Instruction**：

You are a project risk manager creating a risk assessment.

Analyze the following project information and create a comprehensive risk assessment.

Risk Assessment Report

Project Overview

[Brief summary of the project]

Risk Register

ID	Risk Description	Category	Probability	Impact	Risk Score	Priority
R1	[Description]	[Category]	[1-5]	[1-5]	[P*I]	[H/M/L]

Risk Scoring Matrix

Impact →     1-Minimal  2-Minor  3-Moderate  4-Major  5-Severe
Probability ↓
5-Almost Certain   5        10        15        20       25
4-Likely           4         8        12        16       20
3-Possible         3         6         9        12       15
2-Unlikely         2         4         6         8       10
1-Rare             1         2         3         4        5

Legend: 1-6=Low, 7-14=Medium, 15-25=High

Detailed Risk Analysis

R1: [Risk Name]

Category: [Technical/Schedule/Resource/External/Financial] Probability: [1-5] - [Justification] Impact: [1-5] - [Justification] Risk Score: [Score] ([Priority])

Triggers/Warning Signs:

[Early indicator 1]
[Early indicator 2]

Mitigation Strategy:

Action	Owner	Deadline	Status

Contingency Plan: [If risk materializes, what's the backup plan]

[Repeat for top 5-10 risks]

Risk Summary by Category

Category	High Risks	Medium Risks	Low Risks

Top 5 Risks Requiring Immediate Attention

[Risk with mitigation status]
[Risk with mitigation status]

Monitoring Plan

[How and when risks will be reviewed]

Project information: {{input_content}}

**使用示例**：
> 输入：包含时间表和团队信息的软件开发项目简介
> 输出：识别出 15 项风险，包含完整分析、缓解策略和监控计划

**专业提示**：在项目执行期间每周审查并更新风险登记表。

---

### 配方 28：状态报告格式化工具
**类别**：商业
**难度**：初级
**推荐提供商**：任何提供商（格式化任务）

**功能说明**：将原始状态笔记转化为精炼、可直接呈报给管理层的状态报告。

**命令**：
- **Name**：`status-report`
- **Execution Mode**：Combination

**Instruction**：

Format the following status notes into a professional status report.

Status Report

Project: [Inferred or "Project Name"] Reporting Period: [Inferred or "Week of [Date]"] Status: [On Track / At Risk / Delayed] [Use appropriate indicator] Report Author: [TBD]

Executive Summary

[2-3 sentence overview of current status]

Overall Health Indicators

Area	Status	Trend
Schedule	[Green/Yellow/Red]	[Up/Down/Stable]
Budget	[Green/Yellow/Red]	[Up/Down/Stable]
Scope	[Green/Yellow/Red]	[Up/Down/Stable]
Resources	[Green/Yellow/Red]	[Up/Down/Stable]

Accomplishments This Period

[Achievement 1]
[Achievement 2]
[Achievement 3]

In Progress

Task	Owner	% Complete	Target Date

Planned for Next Period

[Planned item 1]
[Planned item 2]

Risks & Issues

Type	Description	Impact	Mitigation	Owner
Risk	[Description]	[H/M/L]	[Action]	[Name]
Issue	[Description]	[H/M/L]	[Resolution]	[Name]

Blockers (Requiring Escalation)

[Blocker if any]

Key Decisions Needed

[Decision 1 - by whom, by when]

Metrics

[Any relevant metrics or KPIs]

Raw status notes: {{input_content}}

**使用示例**：
> 输入：项目经理笔记中的要点列表
> 输出：格式化的单页状态报告，可直接分发给相关方

**专业提示**：设置一个每周重复的日历提醒，在每周五用当周笔记运行此命令。

---

### 配方 29：相关方更新邮件
**类别**：商业
**难度**：初级
**推荐提供商**：任何提供商

**功能说明**：根据简短笔记起草专业的相关方更新邮件。

**命令**：
- **Name**：`stakeholder-update`
- **Execution Mode**：Combination

**Instruction**：

Draft a professional stakeholder update email based on the following notes.

Stakeholder Update Email

Subject Line Options:

[Option focusing on achievement]
[Option focusing on timeline]
[Option focusing on request/next steps]

Email Draft:

Dear [Stakeholder/Team],

TL;DR: [One sentence summary - the most important thing to know]

Progress Update

[Opening paragraph: Where we are in the project journey]

Key Accomplishments:

[Achievement 1]
[Achievement 2]

Current Focus: [What the team is working on now]

Looking Ahead: [What's coming in the next period]

[If there are challenges]: Items Needing Attention: [Brief, solution-focused description of any issues]

Action Required (if any):

[What you need from stakeholders, by when]

[If there are positive developments]: Wins Worth Celebrating: [Quick recognition of team or milestone]

Next Update: [Date]

Please let me know if you have any questions or would like to schedule a deeper discussion on any of these items.

Best regards, [Sender]

Alternative Tone Versions:

Brief Version (for busy executives): [3-4 sentences max]

Detailed Version (for project sponsors): [Expanded with more context]

Notes for update: {{input_content}}

**使用示例**：
> 输入："milestone 2 done, team working on database migration, slight delay expected, need approval for additional budget"
> 输出：包含多个标题选项、TL;DR 摘要的专业邮件，并妥善处理预算申请的升级说明

**专业提示**：在 Space 中附上相关方偏好信息（例如："CEO 偏好简短更新，CTO 希望获得技术细节"）。

---

### 配方 30：决策矩阵生成器
**类别**：商业
**难度**：中级
**推荐提供商**：Claude（分析能力强）

**功能说明**：生成加权决策矩阵，以支持客观决策。

**命令**：
- **Name**：`decision-matrix`
- **Execution Mode**：Combination

**Instruction**：

You are a decision analysis specialist creating a weighted decision matrix.

Analyze the following options and create a comprehensive decision matrix.

Decision Analysis: [Decision Topic]

Decision Context

[Brief description of what decision needs to be made]

Options Under Consideration

[Option A]: [Brief description]
[Option B]: [Brief description]
[Option C]: [Brief description]

Evaluation Criteria

Criterion	Weight (1-10)	Why Important
[Criterion 1]	[Weight]	[Justification]
[Criterion 2]	[Weight]	[Justification]

Weighted Decision Matrix

Criterion	Weight	Option A	Score	Option B	Score	Option C	Score
[C1]	[W]	[Rating 1-5]	[W*R]	[Rating 1-5]	[W*R]	[Rating 1-5]	[W*R]
[C2]	[W]	[Rating 1-5]	[W*R]	[Rating 1-5]	[W*R]	[Rating 1-5]	[W*R]
TOTAL			[Sum]		[Sum]		[Sum]

Rating Scale: 1=Poor, 2=Below Average, 3=Average, 4=Good, 5=Excellent

Analysis Summary

Winner: [Option with highest score] Score Breakdown:

[Option A]: [Score] ([Percentage]%)
[Option B]: [Score] ([Percentage]%)
[Option C]: [Score] ([Percentage]%)

Sensitivity Analysis

[What would need to change for a different option to win]

Qualitative Considerations

[Factors not captured in the matrix]

Risk Comparison

Option	Key Risks	Mitigation Difficulty

Recommendation

Primary Recommendation: [Option] because [key reasons]

Conditions for Reconsideration: [When to revisit this decision]

Decision information: {{input_content}}

**使用示例**：
> 输入："Choosing between AWS, Azure, and GCP for our cloud platform. Care about cost, performance, team expertise, and vendor lock-in."
> 输出：包含各项评分、敏感性分析和推荐结论的完整加权矩阵

**专业提示**：在运行分析前先让相关方参与权重设定，以获得他们的认同。

---

## 创意配方

### 配方 31：故事情节大纲生成器
**类别**：创意
**难度**：中级
**推荐提供商**：Claude（兼具创意与结构性）

**功能说明**：将故事构思发展为带有人物弧光的结构化情节大纲。

**命令**：
- **Name**：`story-plot-outline`
- **Execution Mode**：Combination

**Instruction**：

You are a story consultant developing a plot outline from a story concept.

Story Development: [Working Title]

Logline

[One sentence that captures the essence: Protagonist + Goal + Obstacle + Stakes]

Genre & Tone

Primary Genre: [Genre] Subgenre: [If applicable] Tone: [Light/Dark/Dramatic/Comedic/etc.] Comparable Works: [2-3 similar stories]

Story Structure (Three-Act)

Act One: Setup (25%)

Hook: [Opening scene/moment] Ordinary World: [Status quo before the story begins] Inciting Incident: [The event that starts the story] First Plot Point: [Decision that launches into Act Two]

Act Two: Confrontation (50%)

Rising Action: [Key challenges and developments] Midpoint: [Major revelation or shift] Darkest Moment: [All seems lost] Second Plot Point: [Decision that launches into Act Three]

Act Three: Resolution (25%)

Climax: [Final confrontation] Resolution: [How things settle] Final Image: [Closing scene]

Character Arcs

Protagonist: [Name]

Want: [External goal]
Need: [Internal growth needed]
Flaw: [What holds them back]
Arc: [How they change]

Antagonist: [Name]

Motivation: [Why they oppose protagonist]
Humanity: [What makes them relatable]

Supporting Characters:

[Character]: [Role in story]

Theme

Central Theme: [One sentence] Thematic Question: [What the story asks]

Key Scenes

[Scene 1: Description]
[Scene 2: Description] [Continue for major scenes]

Subplots

Subplot A: [Description and how it supports theme]
Subplot B: [Description and how it supports theme]

Story concept: {{input_content}}

**使用示例**：
> 输入："A retired detective is pulled back into one last case when her estranged daughter goes missing"
> 输出：包含人物弧光、主题和 12 个关键场景的完整三幕大纲

**专业提示**：先反复打磨大纲再动笔写作，之后将其放入 Space 中，作为写作过程中保持一致性的参考。

---

### 配方 32：人物档案生成器
**类别**：创意
**难度**：中级
**推荐提供商**：Claude（擅长细腻的人物刻画）

**功能说明**：根据基本描述生成全面的人物档案。

**命令**：
- **Name**：`character-profile`
- **Execution Mode**：Combination

**Instruction**：

You are a character development specialist creating a detailed character profile.

Character Profile: [Character Name]

Quick Reference

Attribute	Value
Full Name	[Name]
Age	[Age]
Occupation	[Job]
Role in Story	[Protagonist/Antagonist/Supporting]

Physical Description

Appearance: [Detailed physical description] Distinguishing Features: [Unique characteristics] Typical Attire: [How they usually dress] Body Language: [How they carry themselves]

Psychology

Personality Type: [MBTI or similar] Dominant Traits: [3-5 key traits] Strengths:

[Strength 1]
[Strength 2]

Weaknesses/Flaws:

[Flaw 1]
[Flaw 2]

Fears: [What terrifies them] Desires: [What they want most] Secrets: [What they hide]

Background

Childhood: [Brief formative years] Key Life Events: [Moments that shaped them] Relationships:

Family: [Status]
Friends: [Types of relationships]
Romantic: [History/current]

Trauma/Wounds: [Emotional baggage]

Voice & Mannerisms

Speech Pattern: [How they talk] Vocabulary: [Word choices] Catchphrases: [Recurring expressions] Habits/Tics: [Behavioral quirks]

Story Function

Want (External Goal): [What they're pursuing] Need (Internal Growth): [What they must learn] Arc: [How they change from beginning to end] Conflict with Theme: [How they embody/challenge the theme]

Character in Action

How they respond to:

Conflict: [Response style]
Success: [Response style]
Failure: [Response style]
Love: [Response style]

Writer's Notes

Inspiration: [Real people or characters that inspired this] Challenges: [Tricky aspects to write]

Character description: {{input_content}}

**使用示例**：
> 输入："Middle-aged librarian who secretly writes romance novels, main character of a cozy mystery"
> 输出：包含心理、背景、说话方式和故事功能的完整档案

**专业提示**：为所有主要人物创建档案，并存放在 Space 中以保持一致性。

---

### 配方 33：对话改善工具
**类别**：创意
**难度**：中级
**推荐提供商**：Claude（对话自然流畅）

**功能说明**：让虚构对话更自然、更贴合人物、更具感染力。

**命令**：
- **Name**：`improve-dialogue`
- **Execution Mode**：Combination

**Instruction**：

You are a dialogue specialist improving fictional dialogue.

Dialogue Enhancement

Original Dialogue

Analysis

Current Issues:

[Issue 1: e.g., "too on-the-nose"]
[Issue 2: e.g., "all characters sound the same"]

Improved Version

[Enhanced dialogue with character names and actions]

What Was Changed

Change	Before	After	Why
[Type]	[Original phrase]	[New phrase]	[Improvement reason]

Techniques Applied

Subtext: [Where meaning is implied not stated]
Interruptions/Overlap: [Natural conversation flow]
Character Voice: [How each character sounds distinct]
Beats: [Action between lines]

Alternative Version (Different Tone)

[Same scene with different emotional undertone]

Tips for This Scene

[Suggestion for further improvement]
[What to avoid]

Improvement guidelines:

Remove exposition dumps ("As you know, Bob...")
Add subtext (characters don't say exactly what they mean)
Give each character a distinct voice
Include beats (actions between dialogue)
Use interruptions and incomplete sentences naturally
Show conflict through word choice

**使用示例**：
> 输入：两个角色以平淡、说明式的对话讨论一次背叛
> 输出：同一段对话，但加入了潜台词、情感张力和鲜明各异的语气

**专业提示**：在 Space 中放入人物档案，以获得语气一致的改善效果。

---

### 配方 34：场景描写增强工具
**类别**：创意
**难度**：中级
**推荐提供商**：Claude（意象生动）

**功能说明**：将基础的场景描述转化为身临其境、感官丰富的文字。

**命令**：
- **Name**：`enhance-scene`
- **Execution Mode**：Combination

**Instruction**：

You are a descriptive writing specialist enhancing scene descriptions.

Scene Enhancement

Original Description

Enhanced Version

[Richly detailed scene description using sensory details]

Sensory Details Added

Sense	Details Included
Sight	[Visual elements]
Sound	[Auditory elements]
Smell	[Olfactory elements]
Touch/Texture	[Tactile elements]
Taste	[If applicable]

Mood & Atmosphere

Established Mood: [The feeling evoked] Techniques Used: [Pathetic fallacy, contrast, etc.]

Alternative Versions

Minimalist Version: [Same scene, sparse prose style]

Gothic/Dark Version: [Same scene with darker atmosphere]

Fast-Paced Version: [Same scene with quick, punchy sentences]

Writing Techniques Applied

Specific > General: [Example from text]
Active Verbs: [Example from text]
Unique Comparisons: [Metaphors/similes used]
Character Perspective: [How POV shapes description]

Enhancement guidelines:

Show, don't tell
Use specific, concrete details
Engage multiple senses
Reflect character's emotional state
Avoid cliches
Vary sentence length for rhythm

**使用示例**：
> 输入："It was a rainy night in the city. The detective walked down the street."
> 输出：充满氛围感的黑色电影式描写，包含霓虹灯的倒影、远处的警笛声，以及侦探湿漉漉的脚步回响

**专业提示**：指定你的题材和视角人物，以获得量身定制的增强效果。

---

### 配方 35：写作风格模仿工具
**类别**：创意
**难度**：高级
**推荐提供商**：Claude（擅长风格分析）

**功能说明**：将内容改写为指定作者或题材的风格。

**命令**：
- **Name**：`style-mimic`
- **Execution Mode**：Combination

**Instruction**：

You are a literary style analyst and writer.

Rewrite the following content in the specified style.

Style Analysis & Rewrite

Target Style: [Author/Genre from input or inferred]

Style Characteristics

Element	Characteristics
Sentence Structure	[Short/Long/Varied/Complex]
Vocabulary	[Simple/Sophisticated/Technical/Poetic]
Tone	[Formal/Casual/Ironic/Earnest]
Narrative Voice	[Distant/Intimate/Unreliable]
Signature Techniques	[What makes this style recognizable]

Original Content

Rewritten in [Target] Style

[Complete rewrite embodying the target style]

Style Elements Applied

[Element 1]: [How it was applied]
[Element 2]: [How it was applied]
[Element 3]: [How it was applied]

Comparison

Original	Rewrite	Style Element
[Phrase]	[Phrase]	[What changed]

Alternative Style Versions

Hemingway Style (if not already): [Sparse, direct, short sentences]

Austen Style (if not already): [Witty, observational, socially aware]

Note: Specify the target author/style in your input, or I will suggest appropriate styles based on the content.

Content and target style:

**使用示例**：
> 输入："Rewrite this product description in the style of Douglas Adams: 'Our software helps you manage tasks efficiently.'"
> 输出：一段异想天开、荒诞不经的描写，围绕着"在宇宙中真正完成任务"这件事的不可能性展开

**专业提示**：将这个命令用于创意练习，或通过对比不同风格来找到属于自己的写作声音。

---

## 效率配方

### 配方 36：每日站会格式化工具
**类别**：效率
**难度**：初级
**推荐提供商**：任何提供商（格式化任务）

**功能说明**：将粗略的笔记格式化为清晰、结构化的每日站会更新。

**命令**：
- **Name**：`standup-format`
- **Execution Mode**：Combination

**Instruction**：

Format the following notes into a clear daily standup update.

Daily Standup - [Date]

Yesterday

[What was accomplished - bullet points]

Today

[What's planned - bullet points]

Blockers

[Any impediments - or "None" if clear]

Quick Version (for chat/Slack):

Yesterday: [One line summary] Today: [One line summary] Blockers: [One line or "None"]

Time Tracking (if hours mentioned):

Task	Hours

Raw notes: {{input_content}}

**使用示例**：
> 输入："worked on api endpoint, got stuck on auth, today finishing api and starting frontend, need credentials from devops"
> 输出：格式化的站会更新，包含清晰的分节和适合发送到 Slack 的简版

**专业提示**：为此命令设置一个快捷键，在每天站会前运行。

---

### 配方 37：每周回顾模板填充工具
**类别**：效率
**难度**：中级
**推荐提供商**：Claude（善于反思式分析）

**功能说明**：将一周的笔记转化为附带洞见的结构化每周回顾。

**命令**：
- **Name**：`weekly-review`
- **Execution Mode**：Combination

**Instruction**：

Create a comprehensive weekly review from the following notes.

Weekly Review: Week of [Date Range]

Accomplishments

Key Wins:

[Major accomplishment 1]
[Major accomplishment 2]

Completed Tasks:

[Task list]

Progress on Goals:

Goal	Progress	Notes

Challenges & Learnings

Obstacles Faced:

[Challenge 1]: [How addressed]

Lessons Learned:

[Insight 1]
[Insight 2]

What Didn't Go Well:

[Item]: [Root cause if known]

Reflection

Energy Levels: [High/Medium/Low] - [Pattern observed] Focus Quality: [Assessment] Work-Life Balance: [Assessment]

Next Week Planning

Top 3 Priorities:

[Priority 1]
[Priority 2]
[Priority 3]

Meetings/Commitments:

[Key meeting 1]

Tasks to Delegate/Defer:

[Task that should be delegated]

Habits & Systems

What Worked:

[System that helped]

What to Adjust:

[System to modify]

Gratitude & Recognition

[Something/someone to appreciate]

Week's notes: {{input_content}}

**使用示例**：
> 输入：一周内杂乱的笔记，包含任务、烦恼和成就
> 输出：包含洞见、心得和下周优先事项的结构化反思

**专业提示**：将此命令安排在每周五下午运行，有意识地为这一周工作画上句号。

---

### 配方 38：学习笔记整理工具
**类别**：效率
**难度**：中级
**推荐提供商**：Claude（擅长教学式结构化）

**功能说明**：将原始学习笔记整理为结构化、便于复习的学习材料。

**命令**：
- **Name**：`organize-learning-notes`
- **Execution Mode**：Combination

**Instruction**：

Organize these learning notes into structured study materials.

Study Notes: [Topic]

Quick Summary

[3-5 sentence overview of the topic]

Key Concepts

Concept 1: [Name]

Definition: [Clear definition] Key Points:

[Point 1]
[Point 2] Example: [Practical example] Connection: [How it relates to other concepts]

[Repeat for each major concept]

Important Terms

Term	Definition	Example
[Term]	[Definition]	[Example]

Formulas/Rules (if applicable)

[Any formulas or rules]

Mental Models

[Analogies or frameworks to remember the concepts]

Common Mistakes to Avoid

[Mistake 1]: [Why it's wrong]
[Mistake 2]: [Why it's wrong]

Practice Questions

Easy:

[Question] - Answer: [Answer]

Medium:

[Question] - Answer: [Answer]

Hard:

[Question] - Answer: [Answer]

Connections to Prior Knowledge

[How this relates to previously learned material]

Further Study

[Resource 1]
[Topic to explore deeper]

Spaced Repetition Cards

Front (Question)	Back (Answer)
[Q1]	[A1]

Raw notes: {{input_content}}

**使用示例**：
> 输入：一堂机器学习课程的零散笔记
> 输出：包含概念、练习题和可直接用于制作抽认卡的内容的有条理学习指南

**专业提示**：将间隔重复卡片导出到你的抽认卡应用，以实现长期记忆。

---

### 配方 39：速查卡生成工具
**类别**：效率
**难度**：中级
**推荐提供商**：任何提供商

**功能说明**：将信息浓缩为紧凑的速查卡格式。

**命令**：
- **Name**：`quick-reference-card`
- **Execution Mode**：Combination

**Instruction**：

Create a compact quick reference card from the following information.

Quick Reference: [Topic]

Essential Commands/Actions

Action	How To	Example
[Action]	[Instruction]	[Example]

Key Shortcuts

Shortcut	Function
[Key combo]	[What it does]

Common Patterns

[Pattern 1]: [Template]
[Pattern 2]: [Template]

Cheat Sheet

Do This:

[Best practice 1]
[Best practice 2]

Avoid This:

[Anti-pattern 1]
[Anti-pattern 2]

Quick Lookup

Situation	Solution
[When X]	[Do Y]

Emergency Fixes

Problem	Quick Fix
[Issue]	[Solution]

Memory Aids

[Mnemonics or quick ways to remember]

Version: [1.0] Last Updated: [Date]

Source information: {{input_content}}

**使用示例**：
> 输入：一门新编程语言或工具的文档
> 输出：包含命令、快捷键和常用模式的单页速查卡

**专业提示**：将这些卡片打印出来，或另存为 PDF，以便工作时快速查阅。

---

### 配方 40：清单生成工具
**类别**：效率
**难度**：初级
**推荐提供商**：任何提供商

**功能说明**：根据流程描述或需求生成全面的清单。

**命令**：
- **Name**：`generate-checklist`
- **Execution Mode**：Combination

**Instruction**：

Generate a comprehensive checklist from the following process or requirements.

Checklist: [Process Name]

Pre-Requisites

[Prerequisite 1]
[Prerequisite 2]

Main Steps

Phase 1: [Phase Name]

[Step 1]
- [Sub-step if needed]
[Step 2]
[Step 3]

Phase 2: [Phase Name]

[Step 4]
[Step 5]

Phase 3: [Phase Name]

[Step 6]
[Step 7]

Verification

[Verification step 1]
[Verification step 2]

Cleanup/Follow-up

[Cleanup step 1]
[Follow-up action]

Notes

[Important consideration 1]
[Important consideration 2]

Common Mistakes to Check

Verified: [Not making mistake 1]
Verified: [Not making mistake 2]

Compact Version (for quick use):

[ ] Step 1
[ ] Step 2
[ ] Step 3
...

Estimated Time: [Time estimate] Last Updated: [Date] Owner: [Who is responsible]

Process description: {{input_content}}

**使用示例**：
> 输入："Before deploying to production, we need to run tests, update version number, create release notes, deploy to staging, test staging, then deploy to prod, and notify the team"
> 输出：详细的部署清单，包含各阶段、验证步骤和回滚注意事项

**专业提示**：将常用的清单另存为可重复使用的模板，放在 Space 中。

---

## 附录：配方速查表

### 按难度
| 初级 | 中级 | 高级 | 专家级 |
|----------|--------------|----------|--------|
| 要点转叙述 | 执行摘要 | 代码评审 | 安全扫描 |
| SEO 元描述 | 语气转换 | 单元测试生成 | 性能建议 |
| 错误消息 | 邮件摘要 | 文献综述 | |
| 站会格式化 | SWOT 分析 | 重构建议 | |
| 清单生成 | 决策矩阵 | 风格模仿 | |

### 按推荐提供商
| Claude 最佳 | GPT-5.4 最佳 | 任何提供商 |
|-------------|-------------------|--------------|
| 语气转换 | SEO 元描述 | 要点转叙述 |
| 技术转通俗 | API 文档 | 错误消息 |
| 代码评审 | 提案大纲 | 引用格式化 |
| 文献综述 | 邮件摘要 | 站会格式化 |
| 人物档案 | 状态报告 | 清单生成 |

### 最常用的 5 个配方（推荐入门套装）
1. **执行摘要生成器** - 适用于任何长文档
2. **语气转换工具** - 日常沟通所需
3. **代码评审工具** - 开发工作流程
4. **会议记录转行动项** - 每次会议之后
5. **站会格式化工具** - 开发者的每日惯例

---

## 后续步骤

1. **从小处着手**：挑选 3-5 个符合你日常工作的配方
2. **定制调整**：修改指令以匹配你的具体需求
3. **组织归类**：使用 Command Groups 对你的配方进行分类
4. **持续迭代**：根据输出质量优化 prompt
5. **分享共享**：导出效果良好的命令供团队使用

**相关教程**：
- [管理 Commands](/desktop-app/commands-and-spaces/managing-commands)
- [管理 Spaces](/desktop-app/commands-and-spaces/managing-spaces)
- [Command Groups](/desktop-app/commands-and-spaces/command-groups)

如何使用本秘籍手册​

理解变量​

写作类秘籍​

秘籍 1:执行摘要生成器​

秘籍 2:邮件线程摘要器​

秘籍 3:语气转换器(多模式)​

秘籍 4:要点转散文转换器​

秘籍 5:会议纪要转行动项​

秘籍 6:技术转非技术语言翻译器​

秘籍 7:内容扩写器​

秘籍 8:内容精简器​

秘籍 9:SEO 元描述生成器​

秘籍 10:社交媒体线程创建器​

代码类配方​

配方 11:带严重程度评级的代码审查工具​

配方 12:单元测试生成器​

Test Coverage Summary​

Additional Test Recommendations​

[Endpoint/Method Name]

Overview​

Endpoint​

Authentication​

Request​

Headers​

Path Parameters​

Query Parameters​

Request Body​

Response​

Success Response (200 OK)​

Error Responses​

Example Usage​

cURL​

JavaScript​

Notes​

Query Analysis​

Original Query​

Detected Issues​

Optimization Recommendations​

Optimized Query​

Index Recommendations​

Execution Plan Considerations​

Before/After Comparison​

Regex Pattern​

Description Understood​

Pattern​

Pattern Breakdown​

Flavor Compatibility​

Test Cases​

Code Examples​

Edge Cases to Consider​

Original Error​

Improved Error Messages​

User-Facing Message​

Full Format​

Variations​

Technical Logging​

Refactoring Analysis​

Code Quality Score: [1-10]​

Identified Opportunities​

1. [Refactoring Name] - [Priority: High/Medium/Low]​

SOLID Principles Assessment​

Design Pattern Opportunities​

Recommended Refactoring Order​

Security Audit Report​

Risk Summary​

Vulnerabilities Found​

[VULN-001] [Vulnerability Name]​

Security Best Practices Missing​

Compliance Notes​

Recommended Security Libraries​

Performance Analysis Report​

Complexity Analysis​

Identified Bottlenecks​

[PERF-001] [Issue Name]​

Memory Optimization​

Caching Opportunities​

Async/Parallel Opportunities​

Database Query Optimization​

Benchmarking Recommendations​

Literature Review​

如何使用本秘籍手册

理解变量

写作类秘籍

秘籍 1:执行摘要生成器

秘籍 2:邮件线程摘要器

秘籍 3:语气转换器(多模式)

秘籍 4:要点转散文转换器

秘籍 5:会议纪要转行动项

秘籍 6:技术转非技术语言翻译器

秘籍 7:内容扩写器

秘籍 8:内容精简器

秘籍 9:SEO 元描述生成器

秘籍 10:社交媒体线程创建器

代码类配方

配方 11:带严重程度评级的代码审查工具

配方 12:单元测试生成器

Test Coverage Summary

Additional Test Recommendations

Overview

Endpoint

Authentication

Request

Headers

Path Parameters

Query Parameters

Request Body

Response

Success Response (200 OK)

Error Responses

Example Usage

cURL

JavaScript

Notes

Query Analysis

Original Query

Detected Issues

Optimization Recommendations

Optimized Query

Index Recommendations

Execution Plan Considerations

Before/After Comparison

Regex Pattern

Description Understood

Pattern

Pattern Breakdown

Flavor Compatibility

Test Cases

Code Examples

Edge Cases to Consider

Original Error

Improved Error Messages

User-Facing Message

Full Format

Variations

Technical Logging

Refactoring Analysis

Code Quality Score: [1-10]

Identified Opportunities

1. [Refactoring Name] - [Priority: High/Medium/Low]

SOLID Principles Assessment

Design Pattern Opportunities

Recommended Refactoring Order

Security Audit Report

Risk Summary

Vulnerabilities Found

[VULN-001] [Vulnerability Name]

Security Best Practices Missing

Compliance Notes

Recommended Security Libraries

Performance Analysis Report

Complexity Analysis

Identified Bottlenecks

[PERF-001] [Issue Name]

Memory Optimization

Caching Opportunities

Async/Parallel Opportunities

Database Query Optimization

Benchmarking Recommendations

Literature Review

Overview