Published 29 August 2026 · Source dated 24 August 2026
An August 2026 post argues "graph engineering" — structuring context for AI agents — is becoming the differentiating skill behind better agent output. It's early-stage and mostly discussed in engineering circles, not yet a standard design method.
A Substack piece by Sri Nithya Thimmaraju, summarised across CTO and AI-market networks in August 2026, argues that how you structure context (not just prompt wording) determines whether an AI agent produces useful work — referencing Anthropic's own research on this. It's framed as the skill layer above prompting.
For designers dipping into AI-assisted workflows (Figma's agent, MCP-connected tools), this matters conceptually: the quality of your component docs, naming and file structure IS the context you're engineering, whether you call it that or not.
Label: **Hype** — buzzy term, real underlying idea, but no established design-specific method yet. Treat with curiosity, not urgency.
Coach
Next time you brief an AI tool inside Figma, write the context out as a short list first (component names, constraints, goal) — see if structured input changes the output quality.
Jakob Nielsen's ten usability heuristics have been the backbone of UX critique since 1994. They're worth relearning properly, not just skimming the list.
AI tools can generate screens fast, but they don't validate usability — that's still on you. Classic heuristic evaluation is more relevant, not less, now that production speed has gone up.
More first drafts are arriving via AI agents, but the fundamentals of a good design critique haven't moved. IxDF's literature on critique still holds regardless of who — or what — made the first version.