Work first visit: slim sign-in line, Finish setting up row, one empty-state line, no duplicate My Day tiles

Merged
BI
1mo ago
+393-17

User description

Requested by Josh · project thread

Summary

Site recommendations 12 Oct 2026, items 2 and 7.

Before: signed out, On Call Now opened with a large "Hospital numbers are for signed-in members" card that pushed the shift half a screen down; nothing pointed a new doctor to Work setup outside My Day; some empty On Call rows said "Not set up for this hospital" with nothing to tap; while on call, My Day showed Log a call and Handover in the hero and again in the tiles straight below.

After: one slim line "Sign in to see your hospital's numbers" with a Sign in button; a one-line "Finish setting up" row (with a cross to hide it on this device, with Undo) on the first page of On Call, Teaching and CPD while setup is incomplete; empty rows use one shared line, a sentence plus at most one real link (Service handbook); while on call the My Day tiles are Playbook, Contacts, Who's on and Remind me (unchanged off call).

How: new shared WorkEmptyLine (mode-kit) and WorkSetupRow (work-setup, same device-only progress as My Day's Set up Work card); handbook-state big card replaced by the slim notice; My Day on-call tile list swapped.

Areas touched: Personal practice, App experience, Design system (plus 1 file not yet placed in any area)

Safety: no crisis line, phone number, escalation step or their wording changed or moved; crisis lines still sit directly under the sign-in line.

Screenshots (before and after, 390 light and dark, 1440, 320): /mnt/project-files/site-recommendations-2026-10-12/built/work-firstrun/ in the project files.

Verification

  • eslint on changed files: clean
  • npm run test:focused: "Test Files 85 passed (85), Tests 1168 passed"
  • typecheck passed; prettier written
  • Browser: planner says full UI level; full suite to run on this draft before it goes ready

Risk and rollout

  • Risk: low; UI only, example and signed-out states. Admin and Roster skipped (owned by other open PRs).
  • Rollback: revert this PR.
  • Provider or production effects: None

Notes

  • Signed out, On Call shows the sign-in line and the Finish setting up row stacked (setup works signed out). My Day's card hides when signed out; matching that needs a non-throwing auth hook, left as is.
  • my-day-today-cards.tsx is also edited by draft #3489; this PR only swaps the on-call tile list.
  • On a computer the existing first-visit "AI Search, NEW" tip now sits over the slim line's Sign in button until Got it is tapped (search chrome, not changed here).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Mws6schjKQbpCQqQzPMKSL

Generated by Claude Code

Summary by cubic

Trims the first-visit experience across On Call, Teaching, CPD, and My Day: the signed-out "Hospital numbers are for signed-in members" card becomes a slim "Sign in to see your hospital's numbers" line, incomplete Work setup shows a dismissible "Finish setting up" row on each area's first page, and empty On Call rows now offer one real action (Service handbook) instead of dead-ending at "Not set up for this hospital". While on call, My Day swaps its Log a call and Handover tiles for Playbook and Contacts, since the hero already offers those.

Crisis lines, phone numbers, escalation steps, and their wording are untouched; crisis lines stay above the setup row. The empty shift-lists sheet explains itself instead of showing a blank: while the handbook is still loading, signed out, or unavailable it says shift lists are not available right now; once it has loaded it says the service has added no lists, and a reader with no service at all sees the "Not set up" line with the handbook action rather than an outage message.

CodeAnt-AI Description

Add setup prompts and simplify On Call guidance

What Changed

  • On Call pages replace the large signed-out notice with a compact sign-in line, keeping crisis contacts below it.
  • On Call, Teaching, and CPD show a “Finish setting up” row while setup is incomplete. It resumes where setup was left off and can be hidden on this device.
  • Missing On Call information now uses a clear empty-state message and links to the Service handbook where relevant. Shift lists show as unavailable until the handbook is ready, rather than implying none are set up.
  • While on call, My Day tiles show Playbook and Contacts instead of repeating Log a call and Handover from the hero.

Impact

✅ Less screen space used by the signed-out prompt
✅ Resume or hide setup from On Call, Teaching, and CPD
✅ No repeated call or handover tiles while on call

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.