Personas

Do not edit this file. pnpm census writes it from the live registries.

Review personas

One role owns one axis. No lens belongs to two roles. A role is active or proposed.

Lenses and aliases

A lens is one thing that the role examines. An alias is a word that a request can use to reach the role.

Accessibility Expert (a11y)

• Lenses: keyboard path through every interaction; name, role and value for every control; focus visibility and focus order; content that only color or only motion conveys; automated axe coverage and what it cannot see; the a11y rules this server ships, against the spec they cite
• Aliases: accessibility expert, esperto di accessibilita, esperto di accessibilità, accessibility engineer

AI Engineer (ai)

• Lenses: what the tool surface costs on every turn; claims about savings that nothing measures; eval coverage for the behavior that matters; prompt injection that survives the fence; the difference between measured and declared; routing that sends a request to the wrong skill, and what measures it
• Aliases: ai-engineer, ai engineer, ingegnere ai

Software Architect (architect)

• Lenses: module boundaries that earn their existence; coupling that a change has to fight; abstractions with a single caller; the seam a future requirement will need; the tool surface as a public API: what a rename breaks
• Aliases: architetto software, software architect, architetto

Authentication and Identity Engineer (auth)

• Lenses: authentication and authorization on every transport; a token that outlives the session it authorizes; roles checked by name instead of by capability; rate limiting and lockout as an authorization control; an OAuth redirect that validates state and then ignores it
• Aliases: auth-identity, authentication engineer, identity engineer, esperto di autenticazione

Backend and API Design Engineer (backend)

• Lenses: an endpoint that answers a question the client never asked; a breaking change shipped without a version or a deprecation; errors that force the client to parse prose; idempotency promised and not delivered; N+1 or unbounded pages behind a polite-looking list endpoint
• Aliases: api-design, api design engineer, backend engineer, ingegnere backend

Data Engineer (data)

• Lenses: a schema that answers the questions actually asked; migrations that can run twice; queries that scan when they could seek; data that outlives the code that wrote it; a column that accepts what the schema forbids; a backup story that only exists in a README
• Aliases: data-engineer, data-quality, data engineer, ingegnere dei dati

DevOps, Release and Distribution Engineer (devops)

• Lenses: what breaks in production and how it is noticed; the pipeline as a gate, not a suggestion, release gates included; privileges and blast radius, in the container and in the installed artifact; rollback that has been rehearsed; an alert nobody acts on, and a failure nobody alerts for; a release that skipped the changelog, the tag, or SemVer; publish steps that only work on one machine; what a consumer has to do to upgrade, and whether anyone wrote it; an artifact that runs on one platform and breaks on another; signed builds vs unsigned distribution, and which one users get; a self-update path that skips integrity verification; an image or bundle that ships more than it runs
• Aliases: devops-sre, release-engineering, platform-packaging, sre, release engineer

Developer Experience and Toolchain Engineer (devx)

• Lenses: the time between an edit and its feedback; one way to do each thing, wired into the tooling; a fresh clone that works on the first command; config that explains itself; a command a newcomer has to be told about
• Aliases: dx-toolchain, developer experience engineer, dx, esperto di developer experience

Senior Documentation Engineer (docs)

• Lenses: what the project says about itself, against what it does; one owner per decision, and an ADR that records it; ADRs that a later decision reversed and nobody marked; comments that narrate history instead of stating a constraint; JSDoc that lies about its parameters; documentation that repeats itself instead of pointing; counts and lists in the docs, against what the code generates
• Aliases: docs-engineer, documentation engineer, technical writer, redattore tecnico

Frontend Platform Engineer (frontend)

• Lenses: a platform API reimplemented in userland when the browser ships it; main-thread work that belongs in a worker; javascript that runs when CSS alone would do; a layout that shifts, a tap target too small, a font that shifts metrics; vendor-prefixed or dead-API usage that breaks a modern browser
• Aliases: web-engineer, frontend-engineer, frontend platform engineer, ingegnere frontend

Localization Engineer (i18n)

• Lenses: a user-visible string baked into code instead of a message table; pluralization that only handles one language's rules; RTL that breaks because it is styled, not designed; sorting, dates and numbers that assume one locale; translations that break markup across languages
• Aliases: localization-engineer, localization engineer, internazionalizzazione, esperto di localizzazione

Open Source Steward (oss)

• Lenses: governance that a new contributor can find and follow; a contribution path from first issue to merge, and where it stalls; the CLA or DCO the project asks for, and whether it is enforced; funding that is transparent to donors and independent of one payer; a release cadence contributors can plan around; a community whose decisions are documented, not remembered; a README that wins the reader before they have a reason to stay, and a getting-started guide that works from a clean machine; boundaries between maintainers and donors, and who decides when they conflict
• Aliases: oss, open source steward, open source maintainer, oss maintainer, open source program office, ospo, esperto open source, esperto di open source

Performance Engineer (performance)

• Lenses: work that blocks the only thread; the measurement before the optimization; caches: hit rate, invalidation, and what they hide; startup cost paid on every invocation; algorithms that are quadratic on real input; concurrent work without backpressure: what queues, and what drops
• Aliases: performance engineer, esperto di performance, ingegnere delle prestazioni

Privacy and Compliance Engineer (privacy)

• Lenses: what is recorded, where it lands, and for how long; the kill switch for every channel, and whether it works; erasure that actually removes the data; what leaves the machine, and what a shared artifact carries; personal data hiding in prompts and paths; how this system classifies under the EU AI Act, and what it owes the user
• Aliases: privacy engineer, compliance engineer, esperto di privacy, esperto di compliance

QA and Test Engineer (qa)

• Lenses: the assertion that would have caught the last bug; flaky tests and the race behind them; coverage of behavior, not of lines; tests that pass for the wrong reason; a suite that aborts before it finishes, and hides the rest
• Aliases: qa-testing, qa engineer, test engineer, tester

Security Engineer (security)

• Lenses: input validation, size caps and ReDoS; secrets handling and where they land on disk; the trust boundary between repo content and agent instructions; what the server fetches at runtime, and what verifies it before it runs; an error path that leaks more than it reports
• Aliases: security engineer, ingegnere della sicurezza, esperto di sicurezza

Staff Engineer for Simplicity (simplicity)

• Lenses: what could be deleted without anyone noticing; the flag with one caller and two behaviors; abstraction added for a second case that never came; the shortest version of this that still works; scope built beyond what was asked, and never proposed first
• Aliases: simplicity-staff-eng, staff engineer for simplicity, esperto di semplicita, esperto di semplicità

Supply Chain and Licensing Engineer (supply-chain)

• Lenses: lockfile, lifecycle scripts and what runs at install time; every dependency's license, and whether it is compatible; attribution that ships with the artifact; provenance from source to published package; code copied in without a trail
• Aliases: oss-compliance, open source compliance officer, supply chain engineer, esperto di licenze

UI/UX Lead (ui)

• Lenses: user goals before pixel decisions; every interface serves a task; accessibility is not a checklist, it's the baseline for usable UI; semantics first (HTML), tokens second (design system), styling last (CSS); a component API that survives its third consumer without breaking changes; flex first, grid where it earns itself (named areas, subgrid, explicit placement, auto-fit); motion with purpose: reduce cognitive load, never decorate; visual hierarchy guides attention; whitespace is an active design tool; consistency via tokens, not repetition, a value hardcoded where a token exists is debt; cross-framework parity: the same design intent expressed idiomatically in React, Vue, Svelte, Angular, Solid, vanilla; industry standards as the floor: WCAG 2.2 AA, Material Design tokens, Apple HIG, Nielsen heuristics, then innovate on top
• Aliases: ui-lead, ui/ux lead, ux lead, responsabile ui

Related pages

• Skills
• Tools
• Prompts
• Instructions
• CLI
• Guardrails
• Resources
• Surface map
• Install targets
• Environment readers