Tutorial: Advanced Automation Recipes

Goal: A comprehensive cookbook of copy-paste ready command recipes for power users. Level: Intermediate to Expert Time: Reference guide (use as needed)

This tutorial provides 40 production-ready command recipes organized by category. Each recipe includes complete instructions you can copy directly into Rephlo.

How to Use This Cookbook

Find a recipe that matches your use case
Create a new Command in Rephlo (Dashboard > Commands > New)
Copy the instruction from the recipe into the Instruction field
Configure execution mode as specified (Standalone or Combination)
Optionally attach a Space for context-aware recipes
Save and test with sample input

Understanding Variables

{{input_text}} - The text you have selected on screen
{{space_data_all}} - All documents from your active Space
{{filename}} - Content from a specific file in your Space (e.g., {{style_guide_pdf}})

Writing Recipes

Recipe 1: Executive Summary Generator

Category: Writing Difficulty: Intermediate Provider Recommendation: Claude (excellent at structured summaries) or GPT-5.1

What It Does: Transforms lengthy documents, reports, or meeting transcripts into concise executive summaries with key takeaways and action items.

The Command:

Name: executive-summary
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: A 2000-word quarterly sales report Output: A structured 250-word summary with revenue highlights, team performance, Q2 recommendations, and risk factors

Pro Tip: Attach a Space with your company's executive summary templates for consistent formatting across all reports.

Recipe 2: Email Thread Summarizer

Category: Writing Difficulty: Intermediate Provider Recommendation: GPT-5.1 or Claude (fast and accurate)

What It Does: Condenses long email chains into actionable summaries, identifying decisions made, open questions, and next steps.

The Command:

Name: email-summarizer
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: 15-message email thread about project timeline Output: Structured summary showing 3 decisions, 2 open questions, and 4 action items with owners

Pro Tip: Create a keyboard shortcut (Hotkey) for this command since email summarization is used frequently.

Recipe 3: Tone Shifter (Multi-Mode)

Category: Writing Difficulty: Intermediate Provider Recommendation: Claude (nuanced tone understanding)

What It Does: Transforms text between formal, casual, and technical tones while preserving the core message.

The Command:

Name: tone-shift-formal
Execution Mode: Combination

Instruction:

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_text}}

Provide only the rewritten text with no explanations.

Variant Commands (create separate commands for each):

Casual Tone (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_text}}

Provide only the rewritten text with no explanations.

Technical Tone (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_text}}

Provide only the rewritten text with no explanations.

Usage Example:

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

Pro Tip: Group all tone-shift commands under a "Tone Shift" Command Group for quick access.

Recipe 4: Bullet Points to Prose Converter

Category: Writing Difficulty: Beginner Provider Recommendation: Any provider (straightforward task)

What It Does: Transforms bullet-point notes into flowing, readable paragraphs.

The Command:

Name: bullets-to-prose
Execution Mode: Combination

Instruction:

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_text}}

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

Usage Example:

Input: "- Q3 sales up 15%\n- New product launch successful\n- Hired 5 new reps\n- Expanding to APAC region" Output: "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."

Pro Tip: This pairs well with the Executive Summary Generator for comprehensive report creation.

Recipe 5: Meeting Notes to Action Items

Category: Writing Difficulty: Intermediate Provider Recommendation: GPT-5.1 (fast extraction) or Claude

What It Does: Extracts actionable tasks from meeting notes with owners, deadlines, and priority levels.

The Command:

Name: meeting-action-items
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: Raw meeting notes from a 1-hour project sync Output: Structured table with 8 action items, 3 decisions, and 2 parking lot items

Pro Tip: Attach a Space with your team roster for better owner identification.

Recipe 6: Technical to Non-Technical Translator

Category: Writing Difficulty: Advanced Provider Recommendation: Claude (excellent at analogies and simplification)

What It Does: Translates technical jargon into plain language that non-technical stakeholders can understand.

The Command:

Name: tech-to-plain
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: "The API endpoint is returning 503 errors due to thread pool exhaustion caused by synchronous blocking calls in the async pipeline." Output: "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."

Pro Tip: Save common analogies in a Space for consistent explanations across your team.

Recipe 7: Content Expander

Category: Writing Difficulty: Intermediate Provider Recommendation: Claude or GPT-5.1 (creative expansion)

What It Does: Expands brief notes or outlines into detailed, fleshed-out content.

The Command:

Name: content-expand
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: "Remote work increases productivity. Fewer meetings. Better focus time." Output: A 300-word section explaining productivity benefits with statistics, examples of reduced meeting overhead, and research on deep work principles.

Pro Tip: Combine with a Style Guide Space for brand-consistent expansion.

Recipe 8: Content Condenser

Category: Writing Difficulty: Intermediate Provider Recommendation: Claude (excellent at preserving meaning while reducing length)

What It Does: Reduces lengthy content to its essential points without losing critical information.

The Command:

Name: content-condense
Execution Mode: Combination

Instruction:

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_text}}

Provide only the condensed version.

Usage Example:

Input: 1000-word project update Output: 300-word version with all decisions, metrics, and action items preserved

Pro Tip: Use this before the Executive Summary Generator for maximum compression.

Recipe 9: SEO Meta Description Generator

Category: Writing Difficulty: Beginner Provider Recommendation: GPT-5.1 (fast, SEO-aware)

What It Does: Creates optimized meta descriptions for web pages based on content.

The Command:

Name: seo-meta-description
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: Blog post about remote work productivity tips Output: Three meta descriptions, e.g., "Boost your remote work productivity with 7 proven strategies. Learn how top performers stay focused and achieve more from home. Start today."

Pro Tip: Create a Space with your brand keywords and tone guidelines for consistent SEO voice.

Category: Writing Difficulty: Advanced Provider Recommendation: Claude (creative, engaging content)

What It Does: Transforms long-form content into engaging social media thread format (Twitter/X style).

The Command:

Name: social-thread-creator
Execution Mode: Combination

Instruction:

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_text}}

Output the complete thread ready to post.

Usage Example:

Input: 800-word article about productivity systems Output: 8-tweet thread with hook, key insights, and engagement closer

Pro Tip: Test threads on a note-taking app first to verify character counts.

Code Recipes

Recipe 11: Code Reviewer with Severity Ratings

Category: Code Difficulty: Advanced Provider Recommendation: Claude (excellent code understanding) or GPT-5.1

What It Does: Performs a comprehensive code review with categorized issues and severity ratings.

The Command:

Name: code-review
Execution Mode: Combination

Instruction:

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_text}}

Usage Example:

Input: 50-line function with nested loops and no error handling Output: Detailed review with 2 critical issues (missing null checks), 3 high issues (performance), and refactored code sample

Pro Tip: Attach a Space with your team's coding standards for project-specific reviews.

Recipe 12: Unit Test Generator

Category: Code Difficulty: Advanced Provider Recommendation: Claude or GPT-5.1 (strong test pattern knowledge)

What It Does: Generates comprehensive unit tests for the given code with edge cases.

The Command:

Name: generate-unit-tests
Execution Mode: Combination

Instruction:

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_text}}

**Usage Example**:
> Input: A `CalculateDiscount(price, customerType)` function
> Output: 15 unit tests covering valid discounts, zero price, negative price, unknown customer types, and null inputs

**Pro Tip**: Create language-specific variants (e.g., `generate-tests-csharp`) for optimized output.

---

### Recipe 13: API Documentation Writer
**Category**: Code
**Difficulty**: Intermediate
**Provider Recommendation**: GPT-5.1 or Claude

**What It Does**: Generates comprehensive API documentation from code or endpoint definitions.

**The Command**:
- **Name**: `api-documentation`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: A C# controller action for user registration
> Output: Complete API documentation with request/response schemas, error codes, and example calls

**Pro Tip**: Attach your API style guide Space for consistent documentation across endpoints.

---

### Recipe 14: SQL Query Optimizer
**Category**: Code
**Difficulty**: Advanced
**Provider Recommendation**: Claude (strong analytical capabilities)

**What It Does**: Analyzes SQL queries and suggests performance optimizations.

**The Command**:
- **Name**: `sql-optimizer`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: Complex JOIN query with WHERE clauses on non-indexed columns
> Output: Optimized query with 3 index recommendations and estimated 70% performance improvement

**Pro Tip**: Include your database schema in a Space for table-aware recommendations.

---

### Recipe 15: Regex Pattern Generator
**Category**: Code
**Difficulty**: Intermediate
**Provider Recommendation**: Any provider (pattern matching is well-understood)

**What It Does**: Generates regex patterns from natural language descriptions with test cases.

**The Command**:
- **Name**: `regex-generator`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: "Match email addresses but not those from gmail.com"
> Output: Complete regex with negative lookahead, explanation, test cases, and code samples in 3 languages

**Pro Tip**: Always test generated patterns with real data before production use.

---

### Recipe 16: Error Message Improver
**Category**: Code
**Difficulty**: Beginner
**Provider Recommendation**: Any provider

**What It Does**: Rewrites technical error messages to be user-friendly and actionable.

**The Command**:
- **Name**: `error-message-improver`
- **Execution Mode**: Combination

**Instruction**:

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

**Usage Example**:
> Input: "NullReferenceException: Object reference not set to an instance of an object at UserService.GetProfile()"
> Output: "We couldn't load your profile. Please try refreshing the page. If the problem continues, contact support with code NRE-USR-001."

**Pro Tip**: Collect improved messages in a Space to build a consistent error message library.

---

### Recipe 17: Code Comment Generator
**Category**: Code
**Difficulty**: Beginner
**Provider Recommendation**: Any provider

**What It Does**: Adds comprehensive comments to uncommented code.

**The Command**:
- **Name**: `add-code-comments`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: Uncommented C# service class
> Output: Same class with XML documentation on all public methods and inline comments on complex algorithms

**Pro Tip**: Use this before code reviews to ensure documentation standards are met.

---

### Recipe 18: Refactoring Suggester
**Category**: Code
**Difficulty**: Advanced
**Provider Recommendation**: Claude (excellent pattern recognition)

**What It Does**: Analyzes code and suggests specific refactoring opportunities with before/after examples.

**The Command**:
- **Name**: `refactoring-suggestions`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: 200-line method with multiple responsibilities
> Output: 5 refactoring suggestions including Extract Method, Introduce Parameter Object, and Replace Conditional with Strategy

**Pro Tip**: Attach your architecture decision records (ADRs) in a Space for context-aware suggestions.

---

### Recipe 19: Security Vulnerability Scanner
**Category**: Code
**Difficulty**: Expert
**Provider Recommendation**: Claude (thorough analysis)

**What It Does**: Scans code for common security vulnerabilities and provides remediation guidance.

**The Command**:
- **Name**: `security-scan`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: API endpoint handling user input
> Output: 3 vulnerabilities found (SQL injection, missing input validation, hardcoded API key) with specific fixes

**Pro Tip**: Run this on all code before merging to production. Create a mandatory review step.

---

### Recipe 20: Performance Optimization Advisor
**Category**: Code
**Difficulty**: Expert
**Provider Recommendation**: Claude (deep algorithmic analysis)

**What It Does**: Identifies performance bottlenecks and suggests optimizations with complexity analysis.

**The Command**:
- **Name**: `performance-advisor`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: Data processing function with nested loops
> Output: O(n^2) to O(n log n) optimization using sorting, plus caching recommendation for repeated lookups

**Pro Tip**: Combine with actual profiler data in a Space for targeted optimizations.

---

## Research Recipes

### Recipe 21: Literature Review Synthesizer
**Category**: Research
**Difficulty**: Advanced
**Provider Recommendation**: Claude (excellent at synthesis and academic tone)

**What It Does**: Synthesizes multiple research sources into a cohesive literature review section.

**The Command**:
- **Name**: `literature-synthesizer`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: Notes from 10 research papers on remote work productivity
> Output: 800-word literature review with thematic analysis, comparison table, and identified research gaps

**Pro Tip**: Attach your bibliography in a Space for consistent citation formatting.

---

### Recipe 22: Competitive Analysis Framework
**Category**: Research
**Difficulty**: Intermediate
**Provider Recommendation**: GPT-5.1 or Claude

**What It Does**: Structures competitive intelligence into a standardized analysis framework.

**The Command**:
- **Name**: `competitive-analysis`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: Notes from competitor websites, reviews, and pricing pages
> Output: Structured analysis with feature matrix, positioning insights, and strategic recommendations

**Pro Tip**: Keep competitor intelligence updated in a Space for ongoing analysis.

---

### Recipe 23: SWOT Analysis Generator
**Category**: Research
**Difficulty**: Intermediate
**Provider Recommendation**: Any provider

**What It Does**: Creates a comprehensive SWOT analysis from unstructured business information.

**The Command**:
- **Name**: `swot-analysis`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: Company annual report excerpts and market research notes
> Output: Complete SWOT with strategic implications and priority actions

**Pro Tip**: Run quarterly with updated information to track strategic changes over time.

---

### Recipe 24: Research Question Refiner
**Category**: Research
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (excellent at academic framing)

**What It Does**: Transforms vague research ideas into well-formed, researchable questions.

**The Command**:
- **Name**: `research-question-refiner`
- **Execution Mode**: Combination

**Instruction**:

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

**Usage Example**:
> Input: "I want to study how social media affects teenagers"
> Output: Refined RQ: "To what extent does daily Instagram usage (>2 hours) correlate with self-reported anxiety levels among urban teenagers aged 13-17?"

**Pro Tip**: Use this at the start of any research project to ensure strong foundations.

---

### Recipe 25: Citation Formatter
**Category**: Research
**Difficulty**: Beginner
**Provider Recommendation**: Any provider

**What It Does**: Converts raw citation information into properly formatted citations in multiple styles.

**The Command**:
- **Name**: `format-citation`
- **Execution Mode**: Combination

**Instruction**:

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_text}}

**Usage Example**:
> Input: "John Smith and Jane Doe wrote an article called The Future of AI in the Journal of Technology 2023 volume 15 pages 100-120"
> Output: Properly formatted citations in 6 academic styles

**Pro Tip**: Create a Space with your institution's preferred style guide for priority formatting.

---

## Business Recipes

### Recipe 26: Proposal Outline Generator
**Category**: Business
**Difficulty**: Intermediate
**Provider Recommendation**: GPT-5.1 or Claude

**What It Does**: Creates comprehensive proposal outlines from brief project descriptions.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "We need to migrate our legacy system to cloud, about 6 months timeline, mid-size retail company"
> Output: Complete proposal outline tailored for cloud migration with retail-specific considerations

**Pro Tip**: Attach past successful proposals in a Space for consistent structure and language.

---

### Recipe 27: Risk Assessment Matrix Creator
**Category**: Business
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (thorough analysis)

**What It Does**: Identifies project risks and creates a structured risk assessment matrix.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: Software development project brief with timeline and team info
> Output: 15 identified risks with full analysis, mitigation strategies, and monitoring plan

**Pro Tip**: Review and update the risk register weekly during project execution.

---

### Recipe 28: Status Report Formatter
**Category**: Business
**Difficulty**: Beginner
**Provider Recommendation**: Any provider (formatting task)

**What It Does**: Transforms raw status notes into a polished, executive-ready status report.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: Bullet points from a project manager's notes
> Output: Formatted one-page status report ready for stakeholder distribution

**Pro Tip**: Create a recurring calendar reminder to run this command every Friday with your week's notes.

---

### Recipe 29: Stakeholder Update Email
**Category**: Business
**Difficulty**: Beginner
**Provider Recommendation**: Any provider

**What It Does**: Drafts professional stakeholder update emails from brief notes.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "milestone 2 done, team working on database migration, slight delay expected, need approval for additional budget"
> Output: Professional email with subject lines, TL;DR, and appropriate escalation of budget request

**Pro Tip**: Attach stakeholder preferences in a Space (e.g., "CEO prefers brief updates, CTO wants technical detail").

---

### Recipe 30: Decision Matrix Builder
**Category**: Business
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (analytical)

**What It Does**: Creates weighted decision matrices to support objective decision-making.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "Choosing between AWS, Azure, and GCP for our cloud platform. Care about cost, performance, team expertise, and vendor lock-in."
> Output: Complete weighted matrix with scores, sensitivity analysis, and recommendation

**Pro Tip**: Involve stakeholders in weighting criteria before running the analysis for buy-in.

---

## Creative Recipes

### Recipe 31: Story Plot Outliner
**Category**: Creative
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (creative and structured)

**What It Does**: Develops story concepts into structured plot outlines with character arcs.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "A retired detective is pulled back into one last case when her estranged daughter goes missing"
> Output: Complete three-act outline with character arcs, theme, and 12 key scenes

**Pro Tip**: Iterate on the outline before writing, then use it in a Space for consistent reference while drafting.

---

### Recipe 32: Character Profile Builder
**Category**: Creative
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (nuanced character development)

**What It Does**: Creates comprehensive character profiles from basic descriptions.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "Middle-aged librarian who secretly writes romance novels, main character of a cozy mystery"
> Output: Complete profile with psychology, background, voice patterns, and story function

**Pro Tip**: Create profiles for all main characters and store in a Space for consistency.

---

### Recipe 33: Dialogue Improver
**Category**: Creative
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (natural dialogue)

**What It Does**: Enhances dialogue to be more natural, character-specific, and impactful.

**The Command**:
- **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

**Usage Example**:
> Input: Two characters discussing a betrayal in flat, expository dialogue
> Output: Same conversation with subtext, emotional tension, and distinct voices

**Pro Tip**: Include character profiles in a Space for voice-consistent improvements.

---

### Recipe 34: Scene Description Enhancer
**Category**: Creative
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (vivid imagery)

**What It Does**: Transforms basic scene descriptions into immersive, sensory-rich prose.

**The Command**:
- **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

**Usage Example**:
> Input: "It was a rainy night in the city. The detective walked down the street."
> Output: Immersive noir description with neon reflections, distant sirens, and the detective's wet footsteps echoing.

**Pro Tip**: Specify your genre and POV character for tailored enhancements.

---

### Recipe 35: Writing Style Mimicker
**Category**: Creative
**Difficulty**: Advanced
**Provider Recommendation**: Claude (excellent at style analysis)

**What It Does**: Rewrites content in the style of a specified author or genre.

**The Command**:
- **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:

**Usage Example**:
> Input: "Rewrite this product description in the style of Douglas Adams: 'Our software helps you manage tasks efficiently.'"
> Output: A whimsical, absurdist description involving the improbability of actually completing tasks in the universe.

**Pro Tip**: Use this for creative exercises or to find your own writing voice by contrasting styles.

---

## Productivity Recipes

### Recipe 36: Daily Standup Formatter
**Category**: Productivity
**Difficulty**: Beginner
**Provider Recommendation**: Any provider (formatting task)

**What It Does**: Formats rough notes into a clear, structured daily standup update.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "worked on api endpoint, got stuck on auth, today finishing api and starting frontend, need credentials from devops"
> Output: Formatted standup with clear sections and a Slack-ready quick version

**Pro Tip**: Create a hotkey for this command and run it every morning before standup.

---

### Recipe 37: Weekly Review Template Filler
**Category**: Productivity
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (reflective analysis)

**What It Does**: Transforms week's notes into a structured weekly review with insights.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: Jumbled notes from the week including tasks, frustrations, and achievements
> Output: Structured reflection with insights, learnings, and next week's priorities

**Pro Tip**: Schedule this for Friday afternoons to close out the work week intentionally.

---

### Recipe 38: Learning Notes Organizer
**Category**: Productivity
**Difficulty**: Intermediate
**Provider Recommendation**: Claude (educational structuring)

**What It Does**: Organizes raw learning notes into structured, reviewable study materials.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: Messy notes from a machine learning lecture
> Output: Organized study guide with concepts, practice questions, and flashcard-ready content

**Pro Tip**: Export the spaced repetition cards to your flashcard app for long-term retention.

---

### Recipe 39: Quick Reference Card Creator
**Category**: Productivity
**Difficulty**: Intermediate
**Provider Recommendation**: Any provider

**What It Does**: Condenses information into a compact quick reference card format.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: Documentation for a new programming language or tool
> Output: One-page reference card with commands, shortcuts, and common patterns

**Pro Tip**: Print these cards or save as PDF for quick access during work.

---

### Recipe 40: Checklist Generator
**Category**: Productivity
**Difficulty**: Beginner
**Provider Recommendation**: Any provider

**What It Does**: Creates comprehensive checklists from process descriptions or requirements.

**The Command**:
- **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_text}}

**Usage Example**:
> Input: "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"
> Output: Detailed deployment checklist with phases, verification steps, and rollback considerations

**Pro Tip**: Save frequently used checklists as reusable templates in a Space.

---

## Appendix: Recipe Quick Reference

### By Difficulty
| Beginner | Intermediate | Advanced | Expert |
|----------|--------------|----------|--------|
| Bullets to Prose | Executive Summary | Code Reviewer | Security Scanner |
| SEO Meta | Tone Shifter | Unit Test Generator | Performance Advisor |
| Error Message | Email Summarizer | Literature Review | |
| Standup Format | SWOT Analysis | Refactoring Suggester | |
| Checklist Generator | Decision Matrix | Style Mimicker | |

### By Provider Recommendation
| Claude Best | GPT-5.1 Best | Any Provider |
|-------------|-------------------|--------------|
| Tone Shifter | SEO Meta Description | Bullets to Prose |
| Tech to Plain | API Documentation | Error Message |
| Code Reviewer | Proposal Outline | Citation Formatter |
| Literature Review | Email Summarizer | Standup Format |
| Character Profile | Status Report | Checklist Generator |

### Top 5 Most Used (Recommended Starting Set)
1. **Executive Summary Generator** - For any long document
2. **Tone Shifter** - Daily communication needs
3. **Code Reviewer** - Development workflow
4. **Meeting Notes to Action Items** - After every meeting
5. **Standup Format** - Daily developer routine

---

## Next Steps

1. **Start Small**: Pick 3-5 recipes that match your daily work
2. **Customize**: Modify instructions to match your specific needs
3. **Organize**: Use Command Groups to categorize your recipes
4. **Iterate**: Refine prompts based on output quality
5. **Share**: Export successful commands for team use

**Related Tutorials**:
- [Managing Commands](../03-features/01-managing-commands.md)
- [Managing Spaces](../03-features/02-managing-spaces.md)
- [Command Groups](../03-features/07-command-groups.md)

How to Use This Cookbook​

Understanding Variables​

Writing Recipes​

Recipe 1: Executive Summary Generator​

Recipe 2: Email Thread Summarizer​

Recipe 3: Tone Shifter (Multi-Mode)​

Recipe 4: Bullet Points to Prose Converter​

Recipe 5: Meeting Notes to Action Items​

Recipe 6: Technical to Non-Technical Translator​

Recipe 7: Content Expander​

Recipe 8: Content Condenser​

Recipe 9: SEO Meta Description Generator​

Recipe 10: Social Media Thread Creator​

Code Recipes​

Recipe 11: Code Reviewer with Severity Ratings​

Recipe 12: Unit Test Generator​

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​

How to Use This Cookbook

Understanding Variables

Writing Recipes

Recipe 1: Executive Summary Generator

Recipe 2: Email Thread Summarizer

Recipe 3: Tone Shifter (Multi-Mode)

Recipe 4: Bullet Points to Prose Converter

Recipe 5: Meeting Notes to Action Items

Recipe 6: Technical to Non-Technical Translator

Recipe 7: Content Expander

Recipe 8: Content Condenser

Recipe 9: SEO Meta Description Generator

Recipe 10: Social Media Thread Creator

Code Recipes

Recipe 11: Code Reviewer with Severity Ratings

Recipe 12: Unit Test Generator

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