with one click
designing-syntax
// Design custom syntax elements with reuse-first approach for workflow orchestration. Use when user needs custom operators, checkpoints, or syntax patterns not available in core syntax.
// Design custom syntax elements with reuse-first approach for workflow orchestration. Use when user needs custom operators, checkpoints, or syntax patterns not available in core syntax.
Use when user says "create workflow", "create a workflow", "design workflow", "orchestrate", "automate multiple steps", "coordinate agents", "multi-agent workflow". Creates orchestration workflows from natural language using Socratic questioning to plan multi-agent workflows with visualization.
Use when user provides workflow syntax with arrows (-> || ~>), says "run workflow", "execute workflow", "run this", mentions step1 -> step2 patterns. Executes orchestration workflows with real-time visualization, steering, and error recovery.
Manages temporary and defined agents including creation, promotion, cleanup, and namespacing. Use when user creates custom agents, asks about agent lifecycle, temp agents, or agent management.
Use and customize workflow templates for common scenarios. Use when user wants to use a template, asks about available templates, or wants to customize existing workflows.
Debug workflow execution issues including syntax errors, agent failures, variable problems, and execution errors. Use when workflows fail, produce unexpected results, or user asks for debugging help.
Create and execute temporary scripts (Python, Node.js, shell) during workflow execution for API integrations, data processing, and custom tools. Use when user needs to interact with external APIs, process data with specific libraries, or create temporary executable code.
| name | designing-syntax |
| description | Design custom syntax elements with reuse-first approach for workflow orchestration. Use when user needs custom operators, checkpoints, or syntax patterns not available in core syntax. |
I design custom syntax elements following a reuse-first approach. Only create new syntax when existing patterns don't fit.
I activate when you:
Before creating new syntax, I check:
->, ||, ~>, @, [...]library/syntax/Only create new if no match exists.
Custom flow control operators.
Example: => (merge with dedup)
---
symbol: =>
description: Merge with deduplication
---
Executes left then right, removes duplicates from combined output.
Reusable sub-workflows.
Example: @deep-review
---
name: @deep-review
type: action
---
Expansion: [code-reviewer:"security" || code-reviewer:"style"] -> merge
Manual approval gates with prompts.
Example: @security-gate
---
name: @security-gate
type: checkpoint
---
Prompt: Review security findings. Verify no critical vulnerabilities.
Custom conditional logic.
Example: if security-critical
---
name: if security-critical
description: Check if changes affect security code
evaluation: Modified files in: auth/, crypto/, permissions/
---
Reusable loop patterns.
Example: retry-with-backoff(n)
---
name: retry-with-backoff
type: loop
params: [attempts]
---
Pattern: @try -> operation -> (if failed)~> wait -> @try
ā DO:
@security-gate not @check)ā DON'T:
library/syntax/
āāā operators/ # Flow control operators
āāā actions/ # Reusable sub-workflows
āāā checkpoints/ # Approval gates
āāā conditions/ # Custom conditionals
āāā loops/ # Loop patterns
āāā aggregators/ # Result combination
āāā guards/ # Pre-execution checks
Need custom syntax? Describe the pattern you keep repeating!