Initial public release
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s

This commit is contained in:
Jens
2026-08-31 21:56:53 +02:00
commit faeb58ef6d
1386 changed files with 263203 additions and 0 deletions
+54
View File
@@ -0,0 +1,54 @@
# Skill: Codex Pass Review
Use this skill at the end of every pass before returning the result.
## Read first
- `docs/30-codex-optimization/CODEX_RUN_CHECKLIST.md`
- `docs/qaqc/CODEX_SELF_REVIEW.md`
- `docs/qaqc/QUALITY_GATES.md`
- active pass prompt
## Review checklist
- [ ] Did the pass stay within scope?
- [ ] Were governance/invariants respected?
- [ ] Were API/database contracts preserved or updated intentionally?
- [ ] Were tests or smoke checks run?
- [ ] Were docs/status/changelog updated?
- [ ] Are limitations explicit?
- [ ] Are next steps clear?
- [ ] Is there any hidden mock/placeholder behavior?
- [ ] Did any new dependency appear?
- [ ] Did any path or convention drift from repo standards?
## Required final response
```md
## Completed
## Changed files
## Commands run
## Test results
## Self-review
## Known limitations
## Next pass
```
## Scoring
Score each from 0-10:
- Scope control.
- Architecture consistency.
- Backend correctness.
- Frontend correctness, if applicable.
- GIS correctness.
- Test coverage.
- Documentation completeness.
- Release readiness.
@@ -0,0 +1,38 @@
# Skill: Frontend MapLibre Workbench
Use this skill when building React/TypeScript UI, MapLibre maps, layer controls, workbench pages, state hooks and API clients.
## Read first
- `docs/UI_PAGE_SPECIFICATIONS.md`
- `docs/DESIGN_SYSTEM.md`
- `docs/GEOINTEL_STYLE_GUIDE.md`
- `docs/FRONTEND_STATE_AND_API_CLIENT.md`
- `docs/FRONTEND_STATE_CONTRACTS.md`
## Frontend rules
- UI supports analysis; it is not the product itself.
- Every data panel needs empty, loading, error and success states.
- API calls go through a typed client layer.
- Do not hardcode fake backend responses into production components.
- Map layers must have stable IDs and documented styles.
- Keep components modular and testable.
## Page checklist
- [ ] Route exists.
- [ ] Data fetching state handled.
- [ ] Empty state useful.
- [ ] Error state actionable.
- [ ] Success state shows real data shape.
- [ ] Layer toggling works for available data.
- [ ] Accessibility basics respected.
## Completion report fields
- Pages/components changed.
- API client methods used.
- UI states covered.
- Visual limitations.
- Tests/build commands run.
+52
View File
@@ -0,0 +1,52 @@
# Skill: GeoAI Backend Build
Use this skill when implementing FastAPI routers, services, schemas, domain logic, adapters or background-job entry points.
## Read first
- `docs/governance/GEOINTEL_CONSTITUTION.md`
- `docs/governance/ARCHITECTURE_INVARIANTS.md`
- `docs/SERVICE_ARCHITECTURE.md`
- `docs/API_CONTRACTS.md`
- active pass prompt
## Backend rules
- Keep routers thin.
- Put business logic in services.
- Put external integrations behind adapters.
- Use typed request/response schemas.
- Return stable error codes from the error catalog.
- Do not let AI/model code write directly to the database.
- Do not perform long processing synchronously when it belongs in jobs.
## Expected package pattern
```text
backend/app/
api/
core/
db/
models/
schemas/
services/
workers/
adapters/
```
## Implementation checklist
- [ ] Add/extend schemas.
- [ ] Add/extend service.
- [ ] Add/extend router.
- [ ] Add validation.
- [ ] Add tests or smoke checks.
- [ ] Update docs/log/changelog when behavior changes.
## Completion report fields
- Endpoints added/changed.
- Services added/changed.
- Validation rules added.
- Tests run.
- Contract deviations, if any.
+44
View File
@@ -0,0 +1,44 @@
# Skill: PostGIS Migration
Use this skill when creating database models, migrations, geometry storage or spatial indexes.
## Read first
- `docs/DATABASE_SCHEMA.md`
- `docs/DATABASE_IMPLEMENTATION_PLAN.md`
- `docs/standards/GIS_STANDARDS.md`
- `docs/specs/STATE_MACHINES.md`
- relevant ADRs
## Spatial rules
- PostgreSQL + PostGIS is mandatory.
- Store canonical geometry in PostGIS geometry columns.
- Preserve original CRS metadata on datasets.
- Normalize internal spatial operations according to GIS standards.
- Create spatial indexes for queryable geometries.
- Use explicit units for area, distance and length.
## Migration checklist
- [ ] Add model.
- [ ] Add migration.
- [ ] Add indexes.
- [ ] Add constraints.
- [ ] Add state enum where required.
- [ ] Add rollback-safe migration where practical.
- [ ] Add fixture/test coverage for geometry roundtrip.
## Forbidden shortcuts
- No geometry as unvalidated plain text for canonical records.
- No silent CRS assumptions.
- No schema drift from docs without updating the contract.
## Completion report fields
- Tables changed.
- Geometry columns added.
- Indexes added.
- Migration commands run.
- Compatibility risks.
+45
View File
@@ -0,0 +1,45 @@
# Skill: QA/QC Review
Use this skill for comparing predicted geospatial outputs against reference layers such as GRB buildings.
## Read first
- `docs/QA_QC_SPECIFICATION.md`
- `docs/QA_QC_ENGINE.md`
- `docs/qaqc/ANTI_REGRESSION_RULES.md`
- `docs/API_EXAMPLE_RESPONSES.md`
## QA/QC rules
- Reference data and predicted data must remain separate.
- Matching thresholds must be explicit.
- False positives and false negatives must be exportable.
- Metrics must be reproducible from stored inputs.
- Do not hide low-confidence results; classify or flag them.
## Core metrics
- IoU.
- Precision.
- Recall.
- F1.
- Matched count.
- Unmatched reference count.
- Unmatched prediction count.
## Implementation checklist
- [ ] Define matching method.
- [ ] Implement geometry overlap calculation.
- [ ] Calculate metrics.
- [ ] Persist or return QA results.
- [ ] Create GeoJSON outputs for matched/unmatched classes.
- [ ] Add fixture-based tests.
## Completion report fields
- Matching method.
- Thresholds.
- Metrics returned.
- Fixtures used.
- Known QA limitations.
+37
View File
@@ -0,0 +1,37 @@
# Skill: Raster Pipeline
Use this skill for GeoTIFF/raster metadata, clipping, tiling, band handling and remote-sensing indices.
## Read first
- `docs/RASTER_OPERATIONS_SPEC.md`
- `docs/standards/RASTER_STANDARDS.md`
- `docs/DETECTION_PIPELINE_SPEC.md` when preparing AI tiles
- `docs/STORAGE_ARCHITECTURE.md`
## Raster rules
- Preserve georeferencing metadata.
- Never drop CRS silently.
- Keep raster-derived outputs traceable to source dataset and parameters.
- Use deterministic tile naming.
- Store heavy outputs under documented storage roots, not random folders.
- For V1, prefer metadata and small fixtures over heavy real rasters.
## Operations checklist
- [ ] Validate raster readable.
- [ ] Extract CRS, bounds, transform, dimensions, band count, dtype.
- [ ] Clip by area where requested.
- [ ] Generate tiles with configured tile size and overlap.
- [ ] Preserve mapping from tile pixels to map coordinates.
- [ ] Emit metadata JSON for downstream services.
- [ ] Add tests with tiny raster fixtures when possible.
## Completion report fields
- Raster operations implemented.
- Metadata fields produced.
- Storage paths used.
- Tests run.
- Known limitations.
+37
View File
@@ -0,0 +1,37 @@
# Skill: Vector Processing
Use this skill for GeoJSON/shapefile/GPKG ingestion, clipping, buffering, spatial joins, polygon validation and exports.
## Read first
- `docs/VECTOR_OPERATIONS_SPEC.md`
- `docs/GEOSPATIAL_VALIDATION_RULES.md`
- `docs/standards/GIS_STANDARDS.md`
- `docs/API_CONTRACTS.md`
## Vector rules
- Validate geometry before storage or analysis.
- Repair simple invalid geometries only when documented and reported.
- Preserve source metadata.
- Use explicit CRS transformation.
- Export GeoJSON with stable properties.
- Keep analysis outputs traceable to input layer and analysis run.
## Operations checklist
- [ ] Load vector data.
- [ ] Validate schema and geometry.
- [ ] Reproject if needed.
- [ ] Clip to area.
- [ ] Perform requested spatial operation.
- [ ] Store or export result.
- [ ] Add tests using small fixtures.
## Completion report fields
- Operations implemented.
- Geometry types supported.
- CRS behavior.
- Tests run.
- Unsupported edge cases.