Methods and practice you can apply, not slogans.
Gate: all
Zalando's design team argues AI is making design trends flare up and fade faster than ever, which means 'best practice' documentation goes stale quicker too. Worth building shorter review cycles into how you work.
medium.com (opens in a new tab)
Your move
Pick one 'standard' pattern in your current project and spend 20 minutes checking if it's still the best option, or just the familiar one.
Cursor and Claude Code speak the same Model Context Protocol, so an MCP server config you write once now works in both without changes. That's a genuinely useful shortcut for anyone juggling AI tools.
claudefa.st (opens in a new tab)
Your move
if you set up an MCP server for one AI tool, save the config file somewhere you can find it — you'll likely reuse it in the next tool you try.
A Medium piece on agency workflows describes teams restructuring around "human plus helper" pairs rather than full AI swaps. The productivity and conversion stats it cites come from the author's own case studies, not an independent study.
medium.com (opens in a new tab)
Your move
Map your last design task into "judgement" vs "mechanical" steps, and note which mechanical ones you'd trust an agent with.
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.
facebook.com (opens in a new tab)
Your move
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.
Reporting on multi-agent AI systems this summer found that most failures trace back to orchestration and process gaps, not the underlying models being incapable. The same lesson applies directly to how you structure your own design workflow.
rauljitechnologies.com (opens in a new tab)
Your move
Before adding any AI tool to your workflow this week, map your current process on paper and mark the one handoff or review step that's genuinely unclear — fix that first.
Creativeboom rounds up design trends practitioners are tired of this year — practitioner sentiment, not hard data. Useful as a gut-check before leaning on a trendy style.
creativeboom.com (opens in a new tab)
Your move
Before your next portfolio update, check your work against this list — if you're leaning on a trend it flags as tired, decide if it's earning its place or just decoration.
A design trends piece makes the case that most 2026 "trends" are noise and only a handful actually change how people work. Worth borrowing that filter before you spend a week copying a moodboard.
think.design (opens in a new tab)
Your move
Next trend post you see this week, write one sentence on whether it changes a real decision in your process — or just the surface.
Industry surveys show most teams using AI agents keep a human review step before anything ships — augmentation, not replacement. That review habit is a method worth building now.
moclaw.ai (opens in a new tab)
Your move
Next time you use any AI tool for a design task, write one sentence in your process notes explaining what you changed and why — build the review-gate habit before it's expected of you.
