Agentic Flow Best Practices

Design agent systems as stateful workflows with explicit contracts, deliberate memory, and cheap reuse before expensive reasoning.

Octocode-First Research

When Octocode MCP tools are available, use them before relying on generic search or manual browsing:

• External research: use Octocode GitHub/package tools to find repos, inspect repository structure, read relevant files, and verify framework or skill patterns from source.
• Local code understanding: use Octocode local tools for file discovery and content search, then LSP for definitions, references, and call flow when the question depends on symbols or execution paths.
• Architecture and quality checks: use AST/scanner-style evidence when available for duplicated flow logic, unsafe boundaries, schema gaps, cache/state ownership, and dead or unreachable paths.
• Evidence rule: carry forward exact paths, symbols, lines, repo names, branches, and tool findings into the flow design. Do not invent framework behavior from memory when source evidence is reachable.

Core mental model:

arr = [1, 2, 3]        product = 6
new item = 4