pawflow-developer

Guides contributions to the PawFlow agent platform codebase with architecture and conventions.

26|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/allcolor/PawFlow-Agents --skill pawflow-developer-allcolor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pawflow-developer
Source: https://github.com/allcolor/PawFlow-Agents/tree/main/data/repository/skills/global/pawflow-developer
Command: npx skills add https://github.com/allcolor/PawFlow-Agents --skill pawflow-developer-allcolor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributing to a large (~144K lines) Python agent orchestration platform without knowing its architecture leads to inconsistent, incorrect changes. This Skill provides the architectural context, patterns, and development rules needed to modify PawFlow correctly. ## Core Features & Use Cases - Architecture Orientation: Explains the two major subsystems (NiFi-inspired pipeline engine and multi-agent LLM system) and the full directory layout of core/, tasks/, services/, and engine/. - Pattern Enforcement: Documents key conventions such as thread-safe singleton stores, JSONL append-only conversation persistence, relay-backed tool handlers, and the ${scope.key} expression language. - Development Rules: Lists concrete contribution rules covering tests, docs, parameter validation, async actions, and force-stop semantics. - Use Case: When asked to add a new tool handler to PawFlow, the agent knows to place it in core/handlers/, register it via ToolRegistry, route execution through the relay layer, and add focused tests. ## Quick Start Load the pawflow-developer skill and help me add a new tool handler to the PawFlow codebase following its conventions.

Frequently Asked Questions about pawflow-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new tool handler to PawFlow?▼

Create one class per tool in core/handlers/ and register it through the ToolRegistry in core/tool_registry.py. Filesystem, shell, browser, desktop, and media actions must route through the relay/tool layer rather than direct server filesystem access.

What is the architecture of the PawFlow agent platform?▼

PawFlow has two major subsystems sharing core/ primitives: a NiFi-inspired pipeline engine with FlowFile, Task, Service, and Flow, and a multi-agent system with LLM tool-use loops, SSE streaming, memory, and multi-provider support.

How does PawFlow persist conversations?▼

Conversations are stored as JSONL append-only files via ConversationStore. New records are appended instead of rewriting history, and every message must have a UUID and timestamp when created.

How are LLM providers selected in PawFlow?▼

Providers such as Anthropic, OpenAI, Claude Code, and Gemini CLI are implemented as mixins in core/llm_providers/ and selected by service configuration. Provider or model behavior should not be hardcoded when a service resolution path exists.

What are the development rules for contributing to PawFlow?▼

All docs and comments must be in English, new behavior needs focused tests and doc updates, changes should be surgical and match local style, required params must fail clearly without fallbacks, and actions must be async without blocking UI or HTTP workers.