一键在 Manus 中运行任何 Skill

flow-controller-context

星标9

分支1

更新时间2026年6月26日 21:34

Applies project context and guardrails when working with the FlowController class. Use when modifying FlowController behavior, orchestration logic, or related control-flow APIs.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Prudent-Patterns

Prudent-Patterns/pyllments

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

FlowController Context

Baseline expectations

Keep control-flow APIs explicit and easy to reason about.
Prefer small, composable methods over monolithic branching logic.
Preserve existing behavior unless a change is intentional and tested.

Readiness and emission

FlowController-backed elements should treat incoming payloads as filling readiness slots, not necessarily as immediate output commands.
Sync flow functions that need to emit must return the emit coroutine so InputPort.receive() can await it; async flow functions should directly await emits.
Persist required inputs when a later trigger may need them, then clear only the ports actually consumed by a successful emission.
If a trigger arrives before all required data is present, keep a pending trigger or return without emitting; do not sleep or schedule hidden background retries.
Resource readiness belongs in awaited readiness checks (model.await_ready, port readiness_check) rather than connection callbacks.

Safety checklist

Control transitions are deterministic.
Required data readiness is explicit and testable.
Trigger handling does not emit partial output when required inputs are missing.
Error paths are explicit and observable.
Public API changes are documented and test-covered.
Integration points with Elements/Ports remain compatible.

同仓库更多 Skills

同仓库

docs-elements-authoring

Prudent-Patterns/pyllments

Writes and updates Pyllments element documentation in Quarto using project conventions. Use when editing docs/elements/*.qmd or generating docs from element/model source files.

2026-07-049

elements-authoring

Prudent-Patterns/pyllments

Implements or refactors Pyllments elements with correct element-model-view-port patterns. Use when creating or modifying files in pyllments/elements or when the user asks about element design, wiring, or reactivity.

2026-07-049

model-authoring

Prudent-Patterns/pyllments

Implements or refactors Pyllments models using param-based state and element-facing methods. Use when working on element models or when discussing where business logic should live.

2026-07-049

ports-connectivity

Prudent-Patterns/pyllments

Designs and updates Pyllments port wiring and payload flow contracts. Use when editing pyllments/ports/ports.py, element port definitions, or when discussing input/output port behavior and emission rules.

2026-06-269

recipe-authoring

Prudent-Patterns/pyllments

Creates and updates runnable Pyllments recipes with config-driven entrypoints and element wiring. Use when editing files under recipes or when implementing CLI-runnable recipe flows.

2026-06-269

drawio-diagrams

Prudent-Patterns/pyllments

Creates and edits draw.io diagram XML (.drawio) for local viewers. Use when the user asks for draw.io, diagrams.net, mxfile, architecture diagrams, flowcharts, or modifying .drawio files.

2026-05-319

name	flow-controller-context
description	Applies project context and guardrails when working with the FlowController class. Use when modifying FlowController behavior, orchestration logic, or related control-flow APIs.

FlowController Context

Baseline expectations

Keep control-flow APIs explicit and easy to reason about.
Prefer small, composable methods over monolithic branching logic.
Preserve existing behavior unless a change is intentional and tested.

Readiness and emission

FlowController-backed elements should treat incoming payloads as filling readiness slots, not necessarily as immediate output commands.
Sync flow functions that need to emit must return the emit coroutine so InputPort.receive() can await it; async flow functions should directly await emits.
Persist required inputs when a later trigger may need them, then clear only the ports actually consumed by a successful emission.
If a trigger arrives before all required data is present, keep a pending trigger or return without emitting; do not sleep or schedule hidden background retries.
Resource readiness belongs in awaited readiness checks (model.await_ready, port readiness_check) rather than connection callbacks.

Safety checklist

Control transitions are deterministic.
Required data readiness is explicit and testable.
Trigger handling does not emit partial output when required inputs are missing.
Error paths are explicit and observable.
Public API changes are documented and test-covered.
Integration points with Elements/Ports remain compatible.