Use Cases

Overview

This module is the canonical text spec for every screen in the EMS portals, and for the public sites (prefix P). Each page covers one screen ID and contains the actor, flows, acceptance criteria, API surface, and links to the design URL Claude Design produced. The pages drive both Claude Design sessions (use-case page → design brief) and Claude Code implementation (use-case page + design URL → Angular).

For the workflow that ties this module to Claude Design and Claude Code, see Claude Design ⇄ Claude Code Workflow.

Screen ID Convention

Every page is named <prefix><NN>-<kebab-name>.adoc where <prefix> is one of:

Prefix Scope

S

Super-tenant admin / configuration screens (cross-tenant, platform-level)

T

Tenant-specific admin / configuration screens (within one tenant’s scope)

E

Event-specific screens

M

Membership-specific screens

A

Affiliation-specific screens

C

Common — anything that doesn’t fit the above (structural, landing pages, cross-cutting components)

P

Public site — customers' public websites (event pages, event lists, registration hand-over, site set-up and operation), independent of the CMS that implements them

NN is two digits with leading zero. Numbers are allocated sequentially per prefix; gaps are fine. The same ID identifies the screen in Claude Design’s project folder, in this module, and in the matching ADO work item.

A screen ID is never renamed. If a use case is split, new IDs get fresh numbers; the original is retired or kept as a parent.

Catalogue

Common ©

Super-Tenant (S)

Tenant (T)

Event (E)

Membership (M)

Affiliation (A)

None yet.

Public Site (P)

Use cases for customers' public websites, written independently of the CMS. They walk through the Public Site Requirements.

Adding a New Use Case

  1. Pick the next available number for the right prefix.

  2. Create the page from the template at modules/use-cases/partials/use-case-template.adoc.

  3. Add the page to this catalogue and to nav.adoc.

  4. Create a matching folder in Claude Design’s project with the identical name.

  5. Create an ADO work item titled [<id>] <screen-name> with phase tag design-todo.

Page Status

Each page carries a :status: attribute:

Status Meaning

design-todo

Use-case spec exists; no design session yet. Claude Design can pick up.

in-design

Claude Design is iterating; design URL not yet stable.

handoff-ready

Design is signed off; :design-url: populated and stable; Claude Code can implement.

implementing

Claude Code is porting / integrating.

done

Merged + deployed.

See Claude Design ⇄ Claude Code Workflow § Session Ownership Discipline for transitions.

Related Documentation