The Assembly Language for AI Cognition.
- Version: 5.1
- Date: January 9, 2026
- Author: Bradley Ross
- Contact: GitHub @bar181 | LinkedIn /in/bradaross
The Assembly Language for AI Cognition.
Watchmode API - Most accurate streaming availability for 200+ services across 50+ countries, includes web links, iOS/Android deeplinks, episodes, seasons, similar titles algorithm, and proprietary relevance scoring
Flix Patrol https://flixpatrol.com/about/api/
OMDb API - Long-standing favorite for title and episode data, returns plots, genres, release dates, ratings from IMDb/Rotten Tomatoes/Metascore, and poster URLs
| { | |
| "env": { | |
| "CLAUDE_FLOW_AUTO_COMMIT": "false", | |
| "CLAUDE_FLOW_AUTO_PUSH": "false", | |
| "CLAUDE_FLOW_HOOKS_ENABLED": "true", | |
| "CLAUDE_FLOW_TELEMETRY_ENABLED": "true", | |
| "CLAUDE_FLOW_REMOTE_EXECUTION": "true", | |
| "CLAUDE_FLOW_CHECKPOINTS_ENABLED": "true", | |
| "AGENTDB_LEARNING_ENABLED": "true", | |
| "AGENTDB_REASONING_ENABLED": "true", |
Start all Planning Mode responses with '🤔 [CURRENT PHASE]'
You are a senior software architect and technical product manager with extensive experience designing scalable, maintainable systems. Your purpose is to thoroughly analyze requirements, ask questions, and design optimal solutions in with the final output as a full SOW and Implementation Plan. You must resist the urge to immediately write code and instead focus on comprehensive planning and architecture design.
Claude Flow treats memory as the backbone and MCP tools as the hands. You get concurrent agents that coordinate cleanly, keep context tight, and ship durable artifacts without dragging long text through prompts. It feels like an ops layer for intelligence.
The stack is simple. Claude Code as the client. Claude Flow as the MCP server. SQLite memory at .swarm/memory.db for state, events, patterns, workflow checkpoints, and consensus. Artifacts hold the big payloads. Manifests in memory link everything with ids, tags, and checksums.
Coordination is explicit. Agents write hints to a shared blackboard, gate risky steps behind consensus, and record every transition as an event. Hooks inject minimal context before tools run and persist verified outcomes after. Small bundles in, durable facts out.
Planning keeps runs stable. Use GOAP to sequence actions with clear preconditions. Use OODA to shorten loops.
Observe metrics, orient with patterns, decide through votes, act with orchestration. Topology adapts from hi
window.openai bridge into the iframe for props and events. ([OpenAI][1])The tutorial walks through the full process:
And it scales, you can run batch classification, deploy an API endpoint, and monitor real-time performance metrics without leaving the Flow Nexus environment.