When viewing the ASE Task List in the simulator, each task that involves specific tools would show small orange "tool pills" you can click to see what's used. Example below using B2 Surface Preparation tasks:
A. Surface Preparation 15 Qs · 27%
Clicking an orange tool pill would open a popup with the tool's photo, description, and "Practice ID of this tool" button.
What we'd actually build
Once you give the green light, here's the order of operations:
1. Data structure (Firestore)
One collection per module — same pattern as the existing question banks:
tools_b2/{toolId}
name: "HVLP Spray Gun"
category: "Spray Equipment"
description: "High Volume Low Pressure paint gun used for finish coats."
imageUrl: ""
taskRefs: ["B2-A.9", "B2-C.4"]
distractors: ["LVLP Gun", "Conventional Spray Gun", "Pressure Pot"]
module: "B2"
2. Admin uploader (you upload, I build the form)
A new section in admin_uploader.html (or dashboard2) where you fill in: name, category, description, upload image, 3 wrong-answer distractors, link to ASE tasks. Just like your existing terminology uploader.
3. Three student-facing surfaces
Reference Gallery
New sidebar nav item "Tools & Parts" in the simulator. Grid view with filter by category, search, click-to-zoom.
Tool ID Quiz Mode
New start-screen card "Tool Identification". 10-question randomized quiz. Score counts toward the module leaderboard accuracy %.
Task List Pills
Each ASE task in the Task List shows orange pills for the tools used in that task. Click a pill → tool detail popup → quick "Practice ID" button.
4. Code work estimate
- Backend (Firestore rules, collection) — 30 min
- Admin uploader form — 1 hour
- Reference Gallery view in simulator — 2 hours
- Tool ID Quiz mode — 2 hours (reuses existing quiz engine)
- Task List pill integration — 1 hour
- Testing + polish — 1 hour
- Total: ~7-8 hours
5. Your content work (the bigger task)
- ~30 tools per module × 5 modules = ~150 tools to compile
- For each: name, category, 1-line description, photo, 3 distractor names, task associations
- Images: phone photos work fine, or stock from Unsplash (free, commercial-OK). Avoid manufacturer product pages (copyright)
- Realistic timeline: 1-2 hours per module = ~7-10 hours total content work
6. Suggested rollout order
- Phase 1 — I build all the code (~8 hrs), starting with B2 only
- Phase 2 — You compile + upload B2 tools (~1-2 hrs). Goes live with B2 only.
- Phase 3 — You upload B3/B4/B5/B6 at your pace. Each unlocks as you finish.
Recommendation: Click the Reference Gallery and Tool ID Quiz tabs above and try them. If the look + flow feels right, tell me "ship Phase 1 for B2" and I'll build the backend + admin uploader + B2 frontend. You upload your first batch of B2 tools, and we go live. If the design needs tweaks, tell me what to change before I commit to it.