提示优化器
- 作者仓库星标 0
- 作者更新于 2026年8月24日 07:33
- 作者仓库 claude-code-skills
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @daymade · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
识别弱点: 过于宽泛 - “添加用户身份验证”→ 缺少密码要求、会话管理 缺少触发器 - “发送通知”→ 缺少通知触发的时间/原因 不明确的操作 - “使其用户友好”→ 没有可衡量的可用性标准 无限制 - “处理付款”→ 缺少安全性、合规性要求
将需求转换为 EARS 模式。完整的语法规则请参见`references/ears_syntax.md`。五个核心模式: 无处不在:`The system shall <action>` 事件驱动:`When <trigger>, the system shall <action>` 状态驱动:`While <state>, the system shall <action>`
将要求与已建立的框架相匹配。完整目录请参见`references/domain_theories.md`。常见领域映射:生产力 → GTD、番茄工作法、艾森豪威尔矩阵 行为变化 → BJ Fogg 模型 (B=MAT)、原子习惯 用户体验设计 → 希克定律、菲茨定律、格式塔原理
使用真实数据生成具体示例: 用户场景:“当用户在移动设备上登录时...” 数据示例:“产品:‘笔记本电脑’,价格:999 美元,库存:15” 工作流程示例:“任务:编写报告 → 子任务:研究 (2 小时)、草稿 (3 小时)、编辑 (1 小时)” 示例必须现实、具体、多样(成功/错误/边缘情况)且可测试。
使用标准框架的结构: 质量标准: 角色特异性:“专门从事时间管理应用程序的产品设计师”>“设计师” 理论基础:明确的参考框架 可操作的工作流程:清晰的输入/输出和决策点
以结构化格式输出:
# Prompt Optimizer
## Overview
Optimize vague prompts into precise, actionable specifications using EARS (Easy Approach to Requirements Syntax) - a Rolls-Royce methodology for transforming natural language into structured, testable requirements.
**Methodology inspired by:** This skill's approach to combining EARS with domain theory grounding was inspired by [阿星AI工作室 (A-Xing AI Studio)](https://mp.weixin.qq.com/s/yUVX-9FovSq7ZGChkHpuXQ), which demonstrated practical EARS application for prompt enhancement.
**Four-layer enhancement process:**
1. **EARS syntax transformation** - Convert descriptive language to normative specifications
2. **Domain theory grounding** - Apply relevant industry frameworks (GTD, BJ Fogg, Gestalt, etc.)
3. **Example extraction** - Surface concrete use cases with real data
4. **Structured prompt generation** - Format using Role/Skills/Workflows/Examples/Formats framework
## When to Use
Apply when:
- User provides vague feature requests ("build a dashboard", "create a reminder app")
- Requirements lack specific conditions, triggers, or measurable outcomes
- Natural language descriptions need conversion to testable specifications
- User explicitly requests prompt optimization or requirement refinement
## Six-Step Optimization Workflow
### Step 1: Analyze Original Requirement
Identify weaknesses:
- **Overly broad** - "Add user authentication" → Missing password requirements, session management
- **Missing triggers** - "Send notifications" → Missing when/why notifications trigger
- **Ambiguous actions** - "Make it user-friendly" → No measurable usability criteria
- **No constraints** - "Process payments" → Missing security, compliance requirements
### Step 2: Apply EARS Transformation
Convert requirements to EARS patterns. See `references/ears_syntax.md` for complete syntax rules.
**Five core patterns:**
1. **Ubiquitous**: `The system shall <action>`
2. **Event-driven**: `When <trigger>, the system shall <action>`
3. **State-driven**: `While <state>, the system shall <action>`
4. **Conditional**: `If <condition>, the system shall <action>`
5. **Unwanted behavior**: `If <condition>, the system shall prevent <unwanted action>`
**Quick example:**
```
Before: "Create a reminder app with task management"
After (EARS):
1. When user creates a task, the system shall guide decomposition into executable sub-tasks
2. When task deadline is within 30 minutes AND user has not started, the system shall send notification with sound alert
3. When user completes a sub-task, the system shall update progress and provide positive feedback
```
**Transformation checklist:**
- [ ] Identify implicit conditions and make explicit
- [ ] Specify triggering events or states
- [ ] Use precise action verbs (shall, must, should)
- [ ] Add measurable criteria ("within 30 minutes", "at least 8 characters")
- [ ] Break compound requirements into atomic statements
- [ ] Remove ambiguous language ("user-friendly", "fast")
### Step 3: Identify Domain Theories
Match requirements to established frameworks. See `references/domain_theories.md` for full catalog.
**Common domain mappings:**
- **Productivity** → GTD, Pomodoro, Eisenhower Matrix
- **Behavior Change** → BJ Fogg Model (B=MAT), Atomic Habits
- **UX Design** → Hick's Law, Fitts's Law, Gestalt Principles
- **Security** → Zero Trust, Defense in Depth, Privacy by Design
**Selection process:**
1. Identify primary domain from requirement keywords
2. Match to 2-4 complementary theories
3. Apply theory principles to specific features
4. Cite theories in enhanced prompt for credibility
### Step 4: Extract Concrete Examples
Generate specific examples with real data:
- User scenarios: "When user logs in on mobile device..."
- Data examples: "Product: 'Laptop', Price: $999, Stock: 15"
- Workflow examples: "Task: Write report → Sub-tasks: Research (2h), Draft (3h), Edit (1h)"
Examples must be **realistic**, **specific**, **varied** (success/error/edge cases), and **testable**.
### Step 5: Generate Enhanced Prompt
Structure using the standard framework:
```markdown
# Role
[Specific expert role with domain expertise]
## Skills
- [Core capability 1]
- [Core capability 2]
[List 5-8 skills aligned with domain theories]
## Workflows
1. [Phase 1] - [Key activities]
2. [Phase 2] - [Key activities]
[Complete step-by-step process]
## Examples
[Concrete examples with real data, not placeholders]
## Formats
[Precise output specifications:
- File types, structure requirements
- Design/styling expectations
- Technical constraints
- Deliverable checklist]
```
**Quality criteria:**
- **Role specificity**: "Product designer specializing in time management apps" > "Designer"
- **Theory grounding**: Reference frameworks explicitly
- **Actionable workflows**: Clear inputs/outputs and decision points
- **Concrete examples**: Real data, not "Example 1", "Example 2"
- **Measurable formats**: Specific requirements, not "good design"
### Step 6: Present Optimization Results
Output in structured format:
```markdown
## Original Requirement
[User's vague requirement]
**Identified Issues:**
- [Issue 1: e.g., "Lacks specific trigger conditions"]
- [Issue 2: e.g., "No measurable success criteria"]
## EARS Transformation
[Numbered list of EARS-formatted requirements]
## Domain & Theories
**Primary Domain:** [e.g., Authentication Security]
**Applicable Theories:**
- **[Theory 1]** - [Brief relevance]
- **[Theory 2]** - [Brief relevance]
## Enhanced Prompt
[Complete Role/Skills/Workflows/Examples/Formats prompt]
---
**How to use:**
[Brief guidance on applying the prompt]
```
## Advanced Techniques
For complex scenarios, see `references/advanced_techniques.md`:
- **Multi-stakeholder requirements** - EARS statements for each user type
- **Non-functional requirements** - Performance, security, scalability with quantified thresholds
- **Complex conditional logic** - Nested conditions with boolean operators
## Quick Reference
**Do's:**
✅ Break down compound requirements (one EARS statement per requirement)
✅ Specify measurable criteria (numbers, timeframes, percentages)
✅ Include error/edge cases
✅ Ground in established theories
✅ Use concrete examples with real data
**Don'ts:**
❌ Avoid vague language ("fast", "user-friendly")
❌ Don't assume implicit knowledge
❌ Don't mix multiple actions in one statement
❌ Don't use placeholders in examples
## Resources
Load these reference files as needed:
- **`references/ears_syntax.md`** - Complete EARS syntax rules, all 5 patterns, transformation guidelines, benefits
- **`references/domain_theories.md`** - 40+ theories mapped to 10 domains (productivity, UX, gamification, learning, e-commerce, security, etc.)
- **`references/examples.md`** - Four complete transformation examples (procrastination app, e-commerce product page, learning dashboard, password reset security) with before/after comparisons and reusable template
- **`references/advanced_techniques.md`** - Multi-stakeholder requirements, non-functional specs, complex conditional logic patterns
**When to load references:**
- EARS syntax clarification needed → `ears_syntax.md`
- Domain theory selection requires extensive options → `domain_theories.md`
- User requests multiple optimization examples → `examples.md`
- Complex requirements with multiple stakeholders or non-functional specs → `advanced_techniques.md`
按说明文件中的顺序排列。
概述
何时使用
步骤一:分析原始需求
第 2 步:应用 EARS 转换
第 3 步:识别领域理论
文件/命令 -> references/ears_syntax.md · The system shall <action> · When <trigger>, the system shall <action> · While <state>, the system shall <action> · If <condition>, the system shall <action> · If <condition>, the system shall prevent <unwanted action> · references/domain_theories.md · references/advanced_techniques.md
内容校验值 -> 49f98323a4f1
当前原文的自动摘译,尚未人工审校。
概述
使用 EARS(需求语法简易方法)将模糊提示优化为精确、可操作的规范,EARS 是一种将自然语言转换为结构化、可测试需求的劳斯莱斯方法。方法论灵感来源:该技能将 EARS 与领域理论基础相结合的方法受到阿星 AI 工作室 (A-Xing AI Studio) 的启发,该工作室展示了 EARS 的实际应用,以实现快速增强。
何时使用
适用于以下情况: 用户提供模糊的功能请求(“构建仪表板”、“创建提醒应用程序”) 需求缺乏特定条件、触发器或可衡量的结果 自然语言描述需要转换为可测试的规范 用户明确请求及时优化或需求细化