@ckelsoe/prompt-architect 3.0.0 → 3.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +1 -1
- package/.claude-plugin/plugin.json +1 -1
- package/CHANGELOG.md +264 -264
- package/LICENSE +21 -21
- package/README.md +1064 -1184
- package/adapters/README.md +75 -267
- package/adapters/for-windsurf.md +136 -136
- package/adapters/system-prompt.md +243 -243
- package/package.json +139 -135
- package/scripts/build-skill.js +64 -0
- package/scripts/install.js +35 -56
- package/scripts/test.js +205 -213
- package/scripts/validate-skill.js +350 -350
- package/skills/prompt-architect/SKILL.md +331 -331
- package/skills/prompt-architect/assets/templates/ape_template.txt +5 -5
- package/skills/prompt-architect/assets/templates/bab_template.txt +15 -15
- package/skills/prompt-architect/assets/templates/broke_template.txt +15 -15
- package/skills/prompt-architect/assets/templates/cai-critique-revise_template.txt +18 -18
- package/skills/prompt-architect/assets/templates/care_template.txt +16 -16
- package/skills/prompt-architect/assets/templates/chain-of-density_template.txt +46 -46
- package/skills/prompt-architect/assets/templates/chain-of-thought_template.txt +49 -49
- package/skills/prompt-architect/assets/templates/co-star_template.txt +17 -17
- package/skills/prompt-architect/assets/templates/crispe_template.txt +14 -14
- package/skills/prompt-architect/assets/templates/ctf_template.txt +15 -15
- package/skills/prompt-architect/assets/templates/devils-advocate_template.txt +25 -25
- package/skills/prompt-architect/assets/templates/hybrid_template.txt +101 -101
- package/skills/prompt-architect/assets/templates/least-to-most_template.txt +16 -16
- package/skills/prompt-architect/assets/templates/plan-and-solve_template.txt +7 -7
- package/skills/prompt-architect/assets/templates/pre-mortem_template.txt +27 -27
- package/skills/prompt-architect/assets/templates/race_template.txt +19 -19
- package/skills/prompt-architect/assets/templates/rcot_template.txt +31 -31
- package/skills/prompt-architect/assets/templates/react_template.txt +27 -27
- package/skills/prompt-architect/assets/templates/reverse-role_template.txt +11 -11
- package/skills/prompt-architect/assets/templates/rise-ie_template.txt +23 -23
- package/skills/prompt-architect/assets/templates/rise-ix_template.txt +28 -28
- package/skills/prompt-architect/assets/templates/risen_template.txt +21 -21
- package/skills/prompt-architect/assets/templates/rpef_template.txt +26 -26
- package/skills/prompt-architect/assets/templates/rtf_template.txt +13 -13
- package/skills/prompt-architect/assets/templates/self-refine_template.txt +16 -16
- package/skills/prompt-architect/assets/templates/skeleton-of-thought_template.txt +15 -15
- package/skills/prompt-architect/assets/templates/step-back_template.txt +10 -10
- package/skills/prompt-architect/assets/templates/tidd-ec_template.txt +45 -45
- package/skills/prompt-architect/assets/templates/tree-of-thought_template.txt +30 -30
- package/skills/prompt-architect/references/frameworks/ape.md +200 -200
- package/skills/prompt-architect/references/frameworks/bab.md +242 -242
- package/skills/prompt-architect/references/frameworks/broke.md +242 -242
- package/skills/prompt-architect/references/frameworks/cai-critique-revise.md +230 -230
- package/skills/prompt-architect/references/frameworks/care.md +235 -235
- package/skills/prompt-architect/references/frameworks/chain-of-density.md +479 -479
- package/skills/prompt-architect/references/frameworks/chain-of-thought.md +424 -424
- package/skills/prompt-architect/references/frameworks/co-star.md +256 -256
- package/skills/prompt-architect/references/frameworks/crispe.md +253 -253
- package/skills/prompt-architect/references/frameworks/ctf.md +207 -207
- package/skills/prompt-architect/references/frameworks/devils-advocate.md +206 -206
- package/skills/prompt-architect/references/frameworks/least-to-most.md +226 -226
- package/skills/prompt-architect/references/frameworks/plan-and-solve.md +210 -210
- package/skills/prompt-architect/references/frameworks/pre-mortem.md +197 -197
- package/skills/prompt-architect/references/frameworks/race.md +243 -243
- package/skills/prompt-architect/references/frameworks/rcot.md +203 -203
- package/skills/prompt-architect/references/frameworks/react.md +304 -304
- package/skills/prompt-architect/references/frameworks/reverse-role.md +189 -189
- package/skills/prompt-architect/references/frameworks/rise.md +555 -555
- package/skills/prompt-architect/references/frameworks/risen.md +297 -297
- package/skills/prompt-architect/references/frameworks/rpef.md +195 -195
- package/skills/prompt-architect/references/frameworks/rtf.md +358 -358
- package/skills/prompt-architect/references/frameworks/self-refine.md +205 -205
- package/skills/prompt-architect/references/frameworks/skeleton-of-thought.md +186 -186
- package/skills/prompt-architect/references/frameworks/step-back.md +206 -206
- package/skills/prompt-architect/references/frameworks/tidd-ec.md +470 -470
- package/skills/prompt-architect/references/frameworks/tree-of-thought.md +260 -260
- package/skills/prompt-architect/scripts/framework_analyzer.py +807 -807
- package/skills/prompt-architect/scripts/prompt_evaluator.py +336 -336
- package/adapters/for-cursor.mdc +0 -138
- package/adapters/for-gemini-cli.md +0 -70
- package/adapters/for-github-copilot.md +0 -141
- package/adapters/for-openai-codex-cli.md +0 -158
|
@@ -1,555 +1,555 @@
|
|
|
1
|
-
# RISE Framework - Dual Variant Support
|
|
2
|
-
|
|
3
|
-
## Overview
|
|
4
|
-
|
|
5
|
-
RISE is a streamlined 4-component framework that exists in **two legitimate variants**, each serving different use cases. Both versions are well-documented in authoritative sources and provide effective prompt structuring.
|
|
6
|
-
|
|
7
|
-
**Important**: This skill supports BOTH variants. Selection guidance is provided below to help choose the right version for your task.
|
|
8
|
-
|
|
9
|
-
---
|
|
10
|
-
|
|
11
|
-
## The Two RISE Variants
|
|
12
|
-
|
|
13
|
-
### RISE-IE: Input-Expectation (Data-Focused)
|
|
14
|
-
**Components**: Role, **Input**, Steps, **Expectation**
|
|
15
|
-
|
|
16
|
-
**Best for**: Data analysis, transformations, processing tasks
|
|
17
|
-
|
|
18
|
-
**Sources**: Fabio Vivas, Juuzt.ai
|
|
19
|
-
|
|
20
|
-
### RISE-IX: Instructions-Examples (Instruction-Focused)
|
|
21
|
-
**Components**: Role, **Instructions**, Steps, **Examples**
|
|
22
|
-
|
|
23
|
-
**Best for**: Content creation, learning tasks, example-based work
|
|
24
|
-
|
|
25
|
-
**Sources**: AiPromptsX, The Prompt Warrior, Thoughts Brewing
|
|
26
|
-
|
|
27
|
-
---
|
|
28
|
-
|
|
29
|
-
## RISE-IE (Input-Expectation Variant)
|
|
30
|
-
|
|
31
|
-
### When to Use RISE-IE
|
|
32
|
-
|
|
33
|
-
**Perfect for:**
|
|
34
|
-
- ✅ Data analysis and transformation tasks
|
|
35
|
-
- ✅ Input → output processing workflows
|
|
36
|
-
- ✅ Working with specific data formats (CSV, JSON, logs)
|
|
37
|
-
- ✅ Tasks where input characteristics are well-defined
|
|
38
|
-
- ✅ Analytical and technical tasks
|
|
39
|
-
- ✅ Report generation from structured data
|
|
40
|
-
|
|
41
|
-
**Use RISE-IE when you have**:
|
|
42
|
-
- Well-defined input data or content
|
|
43
|
-
- Clear transformation requirements
|
|
44
|
-
- Specific output format needs
|
|
45
|
-
- Analytical processing goals
|
|
46
|
-
|
|
47
|
-
### RISE-IE Components
|
|
48
|
-
|
|
49
|
-
#### R - Role
|
|
50
|
-
**Purpose:** Define the perspective or expertise needed for the task.
|
|
51
|
-
|
|
52
|
-
**Questions to Ask:**
|
|
53
|
-
- What expertise is required?
|
|
54
|
-
- What viewpoint should be taken?
|
|
55
|
-
- What knowledge level is needed?
|
|
56
|
-
|
|
57
|
-
**Examples:**
|
|
58
|
-
- "Act as a data analyst..."
|
|
59
|
-
- "You are a content editor..."
|
|
60
|
-
- "Take the perspective of a UX researcher..."
|
|
61
|
-
|
|
62
|
-
#### I - Input
|
|
63
|
-
**Purpose:** Specify what's being provided and its characteristics.
|
|
64
|
-
|
|
65
|
-
**Questions to Ask:**
|
|
66
|
-
- What data/content is being provided?
|
|
67
|
-
- What format is it in?
|
|
68
|
-
- Are there any input constraints?
|
|
69
|
-
- What should Claude expect to receive?
|
|
70
|
-
|
|
71
|
-
**Examples:**
|
|
72
|
-
- "You'll receive a CSV file with sales data..."
|
|
73
|
-
- "Input is a collection of user feedback emails..."
|
|
74
|
-
- "You have access to JSON API responses..."
|
|
75
|
-
|
|
76
|
-
#### S - Steps
|
|
77
|
-
**Purpose:** Define how to process the input.
|
|
78
|
-
|
|
79
|
-
**Questions to Ask:**
|
|
80
|
-
- How should the input be processed?
|
|
81
|
-
- What transformations are needed?
|
|
82
|
-
- What's the processing sequence?
|
|
83
|
-
- What analysis should be performed?
|
|
84
|
-
|
|
85
|
-
**Examples:**
|
|
86
|
-
- "1. Parse CSV, 2. Calculate metrics, 3. Identify trends..."
|
|
87
|
-
- "Extract key themes, categorize by sentiment, count occurrences..."
|
|
88
|
-
|
|
89
|
-
#### E - Expectation
|
|
90
|
-
**Purpose:** Define what the output should look like.
|
|
91
|
-
|
|
92
|
-
**Questions to Ask:**
|
|
93
|
-
- What format should output take?
|
|
94
|
-
- What should be included?
|
|
95
|
-
- How detailed should it be?
|
|
96
|
-
- What's the deliverable?
|
|
97
|
-
|
|
98
|
-
**Examples:**
|
|
99
|
-
- "Provide a summary table with top 10 items..."
|
|
100
|
-
- "Generate a JSON object with categorized results..."
|
|
101
|
-
- "Create a report with charts and key findings..."
|
|
102
|
-
|
|
103
|
-
### RISE-IE Template
|
|
104
|
-
|
|
105
|
-
```
|
|
106
|
-
ROLE:
|
|
107
|
-
[Perspective or expertise needed]
|
|
108
|
-
|
|
109
|
-
INPUT:
|
|
110
|
-
[Description of provided data/content:
|
|
111
|
-
- Format and structure
|
|
112
|
-
- Key characteristics
|
|
113
|
-
- Any quirks or special considerations]
|
|
114
|
-
|
|
115
|
-
STEPS:
|
|
116
|
-
1. [Processing action 1]
|
|
117
|
-
2. [Processing action 2]
|
|
118
|
-
3. [Processing action 3]
|
|
119
|
-
4. [Continue with transformation/analysis steps...]
|
|
120
|
-
|
|
121
|
-
EXPECTATION:
|
|
122
|
-
[Output format and content requirements:
|
|
123
|
-
- Format and structure
|
|
124
|
-
- Required elements
|
|
125
|
-
- Level of detail
|
|
126
|
-
- Length or size constraints]
|
|
127
|
-
```
|
|
128
|
-
|
|
129
|
-
### RISE-IE Complete Example
|
|
130
|
-
|
|
131
|
-
**Before RISE-IE:**
|
|
132
|
-
"Analyze these customer reviews."
|
|
133
|
-
|
|
134
|
-
**After RISE-IE:**
|
|
135
|
-
```
|
|
136
|
-
ROLE:
|
|
137
|
-
You are a customer insights analyst with expertise in sentiment analysis and theme extraction.
|
|
138
|
-
|
|
139
|
-
INPUT:
|
|
140
|
-
You'll receive 50 customer reviews from our mobile app. Each review contains:
|
|
141
|
-
- Star rating (1-5)
|
|
142
|
-
- Written feedback
|
|
143
|
-
- Date of review
|
|
144
|
-
- User segment (free/premium)
|
|
145
|
-
|
|
146
|
-
STEPS:
|
|
147
|
-
1. Categorize reviews by sentiment (positive, neutral, negative)
|
|
148
|
-
2. Extract common themes and topics mentioned
|
|
149
|
-
3. Identify feature requests vs. complaints vs. praise
|
|
150
|
-
4. Segment findings by user type (free vs. premium)
|
|
151
|
-
5. Highlight urgent issues mentioned multiple times
|
|
152
|
-
6. Note any patterns in timing or trends
|
|
153
|
-
|
|
154
|
-
EXPECTATION:
|
|
155
|
-
Provide a structured analysis with:
|
|
156
|
-
- Summary table showing sentiment distribution
|
|
157
|
-
- Top 5 themes with frequency counts
|
|
158
|
-
- List of feature requests ranked by mentions
|
|
159
|
-
- Critical issues requiring immediate attention
|
|
160
|
-
- Comparison of free vs. premium user feedback
|
|
161
|
-
- 2-3 actionable recommendations
|
|
162
|
-
```
|
|
163
|
-
|
|
164
|
-
---
|
|
165
|
-
|
|
166
|
-
## RISE-IX (Instructions-Examples Variant)
|
|
167
|
-
|
|
168
|
-
### When to Use RISE-IX
|
|
169
|
-
|
|
170
|
-
**Perfect for:**
|
|
171
|
-
- ✅ Content creation tasks
|
|
172
|
-
- ✅ Writing with specific style requirements
|
|
173
|
-
- ✅ Tasks benefiting from examples
|
|
174
|
-
- ✅ Learning and educational content
|
|
175
|
-
- ✅ Creative work requiring reference points
|
|
176
|
-
- ✅ Replicating existing formats or styles
|
|
177
|
-
|
|
178
|
-
**Use RISE-IX when you have**:
|
|
179
|
-
- A specific task or directive to follow
|
|
180
|
-
- Examples of desired output style
|
|
181
|
-
- Need to replicate a format or approach
|
|
182
|
-
- Creative or communication-focused goals
|
|
183
|
-
|
|
184
|
-
### RISE-IX Components
|
|
185
|
-
|
|
186
|
-
#### R - Role
|
|
187
|
-
**Purpose:** Define who the AI should embody (persona or expertise).
|
|
188
|
-
|
|
189
|
-
**Questions to Ask:**
|
|
190
|
-
- What persona is most appropriate?
|
|
191
|
-
- What expertise level is needed?
|
|
192
|
-
- What perspective should be taken?
|
|
193
|
-
|
|
194
|
-
**Examples:**
|
|
195
|
-
- "You are a senior content strategist..."
|
|
196
|
-
- "Act as a creative copywriter..."
|
|
197
|
-
- "Take on the role of a technical writer..."
|
|
198
|
-
|
|
199
|
-
#### I - Instructions
|
|
200
|
-
**Purpose:** Specify the main task or directive.
|
|
201
|
-
|
|
202
|
-
**Questions to Ask:**
|
|
203
|
-
- What is the primary task?
|
|
204
|
-
- What are the core requirements?
|
|
205
|
-
- What should be accomplished?
|
|
206
|
-
- What guidelines should be followed?
|
|
207
|
-
|
|
208
|
-
**Examples:**
|
|
209
|
-
- "Create a blog post outline about sustainable fashion"
|
|
210
|
-
- "Write product descriptions for eco-friendly products"
|
|
211
|
-
- "Develop an email sequence for customer onboarding"
|
|
212
|
-
|
|
213
|
-
#### S - Steps
|
|
214
|
-
**Purpose:** Outline the process or methodology to follow.
|
|
215
|
-
|
|
216
|
-
**Questions to Ask:**
|
|
217
|
-
- What's the sequence of actions?
|
|
218
|
-
- How should the task be approached?
|
|
219
|
-
- What's the workflow?
|
|
220
|
-
- What methodology should be used?
|
|
221
|
-
|
|
222
|
-
**Examples:**
|
|
223
|
-
- "1. Research trends, 2. Identify pain points, 3. Structure content, 4. Add CTAs"
|
|
224
|
-
- "Start with hook, develop key points, conclude with action items"
|
|
225
|
-
|
|
226
|
-
#### E - Examples
|
|
227
|
-
**Purpose:** Provide positive examples showing desired output.
|
|
228
|
-
|
|
229
|
-
**Questions to Ask:**
|
|
230
|
-
- What does good output look like?
|
|
231
|
-
- Can you provide reference examples?
|
|
232
|
-
- What style should be emulated?
|
|
233
|
-
- What format should be followed?
|
|
234
|
-
|
|
235
|
-
**Examples:**
|
|
236
|
-
- "Similar to our 'Eco-Friendly Living' post format with 3 main sections"
|
|
237
|
-
- "Follow the style of these product descriptions: [examples]"
|
|
238
|
-
- "Match the tone and structure of this email: [example]"
|
|
239
|
-
|
|
240
|
-
### RISE-IX Template
|
|
241
|
-
|
|
242
|
-
```
|
|
243
|
-
ROLE:
|
|
244
|
-
[Persona or expertise level]
|
|
245
|
-
|
|
246
|
-
INSTRUCTIONS:
|
|
247
|
-
[Main task or directive:
|
|
248
|
-
- What to create or accomplish
|
|
249
|
-
- Core requirements
|
|
250
|
-
- Key guidelines to follow]
|
|
251
|
-
|
|
252
|
-
STEPS:
|
|
253
|
-
1. [Approach or methodology step 1]
|
|
254
|
-
2. [Step 2]
|
|
255
|
-
3. [Step 3]
|
|
256
|
-
4. [Continue with workflow/process steps...]
|
|
257
|
-
|
|
258
|
-
EXAMPLES:
|
|
259
|
-
[Positive examples showing desired output:
|
|
260
|
-
- Reference materials
|
|
261
|
-
- Style to emulate
|
|
262
|
-
- Format to follow
|
|
263
|
-
- Similar successful outputs]
|
|
264
|
-
```
|
|
265
|
-
|
|
266
|
-
### RISE-IX Complete Example
|
|
267
|
-
|
|
268
|
-
**Before RISE-IX:**
|
|
269
|
-
"Write product descriptions for our sustainable clothing line."
|
|
270
|
-
|
|
271
|
-
**After RISE-IX:**
|
|
272
|
-
```
|
|
273
|
-
ROLE:
|
|
274
|
-
You are a senior copywriter specializing in sustainable fashion and eco-conscious brands.
|
|
275
|
-
|
|
276
|
-
INSTRUCTIONS:
|
|
277
|
-
Create compelling product descriptions for our new sustainable clothing line that:
|
|
278
|
-
- Highlight eco-friendly materials and production methods
|
|
279
|
-
- Appeal to environmentally conscious millennials
|
|
280
|
-
- Emphasize both style and sustainability
|
|
281
|
-
- Include specific product details and benefits
|
|
282
|
-
- Drive purchase intent through emotional connection
|
|
283
|
-
|
|
284
|
-
STEPS:
|
|
285
|
-
1. Start with an attention-grabbing opening about the product's unique appeal
|
|
286
|
-
2. Describe the sustainable materials and ethical production process
|
|
287
|
-
3. Highlight the product's style, fit, and versatility
|
|
288
|
-
4. Include specific technical details (materials, care, sizing)
|
|
289
|
-
5. End with a call-to-action emphasizing the impact of their purchase
|
|
290
|
-
|
|
291
|
-
EXAMPLES:
|
|
292
|
-
Similar to these high-performing descriptions:
|
|
293
|
-
|
|
294
|
-
Example 1: "The Ocean Breeze Tee - Crafted from 100% recycled ocean plastics,
|
|
295
|
-
this impossibly soft tee proves sustainability never has to sacrifice style. Each
|
|
296
|
-
purchase removes 5 plastic bottles from our oceans..."
|
|
297
|
-
|
|
298
|
-
Example 2: "Evergreen Denim Jacket - Timeless style meets zero-waste innovation.
|
|
299
|
-
Woven from organic cotton with natural indigo dye, this jacket gets better with
|
|
300
|
-
every wear while treading lightly on the planet..."
|
|
301
|
-
```
|
|
302
|
-
|
|
303
|
-
---
|
|
304
|
-
|
|
305
|
-
## Selection Guide: Which RISE Variant to Use?
|
|
306
|
-
|
|
307
|
-
### Quick Decision Matrix
|
|
308
|
-
|
|
309
|
-
| Your Task Type | Recommended Variant | Key Indicator |
|
|
310
|
-
|----------------|-------------------|---------------|
|
|
311
|
-
| Data analysis | **RISE-IE** | You have specific data to process |
|
|
312
|
-
| CSV/JSON processing | **RISE-IE** | Input format is technical |
|
|
313
|
-
| Report generation | **RISE-IE** | Transforming data → output |
|
|
314
|
-
| Content writing | **RISE-IX** | Creating new content |
|
|
315
|
-
| Style replication | **RISE-IX** | Need examples to follow |
|
|
316
|
-
| Email/blog creation | **RISE-IX** | Communication-focused |
|
|
317
|
-
| Code analysis | **RISE-IE** | Processing code as input |
|
|
318
|
-
| Creative work | **RISE-IX** | Examples show desired style |
|
|
319
|
-
|
|
320
|
-
### Detailed Selection Criteria
|
|
321
|
-
|
|
322
|
-
**Choose RISE-IE (Input-Expectation) when:**
|
|
323
|
-
- ✅ You have well-defined input data (files, datasets, content)
|
|
324
|
-
- ✅ Task is analytical or technical
|
|
325
|
-
- ✅ Focus is on transformation/processing
|
|
326
|
-
- ✅ Output format is more important than style
|
|
327
|
-
- ✅ Working with structured data (CSV, JSON, logs)
|
|
328
|
-
- ✅ Need to specify what you're providing as input
|
|
329
|
-
|
|
330
|
-
**Choose RISE-IX (Instructions-Examples) when:**
|
|
331
|
-
- ✅ Task is creative or communication-focused
|
|
332
|
-
- ✅ You have examples of desired output
|
|
333
|
-
- ✅ Need to replicate a specific style or format
|
|
334
|
-
- ✅ Instructions are the core driver (not input data)
|
|
335
|
-
- ✅ Examples would clarify expectations
|
|
336
|
-
- ✅ Creating content rather than processing data
|
|
337
|
-
|
|
338
|
-
### Can't Decide? Ask Yourself:
|
|
339
|
-
|
|
340
|
-
**"Am I providing specific data/content to be processed?"**
|
|
341
|
-
- YES → **RISE-IE** (Input-Expectation)
|
|
342
|
-
- NO → **RISE-IX** (Instructions-Examples)
|
|
343
|
-
|
|
344
|
-
**"Do I have examples that would help clarify what I want?"**
|
|
345
|
-
- YES → **RISE-IX** (Instructions-Examples)
|
|
346
|
-
- NO → **RISE-IE** might be better
|
|
347
|
-
|
|
348
|
-
**"Is this primarily a data transformation task?"**
|
|
349
|
-
- YES → **RISE-IE** (Input-Expectation)
|
|
350
|
-
- NO → **RISE-IX** (Instructions-Examples)
|
|
351
|
-
|
|
352
|
-
---
|
|
353
|
-
|
|
354
|
-
## Common Use Cases by Variant
|
|
355
|
-
|
|
356
|
-
### RISE-IE Use Cases
|
|
357
|
-
|
|
358
|
-
1. **Data Analysis**
|
|
359
|
-
- CSV/Excel analysis
|
|
360
|
-
- Log file processing
|
|
361
|
-
- Survey data interpretation
|
|
362
|
-
- Database query results processing
|
|
363
|
-
|
|
364
|
-
2. **Content Processing**
|
|
365
|
-
- Text summarization
|
|
366
|
-
- Document transformation
|
|
367
|
-
- Email categorization
|
|
368
|
-
- Content extraction
|
|
369
|
-
|
|
370
|
-
3. **Code Analysis**
|
|
371
|
-
- Code review with specific focus
|
|
372
|
-
- Dependency analysis
|
|
373
|
-
- Performance profiling
|
|
374
|
-
- Test coverage assessment
|
|
375
|
-
|
|
376
|
-
4. **Format Conversions**
|
|
377
|
-
- JSON to CSV conversion
|
|
378
|
-
- Markdown to HTML
|
|
379
|
-
- Data cleaning and normalization
|
|
380
|
-
|
|
381
|
-
### RISE-IX Use Cases
|
|
382
|
-
|
|
383
|
-
1. **Content Creation**
|
|
384
|
-
- Blog post writing
|
|
385
|
-
- Product descriptions
|
|
386
|
-
- Email campaigns
|
|
387
|
-
- Social media content
|
|
388
|
-
|
|
389
|
-
2. **Documentation**
|
|
390
|
-
- User guides following templates
|
|
391
|
-
- API documentation matching style
|
|
392
|
-
- Tutorial creation based on examples
|
|
393
|
-
|
|
394
|
-
3. **Creative Writing**
|
|
395
|
-
- Marketing copy
|
|
396
|
-
- Brand messaging
|
|
397
|
-
- Storytelling with reference examples
|
|
398
|
-
- Style-matched content
|
|
399
|
-
|
|
400
|
-
4. **Educational Content**
|
|
401
|
-
- Lesson plans following examples
|
|
402
|
-
- Quiz creation matching format
|
|
403
|
-
- Study guides based on templates
|
|
404
|
-
|
|
405
|
-
---
|
|
406
|
-
|
|
407
|
-
## Comparison with Other Frameworks
|
|
408
|
-
|
|
409
|
-
### RISE-IE vs. RISE-IX
|
|
410
|
-
|
|
411
|
-
| Aspect | RISE-IE | RISE-IX |
|
|
412
|
-
|--------|---------|---------|
|
|
413
|
-
| **Focus** | Data transformation | Content creation |
|
|
414
|
-
| **Key Component** | Input specification | Examples provision |
|
|
415
|
-
| **Best For** | Analytical tasks | Creative tasks |
|
|
416
|
-
| **Learning Curve** | Technical | Accessible |
|
|
417
|
-
| **Example Type** | Input/output specs | Style references |
|
|
418
|
-
|
|
419
|
-
### RISE (Both) vs. RISEN
|
|
420
|
-
|
|
421
|
-
**Use RISE for:**
|
|
422
|
-
- Simpler transformations
|
|
423
|
-
- When narrowing/constraints aren't critical
|
|
424
|
-
- Standard processing or creation
|
|
425
|
-
- Routine tasks
|
|
426
|
-
|
|
427
|
-
**Use RISEN for:**
|
|
428
|
-
- Complex multi-step processes
|
|
429
|
-
- When boundaries and constraints matter
|
|
430
|
-
- Multiple valid approaches (need to specify one)
|
|
431
|
-
- Tasks requiring extensive guidance and limitations
|
|
432
|
-
|
|
433
|
-
### RISE (Both) vs. RTF
|
|
434
|
-
|
|
435
|
-
**Use RISE for:**
|
|
436
|
-
- Multi-step processing or creation
|
|
437
|
-
- When input or examples add clarity
|
|
438
|
-
- More complex than simple directives
|
|
439
|
-
|
|
440
|
-
**Use RTF for:**
|
|
441
|
-
- Simple, straightforward tasks
|
|
442
|
-
- Quick requests
|
|
443
|
-
- When role-task-format is sufficient
|
|
444
|
-
|
|
445
|
-
### RISE (Both) vs. CO-STAR
|
|
446
|
-
|
|
447
|
-
**Use RISE for:**
|
|
448
|
-
- Focused tasks without multiple audience considerations
|
|
449
|
-
- When tone/style are secondary
|
|
450
|
-
- Straightforward processing or creation
|
|
451
|
-
|
|
452
|
-
**Use CO-STAR for:**
|
|
453
|
-
- Complex communication requirements
|
|
454
|
-
- Multiple audience considerations
|
|
455
|
-
- When tone and style are critical
|
|
456
|
-
|
|
457
|
-
---
|
|
458
|
-
|
|
459
|
-
## Assessment Checklist
|
|
460
|
-
|
|
461
|
-
### For RISE-IE (Input-Expectation):
|
|
462
|
-
- [ ] Role is appropriate for the analytical task
|
|
463
|
-
- [ ] Input is thoroughly described
|
|
464
|
-
- [ ] Input format and structure are specified
|
|
465
|
-
- [ ] Steps are specific and sequential
|
|
466
|
-
- [ ] Processing methods are clear
|
|
467
|
-
- [ ] Expectation defines exact output format
|
|
468
|
-
- [ ] Output requirements are detailed
|
|
469
|
-
- [ ] All input characteristics are handled in steps
|
|
470
|
-
|
|
471
|
-
### For RISE-IX (Instructions-Examples):
|
|
472
|
-
- [ ] Role matches the creative/communication task
|
|
473
|
-
- [ ] Instructions are clear and comprehensive
|
|
474
|
-
- [ ] Steps outline the methodology
|
|
475
|
-
- [ ] Workflow is logical and sequential
|
|
476
|
-
- [ ] Examples effectively demonstrate desired output
|
|
477
|
-
- [ ] Examples match the task type
|
|
478
|
-
- [ ] Examples show style, format, or approach to emulate
|
|
479
|
-
- [ ] Sufficient examples provided (2-3 recommended)
|
|
480
|
-
|
|
481
|
-
---
|
|
482
|
-
|
|
483
|
-
## Tips for Effective Use
|
|
484
|
-
|
|
485
|
-
### RISE-IE Tips
|
|
486
|
-
|
|
487
|
-
1. **Be Specific About Input**
|
|
488
|
-
- Mention format, structure, and characteristics
|
|
489
|
-
- Note any data quirks or issues
|
|
490
|
-
- Specify what to expect in the data
|
|
491
|
-
|
|
492
|
-
2. **Detail Processing Steps**
|
|
493
|
-
- Be specific about transformations
|
|
494
|
-
- Clarify calculation methods
|
|
495
|
-
- Explain analysis approaches
|
|
496
|
-
|
|
497
|
-
3. **Define Clear Expectations**
|
|
498
|
-
- Specify exact output format
|
|
499
|
-
- Define completeness criteria
|
|
500
|
-
- Mention all required sections
|
|
501
|
-
|
|
502
|
-
### RISE-IX Tips
|
|
503
|
-
|
|
504
|
-
1. **Write Clear Instructions**
|
|
505
|
-
- Be specific about what to create
|
|
506
|
-
- Include all requirements upfront
|
|
507
|
-
- Mention any constraints or guidelines
|
|
508
|
-
|
|
509
|
-
2. **Provide Quality Examples**
|
|
510
|
-
- Choose examples that clearly show desired output
|
|
511
|
-
- Include 2-3 examples when possible
|
|
512
|
-
- Highlight what makes examples good
|
|
513
|
-
|
|
514
|
-
3. **Align Steps with Instructions**
|
|
515
|
-
- Ensure steps support the main directive
|
|
516
|
-
- Make workflow logical and complete
|
|
517
|
-
- Include creative process steps
|
|
518
|
-
|
|
519
|
-
---
|
|
520
|
-
|
|
521
|
-
## Quick Reference
|
|
522
|
-
|
|
523
|
-
### RISE-IE (Input-Expectation)
|
|
524
|
-
|
|
525
|
-
| Component | Focus | Key Question |
|
|
526
|
-
|-----------|-------|--------------|
|
|
527
|
-
| Role | Expertise | "What perspective is needed?" |
|
|
528
|
-
| Input | Source Data | "What am I working with?" |
|
|
529
|
-
| Steps | Processing | "How do I transform it?" |
|
|
530
|
-
| Expectation | Output | "What should I produce?" |
|
|
531
|
-
|
|
532
|
-
### RISE-IX (Instructions-Examples)
|
|
533
|
-
|
|
534
|
-
| Component | Focus | Key Question |
|
|
535
|
-
|-----------|-------|--------------|
|
|
536
|
-
| Role | Persona | "Who should I be?" |
|
|
537
|
-
| Instructions | Directive | "What should I create?" |
|
|
538
|
-
| Steps | Methodology | "How should I approach it?" |
|
|
539
|
-
| Examples | References | "What does good look like?" |
|
|
540
|
-
|
|
541
|
-
---
|
|
542
|
-
|
|
543
|
-
## Summary
|
|
544
|
-
|
|
545
|
-
RISE framework exists in two well-documented variants:
|
|
546
|
-
|
|
547
|
-
**RISE-IE (Input-Expectation)**: Best for data processing, analysis, and transformation tasks where you have specific input to work with.
|
|
548
|
-
|
|
549
|
-
**RISE-IX (Instructions-Examples)**: Best for content creation, writing, and tasks where examples help clarify desired output style.
|
|
550
|
-
|
|
551
|
-
Both variants are legitimate and effective. Choose based on whether your task is more analytical/data-focused (IE) or creative/instruction-focused (IX).
|
|
552
|
-
|
|
553
|
-
When in doubt, ask: **"Am I processing data or creating content?"**
|
|
554
|
-
- Processing data → **RISE-IE**
|
|
555
|
-
- Creating content → **RISE-IX**
|
|
1
|
+
# RISE Framework - Dual Variant Support
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
RISE is a streamlined 4-component framework that exists in **two legitimate variants**, each serving different use cases. Both versions are well-documented in authoritative sources and provide effective prompt structuring.
|
|
6
|
+
|
|
7
|
+
**Important**: This skill supports BOTH variants. Selection guidance is provided below to help choose the right version for your task.
|
|
8
|
+
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
## The Two RISE Variants
|
|
12
|
+
|
|
13
|
+
### RISE-IE: Input-Expectation (Data-Focused)
|
|
14
|
+
**Components**: Role, **Input**, Steps, **Expectation**
|
|
15
|
+
|
|
16
|
+
**Best for**: Data analysis, transformations, processing tasks
|
|
17
|
+
|
|
18
|
+
**Sources**: Fabio Vivas, Juuzt.ai
|
|
19
|
+
|
|
20
|
+
### RISE-IX: Instructions-Examples (Instruction-Focused)
|
|
21
|
+
**Components**: Role, **Instructions**, Steps, **Examples**
|
|
22
|
+
|
|
23
|
+
**Best for**: Content creation, learning tasks, example-based work
|
|
24
|
+
|
|
25
|
+
**Sources**: AiPromptsX, The Prompt Warrior, Thoughts Brewing
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## RISE-IE (Input-Expectation Variant)
|
|
30
|
+
|
|
31
|
+
### When to Use RISE-IE
|
|
32
|
+
|
|
33
|
+
**Perfect for:**
|
|
34
|
+
- ✅ Data analysis and transformation tasks
|
|
35
|
+
- ✅ Input → output processing workflows
|
|
36
|
+
- ✅ Working with specific data formats (CSV, JSON, logs)
|
|
37
|
+
- ✅ Tasks where input characteristics are well-defined
|
|
38
|
+
- ✅ Analytical and technical tasks
|
|
39
|
+
- ✅ Report generation from structured data
|
|
40
|
+
|
|
41
|
+
**Use RISE-IE when you have**:
|
|
42
|
+
- Well-defined input data or content
|
|
43
|
+
- Clear transformation requirements
|
|
44
|
+
- Specific output format needs
|
|
45
|
+
- Analytical processing goals
|
|
46
|
+
|
|
47
|
+
### RISE-IE Components
|
|
48
|
+
|
|
49
|
+
#### R - Role
|
|
50
|
+
**Purpose:** Define the perspective or expertise needed for the task.
|
|
51
|
+
|
|
52
|
+
**Questions to Ask:**
|
|
53
|
+
- What expertise is required?
|
|
54
|
+
- What viewpoint should be taken?
|
|
55
|
+
- What knowledge level is needed?
|
|
56
|
+
|
|
57
|
+
**Examples:**
|
|
58
|
+
- "Act as a data analyst..."
|
|
59
|
+
- "You are a content editor..."
|
|
60
|
+
- "Take the perspective of a UX researcher..."
|
|
61
|
+
|
|
62
|
+
#### I - Input
|
|
63
|
+
**Purpose:** Specify what's being provided and its characteristics.
|
|
64
|
+
|
|
65
|
+
**Questions to Ask:**
|
|
66
|
+
- What data/content is being provided?
|
|
67
|
+
- What format is it in?
|
|
68
|
+
- Are there any input constraints?
|
|
69
|
+
- What should Claude expect to receive?
|
|
70
|
+
|
|
71
|
+
**Examples:**
|
|
72
|
+
- "You'll receive a CSV file with sales data..."
|
|
73
|
+
- "Input is a collection of user feedback emails..."
|
|
74
|
+
- "You have access to JSON API responses..."
|
|
75
|
+
|
|
76
|
+
#### S - Steps
|
|
77
|
+
**Purpose:** Define how to process the input.
|
|
78
|
+
|
|
79
|
+
**Questions to Ask:**
|
|
80
|
+
- How should the input be processed?
|
|
81
|
+
- What transformations are needed?
|
|
82
|
+
- What's the processing sequence?
|
|
83
|
+
- What analysis should be performed?
|
|
84
|
+
|
|
85
|
+
**Examples:**
|
|
86
|
+
- "1. Parse CSV, 2. Calculate metrics, 3. Identify trends..."
|
|
87
|
+
- "Extract key themes, categorize by sentiment, count occurrences..."
|
|
88
|
+
|
|
89
|
+
#### E - Expectation
|
|
90
|
+
**Purpose:** Define what the output should look like.
|
|
91
|
+
|
|
92
|
+
**Questions to Ask:**
|
|
93
|
+
- What format should output take?
|
|
94
|
+
- What should be included?
|
|
95
|
+
- How detailed should it be?
|
|
96
|
+
- What's the deliverable?
|
|
97
|
+
|
|
98
|
+
**Examples:**
|
|
99
|
+
- "Provide a summary table with top 10 items..."
|
|
100
|
+
- "Generate a JSON object with categorized results..."
|
|
101
|
+
- "Create a report with charts and key findings..."
|
|
102
|
+
|
|
103
|
+
### RISE-IE Template
|
|
104
|
+
|
|
105
|
+
```
|
|
106
|
+
ROLE:
|
|
107
|
+
[Perspective or expertise needed]
|
|
108
|
+
|
|
109
|
+
INPUT:
|
|
110
|
+
[Description of provided data/content:
|
|
111
|
+
- Format and structure
|
|
112
|
+
- Key characteristics
|
|
113
|
+
- Any quirks or special considerations]
|
|
114
|
+
|
|
115
|
+
STEPS:
|
|
116
|
+
1. [Processing action 1]
|
|
117
|
+
2. [Processing action 2]
|
|
118
|
+
3. [Processing action 3]
|
|
119
|
+
4. [Continue with transformation/analysis steps...]
|
|
120
|
+
|
|
121
|
+
EXPECTATION:
|
|
122
|
+
[Output format and content requirements:
|
|
123
|
+
- Format and structure
|
|
124
|
+
- Required elements
|
|
125
|
+
- Level of detail
|
|
126
|
+
- Length or size constraints]
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
### RISE-IE Complete Example
|
|
130
|
+
|
|
131
|
+
**Before RISE-IE:**
|
|
132
|
+
"Analyze these customer reviews."
|
|
133
|
+
|
|
134
|
+
**After RISE-IE:**
|
|
135
|
+
```
|
|
136
|
+
ROLE:
|
|
137
|
+
You are a customer insights analyst with expertise in sentiment analysis and theme extraction.
|
|
138
|
+
|
|
139
|
+
INPUT:
|
|
140
|
+
You'll receive 50 customer reviews from our mobile app. Each review contains:
|
|
141
|
+
- Star rating (1-5)
|
|
142
|
+
- Written feedback
|
|
143
|
+
- Date of review
|
|
144
|
+
- User segment (free/premium)
|
|
145
|
+
|
|
146
|
+
STEPS:
|
|
147
|
+
1. Categorize reviews by sentiment (positive, neutral, negative)
|
|
148
|
+
2. Extract common themes and topics mentioned
|
|
149
|
+
3. Identify feature requests vs. complaints vs. praise
|
|
150
|
+
4. Segment findings by user type (free vs. premium)
|
|
151
|
+
5. Highlight urgent issues mentioned multiple times
|
|
152
|
+
6. Note any patterns in timing or trends
|
|
153
|
+
|
|
154
|
+
EXPECTATION:
|
|
155
|
+
Provide a structured analysis with:
|
|
156
|
+
- Summary table showing sentiment distribution
|
|
157
|
+
- Top 5 themes with frequency counts
|
|
158
|
+
- List of feature requests ranked by mentions
|
|
159
|
+
- Critical issues requiring immediate attention
|
|
160
|
+
- Comparison of free vs. premium user feedback
|
|
161
|
+
- 2-3 actionable recommendations
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
---
|
|
165
|
+
|
|
166
|
+
## RISE-IX (Instructions-Examples Variant)
|
|
167
|
+
|
|
168
|
+
### When to Use RISE-IX
|
|
169
|
+
|
|
170
|
+
**Perfect for:**
|
|
171
|
+
- ✅ Content creation tasks
|
|
172
|
+
- ✅ Writing with specific style requirements
|
|
173
|
+
- ✅ Tasks benefiting from examples
|
|
174
|
+
- ✅ Learning and educational content
|
|
175
|
+
- ✅ Creative work requiring reference points
|
|
176
|
+
- ✅ Replicating existing formats or styles
|
|
177
|
+
|
|
178
|
+
**Use RISE-IX when you have**:
|
|
179
|
+
- A specific task or directive to follow
|
|
180
|
+
- Examples of desired output style
|
|
181
|
+
- Need to replicate a format or approach
|
|
182
|
+
- Creative or communication-focused goals
|
|
183
|
+
|
|
184
|
+
### RISE-IX Components
|
|
185
|
+
|
|
186
|
+
#### R - Role
|
|
187
|
+
**Purpose:** Define who the AI should embody (persona or expertise).
|
|
188
|
+
|
|
189
|
+
**Questions to Ask:**
|
|
190
|
+
- What persona is most appropriate?
|
|
191
|
+
- What expertise level is needed?
|
|
192
|
+
- What perspective should be taken?
|
|
193
|
+
|
|
194
|
+
**Examples:**
|
|
195
|
+
- "You are a senior content strategist..."
|
|
196
|
+
- "Act as a creative copywriter..."
|
|
197
|
+
- "Take on the role of a technical writer..."
|
|
198
|
+
|
|
199
|
+
#### I - Instructions
|
|
200
|
+
**Purpose:** Specify the main task or directive.
|
|
201
|
+
|
|
202
|
+
**Questions to Ask:**
|
|
203
|
+
- What is the primary task?
|
|
204
|
+
- What are the core requirements?
|
|
205
|
+
- What should be accomplished?
|
|
206
|
+
- What guidelines should be followed?
|
|
207
|
+
|
|
208
|
+
**Examples:**
|
|
209
|
+
- "Create a blog post outline about sustainable fashion"
|
|
210
|
+
- "Write product descriptions for eco-friendly products"
|
|
211
|
+
- "Develop an email sequence for customer onboarding"
|
|
212
|
+
|
|
213
|
+
#### S - Steps
|
|
214
|
+
**Purpose:** Outline the process or methodology to follow.
|
|
215
|
+
|
|
216
|
+
**Questions to Ask:**
|
|
217
|
+
- What's the sequence of actions?
|
|
218
|
+
- How should the task be approached?
|
|
219
|
+
- What's the workflow?
|
|
220
|
+
- What methodology should be used?
|
|
221
|
+
|
|
222
|
+
**Examples:**
|
|
223
|
+
- "1. Research trends, 2. Identify pain points, 3. Structure content, 4. Add CTAs"
|
|
224
|
+
- "Start with hook, develop key points, conclude with action items"
|
|
225
|
+
|
|
226
|
+
#### E - Examples
|
|
227
|
+
**Purpose:** Provide positive examples showing desired output.
|
|
228
|
+
|
|
229
|
+
**Questions to Ask:**
|
|
230
|
+
- What does good output look like?
|
|
231
|
+
- Can you provide reference examples?
|
|
232
|
+
- What style should be emulated?
|
|
233
|
+
- What format should be followed?
|
|
234
|
+
|
|
235
|
+
**Examples:**
|
|
236
|
+
- "Similar to our 'Eco-Friendly Living' post format with 3 main sections"
|
|
237
|
+
- "Follow the style of these product descriptions: [examples]"
|
|
238
|
+
- "Match the tone and structure of this email: [example]"
|
|
239
|
+
|
|
240
|
+
### RISE-IX Template
|
|
241
|
+
|
|
242
|
+
```
|
|
243
|
+
ROLE:
|
|
244
|
+
[Persona or expertise level]
|
|
245
|
+
|
|
246
|
+
INSTRUCTIONS:
|
|
247
|
+
[Main task or directive:
|
|
248
|
+
- What to create or accomplish
|
|
249
|
+
- Core requirements
|
|
250
|
+
- Key guidelines to follow]
|
|
251
|
+
|
|
252
|
+
STEPS:
|
|
253
|
+
1. [Approach or methodology step 1]
|
|
254
|
+
2. [Step 2]
|
|
255
|
+
3. [Step 3]
|
|
256
|
+
4. [Continue with workflow/process steps...]
|
|
257
|
+
|
|
258
|
+
EXAMPLES:
|
|
259
|
+
[Positive examples showing desired output:
|
|
260
|
+
- Reference materials
|
|
261
|
+
- Style to emulate
|
|
262
|
+
- Format to follow
|
|
263
|
+
- Similar successful outputs]
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
### RISE-IX Complete Example
|
|
267
|
+
|
|
268
|
+
**Before RISE-IX:**
|
|
269
|
+
"Write product descriptions for our sustainable clothing line."
|
|
270
|
+
|
|
271
|
+
**After RISE-IX:**
|
|
272
|
+
```
|
|
273
|
+
ROLE:
|
|
274
|
+
You are a senior copywriter specializing in sustainable fashion and eco-conscious brands.
|
|
275
|
+
|
|
276
|
+
INSTRUCTIONS:
|
|
277
|
+
Create compelling product descriptions for our new sustainable clothing line that:
|
|
278
|
+
- Highlight eco-friendly materials and production methods
|
|
279
|
+
- Appeal to environmentally conscious millennials
|
|
280
|
+
- Emphasize both style and sustainability
|
|
281
|
+
- Include specific product details and benefits
|
|
282
|
+
- Drive purchase intent through emotional connection
|
|
283
|
+
|
|
284
|
+
STEPS:
|
|
285
|
+
1. Start with an attention-grabbing opening about the product's unique appeal
|
|
286
|
+
2. Describe the sustainable materials and ethical production process
|
|
287
|
+
3. Highlight the product's style, fit, and versatility
|
|
288
|
+
4. Include specific technical details (materials, care, sizing)
|
|
289
|
+
5. End with a call-to-action emphasizing the impact of their purchase
|
|
290
|
+
|
|
291
|
+
EXAMPLES:
|
|
292
|
+
Similar to these high-performing descriptions:
|
|
293
|
+
|
|
294
|
+
Example 1: "The Ocean Breeze Tee - Crafted from 100% recycled ocean plastics,
|
|
295
|
+
this impossibly soft tee proves sustainability never has to sacrifice style. Each
|
|
296
|
+
purchase removes 5 plastic bottles from our oceans..."
|
|
297
|
+
|
|
298
|
+
Example 2: "Evergreen Denim Jacket - Timeless style meets zero-waste innovation.
|
|
299
|
+
Woven from organic cotton with natural indigo dye, this jacket gets better with
|
|
300
|
+
every wear while treading lightly on the planet..."
|
|
301
|
+
```
|
|
302
|
+
|
|
303
|
+
---
|
|
304
|
+
|
|
305
|
+
## Selection Guide: Which RISE Variant to Use?
|
|
306
|
+
|
|
307
|
+
### Quick Decision Matrix
|
|
308
|
+
|
|
309
|
+
| Your Task Type | Recommended Variant | Key Indicator |
|
|
310
|
+
|----------------|-------------------|---------------|
|
|
311
|
+
| Data analysis | **RISE-IE** | You have specific data to process |
|
|
312
|
+
| CSV/JSON processing | **RISE-IE** | Input format is technical |
|
|
313
|
+
| Report generation | **RISE-IE** | Transforming data → output |
|
|
314
|
+
| Content writing | **RISE-IX** | Creating new content |
|
|
315
|
+
| Style replication | **RISE-IX** | Need examples to follow |
|
|
316
|
+
| Email/blog creation | **RISE-IX** | Communication-focused |
|
|
317
|
+
| Code analysis | **RISE-IE** | Processing code as input |
|
|
318
|
+
| Creative work | **RISE-IX** | Examples show desired style |
|
|
319
|
+
|
|
320
|
+
### Detailed Selection Criteria
|
|
321
|
+
|
|
322
|
+
**Choose RISE-IE (Input-Expectation) when:**
|
|
323
|
+
- ✅ You have well-defined input data (files, datasets, content)
|
|
324
|
+
- ✅ Task is analytical or technical
|
|
325
|
+
- ✅ Focus is on transformation/processing
|
|
326
|
+
- ✅ Output format is more important than style
|
|
327
|
+
- ✅ Working with structured data (CSV, JSON, logs)
|
|
328
|
+
- ✅ Need to specify what you're providing as input
|
|
329
|
+
|
|
330
|
+
**Choose RISE-IX (Instructions-Examples) when:**
|
|
331
|
+
- ✅ Task is creative or communication-focused
|
|
332
|
+
- ✅ You have examples of desired output
|
|
333
|
+
- ✅ Need to replicate a specific style or format
|
|
334
|
+
- ✅ Instructions are the core driver (not input data)
|
|
335
|
+
- ✅ Examples would clarify expectations
|
|
336
|
+
- ✅ Creating content rather than processing data
|
|
337
|
+
|
|
338
|
+
### Can't Decide? Ask Yourself:
|
|
339
|
+
|
|
340
|
+
**"Am I providing specific data/content to be processed?"**
|
|
341
|
+
- YES → **RISE-IE** (Input-Expectation)
|
|
342
|
+
- NO → **RISE-IX** (Instructions-Examples)
|
|
343
|
+
|
|
344
|
+
**"Do I have examples that would help clarify what I want?"**
|
|
345
|
+
- YES → **RISE-IX** (Instructions-Examples)
|
|
346
|
+
- NO → **RISE-IE** might be better
|
|
347
|
+
|
|
348
|
+
**"Is this primarily a data transformation task?"**
|
|
349
|
+
- YES → **RISE-IE** (Input-Expectation)
|
|
350
|
+
- NO → **RISE-IX** (Instructions-Examples)
|
|
351
|
+
|
|
352
|
+
---
|
|
353
|
+
|
|
354
|
+
## Common Use Cases by Variant
|
|
355
|
+
|
|
356
|
+
### RISE-IE Use Cases
|
|
357
|
+
|
|
358
|
+
1. **Data Analysis**
|
|
359
|
+
- CSV/Excel analysis
|
|
360
|
+
- Log file processing
|
|
361
|
+
- Survey data interpretation
|
|
362
|
+
- Database query results processing
|
|
363
|
+
|
|
364
|
+
2. **Content Processing**
|
|
365
|
+
- Text summarization
|
|
366
|
+
- Document transformation
|
|
367
|
+
- Email categorization
|
|
368
|
+
- Content extraction
|
|
369
|
+
|
|
370
|
+
3. **Code Analysis**
|
|
371
|
+
- Code review with specific focus
|
|
372
|
+
- Dependency analysis
|
|
373
|
+
- Performance profiling
|
|
374
|
+
- Test coverage assessment
|
|
375
|
+
|
|
376
|
+
4. **Format Conversions**
|
|
377
|
+
- JSON to CSV conversion
|
|
378
|
+
- Markdown to HTML
|
|
379
|
+
- Data cleaning and normalization
|
|
380
|
+
|
|
381
|
+
### RISE-IX Use Cases
|
|
382
|
+
|
|
383
|
+
1. **Content Creation**
|
|
384
|
+
- Blog post writing
|
|
385
|
+
- Product descriptions
|
|
386
|
+
- Email campaigns
|
|
387
|
+
- Social media content
|
|
388
|
+
|
|
389
|
+
2. **Documentation**
|
|
390
|
+
- User guides following templates
|
|
391
|
+
- API documentation matching style
|
|
392
|
+
- Tutorial creation based on examples
|
|
393
|
+
|
|
394
|
+
3. **Creative Writing**
|
|
395
|
+
- Marketing copy
|
|
396
|
+
- Brand messaging
|
|
397
|
+
- Storytelling with reference examples
|
|
398
|
+
- Style-matched content
|
|
399
|
+
|
|
400
|
+
4. **Educational Content**
|
|
401
|
+
- Lesson plans following examples
|
|
402
|
+
- Quiz creation matching format
|
|
403
|
+
- Study guides based on templates
|
|
404
|
+
|
|
405
|
+
---
|
|
406
|
+
|
|
407
|
+
## Comparison with Other Frameworks
|
|
408
|
+
|
|
409
|
+
### RISE-IE vs. RISE-IX
|
|
410
|
+
|
|
411
|
+
| Aspect | RISE-IE | RISE-IX |
|
|
412
|
+
|--------|---------|---------|
|
|
413
|
+
| **Focus** | Data transformation | Content creation |
|
|
414
|
+
| **Key Component** | Input specification | Examples provision |
|
|
415
|
+
| **Best For** | Analytical tasks | Creative tasks |
|
|
416
|
+
| **Learning Curve** | Technical | Accessible |
|
|
417
|
+
| **Example Type** | Input/output specs | Style references |
|
|
418
|
+
|
|
419
|
+
### RISE (Both) vs. RISEN
|
|
420
|
+
|
|
421
|
+
**Use RISE for:**
|
|
422
|
+
- Simpler transformations
|
|
423
|
+
- When narrowing/constraints aren't critical
|
|
424
|
+
- Standard processing or creation
|
|
425
|
+
- Routine tasks
|
|
426
|
+
|
|
427
|
+
**Use RISEN for:**
|
|
428
|
+
- Complex multi-step processes
|
|
429
|
+
- When boundaries and constraints matter
|
|
430
|
+
- Multiple valid approaches (need to specify one)
|
|
431
|
+
- Tasks requiring extensive guidance and limitations
|
|
432
|
+
|
|
433
|
+
### RISE (Both) vs. RTF
|
|
434
|
+
|
|
435
|
+
**Use RISE for:**
|
|
436
|
+
- Multi-step processing or creation
|
|
437
|
+
- When input or examples add clarity
|
|
438
|
+
- More complex than simple directives
|
|
439
|
+
|
|
440
|
+
**Use RTF for:**
|
|
441
|
+
- Simple, straightforward tasks
|
|
442
|
+
- Quick requests
|
|
443
|
+
- When role-task-format is sufficient
|
|
444
|
+
|
|
445
|
+
### RISE (Both) vs. CO-STAR
|
|
446
|
+
|
|
447
|
+
**Use RISE for:**
|
|
448
|
+
- Focused tasks without multiple audience considerations
|
|
449
|
+
- When tone/style are secondary
|
|
450
|
+
- Straightforward processing or creation
|
|
451
|
+
|
|
452
|
+
**Use CO-STAR for:**
|
|
453
|
+
- Complex communication requirements
|
|
454
|
+
- Multiple audience considerations
|
|
455
|
+
- When tone and style are critical
|
|
456
|
+
|
|
457
|
+
---
|
|
458
|
+
|
|
459
|
+
## Assessment Checklist
|
|
460
|
+
|
|
461
|
+
### For RISE-IE (Input-Expectation):
|
|
462
|
+
- [ ] Role is appropriate for the analytical task
|
|
463
|
+
- [ ] Input is thoroughly described
|
|
464
|
+
- [ ] Input format and structure are specified
|
|
465
|
+
- [ ] Steps are specific and sequential
|
|
466
|
+
- [ ] Processing methods are clear
|
|
467
|
+
- [ ] Expectation defines exact output format
|
|
468
|
+
- [ ] Output requirements are detailed
|
|
469
|
+
- [ ] All input characteristics are handled in steps
|
|
470
|
+
|
|
471
|
+
### For RISE-IX (Instructions-Examples):
|
|
472
|
+
- [ ] Role matches the creative/communication task
|
|
473
|
+
- [ ] Instructions are clear and comprehensive
|
|
474
|
+
- [ ] Steps outline the methodology
|
|
475
|
+
- [ ] Workflow is logical and sequential
|
|
476
|
+
- [ ] Examples effectively demonstrate desired output
|
|
477
|
+
- [ ] Examples match the task type
|
|
478
|
+
- [ ] Examples show style, format, or approach to emulate
|
|
479
|
+
- [ ] Sufficient examples provided (2-3 recommended)
|
|
480
|
+
|
|
481
|
+
---
|
|
482
|
+
|
|
483
|
+
## Tips for Effective Use
|
|
484
|
+
|
|
485
|
+
### RISE-IE Tips
|
|
486
|
+
|
|
487
|
+
1. **Be Specific About Input**
|
|
488
|
+
- Mention format, structure, and characteristics
|
|
489
|
+
- Note any data quirks or issues
|
|
490
|
+
- Specify what to expect in the data
|
|
491
|
+
|
|
492
|
+
2. **Detail Processing Steps**
|
|
493
|
+
- Be specific about transformations
|
|
494
|
+
- Clarify calculation methods
|
|
495
|
+
- Explain analysis approaches
|
|
496
|
+
|
|
497
|
+
3. **Define Clear Expectations**
|
|
498
|
+
- Specify exact output format
|
|
499
|
+
- Define completeness criteria
|
|
500
|
+
- Mention all required sections
|
|
501
|
+
|
|
502
|
+
### RISE-IX Tips
|
|
503
|
+
|
|
504
|
+
1. **Write Clear Instructions**
|
|
505
|
+
- Be specific about what to create
|
|
506
|
+
- Include all requirements upfront
|
|
507
|
+
- Mention any constraints or guidelines
|
|
508
|
+
|
|
509
|
+
2. **Provide Quality Examples**
|
|
510
|
+
- Choose examples that clearly show desired output
|
|
511
|
+
- Include 2-3 examples when possible
|
|
512
|
+
- Highlight what makes examples good
|
|
513
|
+
|
|
514
|
+
3. **Align Steps with Instructions**
|
|
515
|
+
- Ensure steps support the main directive
|
|
516
|
+
- Make workflow logical and complete
|
|
517
|
+
- Include creative process steps
|
|
518
|
+
|
|
519
|
+
---
|
|
520
|
+
|
|
521
|
+
## Quick Reference
|
|
522
|
+
|
|
523
|
+
### RISE-IE (Input-Expectation)
|
|
524
|
+
|
|
525
|
+
| Component | Focus | Key Question |
|
|
526
|
+
|-----------|-------|--------------|
|
|
527
|
+
| Role | Expertise | "What perspective is needed?" |
|
|
528
|
+
| Input | Source Data | "What am I working with?" |
|
|
529
|
+
| Steps | Processing | "How do I transform it?" |
|
|
530
|
+
| Expectation | Output | "What should I produce?" |
|
|
531
|
+
|
|
532
|
+
### RISE-IX (Instructions-Examples)
|
|
533
|
+
|
|
534
|
+
| Component | Focus | Key Question |
|
|
535
|
+
|-----------|-------|--------------|
|
|
536
|
+
| Role | Persona | "Who should I be?" |
|
|
537
|
+
| Instructions | Directive | "What should I create?" |
|
|
538
|
+
| Steps | Methodology | "How should I approach it?" |
|
|
539
|
+
| Examples | References | "What does good look like?" |
|
|
540
|
+
|
|
541
|
+
---
|
|
542
|
+
|
|
543
|
+
## Summary
|
|
544
|
+
|
|
545
|
+
RISE framework exists in two well-documented variants:
|
|
546
|
+
|
|
547
|
+
**RISE-IE (Input-Expectation)**: Best for data processing, analysis, and transformation tasks where you have specific input to work with.
|
|
548
|
+
|
|
549
|
+
**RISE-IX (Instructions-Examples)**: Best for content creation, writing, and tasks where examples help clarify desired output style.
|
|
550
|
+
|
|
551
|
+
Both variants are legitimate and effective. Choose based on whether your task is more analytical/data-focused (IE) or creative/instruction-focused (IX).
|
|
552
|
+
|
|
553
|
+
When in doubt, ask: **"Am I processing data or creating content?"**
|
|
554
|
+
- Processing data → **RISE-IE**
|
|
555
|
+
- Creating content → **RISE-IX**
|