User Requirements → Case Location → Process Design → User Confirmation → DSL Generation → Delivery

Please tell me the basic information about the Dify workflow you want to create:

1. **Workflow Name** (English, use hyphens, e.g., document-processor)
2. **One-sentence Description**: What does this workflow do?
3. **Application Type**:
   - workflow: Batch processing task, single-round execution
   - advanced-chat: Advanced chat mode, supports multi-round conversations
   - chatflow: Conversational application, simple multi-round interaction
4. **Target Users**: Who will use this workflow?

5. **Input Method**: How will users provide input?
   - Text input (short text/long text)
   - File upload (image/PDF/audio-video/document)
   - Mixed input

6. **Core Processing**: What processing steps does the workflow need to perform?
   - Data preprocessing → Core processing → Result output
   - Please describe each step as much as possible

7. **Output Format**: What results will be returned finally?
   - Text response
   - Structured data (JSON/Markdown table)
   - File (image/PDF/audio)
   - Mixed output

8. **Large Model Selection**:
   - Model Provider: OpenAI / Anthropic / Domestic Models (SiliconFlow/Qwen/ZeroOneAI, etc.)
   - Model Name: e.g., gpt-4o, deepseek-V3, qwen-max
   - Parameter Settings: temperature (creativity 0-1), max_tokens, etc.

9. **Tools/Plugins**:
   - Built-in Tools: Code execution, knowledge retrieval, HTTP request, TTS, etc.
   - Third-party Plugins: PDF processing, database connection, etc.
   - MCP Service: Is external MCP tool integration needed?

10. **Knowledge Base (Optional)**:
    - Is knowledge base access needed?
    - Knowledge Base ID and Name
    - Retrieval Strategy Configuration

11. **Process Branches**: Are there conditional branches? (Yes/No)
    - If yes, what are the branch conditions? (e.g., different processing paths based on user intent classification)
12. **Loop Processing**: Is iterative processing of batch data needed? (Yes/No)
    - e.g., Batch processing multiple files, processing each item in a list
13. **Session State**: Is session state preservation needed? (Yes/No)
    - e.g., Recording user preferences, cross-round variable transfer
14. **Error Handling**: How to handle failures?
    - Terminate the process and report an error
    - Continue executing other branches
    - Return default results

⚠️ **Critical Step: You must switch to the skill directory before searching!**

**Step 1: Switch to the skill directory (Mandatory)**
```bash
cd "c:\Users\14429\.claude\skills\dify_creator"

undefined

1. Search and read `organized_dsl/INDEX.md`
2. Locate relevant classification directories based on the functional type of user requirements
3. Search for DSL cases with similar functions in the corresponding directory (using `organized_dsl/**/*.yml`)

Based on your requirements, I have located the following relevant classifications:

| Classification | Directory Path |
|------|----------|
| Content Creation | `01_Content_Generation_Creation/` |
| Image Generation | `02_Image_Generation_Design/` |
| Video Generation | `03_Video_Generation/` |
| Data Analysis | `04_Data_Analysis_Visualization/` |
| Document Processing | `05_Document_Processing_OCR/` |
| Knowledge Base RAG | `06_Knowledge_Base_RAG/` |
| Agent Tools | `07_Agent_Tool_Calling/` |
| Education & Learning | `08_Education_Learning/` |
| Business & Office | `09_Business_Office/` |
| Multimedia Processing | `10_Multimedia_Processing/` |
| Code Development | `11_Code_Development/` |
| Creative Entertainment | `12_Creative_Entertainment/` |

The following reference cases related to your requirements have been found:

undefined

I have read the reference cases, and here is the key configuration extraction:

**Node Structure:**

**Key Configuration References:**
- LLM prompt template: ...
- Variable transfer method: ...
- Conditional branch logic: ...

Based on your requirements, I have designed the following workflow structure:

┌─────────────┐
│   Start Node   │  Input: {{input_var}}
└──────┬──────┘
       ↓
┌─────────────┐
│  Preprocessing Node  │  Function: Data cleaning/format conversion
└──────┬──────┘
       ↓
┌─────────────┐
│   Core Processing   │  Function: LLM calling/tool execution
│   (Branch Judgment) │  Condition: {{condition}}
└──────┬──────┘
   ┌────┴────┐
   ↓         ↓
┌──────┐  ┌──────┐
│Branch A │  │Branch B │
└────┬─┘  └────┬─┘
   │          │
   └────┬─────┘
        ↓
┌─────────────┐
│   Result Processing   │  Function: Formatting/aggregation
└──────┬──────┘
       ↓
┌─────────────┐
│   Output Node   │  Output: {{output_var}}
└─────────────┘

---

undefined

undefined

The following items must be confirmed before generating the DSL:

- [ ] User explicitly replied "Confirm" or "Continue"
- [ ] All node configurations have been checked with the user
- [ ] Model and parameters have been approved by the user
- [ ] Output format meets user requirements

**If the above conditions are not met, do NOT proceed to Step 5!**

Based on your feedback, I have made the following adjustments:

1. Modified the LLM node Prompt template
2. Added new conditional branches
3. Adjusted variable transfer logic

Please confirm again.

Confirmation before generating DSL:

- [ ] Selected reference case file (Path: xxx/xxx.yml)
- [ ] Read the node configuration reference guide
- [ ] Obtained user's "Confirm" reply
- [ ] All node configurations have been determined

**If the above steps are not completed, do NOT generate the DSL!**

app:
  description: '{{description}}'
  icon: '{{icon}}'
  icon_background: '{{icon_background}}'
  mode: '{{mode}}'
  name: '{{name}}'
  use_icon_as_answer_icon: false
kind: app
version: {{version-number-of-reference-case}}
workflow:
  conversation_variables: []
  environment_variables: []
  features:
    file_upload: {}
    # ... Other function configurations
  graph:
    edges: []
    nodes: []
  viewport: {}

undefined

undefined

When generating workflows, please strictly follow the following rules:

1. **First Find Reference Cases**
   - Search `organized_dsl/**/*.yml` to find DSL files with similar functions
   - Search `organized_dsl/Dify_DSL_Complete Node Reference Guide.md` to view node configuration instructions

2. **Node Structure Must Be Complete**
   Each node must include:
   - `id`: Unique identifier
   - `data.type`: Node type
   - `data.title`: Node title
   - `position`: Canvas position {x, y}
   - `width`/`height`: Node size (optional)

3. **Do NOT Write from Scratch**
   - ❌ Do not write nodes based on memory or imagination
   - ✅ Must copy the structure of reference cases and replace key fields

4. **Special Notes**
   - **Iteration Nodes**: Must include iteration-start sub-node and all necessary markers
   - **LLM Nodes**: Must include model.provider, model.name, prompt_template
   - **HTTP Requests**: Must include correct authorization and body configurations
   - **Variable References**: Must use the format `{{#node-id.variable#}}`

undefined

version: {{version-number-of-reference-case}}  # ✅ Consistent with reference case

undefined

**Handling of Failed Inspections:**
1. Locate the problematic node
2. Read the reference case
3. Correct the node configuration
4. Re-check until passed

app:
  description: 'Application Description'
  icon: 🤖
  icon_background: '#FFEAD5'
  mode: workflow|advanced-chat|chatflow
  name: Application Name
  use_icon_as_answer_icon: false
kind: app
version: {{version-number-of-reference-case}}
workflow:
  conversation_variables: []   # Session variables
  environment_variables: []    # Environment variables
  features:
    file_upload:               # File upload configuration
      enabled: false
      # ... Detailed configuration
    opening_statement: ''      # Opening statement
    retriever_resource:        # Retrieval resource
      enabled: true
    text_to_speech:            # TTS configuration
      enabled: false
  graph:
    edges: []                  # Connection list
    nodes: []                  # Node list
  viewport:                    # View position
    x: 0
    y: 0
    zoom: 1
dependencies: []               # Plugin dependencies

undefined

---

undefined

undefined

app:
  description: 'Chinese-English Translation Workflow'
  icon: 🌐
  icon_background: '#E3F2FD'
  mode: workflow
  name: zh-en-translator
kind: app
version: {{version-number-of-reference-case}}
workflow:
  graph:
    edges:
    - source: '1741011655068'
      target: '1741011662463'
      type: custom
    - source: '1741011662463'
      target: llm
      type: custom
    - source: llm
      target: answer
      type: custom
    nodes:
    - data:
        title: Start
        type: start
        variables:
        - variable: text
          type: paragraph
          label: Input Chinese Text
          required: true
      id: '1741011655068'
      position: {x: 0, y: 263}
    - data:
        context:
          enabled: false
        model:
          provider: siliconflow
          name: internlm2_5-7b-chat
          mode: chat
        prompt_template:
        - role: system
          text: 'Please translate the following Chinese text into English, only output the translation result: {{#1741011655068.text#}}'
        title: LLM Translation
        type: llm
      id: llm
      position: {x: 382, y: 263}
    - data:
        answer: '{{#llm.text#}}'
        title: Translation Result
        type: answer
      id: answer
      position: {x: 690, y: 263}

organized_dsl/
├── 01_Content_Generation_Creation/
├── 02_Image_Generation_Design/
├── 03_Video_Generation/
├── 04_Data_Analysis_Visualization/
├── 05_Document_Processing_OCR/
├── 06_Knowledge_Base_RAG/
├── 07_Agent_Tool_Calling/
├── 08_Education_Learning/
├── 09_Business_Office/
├── 10_Multimedia_Processing/
├── 11_Code_Development/
├── 12_Creative_Entertainment/
├── 13_Information_Aggregation/
├── 14_Reference_Examples/
├── INDEX.md                    # Case index (search organized_dsl/INDEX.md)
└── Dify_DSL_Complete Node Reference Guide.md  # Node configuration reference (search organized_dsl/Dify_DSL_Complete Node Reference Guide.md)

undefined

undefined

- data:
    positionAbsolute: false      # ✅ Mandatory
    selected: false              # ✅ Mandatory
    title: "Node Name"
    type: "Node Type"
    # ... Other fields
  height: 52
  id: 'node-id'
  position:
    x: 0
    y: 0
  width: 242

- data:
    isInIteration: false         # ✅ Mandatory
    selected: false              # ✅ Mandatory
    sourceType: "Source Node Type"
    targetType: "Target Node Type"
  id: "edge-id"
  source: "source-node-id"
  sourceHandle: "source"
  target: "target-node-id"
  targetHandle: "target"
  type: "custom|true|false|isInIteration"

undefined

undefined

undefined

undefined

undefined

---