how2useliteflow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

LiteFlow 助手

LiteFlow Assistant

本 skill 帮助用户用 AI 使用 LiteFlow（v2.16.X）。它内置了从官方文档与源码蒸馏出的绝大部分用法细节与代码细节，并规定了"答不到时怎么办"的严格流程。

版本对齐：本 skill 内容对齐 LiteFlow v2.16.X（约 v2.16.0）。不同小版本细节可能差异；作答时如涉及具体版本会标注。

This skill helps users use LiteFlow (v2.16.X) with AI. It builds in most usage details and code details distilled from official documentation and source code, and defines strict procedures for "what to do when unable to answer".

Version Alignment: The content of this skill aligns with LiteFlow v2.16.X (approximately v2.16.0). Details may vary across minor versions; the specific version will be noted when answering if involved.

一、何时使用

1. When to Use

用户提到以下任一场景时启用本 skill：

写组件（普通/选择/布尔/次数循环/迭代循环组件，或声明式组件）。
写 EL 规则（THEN/WHEN/IF/SWITCH/FOR/WHILE/ITERATOR/CATCH/RETRY/TIMEOUT/PRE/FINALLY/AND/OR/NOT、tag/data/bind 等）。
上下文（数据上下文、别名、参数注入、表达式取参）。
脚本组件（Groovy/JS/Python/QLExpress/Lua/Aviator/Kotlin/Java 等）。
规则配置源（本地文件/SQL/ZK/Nacos/Etcd/Apollo/Redis/自定义）。
配置项（SpringBoot/Spring/Solon/纯代码）。
执行器（FlowExecutor 的执行方法、LiteflowResponse）。
编写 / 调试测试用例（JUnit5 + SpringBoot 测试范式、
```
BaseTest
```
全局状态清理、各功能的官方测试模块）。
AI Agent 编排（
```
liteflow-react-agent
```
：把 ReAct Agent 当组件编排进 EL、模型/凭据配置、自定义工具、流式输出、会话/记忆）。
调试/报错/链路排查、热刷新、线程池、动态构造、决策路由、生命周期、降级/回滚/切面等高级特性。
询问 LiteFlow 源码实现/代码细节（FlowExecutor、FlowBus、DataBus、Condition 树、两阶段解析等）。

Activate this skill when the user mentions any of the following scenarios:

Writing components (normal/selection/boolean/loop-count/iterator-loop components, or declarative components).
Writing EL rules (THEN/WHEN/IF/SWITCH/FOR/WHILE/ITERATOR/CATCH/RETRY/TIMEOUT/PRE/FINALLY/AND/OR/NOT, tag/data/bind, etc.).
Context (data context, aliases, parameter injection, expression parameter retrieval).
Script components (Groovy/JS/Python/QLExpress/Lua/Aviator/Kotlin/Java, etc.).
Rule configuration sources (local files/SQL/ZK/Nacos/Etcd/Apollo/Redis/custom).
Configuration items (SpringBoot/Spring/Solon/pure code).
Executors (execution methods of FlowExecutor, LiteflowResponse).
Writing/debugging test cases (JUnit5 + SpringBoot testing paradigm,
```
BaseTest
```
global state cleanup, official test modules for each feature).
AI Agent orchestration (
```
liteflow-react-agent
```
: orchestrating ReAct Agent as a component into EL, model/credential configuration, custom tools, streaming output, session/memory).
Advanced features such as debugging/error reporting/link troubleshooting, hot refresh, thread pools, dynamic construction, decision routing, lifecycle, downgrade/rollback/aspect, etc.
Asking about LiteFlow source code implementation/code details (FlowExecutor, FlowBus, DataBus, Condition tree, two-stage parsing, etc.).

二、回答 LiteFlow 问题时的决策流程（必须严格遵守）

2. Decision Process for Answering LiteFlow Questions (Must Be Strictly Followed)

这是最重要的章节。绝不杜撰、绝不用网络内容充当 LiteFlow 行为依据。

第 0 步 — 先查本文件速查表（下方第三节）：约 80% 的常见问题（EL 算子、组件类型、执行 API、核心配置）可直接作答，无需加载任何文件。

第 1 步 — 加载对应 reference：速查表不够时，按"知识地图"（第四节）用

Read

打开

references/<文件>.md

。绝大多数用法与代码细节问题在此解决。作答时标注来源 reference 文件名。

第 2 步 — 本地源码：若 reference 也未覆盖（通常是更冷门或更深层的源码细节），先探测本地 LiteFlow 仓库，按优先级：环境变量

LITEFLOW_REPO

→

~/openSource/liteFlow

→

./liteFlow

。

用
```
scripts/source-lookup.sh path
```
探测（找到则打印绝对路径；找不到退出码 2）。

找到后用

scripts/source-lookup.sh grep <关键词>

（搜

*.java

）/

grepall

find <名字>

show <相对路径> [a-b]

定位，引用
path:line
作答。

第 3 步 — 请求克隆（必须先征得用户同意）：本地也没有、或问题明确需要线上/最新源码时，停下来告知用户并请求确认，例如：

"这部分内容不在我的内置知识里。我可以 git clone LiteFlow 官方仓库（gitee.com/dromara/liteFlow，默认
v2.16.0
tag，与内置内容对齐）到临时目录，从源码里确认后再回答。是否允许？"

用户同意 → 运行

scripts/source-lookup.sh clone

（克隆到缓存

~/.cache/liteflow-skill

），再用

grep/find/show

定位，引用
path:line
作答。

用户拒绝 / 未明确同意 → 如实说明"暂时无法确认，不建议臆测"，不要自行克隆、不要杜撰、不要用网络搜索结果充当 LiteFlow 的行为依据。

This is the most important section. Never fabricate, never use online content as the basis for LiteFlow's behavior.

Step 0 — Check the quick reference in this document first (Section 3 below): About 80% of common questions (EL operators, component types, execution APIs, core configurations) can be answered directly without loading any files.

Step 1 — Load the corresponding reference: When the quick reference is insufficient, use

Read

to open

references/<file>.md

according to the "Knowledge Map" (Section 4). Most usage and code detail issues are resolved here. Mark the source reference file name when answering.

Step 2 — Local source code: If the reference does not cover the issue (usually more obscure or deeper source code details), first detect the local LiteFlow repository, in the priority order: environment variable

LITEFLOW_REPO

→

~/openSource/liteFlow

→

./liteFlow

Use
```
scripts/source-lookup.sh path
```
to detect (prints the absolute path if found; exit code 2 if not found).

After finding it, use

scripts/source-lookup.sh grep <keyword>

(search

*.java

) /

grepall

find <name>

show <relative path> [a-b]

to locate, answer with reference to
path:line
.

Step 3 — Request cloning (must obtain user consent first): If the local repository is not available, or the issue clearly requires online/latest source code, stop and inform the user to request confirmation, for example:

"This content is not in my built-in knowledge. I can git clone the official LiteFlow repository (gitee.com/dromara/liteFlow, default
v2.16.0
tag, aligned with built-in content) to a temporary directory, confirm from the source code and then answer. Is this allowed?"

User agrees → Run
```
scripts/source-lookup.sh clone
```
(clone to cache
```
~/.cache/liteflow-skill
```
), then use
```
grep/find/show
```
to locate, answer with reference to
path:line
.
User refuses / does not explicitly agree → Truthfully state "Cannot confirm temporarily, it is not recommended to speculate", do not clone on your own, do not fabricate, do not use web search results as the basis for LiteFlow's behavior.

绝对禁止

Absolute Prohibitions

在未读到对应 reference 或源码前，凭记忆编造 API、方法名、参数、配置项、默认值或行为。
把网络搜索（WebSearch/网页）结果当作 LiteFlow 真实行为的依据（除非用户明确要求联网查证）。
在用户未明确同意前执行
```
git clone
```
或
```
source-lookup.sh clone
```
。

Fabricate APIs, method names, parameters, configuration items, default values or behaviors based on memory before reading the corresponding reference or source code.
Treat web search (WebSearch/webpage) results as the basis for LiteFlow's actual behavior (unless the user explicitly requests online verification).
Execute
```
git clone
```
or
```
source-lookup.sh clone
```
without the user's explicit consent.

三、高频速查（直接作答，无需加载 reference）

3. High-Frequency Quick Reference (Answer Directly, No Need to Load Reference)

以下均经官方文档 + 源码核对。下方若仍不够，去对应 reference 查细节。

All the following content has been verified against official documentation + source code. If the following is still insufficient, check the corresponding reference for details.

3.1 EL 算子速查（详见

references/el-rules.md

）

3.1 EL Operator Quick Reference (See

references/el-rules.md

for details)

算子	语义	最小示例
`THEN(a,b,c)` （别名 `SER` ）	串行	`THEN(a, b, c)`
`WHEN(a,b,c)` （别名 `PAR` ）	并行（异步）	`WHEN(a, b, c)`
`IF(x, a, b)`	条件（x 为布尔组件/表达式；可 `ELIF` / `ELSE` ）	`IF(x, a, b)`
`SWITCH(x).to(a,b,c)`	选择（x 返回目标 nodeId）	`SWITCH(x).to(a, b, c)`
`FOR(x).DO(y)`	次数循环（x 返回次数）	`FOR(n).DO(a)`
`WHILE(x).DO(y)`	条件循环	`WHILE(x).DO(a)`
`ITERATOR(x).DO(y)`	迭代循环（x 返回 Iterator）	`ITERATOR(it).DO(a)`
`BREAK(x)`	循环中断（配合循环）	`WHILE(x).DO(a).BREAK(b)`
`CATCH(a).DO(b)`	捕获 a 的异常交 b 处理	`CATCH(a).DO(b)`
`RETRY(a).times(n)`	重试	`RETRY(a).times(3)`
`a.maxWaitSeconds(5)` / `maxWaitMilliseconds(...)`	超时控制	`WHEN(a,b).maxWaitSeconds(5)`
`PRE(a,b)` / `FINALLY(a,b)`	前置 / 后置（始终执行）	`THEN(PRE(a), b, FINALLY(c))`
`AND(a,b)` / `OR(a,b)` / `NOT(a)`	布尔与/或/非（用于 IF 条件）	`IF(AND(a,b), c, d)`
`let`	子变量（复用片段）	见 el-rules.md
节点修饰	`tag` / `data` / `bind` / `id`	`a.tag("t").data("k","v")`
链路继承	`extends`	见 el-rules.md

WHEN 并行修饰：

ignoreError

（忽略错误继续）、

any

（任一完成即结束）、

must(a,b)

（必须完成的节点）、

percentage(n)

（按比例）、是否独立线程池等——细节见 el-rules.md。

规则写在哪：

flow.xml

flow.json

flow.el

等规则文件中

<chain name="..."> ... </chain>

，结尾分号可省略；支持注释。

Operator	Semantics	Minimal Example
`THEN(a,b,c)` (alias `SER` )	Serial	`THEN(a, b, c)`
`WHEN(a,b,c)` (alias `PAR` )	Parallel (asynchronous)	`WHEN(a, b, c)`
`IF(x, a, b)`	Condition (x is a boolean component/expression; supports `ELIF` / `ELSE` )	`IF(x, a, b)`
`SWITCH(x).to(a,b,c)`	Selection (x returns target nodeId)	`SWITCH(x).to(a, b, c)`
`FOR(x).DO(y)`	Count loop (x returns the number of times)	`FOR(n).DO(a)`
`WHILE(x).DO(y)`	Condition loop	`WHILE(x).DO(a)`
`ITERATOR(x).DO(y)`	Iterator loop (x returns Iterator)	`ITERATOR(it).DO(a)`
`BREAK(x)`	Loop interruption (used with loops)	`WHILE(x).DO(a).BREAK(b)`
`CATCH(a).DO(b)`	Catch exceptions of a and pass to b for processing	`CATCH(a).DO(b)`
`RETRY(a).times(n)`	Retry	`RETRY(a).times(3)`
`a.maxWaitSeconds(5)` / `maxWaitMilliseconds(...)`	Timeout control	`WHEN(a,b).maxWaitSeconds(5)`
`PRE(a,b)` / `FINALLY(a,b)`	Pre / Post (always executed)	`THEN(PRE(a), b, FINALLY(c))`
`AND(a,b)` / `OR(a,b)` / `NOT(a)`	Boolean AND/OR/NOT (used for IF conditions)	`IF(AND(a,b), c, d)`
`let`	Sub-variable (reuse fragments)	See el-rules.md
Node modifiers	`tag` / `data` / `bind` / `id`	`a.tag("t").data("k","v")`
Link inheritance	`extends`	See el-rules.md

WHEN Parallel Modifiers:

ignoreError

(ignore errors and continue),

any

(end when any completes),

must(a,b)

(nodes that must complete),

percentage(n)

(by proportion), whether to use an independent thread pool, etc. — details see el-rules.md.

Where to write rules: In rule files such as

flow.xml

flow.json

flow.el

within

<chain name="..."> ... </chain>

, the trailing semicolon can be omitted; comments are supported.

3.2 组件类型速查（详见

references/components.md

）

3.2 Component Type Quick Reference (See

references/components.md

for details)

想要的行为	用哪种组件	关键方法/注解
普通处理	`NodeComponent`	`process()`
多路选择（返回 nodeId）	`NodeSwitchComponent`	`processSwitch()` 返回字符串
布尔判断（IF/WHILE 条件）	`NodeBooleanComponent`	`processBoolean()` 返回 boolean
次数循环	`NodeForComponent`	`processFor()` 返回次数
迭代循环	`NodeIteratorComponent`	`processIterator()` 返回 `Iterator`
声明式（不继承基类）	`@LiteflowComponent("id")` 注册 Bean	方法加 `@LiteflowMethod(PROCESS, nodeType=...)` ；或类上加 `@LiteflowCmpDefine(类型)` 声明 nodeType

注册：继承式/声明式组件都用
```
@LiteflowComponent("nodeId")
```
（也可用
```
name
```
设别名）。
组件生命周期钩子（继承式可覆写，声明式用
```
@LiteflowMethod
```
）：
```
isAccess()
```
（准入，false 则跳过）、
```
beforeProcess()
```
/
```
afterProcess()
```
、
```
onSuccess()
```
/
```
onError()
```
、
```
isContinueOnError()
```
、
```
isEnd()
```
、
```
rollback()
```
。

组件内取上下文：

this.getContextBean(XxxContext.class)

this.getFirstContextBean()

；取流程入参：

this.getRequestData()

。

Desired Behavior	Component Type	Key Method/Annotation
Normal processing	`NodeComponent`	`process()`
Multi-way selection (returns nodeId)	`NodeSwitchComponent`	`processSwitch()` returns string
Boolean judgment (IF/WHILE condition)	`NodeBooleanComponent`	`processBoolean()` returns boolean
Count loop	`NodeForComponent`	`processFor()` returns count
Iterator loop	`NodeIteratorComponent`	`processIterator()` returns `Iterator`
Declarative (no base class inheritance)	Register Bean with `@LiteflowComponent("id")`	Add `@LiteflowMethod(PROCESS, nodeType=...)` to the method; or declare nodeType with `@LiteflowCmpDefine(type)` on the class

Registration: Both inherited/declarative components use
```
@LiteflowComponent("nodeId")
```
(can also use
```
name
```
to set alias).
Component lifecycle hooks (overridable for inherited components, use
```
@LiteflowMethod
```
for declarative components):
```
isAccess()
```
(admission, skip if false),
```
beforeProcess()
```
/
```
afterProcess()
```
,
```
onSuccess()
```
/
```
onError()
```
,
```
isContinueOnError()
```
,
```
isEnd()
```
,
```
rollback()
```
.

Retrieve context within component:

this.getContextBean(XxxContext.class)

this.getFirstContextBean()

; Retrieve process input parameters:

this.getRequestData()

3.3 执行 API 速查（详见

references/executor.md

）

3.3 Execution API Quick Reference (See

references/executor.md

for details)

java

@Resource private FlowExecutor flowExecutor;

// 同步执行：chainId + 入参 + 多个上下文 Class（框架实例化）
LiteflowResponse resp = flowExecutor.execute2Resp("chain1", param, OrderContext.class, UserContext.class);

// 直接执行一段 EL（v2.15.0+，无需规则文件）
LiteflowResponse resp2 = flowExecutor.execute2RespWithEL("THEN(a, b, c)", param, OrderContext.class);

// 异步 / 路由
Future<LiteflowResponse> f = flowExecutor.execute2Future("chain1", param, OrderContext.class);
List<LiteflowResponse> rs = flowExecutor.executeRouteChain(param, OrderContext.class);

LiteflowResponse

常用取值（方法名以源码为准）：

需求	方法
是否成功	`resp.isSuccess()`
失败异常	`resp.getCause()` （是 `getCause` ，不是 `getException` ）
异常 code/message	`resp.getCode()` / `resp.getMessage()`
上下文	`resp.getContextBean(XxxContext.class)` / `getFirstContextBean()`
步骤字符串（带耗时）	`resp.getExecuteStepStrWithTime()`
结构化步骤	`resp.getExecuteSteps()` （ `Map<String, List<CmpStep>>` ）/ `getExecuteStepQueue()`
请求/会话/链路 ID	`getRequestId()` / `getConversationId()` / `getChainId()`
超时节点（v2.12.3+）	`getTimeoutItems()`
回滚步骤	`getRollbackStepQueue()` / `getRollbackSteps()`

java

@Resource private FlowExecutor flowExecutor;

// Synchronous execution: chainId + input parameter + multiple context Classes (instantiated by framework)
LiteflowResponse resp = flowExecutor.execute2Resp("chain1", param, OrderContext.class, UserContext.class);

// Directly execute a segment of EL (v2.15.0+, no rule file required)
LiteflowResponse resp2 = flowExecutor.execute2RespWithEL("THEN(a, b, c)", param, OrderContext.class);

// Asynchronous / Routing
Future<LiteflowResponse> f = flowExecutor.execute2Future("chain1", param, OrderContext.class);
List<LiteflowResponse> rs = flowExecutor.executeRouteChain(param, OrderContext.class);

Common values for

LiteflowResponse

(method names are based on source code):

Requirement	Method
Whether successful	`resp.isSuccess()`
Failure exception	`resp.getCause()` (it's `getCause` , not `getException` )
Exception code/message	`resp.getCode()` / `resp.getMessage()`
Context	`resp.getContextBean(XxxContext.class)` / `getFirstContextBean()`
Step string (with time consumption)	`resp.getExecuteStepStrWithTime()`
Structured steps	`resp.getExecuteSteps()` ( `Map<String, List<CmpStep>>` ) / `getExecuteStepQueue()`
Request/session/link ID	`getRequestId()` / `getConversationId()` / `getChainId()`
Timeout nodes (v2.12.3+)	`getTimeoutItems()`
Rollback steps	`getRollbackStepQueue()` / `getRollbackSteps()`

3.4 核心配置速查（详见

references/config.md

，SpringBoot

liteflow.*

）

3.4 Core Configuration Quick Reference (See

references/config.md

for details, SpringBoot

liteflow.*

)

key	默认	说明
`rule-source`	—	规则文件路径，用规则文件时必填；改为代码动态构造时自动失效
`parse-mode`	`PARSE_ALL_ON_START`	另有 `PARSE_ONE_ON_FIRST_EXEC` / `PARSE_ALL_ON_FIRST_EXEC` （懒加载）
`slot-size`	`1024`	上下文槽位数，自动扩容
`when-max-wait-time` (+ `-unit` )	`15000` (ms)	WHEN 并行整体超时
`global-thread-pool-size`	`64`	全局异步节点并发上限
`support-multiple-type`	`false`	多种规则来源混装时设 true
`enable-monitor-file`	`false`	本地规则文件变更自动重载
`fast-load`	`false`	快速解析模式
`enable-virtual-thread`	`true`	仅 JDK21+ 生效
`print-execution-log`	`true`	执行过程日志
`monitor.enable-log`	`false`	简易监控统计

⚠️ v2.16.X 不存在这些配置名，勿臆造：
whenMaxWorkers
（并发由
global-thread-pool-size
控制）、
printExecutionResult
（应为
print-execution-log
）、
chainCache*
。

key	Default	Description
`rule-source`	—	Rule file path, required when using rule files; automatically invalid when changed to code dynamic construction
`parse-mode`	`PARSE_ALL_ON_START`	Also available `PARSE_ONE_ON_FIRST_EXEC` / `PARSE_ALL_ON_FIRST_EXEC` (lazy loading)
`slot-size`	`1024`	Context slot count, automatically expands
`when-max-wait-time` (+ `-unit` )	`15000` (ms)	Overall timeout for WHEN parallel execution
`global-thread-pool-size`	`64`	Global asynchronous node concurrency limit
`support-multiple-type`	`false`	Set to true when mixing multiple rule sources
`enable-monitor-file`	`false`	Auto-reload when local rule files change
`fast-load`	`false`	Fast parsing mode
`enable-virtual-thread`	`true`	Only takes effect for JDK21+
`print-execution-log`	`true`	Execution process log
`monitor.enable-log`	`false`	Simple monitoring statistics

⚠️ These configuration names do not exist in v2.16.X, do not fabricate:
whenMaxWorkers
(concurrency is controlled by
global-thread-pool-size
),
printExecutionResult
(should be
print-execution-log
),
chainCache*
.

四、知识地图（问题类型 → reference 文件）

4. Knowledge Map (Question Type → Reference File)

用

Read

打开

references/

下对应文件获取细节：

问题类型 / 关键词	加载文件
框架定位、执行模型、模块地图、版本/JDK 支持、性能	`references/overview.md`
安装运行、Hello World（SpringBoot/Spring/Solon/其他）	`references/quickstart.md`
全部配置项、各场景差异、LiteflowConfig	`references/config.md`
组件（继承式 5 种 / 声明式 / 生命周期钩子）	`references/components.md`
EL 全语法、组件参数语法、重试/超时/继承/验证	`references/el-rules.md`
数据上下文、别名、参数注入、表达式取参	`references/context.md`
FlowExecutor 方法、入参、LiteflowResponse	`references/executor.md`
测试用例与示例（测试范式、BaseTest 清理、功能→测试模块速查、DEMO）	`references/testing.md`
脚本组件、各语言坐标、绑定变量、动态刷新/验证/卸载	`references/scripts.md`
规则配置源（本地/SQL/ZK/Nacos/Etcd/Apollo/Redis/自定义）	`references/rule-sources.md`
元数据操作器、平滑热刷新、启动不检查	`references/metadata.md`
异步线程池（FlowExecutor 层/组件异步层/虚拟线程）	`references/thread-pools.md`
动态构造 Node/EL/Chain	`references/dynamic-build.md`
决策路由（概念/用法/executeRouteChain）	`references/decision-routing.md`
框架级生命周期（启动时/执行时钩子接口）	`references/lifecycle.md`
高级特性（降级/回滚/切面/隐式子流程/步骤/监控…18 项）	`references/advanced.md`
AI Agent 编排（ReAct Agent 组件、模型/凭据、自定义工具、流式输出、会话记忆、 `liteflow-react-agent` ）	`references/react-agent.md`
源码细节（FlowExecutor/FlowBus/DataBus/Condition 树/算子→类映射）	`references/code-internals.md`
常见坑与 FAQ	`references/faq-pitfalls.md`

Use

Read

to open the corresponding file under

references/

for details:

Question Type / Keywords	Load File
Framework positioning, execution model, module map, version/JDK support, performance	`references/overview.md`
Installation and operation, Hello World (SpringBoot/Spring/Solon/others)	`references/quickstart.md`
All configuration items, scenario differences, LiteflowConfig	`references/config.md`
Components (5 inherited types / declarative / lifecycle hooks)	`references/components.md`
Full EL syntax, component parameter syntax, retry/timeout/inheritance/validation	`references/el-rules.md`
Data context, aliases, parameter injection, expression parameter retrieval	`references/context.md`
FlowExecutor methods, input parameters, LiteflowResponse	`references/executor.md`
Test cases and examples (testing paradigm, BaseTest cleanup, feature→test module quick reference, DEMO)	`references/testing.md`
Script components, coordinates for various languages, bound variables, dynamic refresh/validation/uninstallation	`references/scripts.md`
Rule configuration sources (local/SQL/ZK/Nacos/Etcd/Apollo/Redis/custom)	`references/rule-sources.md`
Metadata operator, smooth hot refresh, no startup check	`references/metadata.md`
Asynchronous thread pools (FlowExecutor layer/component asynchronous layer/virtual threads)	`references/thread-pools.md`
Dynamic construction of Node/EL/Chain	`references/dynamic-build.md`
Decision routing (concept/usage/executeRouteChain)	`references/decision-routing.md`
Framework-level lifecycle (startup/execution hook interfaces)	`references/lifecycle.md`
Advanced features (downgrade/rollback/aspect/implicit sub-process/steps/monitoring...18 items)	`references/advanced.md`
AI Agent orchestration (ReAct Agent components, model/credentials, custom tools, streaming output, session memory, `liteflow-react-agent` )	`references/react-agent.md`
Source code details (FlowExecutor/FlowBus/DataBus/Condition tree/operator→class mapping)	`references/code-internals.md`
Common pitfalls and FAQ	`references/faq-pitfalls.md`

五、引用规范

5. Citation Specifications

用法类问题：作答末尾标注来源 reference 文件名，例如"详见
```
references/el-rules.md
```
"。
代码/源码类问题：引用源码
```
path:line
```
（来自
```
references/code-internals.md
```
或第 2/3 步实地查到的源码）。
涉及版本依赖的 API/配置，标注所对齐版本（默认 v2.16.X）。

Usage-related questions: Mark the source reference file name at the end of the answer, e.g., "See
```
references/el-rules.md
```
for details".
Code/source code-related questions: Cite source code
```
path:line
```
(from
```
references/code-internals.md
```
or source code found in Step 2/3).
For APIs/configurations involving version dependencies, mark the aligned version (default v2.16.X).

六、关于

scripts/source-lookup.sh

6. About

scripts/source-lookup.sh

本地优先 / 受控克隆 + 检索的命令行助手（POSIX sh，macOS 可直接运行）：

子命令	作用
`path`	打印解析到的本地仓库路径（找不到退出码 2，不克隆）
`clone`	显式克隆 gitee 仓库到缓存（默认 `v2.16.0` tag，与内置内容对齐；可用 `LITEFLOW_TAG` 指定其它 tag/分支）；仅在用户同意后调用
`grep <pattern>`	在仓库 `*.java` 中检索（优先 `rg` ，回落 `grep -rn` ）
`grepall <pattern>`	在仓库所有文件中检索
`find <name>`	按文件名查找
`show <relpath> [a-b]`	显示某文件（带行号，可选区间）

环境变量：

LITEFLOW_REPO

（指定本地仓库覆盖探测）、

LITEFLOW_TAG

（可选，指定 tag/分支；不设则克隆

v2.16.0

，显式留空

LITEFLOW_TAG=

才回落 master）、

LITEFLOW_CACHE

（默认

~/.cache/liteflow-skill

）。

职责边界：脚本不做用户交互，是否克隆由本 skill 的决策流程（第 3 步）征得用户同意后决定。

A command-line assistant that prioritizes local usage / controlled cloning + retrieval (POSIX sh, can be run directly on macOS):

Subcommand	Function
`path`	Print the path of the detected local repository (exit code 2 if not found, no cloning)
`clone`	Explicitly clone the gitee repository to cache (default `v2.16.0` tag, aligned with built-in content; can specify other tags/branches using `LITEFLOW_TAG` ); only call after obtaining user consent
`grep <pattern>`	Search in `*.java` files of the repository (prioritize `rg` , fallback to `grep -rn` )
`grepall <pattern>`	Search in all files of the repository
`find <name>`	Search by file name
`show <relpath> [a-b]`	Display a file (with line numbers, optional range)

Environment variables:

LITEFLOW_REPO

(specify local repository to override detection),

LITEFLOW_TAG

(optional, specify tag/branch; if not set, clone

v2.16.0

, only fallback to master if explicitly set to empty

LITEFLOW_TAG=

LITEFLOW_CACHE

(default

~/.cache/liteflow-skill

Responsibility Boundary: The script does not handle user interaction; whether to clone is determined by the decision process of this skill (Step 3) after obtaining user consent.

how2useliteflow

Original

Translation

LiteFlow 助手

LiteFlow Assistant

一、何时使用

1. When to Use

二、回答 LiteFlow 问题时的决策流程（必须严格遵守）

2. Decision Process for Answering LiteFlow Questions (Must Be Strictly Followed)

绝对禁止

Absolute Prohibitions

三、高频速查（直接作答，无需加载 reference）

3. High-Frequency Quick Reference (Answer Directly, No Need to Load Reference)

3.1 EL 算子速查（详见
`references/el-rules.md`
）

3.1 EL Operator Quick Reference (See
`references/el-rules.md`
for details)

3.2 组件类型速查（详见
`references/components.md`
）

3.2 Component Type Quick Reference (See
`references/components.md`
for details)

3.3 执行 API 速查（详见
`references/executor.md`
）

3.3 Execution API Quick Reference (See
`references/executor.md`
for details)

3.4 核心配置速查（详见
`references/config.md`
，SpringBoot
`liteflow.*`
）

3.4 Core Configuration Quick Reference (See
`references/config.md`
for details, SpringBoot
`liteflow.*`
)

四、知识地图（问题类型 → reference 文件）

4. Knowledge Map (Question Type → Reference File)

五、引用规范

5. Citation Specifications

六、关于
`scripts/source-lookup.sh`

6. About
`scripts/source-lookup.sh`

how2useliteflow

Original

Translation

LiteFlow 助手

LiteFlow Assistant

一、何时使用

1. When to Use

二、回答 LiteFlow 问题时的决策流程（必须严格遵守）

2. Decision Process for Answering LiteFlow Questions (Must Be Strictly Followed)

绝对禁止

Absolute Prohibitions

三、高频速查（直接作答，无需加载 reference）

3. High-Frequency Quick Reference (Answer Directly, No Need to Load Reference)

3.1 EL 算子速查（详见 references/el-rules.md）

3.1 EL Operator Quick Reference (See references/el-rules.md for details)

3.2 组件类型速查（详见 references/components.md）

3.2 Component Type Quick Reference (See references/components.md for details)

3.3 执行 API 速查（详见 references/executor.md）

3.3 Execution API Quick Reference (See references/executor.md for details)

3.4 核心配置速查（详见 references/config.md，SpringBoot liteflow.*）

3.4 Core Configuration Quick Reference (See references/config.md for details, SpringBoot liteflow.*)

四、知识地图（问题类型 → reference 文件）

4. Knowledge Map (Question Type → Reference File)

五、引用规范

5. Citation Specifications

六、关于 scripts/source-lookup.sh

6. About scripts/source-lookup.sh

3.1 EL 算子速查（详见
`references/el-rules.md`
）

3.1 EL Operator Quick Reference (See
`references/el-rules.md`
for details)

3.2 组件类型速查（详见
`references/components.md`
）

3.2 Component Type Quick Reference (See
`references/components.md`
for details)

3.3 执行 API 速查（详见
`references/executor.md`
）

3.3 Execution API Quick Reference (See
`references/executor.md`
for details)

3.4 核心配置速查（详见
`references/config.md`
，SpringBoot
`liteflow.*`
）

3.4 Core Configuration Quick Reference (See
`references/config.md`
for details, SpringBoot
`liteflow.*`
)

六、关于
`scripts/source-lookup.sh`

6. About
`scripts/source-lookup.sh`