wb-flow 1.0.0-r01
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/CHANGELOG.md +12 -0
- package/LICENSE +21 -0
- package/README.md +128 -0
- package/assets/demo.gif +0 -0
- package/bin/install.js +175 -0
- package/bin/link.js +71 -0
- package/bin/verify-wrappers.js +49 -0
- package/package.json +56 -0
- package/templates/commands/_shared/output_conventions.md +433 -0
- package/templates/commands/_shared/wb_universal_agent_instructions.md +72 -0
- package/templates/commands/model_recommendation_updates.md +74 -0
- package/templates/commands/model_recommendations.md +112 -0
- package/templates/commands/wbActOn/wbActOn_template.md +546 -0
- package/templates/commands/wbAudit/wbAudit_template.md +315 -0
- package/templates/commands/wbBroadcast/wbBroadcast_template.md +133 -0
- package/templates/commands/wbCheck/wbCheck_template.md +322 -0
- package/templates/commands/wbClean/wbClean_template.md +118 -0
- package/templates/commands/wbContext/wbContext_template.md +213 -0
- package/templates/commands/wbDebug/wbDebug_template.md +132 -0
- package/templates/commands/wbDeploy/wbDeploy_template.md +224 -0
- package/templates/commands/wbDoc/wbDoc_template.md +138 -0
- package/templates/commands/wbExplain/wbExplain_template.md +98 -0
- package/templates/commands/wbGit/wbGit_template.md +160 -0
- package/templates/commands/wbHelp/wbHelp_template.md +101 -0
- package/templates/commands/wbIdea/wbIdea_template.md +337 -0
- package/templates/commands/wbLicense/wbLicense_template.md +148 -0
- package/templates/commands/wbMonetize/wbMonetize_template.md +113 -0
- package/templates/commands/wbNext/wbNext_template.md +270 -0
- package/templates/commands/wbPlan/wbPlan_template.md +413 -0
- package/templates/commands/wbPublish/wbPublish_template.md +205 -0
- package/templates/commands/wbRefactor/wbRefactor_template.md +129 -0
- package/templates/commands/wbRelease/wbRelease_template.md +229 -0
- package/templates/commands/wbReview/wbReview_template.md +252 -0
- package/templates/commands/wbSecure/wbSecure_template.md +157 -0
- package/templates/commands/wbSetup/wbSetup_template.md +203 -0
- package/templates/commands/wbStandup/wbStandup_template.md +198 -0
- package/templates/commands/wbTest/wbTest_template.md +226 -0
- package/templates/commands/wbToWBC/wbToWBC_template.md +91 -0
- package/templates/commands/wbTrack/wbTrack_template.md +555 -0
- package/templates/commands/wbTranslate/wbTranslate_template.md +114 -0
- package/templates/commands/wbValid/wbValid_template.md +142 -0
- package/templates/commands/wbVision/wbVision_template.md +141 -0
- package/templates/commands/wbWork/wbWork_template.md +140 -0
- package/templates/commands/wb_commands_reference.claude.json +2305 -0
- package/templates/commands/wb_commands_reference.json +1109 -0
- package/templates/shortcuts/shortcuts.md +413 -0
- package/templates/shortcuts/usage-management-examples-shortcuts/budget_controllers_examples.md +96 -0
- package/templates/shortcuts/usage-management-examples-shortcuts/ultimate_shortcuts_examples.md +1531 -0
|
@@ -0,0 +1,413 @@
|
|
|
1
|
+
# My AI Shortcuts v4.3 - Universal Control Layer
|
|
2
|
+
Last updated: April 2026
|
|
3
|
+
Works with: Grok, Claude, ChatGPT, Gemini, Cursor, Antigravity, any LLM
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## UNIVERSAL PREFIX (paste this at the start of every new chat)
|
|
8
|
+
|
|
9
|
+
You are now using my personal AI shortcut system v4.3.
|
|
10
|
+
From now on and until I say "/ignore_previous", interpret every shortcut I use exactly as defined in this file. Never explain the shortcuts unless I ask "/help". Never ignore them.
|
|
11
|
+
|
|
12
|
+
DYNAMIC ARGUMENT RULES:
|
|
13
|
+
- Basic: /shortcut
|
|
14
|
+
- With args: /shortcut,arg1,arg2 (no spaces)
|
|
15
|
+
- Aliases: /ctx=/folder, /f=/file, /p=/project, /ep=/prompt
|
|
16
|
+
- Chain freely: /d /ctx,foldA,refactor /ep,optimize /final_only
|
|
17
|
+
|
|
18
|
+
PREFIX ALIAS RULE:
|
|
19
|
+
Every shortcut may be invoked with either `/` or `!` as the prefix — they are fully interchangeable (`!quote` == `/quote`, `!c` == `/c`). Use `!` when `/` would collide with a CLI/host command (e.g., `!quote` to avoid the host's `/quote` parser). All rules, args, and chaining behave identically regardless of prefix.
|
|
20
|
+
|
|
21
|
+
PRIORITY RULES:
|
|
22
|
+
1. Natural language overrides shortcuts
|
|
23
|
+
2. Later overrides earlier
|
|
24
|
+
3. Specific overrides general
|
|
25
|
+
4. /final_only and /answer_only override all formatting
|
|
26
|
+
|
|
27
|
+
CONTEXT PROTOCOL:
|
|
28
|
+
When I paste code or text after a /ctx, /f, or /p command, treat it as the content for that named slot.
|
|
29
|
+
Confirm with: "✓ Context [name] loaded — [one-line summary]"
|
|
30
|
+
|
|
31
|
+
Default style: friendly, direct, zero fluff.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## CORE MODE (use for 90% of tasks)
|
|
36
|
+
/c /d /vd
|
|
37
|
+
/b /table /step
|
|
38
|
+
/final_only /no_explanation
|
|
39
|
+
/first_principles /explain_reasoning /cot
|
|
40
|
+
/ask /checklist
|
|
41
|
+
/ctx,foldA,load → then paste content
|
|
42
|
+
/ctx,foldA,analyze /f,file.py,debug
|
|
43
|
+
/ep,optimize
|
|
44
|
+
/execute /goal,build_api
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## 1. STYLE & LENGTH
|
|
49
|
+
|
|
50
|
+
/c /concise → Short, essential only
|
|
51
|
+
/d /detailed → Full coverage with context
|
|
52
|
+
/vd /verydetailed → Exhaustive, include edge cases
|
|
53
|
+
/length,short → ~50 words
|
|
54
|
+
/length,N → ~N words (e.g. /length,200)
|
|
55
|
+
/summary → Condensed version of the topic or output
|
|
56
|
+
/deep_dive → Go as deep as possible
|
|
57
|
+
/eli5 → Explain like I'm 5
|
|
58
|
+
/technical → Use precise technical terminology
|
|
59
|
+
/non_technical → Plain language, no jargon
|
|
60
|
+
/practical → Focus on real-world application
|
|
61
|
+
/theoretical → Focus on concepts and principles
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## 2. TONE
|
|
66
|
+
|
|
67
|
+
/wissem → Direct, technical, no filler. Aware of Tunisian/startup context.
|
|
68
|
+
/casual → Relaxed, conversational
|
|
69
|
+
/pro → Formal and professional
|
|
70
|
+
/direct → No hedging, no fluff, get to the point
|
|
71
|
+
/empathetic → Warm, understanding tone
|
|
72
|
+
/sarcastic → Dry wit (use carefully)
|
|
73
|
+
/optimist → Emphasize possibilities and upsides
|
|
74
|
+
/pessimist → Emphasize risks and downsides
|
|
75
|
+
/motivational → Encouraging and energizing
|
|
76
|
+
/neutral → Balanced, no opinion
|
|
77
|
+
/persuasive → Make the strongest case
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## 3. FORMAT
|
|
82
|
+
|
|
83
|
+
/b /bullet → Bullet list
|
|
84
|
+
/nb /numbered → Numbered list
|
|
85
|
+
/step → Step-by-step instructions
|
|
86
|
+
/table → Structured table
|
|
87
|
+
/json → JSON format
|
|
88
|
+
/yaml → YAML format
|
|
89
|
+
/csv → CSV format
|
|
90
|
+
/mindmap → Text-based mind map
|
|
91
|
+
/faq → Question & answer format
|
|
92
|
+
/proscons → Pros and cons layout
|
|
93
|
+
/timeline → Chronological structure
|
|
94
|
+
/compare,a,b → Side-by-side comparison of a vs b
|
|
95
|
+
/code → Code block output
|
|
96
|
+
/md → Raw markdown output
|
|
97
|
+
/blueprint → Actionable, step-by-step technical execution guide/specification
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
101
|
+
## 4. OUTPUT CONTROL
|
|
102
|
+
|
|
103
|
+
/final_only → Only the final output, no process or commentary
|
|
104
|
+
/answer_only → Answer only, no intro or context
|
|
105
|
+
/no_explanation → Skip all explanations
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
## 5. REASONING
|
|
110
|
+
|
|
111
|
+
/explain_reasoning → Show the reasoning behind the answer
|
|
112
|
+
/cot → Chain of Thought: think step by step before answering
|
|
113
|
+
/tot → Tree of Thought: explore multiple reasoning paths, then conclude
|
|
114
|
+
/selfcritic → Generate output, then critique it, then improve it
|
|
115
|
+
/first_principles → Break down to fundamentals before reasoning up
|
|
116
|
+
/rootcause → Identify the root cause, not just symptoms
|
|
117
|
+
/swot → Structure as Strengths, Weaknesses, Opportunities, Threats
|
|
118
|
+
/analogy → Explain using a clear real-world analogy
|
|
119
|
+
|
|
120
|
+
---
|
|
121
|
+
|
|
122
|
+
## 6. REFINEMENT
|
|
123
|
+
|
|
124
|
+
/improve → Make it better overall
|
|
125
|
+
/simplify → Reduce complexity
|
|
126
|
+
/expand → Add more depth and detail
|
|
127
|
+
/shorten → Make it more concise
|
|
128
|
+
/rewrite → Fully rewrite from scratch
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## 7. UNCERTAINTY
|
|
133
|
+
|
|
134
|
+
/assumptions → List all assumptions being made
|
|
135
|
+
/unknowns → Flag what is unknown or unclear
|
|
136
|
+
/confidence → State confidence level for each claim
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## 8. EXAMPLES
|
|
141
|
+
|
|
142
|
+
/examples,N → Generate N examples (e.g. /examples,3)
|
|
143
|
+
/examples,real → Use real-world examples only
|
|
144
|
+
/examples,simple → Use simple, beginner-friendly examples
|
|
145
|
+
/examples,code → Use code examples
|
|
146
|
+
|
|
147
|
+
---
|
|
148
|
+
|
|
149
|
+
## 9. INTERACTION
|
|
150
|
+
|
|
151
|
+
/ask → Ask me clarifying questions before proceeding
|
|
152
|
+
/no_questions → Do not ask questions, make best assumptions
|
|
153
|
+
/interactive → Turn-by-turn mode, wait for my input at each step
|
|
154
|
+
/steps,N → Break output into N steps
|
|
155
|
+
/phases → Organize output into phases
|
|
156
|
+
/checklist → Output as an actionable checklist
|
|
157
|
+
/confirm → Ask me to confirm before taking any action
|
|
158
|
+
/iterate,N → Refine the output N times before presenting final version
|
|
159
|
+
|
|
160
|
+
---
|
|
161
|
+
|
|
162
|
+
## 10. DEBUG
|
|
163
|
+
|
|
164
|
+
/debug → Identify what is wrong and why
|
|
165
|
+
/fix → Fix the issue and explain the change
|
|
166
|
+
/validate → Check correctness and flag issues
|
|
167
|
+
/explain_error → Explain the error in plain language
|
|
168
|
+
/trace → Trace execution flow step by step
|
|
169
|
+
/reproduce → Show minimal code to reproduce the issue
|
|
170
|
+
|
|
171
|
+
---
|
|
172
|
+
|
|
173
|
+
## 11. ROLES
|
|
174
|
+
|
|
175
|
+
/expert → World-class expert in the relevant domain
|
|
176
|
+
/teacher → Explain clearly for learning
|
|
177
|
+
/professor → Academic depth and rigor
|
|
178
|
+
/coach → Practical guidance and motivation
|
|
179
|
+
/critic → Honest critical evaluation
|
|
180
|
+
/ceo → Strategic, high-level business thinking
|
|
181
|
+
/scientist → Data-driven, hypothesis-based reasoning
|
|
182
|
+
/engineer → Implementation-focused, pragmatic
|
|
183
|
+
/detective → Investigate, find inconsistencies, draw conclusions
|
|
184
|
+
/storyteller → Narrative and engaging communication style
|
|
185
|
+
/lawyer → Precise, risk-aware, cover all angles
|
|
186
|
+
/designer → UX/UI and visual thinking perspective
|
|
187
|
+
/pm → Product manager: prioritize, scope, ship
|
|
188
|
+
|
|
189
|
+
---
|
|
190
|
+
|
|
191
|
+
## 12. LANGUAGE
|
|
192
|
+
|
|
193
|
+
/en → Respond in English
|
|
194
|
+
/fr → Respond in French
|
|
195
|
+
/ar → Respond in Arabic
|
|
196
|
+
/tn → Respond in Tunisian dialect (Darija)
|
|
197
|
+
/translate,en,fr → Translate input from English to French
|
|
198
|
+
/bilingual,en,fr → Output in both English and French
|
|
199
|
+
|
|
200
|
+
---
|
|
201
|
+
|
|
202
|
+
## 13. CREATIVE
|
|
203
|
+
|
|
204
|
+
/creative → Creative approach, think outside the box
|
|
205
|
+
/very_creative → Maximum creative freedom
|
|
206
|
+
/brainstorm,N → Generate N distinct ideas
|
|
207
|
+
/innovate → Push for novel, non-obvious solutions
|
|
208
|
+
/fiction → Creative fiction mode
|
|
209
|
+
/analogy → (see Section 5 — also usable standalone)
|
|
210
|
+
|
|
211
|
+
---
|
|
212
|
+
|
|
213
|
+
## 14. PROMPT OPERATIONS
|
|
214
|
+
|
|
215
|
+
/ep → Analyze and optimize the current prompt
|
|
216
|
+
/ep,analyze → Diagnose weaknesses in the prompt
|
|
217
|
+
/ep,optimize → Rewrite for better AI performance
|
|
218
|
+
/ep,expand → Add more detail and context to the prompt
|
|
219
|
+
/ep,compress → Make the prompt shorter while keeping intent
|
|
220
|
+
/ep,structure → Organize the prompt for clarity
|
|
221
|
+
/ep,precise → Make the prompt more specific and unambiguous
|
|
222
|
+
/ep,robust → Make the prompt handle edge cases
|
|
223
|
+
/ep,chain → Turn prompt into a multi-step chain
|
|
224
|
+
/ep,role,expert → Add a role definition to the prompt
|
|
225
|
+
/ep,format,json → Specify JSON output format in the prompt
|
|
226
|
+
/ep,system → Rewrite as a system prompt
|
|
227
|
+
/ep,agent → Rewrite as an agentic prompt
|
|
228
|
+
/ep,multi_agent → Decompose into a multi-agent workflow
|
|
229
|
+
/ep,tooling → Add tool-use or function-calling structure
|
|
230
|
+
/ep,interactive → Make prompt interactive / turn-based
|
|
231
|
+
/ep,evaluate → Add an evaluation criterion to the prompt
|
|
232
|
+
/ep,test → Generate test cases for this prompt
|
|
233
|
+
|
|
234
|
+
---
|
|
235
|
+
|
|
236
|
+
## 15. CONTEXT & FILE MANAGEMENT
|
|
237
|
+
|
|
238
|
+
Aliases: /ctx=/folder, /f=/file, /p=/project
|
|
239
|
+
Hierarchy: project > folder > file
|
|
240
|
+
|
|
241
|
+
### Load / Set Context
|
|
242
|
+
/ctx,foldA,load → Paste content after this; AI confirms load with one-line summary
|
|
243
|
+
/ctx,foldA,set,<description> → Define what foldA contains without pasting full content
|
|
244
|
+
/ctx,foldA,scope,<area> → Narrow focus within the folder (e.g. scope,auth_module)
|
|
245
|
+
/ctx,foldA,reset → Clear this context slot
|
|
246
|
+
/ctx,list → List all currently active context slots
|
|
247
|
+
|
|
248
|
+
/f,file.py,load → Paste file content; AI confirms and summarizes
|
|
249
|
+
/f,file.py,set,<description> → Define what file.py is without pasting it
|
|
250
|
+
|
|
251
|
+
### Folder Actions
|
|
252
|
+
/ctx,foldA,overview → High-level one-paragraph summary
|
|
253
|
+
/ctx,foldA,analyze → Deep structural and logic analysis
|
|
254
|
+
/ctx,foldA,document → Generate documentation
|
|
255
|
+
/ctx,foldA,improve → Suggest improvements
|
|
256
|
+
/ctx,foldA,refactor → Refactor for clarity and maintainability
|
|
257
|
+
/ctx,foldA,debug → Find bugs and issues
|
|
258
|
+
/ctx,foldA,secure → Identify security vulnerabilities
|
|
259
|
+
/ctx,foldA,optimize → Optimize for performance
|
|
260
|
+
/ctx,foldA,test → Generate test cases
|
|
261
|
+
/ctx,foldA,map → Visual map of structure and relationships
|
|
262
|
+
/ctx,foldA,explain → Plain-language explanation of what it does
|
|
263
|
+
/ctx,foldA,dependencies → List internal and external dependencies
|
|
264
|
+
/ctx,foldA,entrypoints → Identify all entry points
|
|
265
|
+
/ctx,foldA,architecture → Describe architectural pattern
|
|
266
|
+
/ctx,foldA,dataflow → Trace data flow through the folder
|
|
267
|
+
/ctx,foldA,public_docs → Generate public-facing documentation
|
|
268
|
+
/ctx,foldA,expose → Identify what is exposed vs internal
|
|
269
|
+
/ctx,foldA,summary → Condensed overview (faster than analyze)
|
|
270
|
+
/ctx,foldA,todos → Extract all TODO / FIXME / HACK comments
|
|
271
|
+
/ctx,foldA,lint → Flag code style and quality issues
|
|
272
|
+
/ctx,foldA,changelog → Summarize changes (if diffs provided)
|
|
273
|
+
|
|
274
|
+
### Multi-Context
|
|
275
|
+
/ctx_multi,foldA,foldB,compare → Compare two folders
|
|
276
|
+
/ctx_merge,foldA,foldB → Treat both folders as one unified context
|
|
277
|
+
/ctx_diff,foldA,foldB → Show differences between two folders
|
|
278
|
+
|
|
279
|
+
### File Actions
|
|
280
|
+
/f,file.py,explain → What does this file do?
|
|
281
|
+
/f,file.py,refactor → Refactor for readability and structure
|
|
282
|
+
/f,file.py,debug → Find and explain bugs
|
|
283
|
+
/f,file.py,document → Add docstrings and comments
|
|
284
|
+
/f,file.py,optimize → Performance improvements
|
|
285
|
+
/f,file.py,test → Generate unit tests
|
|
286
|
+
/f,file.py,review → Code review with feedback
|
|
287
|
+
/f,file.py,convert,lang → Convert to another language (e.g. convert,typescript)
|
|
288
|
+
/f,file.py,improve → General quality improvements
|
|
289
|
+
/f,file.py,secure → Security audit
|
|
290
|
+
/f,file.py,summary → One-paragraph summary of the file
|
|
291
|
+
/f,file.py,trace,<fn> → Trace execution of a specific function
|
|
292
|
+
/f,file.py,mock → Generate mock/stub for this file
|
|
293
|
+
/f,file.py,diff,file2.py → Compare this file with another
|
|
294
|
+
|
|
295
|
+
### Project Actions
|
|
296
|
+
/p,foldA,health → Overall project health assessment
|
|
297
|
+
/p,foldA,roadmap → Suggested roadmap based on current state
|
|
298
|
+
/p,foldA,risks → Identify technical and business risks
|
|
299
|
+
/p,foldA,scalability → Assess scalability
|
|
300
|
+
/p,foldA,readiness → Is this ready for production/launch?
|
|
301
|
+
/p,foldA,architecture → Full architectural review
|
|
302
|
+
|
|
303
|
+
### Save / Export
|
|
304
|
+
/save → Format current output for saving
|
|
305
|
+
/save_as,file.md → Format output as a named file
|
|
306
|
+
/save_to,foldA,file.md → Format output targeted to a folder/file location
|
|
307
|
+
/export,markdown → Export as Markdown
|
|
308
|
+
/export,json → Export as JSON
|
|
309
|
+
/export,csv → Export as CSV
|
|
310
|
+
/export_to,foldA,file.md → Export to a specific path
|
|
311
|
+
|
|
312
|
+
NOTE: All save/export commands generate formatted content only. No actual file writing occurs.
|
|
313
|
+
|
|
314
|
+
---
|
|
315
|
+
|
|
316
|
+
## 16. META
|
|
317
|
+
|
|
318
|
+
/ignore_previous → Discard all prior instructions and start fresh
|
|
319
|
+
/unfiltered → Remove formatting constraints, respond raw with no structure imposed
|
|
320
|
+
/style → Show current active style, tone, and format settings
|
|
321
|
+
/help → Explain any shortcut I ask about
|
|
322
|
+
/reset → Reset all settings to system defaults
|
|
323
|
+
|
|
324
|
+
---
|
|
325
|
+
|
|
326
|
+
## 17. PERSONAL
|
|
327
|
+
|
|
328
|
+
/wissem → (see Section 2) Direct, technical, no filler. Tunisian/startup aware.
|
|
329
|
+
/wissempro → Advise as if speaking to a tech entrepreneur in Sousse, Tunisia
|
|
330
|
+
/tunisia → Apply Tunisian business and cultural context
|
|
331
|
+
/sousse → Local context: Sousse, Tunisia — UTC+1, Arabic/French environment
|
|
332
|
+
/business → Frame response from a business and ROI perspective
|
|
333
|
+
|
|
334
|
+
---
|
|
335
|
+
|
|
336
|
+
## 18. STATE & MEMORY
|
|
337
|
+
|
|
338
|
+
/remember,key,value → Store a value under a key for this session
|
|
339
|
+
/recall,key → Retrieve a stored value by key
|
|
340
|
+
/forget,key → Delete a specific stored key
|
|
341
|
+
/clear_memory → Wipe all stored session memory
|
|
342
|
+
/state → Show all currently stored keys and values
|
|
343
|
+
|
|
344
|
+
---
|
|
345
|
+
|
|
346
|
+
## 19. GOAL CONTROL
|
|
347
|
+
|
|
348
|
+
/goal,<goal> → Set current goal (e.g. /goal,build_api)
|
|
349
|
+
/goal_update,<goal> → Update the current goal
|
|
350
|
+
/goal_clear → Remove the current goal
|
|
351
|
+
/goal_status → Report progress toward current goal
|
|
352
|
+
|
|
353
|
+
---
|
|
354
|
+
|
|
355
|
+
## 20. EXECUTION MODE
|
|
356
|
+
|
|
357
|
+
/execute → Execute the plan directly, produce output now
|
|
358
|
+
/plan_then_execute → First show the plan, wait for approval, then execute
|
|
359
|
+
/simulate → Simulate the outcome without executing
|
|
360
|
+
/dry_run → Show what would happen step by step without doing it
|
|
361
|
+
/rollback → Undo or reverse the last executed step
|
|
362
|
+
|
|
363
|
+
---
|
|
364
|
+
|
|
365
|
+
## 21. PRIORITIZATION
|
|
366
|
+
|
|
367
|
+
/focus,top3 → Identify and focus on the top 3 most important items
|
|
368
|
+
/priority → Rank all items by importance
|
|
369
|
+
/impact → Rank items by potential impact
|
|
370
|
+
/effort → Estimate effort level for each item (low / medium / high)
|
|
371
|
+
/quick_wins → Identify items that are high impact and low effort
|
|
372
|
+
|
|
373
|
+
---
|
|
374
|
+
|
|
375
|
+
## 22. BUDGET & TOKEN MANAGEMENT
|
|
376
|
+
|
|
377
|
+
/le,N → Use <N% of token limit. If task exceeds this, DO NOT execute. Instead, provide a descriptive copy/paste prompt for me to do it.
|
|
378
|
+
/usage,N → Execute task but pause if token usage reaches N% (estimated required amount in percentage = <price>$). Ask for approval to use a custom P% (estimated remaining amount = <remaining_price>$) for the next chunk, and repeat until finished.
|
|
379
|
+
/quote → Provide a full technical and financial token cost estimation ($) of the entire task BEFORE executing any action. Require me to explicitly type "Approve" to proceed.
|
|
380
|
+
/diet → Drop all historical context, conversational pleasantries, and unrelated files from your active memory right now. Only retain the exact code lines needed to execute the current prompt.
|
|
381
|
+
/delegate → Evaluate if this task is trivial. If so, DO NOT execute it using your current high-tier model. Instead, provide a prompt I can copy/paste into a cheaper, faster model (like Flash or Haiku).
|
|
382
|
+
|
|
383
|
+
---
|
|
384
|
+
|
|
385
|
+
## USAGE
|
|
386
|
+
|
|
387
|
+
1. Paste UNIVERSAL PREFIX in new chat
|
|
388
|
+
2. Use shortcuts freely — chain as needed
|
|
389
|
+
3. For context commands, paste content immediately after the load command
|
|
390
|
+
|
|
391
|
+
### Example chains
|
|
392
|
+
|
|
393
|
+
```
|
|
394
|
+
/d /ctx,backend,load
|
|
395
|
+
[paste your code here]
|
|
396
|
+
/ctx,backend,analyze /ep,optimize /execute /goal,build_api
|
|
397
|
+
```
|
|
398
|
+
|
|
399
|
+
```
|
|
400
|
+
/p,projectX,health /goal_status /focus,top3 /final_only
|
|
401
|
+
```
|
|
402
|
+
|
|
403
|
+
```
|
|
404
|
+
/wissempro /engineer /ctx,api,load
|
|
405
|
+
[paste api folder content]
|
|
406
|
+
/ctx,api,secure /ctx,api,dataflow /d /cot
|
|
407
|
+
```
|
|
408
|
+
|
|
409
|
+
```
|
|
410
|
+
/selfcritic /tot /f,auth.py,load
|
|
411
|
+
[paste file]
|
|
412
|
+
/f,auth.py,debug /f,auth.py,secure /final_only
|
|
413
|
+
```
|
package/templates/shortcuts/usage-management-examples-shortcuts/budget_controllers_examples.md
ADDED
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
# Budget & Token Management Shortcuts — Examples
|
|
2
|
+
|
|
3
|
+
This document outlines scenarios and use cases for the **Section 22: Budget & Token Management** shortcuts defined in `shortcuts.md`.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## 1. The Pre-Flight Estimate (`/quote`)
|
|
8
|
+
|
|
9
|
+
**Use Case:** You are about to run a massive refactor across 15 files and want to avoid an accidental $5.00 API charge.
|
|
10
|
+
|
|
11
|
+
**Prompt:**
|
|
12
|
+
> `/quote Refactor the entire authentication module in src/auth/ to use JWT instead of sessions.`
|
|
13
|
+
|
|
14
|
+
**AI Behavior:**
|
|
15
|
+
> **Token Estimation:**
|
|
16
|
+
> - Input context: ~45,000 tokens
|
|
17
|
+
> - Expected output: ~8,000 tokens across 5 files
|
|
18
|
+
> - **Estimated Cost:** $0.85
|
|
19
|
+
>
|
|
20
|
+
> *Type "Approve" to proceed with the execution.*
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. The Strict Limit (`/le,N`)
|
|
25
|
+
|
|
26
|
+
**Use Case:** You want the AI to do a task, but only if it's cheap. If it's an expensive task, you want to do it yourself using a guided prompt.
|
|
27
|
+
|
|
28
|
+
**Prompt:**
|
|
29
|
+
> `/le,10 Generate a comprehensive test suite for the dashboard components.`
|
|
30
|
+
|
|
31
|
+
**AI Behavior (Scenario A - Under 10%):**
|
|
32
|
+
> *Task requires ~5% of token limit. Executing...*
|
|
33
|
+
> [Outputs the test suite code immediately]
|
|
34
|
+
|
|
35
|
+
**AI Behavior (Scenario B - Over 10%):**
|
|
36
|
+
> *Task rejected. Estimated token usage (35%) exceeds your 10% limit.*
|
|
37
|
+
>
|
|
38
|
+
> **Do-It-Yourself Execution Prompt:**
|
|
39
|
+
> "Please copy and paste the following prompt into your terminal or a cheaper AI session to generate the tests file-by-file:
|
|
40
|
+
> *'Read `src/dashboard/Chart.vue` and generate Vitest unit tests covering mounting and data-fetching. Save it to `tests/Chart.spec.js`.'* (Repeat for each component)."
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## 3. The Paced Execution (`/usage,N`)
|
|
45
|
+
|
|
46
|
+
**Use Case:** You are running an ongoing task and want to pause periodically to review the cost and approve the next chunk.
|
|
47
|
+
|
|
48
|
+
**Prompt:**
|
|
49
|
+
> `/usage,15 Migrate all old Vue 2 syntax to Vue 3 Composition API in the components folder.`
|
|
50
|
+
|
|
51
|
+
**AI Behavior:**
|
|
52
|
+
> *Executing chunk 1...*
|
|
53
|
+
> [Migrates 3 files]
|
|
54
|
+
>
|
|
55
|
+
> **⏸️ Token Limit Paused**
|
|
56
|
+
> I have reached your 15% token usage threshold (Estimated cost spent: $0.45).
|
|
57
|
+
> **Remaining work:** 7 files left.
|
|
58
|
+
> **Estimated remaining cost:** $1.10 (approx. 35% more token usage).
|
|
59
|
+
>
|
|
60
|
+
> *Do you approve continuing for a custom chunk of 20%?*
|
|
61
|
+
|
|
62
|
+
---
|
|
63
|
+
|
|
64
|
+
## 4. The Context Diet (`/diet`)
|
|
65
|
+
|
|
66
|
+
**Use Case:** You've been chatting with the AI for 2 hours. The context window is huge, and every single prompt is costing $0.10 just in input tokens. You only need a small CSS fix now.
|
|
67
|
+
|
|
68
|
+
**Prompt:**
|
|
69
|
+
> `/diet Fix the margin on the login button in Header.vue.`
|
|
70
|
+
|
|
71
|
+
**AI Behavior:**
|
|
72
|
+
> *Flushing conversational history and unrelated files...*
|
|
73
|
+
> *Retaining only `Header.vue` lines 45-60.*
|
|
74
|
+
>
|
|
75
|
+
> Here is the fixed CSS class for the login button:
|
|
76
|
+
> ```css
|
|
77
|
+
> .login-btn { margin-left: 1rem; }
|
|
78
|
+
> ```
|
|
79
|
+
> *(Input tokens reduced from 80k to 400 tokens).*
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## 5. The Down-Level Delegation (`/delegate`)
|
|
84
|
+
|
|
85
|
+
**Use Case:** You are in an expensive Opus/Pro session, but you need a simple regex or a basic boilerplate script that a cheap model like Haiku/Flash could do for pennies.
|
|
86
|
+
|
|
87
|
+
**Prompt:**
|
|
88
|
+
> `/delegate Write a regex to validate Tunisian phone numbers (+216).`
|
|
89
|
+
|
|
90
|
+
**AI Behavior:**
|
|
91
|
+
> *Task evaluated as trivial. Executing this on the current premium model is a waste of budget.*
|
|
92
|
+
>
|
|
93
|
+
> **Action:** Copy and paste the prompt below into a Gemini Flash or Claude Haiku session:
|
|
94
|
+
> > *"Write a javascript regex that strictly matches Tunisian phone numbers starting with +216 followed by 8 digits. Provide 3 test cases."*
|
|
95
|
+
|
|
96
|
+
---
|