📄

Request My Resume

Thank you for your interest! To receive my resume, please reach out to me through any of the following channels:

Reading routes from Mr. Guo

AI Agent Engineering and Coding

Read about micro-agents, Claude Code internals, memory and retrieval, AI coding workflows, and operational costs and safety.

A model answering one question and an agent working continuously inside a real codebase require different engineering. This topic connects task decomposition and state control with tools, context, permissions, verification, and recovery. The goal is to identify parts of an agent that can be observed, tested, and maintained.

Start with micro-agent architecture and system engineering for the overall picture, then move into the Claude Code runtime series. Use context and retrieval guides for memory or prompting problems, coding workflow articles for application delivery, and operations guides for tokens, SSD writes, hardware, APIs, and hosting bills.

These pages include source-code interpretations, usage records, and engineering retrospectives from the author and technical collaborators, alongside building guides and reference handbooks. Product behavior and costs change with versions. Keep each article’s tested environment and version assumptions in view; an observation on one machine does not describe every installation.

AI Agent System Architecture Guides and Resources

Understand composable agents through micro-agent design, tool collaboration, hybrid models, and building guides.

Define task, state, and tool boundaries before deciding whether multiple agents are needed. Micro-agent guides, OpenCode, Opal, AgentKit, and small-model discussions provide design references alongside building handbooks. Compare lifecycle control, error handling, and testability rather than assuming stronger models or more agents remove the need for engineering boundaries.

Open this route’s guide →

Claude Code Runtime Architecture Guides and Resources

Follow Claude Code source analysis through startup, the main loop, task entities, concurrency, permissions, and verification.

Read the source series from startup assembly to the main loop, tool orchestration, agent runtime, and REPL control plane before exploring individual design highlights. Task entities, semantic concurrency, centralized permissions, and worktree isolation explain long-running execution. Some legacy URLs contain different published versions of a topic; follow one version through the series rather than treating repeats as separate evidence.

Open this route’s guide →

Agent Context Memory and Retrieval Guides and Resources

Study layered and external memory, agentic retrieval, RAG, and the effects of prompting on system behavior.

Remembering a preference, resuming a task, and retrieving a document are different context problems. Compare Claude Code and Gemini CLI memory designs, external memory, RAG, and agentic retrieval here. Personality and PUA prompting articles examine instruction effects; read their experimental limitations rather than treating a headline as a performance guarantee for every task.

Open this route’s guide →

AI Coding Workflows Guides and Resources

Build a delivery workflow with Claude Code/Codex practice, Gemini CLI tools, frontend tests, and Vibe Coding for marketers.

AI coding begins with understandable requirements and ends with verifiable delivery. This collection links production Claude Code practice, Codex comparisons, Gemini CLI tooling, and Vibe Coding guides for marketers. Choose by task: start small tools with requirements and acceptance, examine tool boundaries for code changes, and validate frontend interactions under real viewport conditions rather than relying on generated screenshots.

Open this route’s guide →

Agent Costs Safety and Operations Guides and Resources

Evaluate long-running agents through task metrics, tokens, SSD writes, hardware, API risks, and hosting costs.

Persistent agents face limits in hardware, bills, and incident recovery. Agent evaluation, token use, the Codex SSD investigation, PC configuration, API risks, and Vercel cost analysis provide concrete checks; the storage tool supports local inspection. Establish measurement methods and workload intensity before choosing reversible actions. One incident or heavy automation setup should not be generalized to every user.

Open this route’s guide →
Mr. Guo Logo

© 2026 Mr'Guo

Topic reading guides Twitter Github WeChat