Skip to content
/EUXLab

{the brain} + {the skills}

Every output is the next input

{the system} is {the brain} plus {the skills}, run as one loop. Each skill reads the file the previous step wrote.

See the loopRead the state contract
skills in the loop
5skills in the loop
steps, ask to review
7steps, ask to review
shared paths
8shared paths

01 · Three layers

Memory, steps, and the loop between them

Each layer works alone. Together they compound.

  1. {the brain}

    The long-term memory. An Obsidian vault an LLM maintains: sources, entities, past engagements.

  2. {the skills}

    The steps. Each skill reads a file, does one job, and writes a file.

  3. {the system}

    The loop. The skills chained so each output is the next input.

02 · The loop

Every outcome is the next input

Each skill reads a file, does one thing, and writes the next file. That file is the contract with the next step. Two steps are handwork, and the loop says so.

  1. requestA request arrives. "We need a new dashboard."
  2. /euxlab-grill-the-askasks critical questions about requirements, scope and users
  3. docs/interview-guide.mdthe request sharpened, plus the questions for the interviews
  4. interviewing stakeholders and usersno skill. You talk to stakeholders and users
  5. transcriptsin research/raw/
  6. /euxlab-create-personas-and-job-storiesper transcript
  7. research/personas/role description, workflows, job stories, pain points, needs, and more
  8. /euxlab-synthesize
  9. research/insights/insights I01, I02 with evidence from the transcripts. Contradictions as C01
  10. /euxlab-design-brief
  11. docs/design-brief.mdthe design assignment: scope, requirements, and which insights the design must serve
  12. designingno skill. You do this, in Figma
  13. designscreens and a prototype, each screen naming the insight it serves
  14. /euxlab-design-review
  15. two reportsStandards: heuristics, WCAG. Evidence: which insight does this screen serve, and where is that written
  • skill
  • artifact, what the skill writes
  • handwork, you do this yourself

03 · The state contract

8 paths, each with a writer and a reader

Every skill reads and writes the same folders. Change the contract and you change the loop.

PathWritten byRead byRule
docs/agents/engagement.md/euxlab-setupallclient, design system, consent posture, stakeholders
GLOSSARY.md/euxlab-grill-the-ask, persona skillalla term earns an entry when it is fuzzy, contested, or overloaded
docs/interview-guide.md/euxlab-grill-the-askpersona skill, /euxlab-synthesizethe sharpened request, the graded assumption register, the questions
research/raw/interviewingpersona skill, /euxlab-synthesizeimmutable, consent-checked, may contain PII
research/personas/persona skill/euxlab-synthesize, /euxlab-design-briefrole, workflows, job stories, pain points, needs. No insights. Provisional until synthesis reconciles
research/insights//euxlab-synthesize/euxlab-design-brief, /euxlab-design-reviewone file per insight, ID’d, graded, cited to raw
docs/design-brief.md/euxlab-design-briefdesigning, /euxlab-design-reviewrequirements, each serving named insight IDs
the designdesigning/euxlab-design-reviewevery screen names the insight ID it serves

No brain yet?

Build the memory layer first

{the brain} is a free 7-day email course that builds the project memory. One email per day, one action per day.

The signup form is hosted by Kit, and its script stores a visitor id in your browser. Load it to sign up.