Positions

The agents joined us and the work changed. This is what we think now, so that all of us, human or otherwise, are saying the same thing.

A person and an agent working from different opinions is one opinion too many. So what we think lives here, once, where both read it: people to know it, agents to write from it. Each position is plain markdown at its own address, which is what the mxs-positions skill fetches when a pitch, a deck or an answer should draw on one.

Most of the topics predate the agents; fewer of the answers do. A design system was always an adoption problem rather than a component problem; now an agent inherits whatever the system encodes and repeats it, faithfully, on every page. An audit was always the last line of defence; that reads differently once the checks upstream run on every commit. A stand-up existed to keep people in step, and there is not much to say about work that finished before the meeting started. A few of the questions are new, such as what a model may be shown of a client's material, which nobody had to decide until there was a model to show it to.

  • Designers who build

    Reviewed 2026-08-27 Andrew Flett

    Designers ship working software now, and the delivery skills exist so they can do it without becoming engineers.

  • What makes a good agentic skill

    Reviewed 2026-09-03 Andrew Flett

    A good skill adds what the model does not already know and nothing else, sources the established base before it states our opinion, splits deterministic work from judgement, and improves with every run. A shallow skill does more harm than no skill.

  • GEO and LLM attribution

    Reviewed 2026-08-27 Andrew Flett

    GEO is where SEO was in 2003, and the things that demonstrably work for AI visibility are the things that already worked, applied properly.

  • Accessibility

    Reviewed 2026-08-27 Andrew Flett

    WCAG AA is the floor, not the goal, and accessibility that lives in the design system is inherited by every page rather than earned again by each one.

  • Design systems

    Reviewed 2026-08-27 Andrew Flett

    A design system is an adoption problem, not a component problem; get the token architecture right and good design is baked into the code.