Claude Skills by philbotar

Set-and-forget OpenFlow desktop release. Invoking this skill authorizes the full path: version/tag checks, local gates, wait PR CI, cut desktop bump if needed, merge, tag, wait Release workflow, stop at draft. Use when user invokes openflow-deploy-ready or asks to release / ship / deploy.

Procedural playbook for OpenFlow engine crate edits. Use when changing crates/engine/** — workflow graph, validation, InteractiveEngine, ports, tools policy, telemetry, templates, or completion protocol.

Final verification playbook before handing off OpenFlow work. Use when finishing a change, before commit, PR, or claiming done.

Procedural playbook for OpenFlow orchestration edits. Use when changing crates/orchestration/** — run lifecycle, AppBackend, execution host, ToolPortImpl, persistence, settings, tools, or workflow catalog.

Procedural playbook for OpenFlow providers crate edits. Use when changing crates/providers/** — Rig adapters, mapping, auth, streaming, create_provider, Bedrock credentials, or tool-arg repair.

Procedural playbook for OpenFlow UI edits. Use when changing crates/ui/** — api.ts, AppProvider, screens, panels, canvas, forms, or DTOs.

Create or revise concise, evidence-based documentation for the application in this repository. Use for getting-started guides, feature documentation, task-based how-tos, concepts, configuration, CLI or API reference, troubleshooting, docs-site navigation, and internal cross-linking.

Place OpenFlow changes in the correct crate and layer. Use when unsure which crate owns a change, whether a port is needed, or how to avoid layer violations across engine, providers, orchestration, desktop, and ui.