gis-platform-engineering
Use when implementing GIS maps, spatial data services, maps integrations, geocoding, spatial APIs, or PostGIS-backed geospatial platforms. Load absorbed GIS mapping, maps integration, and PostGIS backend references as needed.
Best use case
gis-platform-engineering is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when implementing GIS maps, spatial data services, maps integrations, geocoding, spatial APIs, or PostGIS-backed geospatial platforms. Load absorbed GIS mapping, maps integration, and PostGIS backend references as needed.
Teams using gis-platform-engineering should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gis-platform-engineering/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gis-platform-engineering Compares
| Feature / Agent | gis-platform-engineering | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when implementing GIS maps, spatial data services, maps integrations, geocoding, spatial APIs, or PostGIS-backed geospatial platforms. Load absorbed GIS mapping, maps integration, and PostGIS backend references as needed.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GIS Platform Engineering Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. Use this parent skill as the active GIS implementation entrypoint. Keep enterprise concepts in `gis-enterprise-domain`; use this skill for build, integration, and platform engineering. <!-- dual-compat-start --> ## Use When - Building GIS map interfaces, layers, spatial search, geocoding flows, route displays, or geospatial APIs. - Integrating third-party map providers, tile services, location capture, or spatial analytics. - Designing PostGIS-backed storage, indexes, queries, and backend services for geospatial products. ## Do Not Use When - The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow. - The request only needs a trivial answer and no reference module needs to be loaded. ## Required Inputs - Gather the concrete system, repository, environment, constraints, and deliverable before loading references. - Identify which absorbed reference file is needed; do not load every migrated reference by default. ## Workflow 1. Load `gis-enterprise-domain` for domain boundaries, organisational concepts, and GIS vocabulary. 2. Load the needed implementation reference: - `references/gis-mapping.md` for map UI, layers, markers, controls, and interaction. - `references/gis-maps-integration.md` for map providers, geocoding, routing, and external integrations. - `references/gis-postgis-backend.md` for PostGIS schema, indexing, spatial SQL, and backend patterns. 3. Pair with `database-design-engineering`, `postgresql-engineering`, `api-design-first`, and frontend skills when the GIS work crosses those boundaries. ## Quality Standards - Treat coordinate reference systems, precision, privacy, and offline/low-bandwidth constraints as first-class design inputs. - Make spatial indexes, query shape, geometry validity, and API payload size explicit for backend work. - Keep map UI usable for inspection, comparison, filtering, and task completion, not only visual display. ## Anti-Patterns - Treating absorbed reference files as active skills or separate routing entrypoints. - Loading every migrated child reference instead of the one that matches the task. - Producing generic advice without constraints, evidence, or next verification steps. ## Outputs - GIS implementation plan, map UI spec, spatial API/schema, integration notes, or PostGIS review. ## References - Load only the eferences/<old-skill>.md files named in the workflow when their depth is required. <!-- dual-compat-end -->
Related Skills
world-class-engineering
Use when designing, building, reviewing, or upgrading production software systems that must be secure, performant, maintainable, scalable, and user-centered. Apply before writing specs, code, architecture, APIs, databases, mobile apps, SaaS platforms, or ERP systems.
mobile-platform-operations
Cross-platform mobile operations orchestration for app icons, mobile RBAC, SaaS planning, Play Store review, and operational mobile delivery assets.
ios-platform-capabilities
iOS platform capability orchestration for biometrics, Bluetooth printing, push notifications, native PDF export, and production networking.
reliability-engineering
Use when designing or reviewing production reliability for APIs, SaaS platforms, background jobs, distributed workflows, mobile backends, or AI-enabled systems. Covers timeout and retry policy, degradation, queue safety, incident readiness, and recovery-aware design.
kubernetes-platform
Use when running Kubernetes as a platform team — bootstrapping self-managed clusters on Debian/Ubuntu, designing multi-tenant RBAC, enforcing Pod Security and resource quotas, and operating cluster lifecycle (upgrades, certs, etcd, ingress, cert-manager, metrics-server). Self-managed first, cloud-managed second.
deployment-release-engineering
Use when designing or reviewing deployment pipelines, rollout strategies, release gates, rollback plans, migration-safe releases, and post-deploy verification for production systems. Covers build promotion, environment strategy, release evidence, and operational safety.
postgresql-engineering
Use when designing, implementing, or reviewing PostgreSQL application data models, SQL, indexes, constraints, extensions, server-side routines, and production query patterns. Load the absorbed PostgreSQL reference files for fundamentals, advanced SQL, schema patterns, and server programming.
mysql-engineering
Use when designing, implementing, or reviewing MySQL application schemas, SQL, indexes, constraints, stored routines, and production query patterns. Load absorbed MySQL best-practice, data-modeling, and advanced-SQL reference files as needed.
database-design-engineering
Use when designing or reviewing relational or document-backed data architecture for SaaS platforms, ERP systems, APIs, analytics stores, or mobile sync. Covers domain modeling, tenancy, indexing, migrations, integrity, retention, and performance tradeoffs.
ai-prompt-engineering
Use when writing, refining, or structuring prompts for AI-powered app features — system prompts, user prompt templates, few-shot examples, chain-of-thought, prompt versioning, and defensive prompting
web-app-security-audit
Use when auditing a PHP/JavaScript/HTML web application for security vulnerabilities. Covers configuration, authentication, authorization, input validation, XSS, API security, HTTP headers, and dependency scanning. Produces a severity-rated audit...
vibe-security-skill
Use when designing or reviewing security for a web application, API, or multi-tenant SaaS — produces threat model, abuse case list, auth/authz matrix, and secret handling plan; covers OWASP Top 10 2025 and the AI-code-generation blind spots. Neighbours — api-design-first owns auth model fields, deployment-release-engineering owns secret rotation choreography, ai-security and llm-security own model-specific threats.