Daily Journal — 2026-05-23
⏱ min read
Freewrite¶
A productive Saturday working across AI tooling, design review, and personal knowledge systems. The day started with CTO brief pipeline work and Hermes configuration, then closed with a thorough Figma review of the M-Flow app — analyzing the member user journey, generating a Speckit epic spec, and surfacing design improvement tasks that need to land in Jira. The Figma Starter plan MCP limit was hit mid-review, which is now a known constraint to plan around.
Big Things Today¶
- [ ] Set up CTO Brief and AI Dev Brief as daily 8am automated emails
- [ ] Finalize Commander AGENTS.md design for Hermes multi-agent setup
- [ ] Provide Jira project key to document M-Flow design improvements as issues
Conversations¶
AI & Tech — CTO Brief Pipeline¶
Iterated on two daily CTO brief formats: a general tech/AI brief and a focused AI Dev brief covering Claude Code, MCP, agents, and prompt engineering. Both briefs were generated live with fresh web searches. Key insight: the user wants to receive both as daily 8am emails once formats are approved. → See [[cto-daily-brief]] | [[cto-brief-ai-sources]]
Hermes Agent — AGENTS.md and MEMORY.md Verification¶
Discovered that Hermes natively supports both AGENTS.md and MEMORY.md. Verified the full configuration surface: four-file project context hierarchy, MEMORY.md as agent-curated store (capped at 2,200 chars), SOUL.md, FTS5 session DB, skills library, and 8 optional external memory plugins. Session ended with starting to draft a Commander AGENTS.md for multi-agent orchestration. → See [[hermes-agent-config]] | [[hermes-commander-setup]]
M-Flow Figma Review — Design Analysis & Jira Documentation¶
Reviewed the M-Flow Figma file (Cover - Website page) covering the full member user journey: Home (Member), Toll History, Account Settings, and mobile screens. Claude analyzed the screens, mapped the user flow, and generated a Speckit epic spec. Design improvement suggestions were surfaced (inconsistent spacing, mobile-desktop padding gaps, etc.). Conversation ended while attempting to create Jira issues — Claude asked for the project key (MFLOW, WEB, DEV etc.) to proceed. Figma Starter plan MCP tool call limit was hit, limiting deeper visual review. → See [[mflow-figma-review]]
วิธีรักษาไซนัสอักเสบ (Sinusitis Treatment)¶
Quick health lookup on sinusitis treatment in Thai. Covered acute vs chronic cases, self-treatment guidelines, and when to see a doctor. Personal health reference, not a project. → See [[sinusitis-treatment]]
Open Tasks Surfaced¶
- [ ] Set up CTO Brief as daily 8am email (general tech/AI format approved)
- [ ] Set up AI Dev Brief as daily 8am email (format approved)
- [ ] Complete Commander AGENTS.md design for Hermes
- [ ] Design first specialist agent (PKM #notes agent) for Hermes
- [ ] Provide Jira project key to create M-Flow design improvement issues
- [ ] Decide on Figma plan upgrade vs. workaround for MCP tool call limit
Insights Worth Developing¶
- [[Context Engineering vs Prompt Engineering]] — the real production failure is bad context assembly, not bad prompts
- [[Agentic Cost Control]] — per-task spend caps, trajectory scoring, webhook stop signals are essential infrastructure
- [[AI Coding Stack 2026]] — Claude Code for hard refactors, Codex for async delegation, Cursor for daily IDE
- [[Figma MCP Plan Limits]] — Starter plan has hard tool call caps; plan AI-assisted design reviews around this constraint