Graduation map
You are the analyst and map author. Read the user's sources, resolve records and evidence, then deliver a shareable, editable HTML. The user may attach files, paste text, provide a permitted link or point to a local folder; do not require them to transcribe an image, prepare JSON, or run a pipeline. Choose available reading tools and use bundled helpers only where useful. Work in the user's output directory; keep private inputs outside this skill and public examples.
Read and reconcile the sources
Read input-sources.md for the supplied formats: image/OCR, TXT/Markdown, Excel/CSV, conversation, PDF/Word, authorized web/form exports, structured data and mixed folders. It defines splitting, sheet roles, provenance and tool fallbacks. For images also read image-to-data.md; enlarging pixels does not resolve ambiguous characters.
Read reconciliation.md before merging or applying corrections. Assign stable person IDs, distinguish detail from summaries, preserve same-name people, and resolve field-level evidence without double counting. Output a short source inventory, reconciled roster/counts and actionable uncertainties. Continue with confirmed records when the rest can remain unknown.
Read data-schema.md to map the analyzed records into the page contract. JSON is an agent working format, not a prerequisite for the user. For an existing page retain its established appearance and behavior unless asked to redesign.
Prepare the data
Use one student record per person and one school record per school/campus location. Students reference schoolId; schools own their location. Keep the class, mother school, schools, graduates, region-label configuration and map settings separate.
Distinguish three independent facts: name confidence, whether the attending campus is confirmed, and whether a representative coordinate is known. A known school center does not establish a historical campus. Use WGS84 longitude/latitude; do not mix GCJ-02 or BD-09 values with this basemap.
Unknown coordinates are null. A known province may contribute to its count without a school point. For ambiguous cross-province campuses, leave the actual destination region unresolved rather than choosing a headquarters. Keep overseas and unresolved records in the roster. Treat a source-image row count as the complete class size only after the user confirms completeness.
Build a single file
Adapt the bundled template or generate a compatible page with your available tools. The following helpers are optional local validation/assembly tools, not readers for arbitrary source files or replacements for your analysis. Run --help before adapting a command; paths are relative to this skill:
python3 scripts/validate_data.py --data /path/to/class.json
python3 scripts/build.py --data /path/to/class.json --output /path/to/class-map.html
Add --source-image /path/to/source.jpg only when the user wants that image embedded. The output then contains the full image and names; it is not anonymized by being a static file.
The resulting HTML puts editable CLASS_INFO, ALMA_MATER, SCHOOLS, GRADUATES, REGION_CONFIG and MAP_CONFIG before presentation code. Saving edits and refreshing rebuilds the view. Counts, labels, summaries, filters and JSON exports must all read the same objects.
Street detail should attempt to enable automatically when its service is reachable. Use the actual source request, not only navigator.onLine; fail quietly to the embedded map on offline, timeout or source/tile failure, and retry on connectivity recovery. Do not add network prompts, failure banners or toasts. Keep a viewer's manual off choice until they re-enable it.
Keep the embedded Leaflet 2D renderer as an independent fallback when WebGL, workers or the 3D engine fail. Limit mobile rendering cost, automatically recover from slow startup/context loss, and clear obsolete error overlays after successful initialization. Read compatibility.md for the capability-based policy and the limits of Xiaomi-related evidence.
Verify the result
Read verification.md for the focused checks: file opening offline, province/person accounting, null locations, labels, state changes, phone controls and touch gestures. School street detail is an optional online layer; distinguish that dependency from offline map functionality.
Inspect the rendered result and report which checks actually ran. For data edits, verify that the displayed names and exported JSON match the user's corrections. Preserve unknown information and give the user a short list of missing campus/address details.
With no real sources, explain the supported analysis and optionally use explicitly fictional examples. Never claim that TXT/Excel parsing, a roster or a real cohort was verified without the corresponding input.
When publishing the workflow
Publication of a reusable skill does not imply permission to publish the class roster. Use a fresh, allowlisted public package with synthetic data, preserve third-party notices, and inspect files and Git history for private inputs. Read publishing.md when publication is requested. Publishing requires the user's authorization; ordinary map creation does not authorize a public repository.
Maintenance: Source reading and reconciliation guidance lives in the linked references; scripts remain optional assembly aids. Do not restore a script-first or image-only entry point.