| name | affh-reorient |
| description | Reorient with the AFFH dashboard codebase at the start of a new session. Use when resuming work on the AFFH dashboard, when asked to refresh context, or when starting a new implementation session. |
| allowed-tools | Read, Glob, Bash |
AFFH Dashboard Session Reorientation
Instructions
Step 1: Read documentation
- Read
CLAUDE.md for project overview, architecture, and conventions
- Check for any progress tracking or implementation notes files
Step 2: Examine codebase structure
- Run
git log --oneline --since="7 days ago" to identify recent changes
- Read main app files (
affh_shinyApp.R, server.R)
- Read helper scripts (
map_helpers.R, data_helpers.R, affh_transform.R etc.)
- Review data directories and lookup tables
Step 3: Assess feature completion
Check recent commits and source files to determine status of known features:
Likely complete (verify): - Context-aware tooltips (geography + variable + value) - Value boxes with comparison display - Sidebar optimizations - Chart rendering fixes - Tables tab enhancements - County name labels on map - Tract selection server-side rendering - Variable sources/notes integration - Alphabetized dropdowns - Data unavailability messaging - Table formatting with selected metric highlighting - Sources & Notes visibility improvements - R/ECAP tract highlighting - Download functionality (map PNG, table CSV) - Address search integration - Enhanced comparisons (statewide for tract/county charts) - Table toggle (all variables vs selected) - Map enhancements and polishing
Step 4: Understand current architecture
Key patterns to confirm are still in place: - Leaflet map built incrementally via leafletProxy(), not a single renderLeaflet() - update_map() in map_helpers.R orchestrates map updates - Reactive chain for geography/variable selection - Data flows from lookup tables → map/charts/tables - reactable for tables, plotly/ggplot for charts
Step 5: Summarize and confirm readiness
Provide: 1. Current architecture summary 2. Key file locations and their purposes 3. Feature completion status (complete / in-progress / not started) 4. Any questions or clarifications needed 5. Confirmation ready to continue implementation
