القائمة
Define and validate the UX contract for small GIS web apps and demo micro-apps. Use when designing, reviewing, or refining a GIS micro-app, example site, or fast-turn client deliverable so the output feels operational, believable, and easy to understand.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create a pre‑publish checklist for ArcGIS Online items with risk and data quality checks
Search ArcGIS Online items and return clean, filtered results with safe defaults
Plan ArcPy workflows for ArcGIS Pro tasks with real project context and safe sequencing
Generate ArcPy scripts for ArcGIS Pro using live map context, layer sampling, and ArcGIS‑aware prompt rules
Package GIS layers into GeoParquet with metadata and validation
Audit ArcGIS Pro projects for broken layers, schema issues, and performance risks
| name | gis-microapp-ux-spec |
| description | Define and validate the UX contract for small GIS web apps and demo micro-apps. Use when designing, reviewing, or refining a GIS micro-app, example site, or fast-turn client deliverable so the output feels operational, believable, and easy to understand. |
Define the UX contract before building the app.
Turn a vague GIS demo or client request into a concrete micro-app UX target that can guide planning, implementation, and validation.
A good GIS micro-app should prove three things quickly:
Every GIS micro-app should include:
When the app is an example or portfolio piece, include:
Use realistic requests, not marketing fluff.
Produce:
If you need the full UX contract and acceptance checklist, read:
references/gis-microapp-ux-spec.mdList or infer the required inputs before doing work.
Return a concise, usable result with the key artifacts or recommendations.
Do not invent data, credentials, or system context. Flag uncertainty and risky operations clearly.