znlgis
- 181 skills
- 0 followers
- 79 repo stars
- 5 days ago last updated
- ▌ Whitebox Tools · znlgisUse when doing advanced raster, terrain or LiDAR geoprocessing with WhiteboxTools v2.4.0 — whitebox_tools --run=Slope/FillDepressions/BreachDepressions/FlowAccumulationFullWorkflow/Watershed/ExtractStreams, lidar_* tools for LAS point clouds, or the whitebox (whitebox-python 2.3.6) WhiteboxTools wrapper in Python. Also for 'whitebox_tools: command not found', mismatched Python frontend versions, and missing DEM/flow-accumulation intermediate outputs.
- ▌ Home Assistant · znlgisUse when automating a smart home with Home Assistant 2026.11 — configuration.yaml and automations.yaml, triggers/conditions/actions YAML, REST API /api/states and /api/services, WebSocket subscribe_events, long-lived access tokens, Docker container installs; also for 'Configuration invalid' after a YAML edit, 401 from the API, template errors, and entities stuck 'unavailable'. Open-source home automation that runs locally.
- ▌ Bamboobuddy · znlgisUse when building or extending BambooBuddy (A Panda's Day) — a pnpm-workspace kids habit game: Vue 3.5 shell plus Phaser 4.2 game packages, the GameModule/GameContext contract, task JSON validated by zod, 8 gameplay templates across 10 daily tasks, IndexedDB saves with four growth stages, and Vitest/Playwright gates. Also for pnpm verify stage failures, TypeScript 7 breaking vue-tsc, Phaser leaking into the first-screen chunk, and Tauri/Capacitor packaging errors.
- ▌ Maplibre Native · znlgisUse when embedding GPU-accelerated vector maps natively in Android, iOS, macOS, Linux, Windows or Node.js with MapLibre Native (C++ core, BSD-2-Clause) — org.maplibre.gl:android-sdk MapView/MapLibre.getInstance/getMapAsync, CocoaPods MapLibre MLNMapView, @maplibre/maplibre-gl-native mbgl.Map render, offline caching, Bazel/CMake builds, or debugging green map screens, missing submodules and NDK build failures.
- ▌ AI Water Front · znlgisUse when building or debugging a Vue 3 + OpenLayers water-utility dashboard wired to a Dify chat assistant — natural-language queries returning GeoJSON highlights, streaming SSE via fetch + ReadableStream, GeoServer REST layer toggling through a Vite dev proxy with Basic auth, resizable panels and localStorage layout; also for CORS/401 on /geoserver/rest and "no features highlighted" from a CRS mismatch. ai-water-front demo stack: Vue 3.3 + Vite 4 + ol 8 + axios.
- ▌ Stac Cog Titiler · znlgisUse when building cloud-native imagery pipelines with STAC 1.1.0, Cloud Optimized GeoTIFF and TiTiler 2.4.0 — rio cogeo create/validate, pystac-client search, stac-fastapi 7.1.1 with stac-fastapi-pgstac 7.2.1, uvicorn stac_fastapi.pgstac.app:app, titiler.application /cog and /stac tilejson endpoints, MosaicJSON mosaics, or debugging HTTP 416 range errors, blank tiles from band index mismatch and 403 on private object storage.
- ▌ Mathmindforge · znlgisUse when building or extending Math Mind Forge (MathMindForge), a pnpm-workspace math-thinking quest game: Vue 3.5 shell plus trimmed Phaser 4.2 canvas, the LevelModule/LevelRuntime action-dispatch contract, six templates over 20 levels, zod content split into static summary plus lazy level detail, the answerComplete auto-judge contract, IndexedDB saves with evidence and badges, and Vitest/Playwright gates. Also for pnpm verify failures and Phaser leaking into the first-screen chunk.
- ▌ Docker Compose · znlgisUse when orchestrating multi-container Docker apps from one compose.yaml — services/networks/volumes, build vs image, ports and bind mounts, env_file and ${VAR} interpolation, depends_on with healthcheck conditions, profiles, deploy.resources limits. Docker Compose v5.7.1 CLI (docker compose up/down/ps/logs/watch). Also for "docker: 'compose' is not a docker command", "port is already allocated", containers starting before the DB is ready, and data lost after "down -v".
- ▌ Vue3 Map Dashboard · znlgisUse when running, studying or extending a Vue 3 enterprise data-wall demo — Element Plus layout, Tianditu JS API v4 dark basemap, realtime personnel tracking, QWeather integration, pinyin search, XLSX loading from public/data, composable architecture plus cache and leveled logging; also for a blank Tianditu map from a missing tk key, "T is not defined" script loading order, and pinyin filtering that breaks on polyphonic names.
- ▌ Openlayers Vue3 Demo · znlgisUse when building a declarative OpenLayers map in Vue 3 with vue3-openlayers — WMS tile layers, a layer tree loaded from the GeoServer REST API, layer switcher / zoom / scale line / context menu controls, and a Vite dev proxy that injects Basic auth; also for an empty layer tree (401 on /rest/layers.json), blank WMS tiles from a flipped bbox or wrong CRS, and "Failed to resolve component: ol-map". Demo pairs Docker GeoServer + PostGIS + Nginx.
- ▌ Huggingface Transformers · znlgisUse when running or fine-tuning Hugging Face Transformers models in Python — pipeline() inference, AutoModel/AutoTokenizer from_pretrained, device_map + dtype memory management, Trainer fine-tuning, BGE embeddings for Chinese RAG; also for CUDA out of memory on load, transformers 5.22 requires Python 3.11 or newer, pipeline summarization task removed in v5, and ImportError after upgrading. transformers 5.22.2 + PyTorch.
- ▌ Chags · znlgisUse when building or extending CHAGS (Chinese Historical Anecdotes Game Series): each Chinese historical anecdote is one small kids game built with Phaser 4.2 inside a Vue 3.5 + Pinia shell (TypeScript 5.9.3, Vite 8, pnpm workspace, zh/en bilingual). Covers the GameModule/GameContext contract, gameplay template library, JSON + zod content model, IndexedDB saves with spaced-review scheduling, Vitest/Playwright quality gates, and Tauri/Capacitor packaging.
- ▌ Llamaindex · znlgisUse when building RAG and agent applications over documents with LlamaIndex — SimpleDirectoryReader loading, node parsers, VectorStoreIndex with local or external vector stores (Chroma, PGVector, Qdrant), query engines and response modes, chat engines, RouterQueryEngine routing, event-driven Workflows, and FunctionAgent tool calling. Includes GIS use cases such as turning standards and GIS documents into a knowledge base. Covers llama-index 0.14.x (MIT, Python 3.10+).
- ▌ Fy Layout 2 · znlgis bundleUse when writing C# plugins for the FeiYang LightCAD/LightBIM platform (construction site layout) — ILcPlugin registration, ElementType with fixed GUID, [CommandClass]/[CommandMethod] commands, TabItem ribbon menus, 2D Action plus Shape/Solid Provider pairs for fence, lawn, foundation pit, road, prefab house. Also for "LightCAD.Core reference not found" build errors, plugins that load but show no commands, and 2D shapes rendering with empty 3D solids.
- ▌ Grass Gis · znlgisUse when doing GIS geoprocessing with GRASS GIS headlessly — grass --exec and --tmp-project for servers and CI, g.region computational region management, r.* raster, v.* vector, r3.* 3D raster and t.* temporal modules, r.import/v.import data import, or Python scripting with grass.script, grass.script.array and grass.tools.
- ▌ Kepler Gl · znlgisUse when building React/Redux web apps or Jupyter notebooks for large-scale geospatial visual exploration with Kepler.gl 3.3.0-alpha.20 — @kepler.gl/components KeplerGl, @kepler.gl/actions addDataToMap, @kepler.gl/processors processGeojson/processCsvData, and the Python keplergl widget. Also for fixing blank maps from a missing reducer or wrong getState (react-redux 'Could not find ... in the context of Connect(...)'), Mapbox token basemap errors, and oversized addDataToMap payloads.
- ▌ Mapserver · znlgisUse when publishing WMS/WFS/WCS/OGC API Features from a MapServer 8.6.6 .map mapfile — MAP/LAYER/CLASS/STYLE objects, STATUS/PROJECTION/EXTENT errors, WEB.METADATA wms_enable_request and wfs_enable_request, SLD binding, FastCGI plus MS_MAP_PATTERN hardening, and blank GetMap / "No query information to decode" symptoms.
- ▌ Ffmpeg · znlgisUse when converting, cutting, stitching or streaming video/audio from the command line — ffmpeg -i / -ss / -t, fps and scale filters, CRF and preset for H.264/H.265, -hwaccel decoding, hls muxer with hls_time and hls_segment_filename, RTSP/UDP ingestion, frame extraction for textures. FFmpeg 9.0.2. Also for "moov atom not found", non-monotonic DTS warnings, colour shifts from missing -pix_fmt/-color_range, and ffprobe checks before batch jobs.
- ▌ Serilog · znlgisUse when adding structured logging to .NET apps — Serilog.AspNetCore UseSerilogRequestLogging, LoggerConfiguration WriteTo.Console/File, appsettings.json ReadFrom.Configuration, DI via builder.Services.AddSerilog(), or diagnosing missing log output, duplicate ASP.NET Core request logs, and JSON log formatting. Serilog: structured diagnostic logging for .NET with message templates and sinks.
- ▌ Spatialite · znlgisUse when adding spatial SQL to a single-file SQLite database with SpatiaLite — mod_spatialite loading, InitSpatialMetaData, AddGeometryColumn, CreateSpatialIndex/MbrWithin, ST_Transform and GEOS predicates, spatialite_tool or ogr2ogr import of Shapefile, and GPKG fallback; also for 'no such module: mod_spatialite', 'no such function: InitSpatialMetaData', and 'the SPATIALITE_SECURITY environment variable' errors. libspatialite 5.1.0.
- ▌ Acme Sh 2 · znlgisUse when automating SSL/TLS certificate issuance and renewal from Let's Encrypt, ZeroSSL or BuyPass — wildcard certs via DNS-01 for 150+ providers, HTTP-01 webroot, --install-cert with reloadcmd, cron auto-renewal. acme.sh: pure POSIX shell ACME client, zero dependencies. Also for "Verify error: Invalid response", "Create new order error" rate limits, ZeroSSL EAB registration failures, and cron that never renews.
- ▌ Hangfire · znlgisUse when running background jobs in .NET — fire-and-forget BackgroundJob.Enqueue, delayed Schedule, recurring Cron jobs via RecurringJob.AddOrUpdate, Hangfire.SqlServer/Hangfire.InMemory storage, or the Hangfire dashboard at /hangfire. Also for jobs stuck in 'Awaiting' state, dashboard returning 401/404 behind a proxy, and duplicate job execution in multi-instance deployments. Hangfire: background job processing for .NET.
- ▌ Qgis Server · znlgisUse when publishing QGIS projects (.qgs/.qgz) as OGC web services — WMS GetMap/GetPrint, WFS and WFS-T, WMTS, OGC API Features via qgis_mapserv.fcgi with Apache mod_fcgid, Nginx, or Docker, plus QGIS_SERVER_* tuning (MAX_THREADS, PARALLEL_RENDERING, LOG_STDERR); covers "Service unknown or unsupported" and MAP/GetCapabilities checks. QGIS 4.2.3 and LTR 3.44.15.
- ▌ Mapbox Gl JS · znlgisUse when building vector web maps with mapbox-gl 3.34.2 — WebGL rendering, Style Spec layers, data-driven expressions, setTerrain raster-dem, fill-extrusion, or debugging 401 'A valid Mapbox access token is required', 'Style is not done loading', and pk./sk. token handling. Note: v2+ is proprietary under Mapbox TOS and requires a token; MapLibre GL JS is the open-source fork.
- ▌ Opendronemap · znlgisUse when turning drone/aerial imagery into orthophotos, DSM/DTM, point clouds or 3D Tiles with OpenDroneMap — odm CLI via docker run --project-path, --dsm --dtm --orthophoto-resolution --pc-quality --3d-tiles, WebODM 4.0.0 compose, /api/token-auth/ and /api/projects/{id}/tasks, pyodm Node('localhost',3000); also for 'odm_orthophoto.tif' outputs and out-of-memory failures.
- ▌ Map 360 Demo · znlgisUse when wiring a 360° panorama viewer to a plan map — Photo Sphere Viewer v5 markers with data.plan positions, two-way link between panorama yaw/pitch and Leaflet coordinates, virtual-tour arrows, marker CRUD with search and JSON import/export, cubemap vs equirectangular adapters, localStorage persistence; also for a black canvas from a missing CubemapAdapter, marker drift after yaw-to-GPS conversion, and PlanPlugin bounds that do not match the image. Vue 3 + Vite + TypeScript.
- ▌ Duckdb Spatial · znlgisUse when doing spatial analysis inside a DuckDB database or SQL pipeline — INSTALL spatial / LOAD spatial, ST_Read over Shapefile/GeoPackage/GeoJSON, ST_Point/ST_GeomFromText, ST_Intersects/ST_Contains/ST_Buffer joins, ST_Area_Spheroid, ST_AsMVT tiles, DuckDB-WASM; also for 'Extension spatial is not installed' or spatial function does not exist, GEOMETRY vs WKB_BLOB friction, CRS type modifiers, and exporting query results to GeoParquet. GEOMETRY became a built-in type in DuckDB 1.5.
- ▌ Maplibre Gl JS · znlgisUse when building open-source vector web maps with maplibre-gl 6.17.0 — Map/addSource/addLayer, Style Spec v25 layers, data-driven expressions, raster-dem terrain with setTerrain, setSky, setMissingStyleImageResolver, addProtocol for PMTiles, or debugging v6 ESM-only import errors, 'WebGL2 is required', blank maps after setStyle and style-spec expression warnings. MapLibre GL JS is the BSD-3-Clause fork of Mapbox GL JS and needs no access token.
- ▌ Projnet4geoapi · znlgisUse when transforming coordinates or reading CRS definitions in .NET with ProjNet 2.1.0 (NuGet ProjNet, repo ProjNet4GeoAPI) — CoordinateSystemFactory.CreateFromWkt, CoordinateTransformationFactory.CreateFromCoordinateSystems, MathTransform.Transform, CoordinateSystemServices SRID registration. Also for 'no suitable transformation' / null from GetCoordinateSystem, EPSG codes beyond 4326 and 3857 returning null, and SharpMap projects needing the legacy ProjNet4GeoAPI 1.4.1 GeoAPI build.
- ▌ Geos · znlgisUse when working with the GEOS C/C++ geometry engine that powers PostGIS, QGIS, Shapely and GDAL — GEOSGeomFromWKT/GEOSIntersection/GEOSBuffer/GEOSMakeValid C API, geos::geom C++ API, OverlayNG robustness, GEOSPrepare and GEOSSTRtree, or debugging TopologyException and self-intersection.
- ▌ Pdal · znlgisUse when processing point cloud data (LAS/LAZ/BPF/EPT/COPC) via CLI or Python — pipeline JSON workflows, format conversion, reprojection, cropping, outlier removal, ground classification (SMRF), and DEM generation from LiDAR. PDAL (Point Data Abstraction Library) is the point cloud equivalent of GDAL: pdal info/translate/pipeline commands plus pdal.Pipeline Python bindings.
- ▌ Proj · znlgisUse when transforming coordinates or inspecting CRS definitions from the command line — cs2cs, projinfo -s/-t, proj projection math, cct, EPSG lookup, datum shift with grid files, WKT/PROJJSON export, or debugging "Cannot find proj.db" and latitude-first axis order. PROJ 9.9.0: the OSGeo engine behind GDAL/QGIS, with the proj.db SQLite database.
- ▌ Open3d · znlgisUse when processing 3D point clouds and meshes in Python — read/write PLY/PCD, voxel downsample, normal estimation, outlier removal, RANSAC + ICP registration, Poisson surface reconstruction, quadric decimation, and headless/offscreen visualization. Open3D is Intel's open-source 3D data processing library with a C++ core and Python API.
- ▌ Crewai · znlgisUse when orchestrating multi-agent work with crewAI 1.15 — Agent/Task/Crew, Process.sequential vs hierarchical, @tool / BaseTool custom tools, or event-driven Flows with @start/@listen/@router and or_/and_ for branching and state; also when tasks ignore their expected_output, tools never fire because the agent lacks them, or a JSON-first project (agents/*.jsonc + crew.jsonc) needs the YAML scaffold via --classic. Includes wiring GIS analysis as tools.
- ▌ Mineru · znlgisUse when turning PDFs, scans, or Office documents into structured Markdown/JSON for RAG or translation pipelines with MinerU 4.2 — mineru parse / mineru-kit parse, quality tiers flash/basic/standard/advanced, DoclibClient Python SDK, V1 HTTP API, or Docker on NVIDIA GPUs; also when magic-pdf commands fail because 4.0 renamed the entrypoints, when a parse returns quality_tier_unavailable, or when a CI image has no GPU and you need the ONNX/llama.cpp CPU path.
- ▌ Ollama · znlgisUse when running local LLMs — ollama pull/run/ps, Modelfile templates, /api/generate|chat|embed NDJSON streaming, OpenAI-compatible /v1/chat/completions and /v1/responses, tuning num_ctx/num_gpu/keep_alive and OLLAMA_* env vars; also for `connection refused` on 127.0.0.1:11434, OOM on a model that does not fit VRAM, CPU-only inference despite a GPU, and pull timeouts behind a proxy. Ollama v0.40.16.
- ▌ Blender · znlgisUse when scripting Blender's bpy API or batch-processing scenes headless — bpy.data mesh/object creation, Geometry Nodes groups via interface.new_socket, glTF/OBJ/STL export (export_scene.gltf, wm.obj_export, wm.stl_export), GIS footprints to building massing, add-on/extension development; also for "context is incorrect" from bpy.ops under blender -b, --python-exit-code CI gating, and ModuleNotFoundError for system packages.
- ▌ Brutile · znlgisUse when fetching or enumerating map tiles in .NET with BruTile 6.0.0 — HttpTileSource over HttpClient, KnownTileSources.Create, ITileSchema.GetTileInfos for a viewport and resolution, MbTilesTileSource for offline MBTiles, or wiring tiles into Mapsui/SharpMap. Also for missing 'BruTile.Desktop' packages, CS0246 on KnownTileSources, MBTiles SQLite native load failures, and 404s from inverted TMS/OSM y-axis.
- ▌ Deck Gl · znlgisUse when visualizing large geospatial datasets in the browser with deck.gl 9.4.1 — ScatterplotLayer/GeoJsonLayer, HexagonLayer/ScreenGridLayer aggregation, MVTLayer/TileLayer, @deck.gl/mapbox MapboxOverlay over MapLibre, or debugging blank canvases, stale data props and mismatched @deck.gl/* subpackage versions.
- ▌ Geonode · znlgisUse when deploying or automating GeoNode 5.1.1 — docker compose with create-envfile.py, geonode/geonode:5.1.1 image, django4geonode logs, /api/v2/resources and /api/v2/uploads/upload (action=upload|replace|upsert|create), OGC WMS/WFS links from resource.links[], geonode-project customization; also for 502 after compose up, 'GeoNode has no attribute' after upgrade, and upload 401/403 with Basic vs Bearer auth.
- ▌ Leaflet · znlgisUse when adding lightweight 2D tile maps to web pages with leaflet 1.9.4 — L.map/L.tileLayer, markers, popups, GeoJSON overlays, layer control, [lat, lng] ordering, or debugging blank maps, broken default marker icons after bundling, and sizing fixed by invalidateSize().
- ▌ Esphome · znlgisUse when flashing or automating ESP32/ESP8266 firmware with ESPHome 2026.10 — YAML configuration with esphome/esp32/api/ota/wifi blocks, esphome run/compile/logs/upload CLI, OTA updates, native API encryption, substitutions and packages; also for 'Component not found', OTA upload failures, boot loops after flashing, and missing sensor entities in Home Assistant. YAML-driven ESP firmware framework.
- ▌ Langchain · znlgisUse when building LLM apps in Python with LangChain 1.4.10 — LCEL chains (prompt | model | parser), create_agent with @tool and checkpointer+thread_id memory, RAG (loaders, splitters, PGVector, retriever), init_chat_model across providers; also for `ModuleNotFoundError: langchain.memory`, agent forgetting earlier turns, tools never called, and langchain-core version mismatch.
- ▌ Polly · znlgisUse when adding retry, timeout, circuit-breaker, rate-limit or fallback resilience to .NET HTTP/database calls — ResiliencePipelineBuilder AddRetry/AddTimeout/AddCircuitBreaker, Polly 8 ResiliencePipeline, Microsoft.Extensions.Http.Resilience AddStandardResilienceHandler, or fixing TimeoutRejectedException, retries multiplying load, and 'The circuit is now open'. Polly: .NET resilience and transient-fault-handling library.
- ▌ Geolibre · znlgisUse when scripting or self-hosting the GeoLibre GIS app — geolibre Python anywidget (Map/add_geojson/add_cog/save_project), geolibre-mcp stdio server for AI agents, ghcr.io/opengeos/geolibre Docker image, DuckDB-WASM SQL workspace, ?data= and ?url= deep links; also for a blank window on Linux WebKitGTK, sidecar path not allowed from GEOLIBRE_CONVERSION_ROOTS, and Jupyter relay not connected. GeoLibre 3.7.0.
- ▌ Node Red · znlgisUse when building IoT data flows and API integration with Node-RED low-code programming — inject/debug/function/change/switch nodes, the msg.payload message model, MQTT in/out broker configuration and pub/sub, HTTP in/out REST endpoints, context storage, subflows, node-red-dashboard panels, and settings.js configuration.
- ▌ Demos · znlgisUse when building or studying Vue 3 frontend map/panorama demo projects — 360° panorama to Leaflet map linkage, Tianditu dashboards, OpenLayers + Dify smart-water frontend, and vue3-openlayers + GeoServer layer trees. Index of 4 skills: map-360-demo, vue3-map-dashboard, ai-water-front, openlayers-vue3-demo.
- ▌ Vllm · znlgisUse when self-hosting an OpenAI-compatible LLM endpoint with vLLM 0.33 — vllm serve, offline LLM.generate / llm.chat, PagedAttention with continuous batching and prefix caching, --tensor-parallel-size / --pipeline-parallel-size, AWQ/GPTQ/FP8 quantization, or wiring LangChain/LlamaIndex clients at http://localhost:8000/v1; also when the server OOMs on long context, chat requests ignore your sampling params because generation_config.json overrides them, or engine startup dies compiling kernels.
- ▌ Gh CLI 2 · znlgisPatterns for invoking the GitHub CLI (gh v2.100.0+) from agents. Use when the task mentions GitHub, gh, pull requests/PRs, issues, releases, gists, Actions/workflow runs, forks, repo cloning, reviews, or you need exact gh commands. Covers pagination, repo targeting, search vs list, discussions, projects, rulesets, skills, and gh api fallback.
- ▌ Triage 2 · znlgisLabel-based issue triage workflow. Use when a batch of issues needs sorting by priority/type, or the task mentions "triage", "分流", "prioritize issues", "label". Pulls issues, classifies them, and applies labels/assignees via gh.
- ▌ Codemap 2 · znlgisGenerate a structured, hierarchical map of a repository or directory for quick orientation. Use when starting work in an unfamiliar codebase, when the task mentions "project structure", "codebase overview", "directory layout", "what does this repo contain", or when you need a bird's-eye view before diving into specific files.
- ▌ Handoff 2 · znlgisCompact the current conversation into a handoff document for the next agent session. Use when handing off work, ending a long session, or the task mentions "handoff", "交接", "hand over", "continue in next session". References artifacts by path — never copies.
- ▌ Reflect 2 · znlgisReview recent work to identify recurring friction and propose minimal, durable improvements to the opencode config. Use when the user says "reflect", "what can we improve", "review our setup", "optimize the config", or after a series of related sessions reveals a pattern worth codifying.
- ▌ Grilling 2 · znlgisUse when requirements are ambiguous before planning or implementing — ask ONE question at a time, prefer multiple choice, until intent is clear. Triggers include "grill", "interview", ambiguous requirements, clarifying questions.
- ▌ Simplify 2 · znlgisBehavior-preserving code simplification — reduce complexity without changing what the code does. Use when the task mentions "simplify", "reduce complexity", "too clever", "hard to read", "reduce nesting", or after a feature lands and the code needs polishing. Oracle analyzes (read-only), light-orchestrator applies the edits.
- ▌ Wait What 2 · znlgisUse when a user message is confusing or doesn't land — restate it in one sentence to confirm before acting. Triggers include "wait what", unclear requests, ambiguous instructions.
- ▌ Git Master 2 · znlgisAdvanced Git operations — rebase, squash, fixup, blame, bisect, reflog, code archaeology (git log -S/-G), worktrees. Use when the task mentions rebase, squash, bisect, blame, reflog, fixup, finding deleted code, tracing commit history, cleaning up a branch, or recovering lost work.
- ▌ To Tickets 2 · znlgisBreak a spec or plan into trackable GitHub issues. Use when a plan/spec needs splitting into work items, or the task mentions "tickets", "工单", "break into issues", "分解任务". Emits one issue per independently completable unit with acceptance criteria.
- ▌ Code Review 2 · znlgisLightweight single-pass code review for a diff/branch/PR. Use when reviewing changes, checking a PR, or the task mentions "code review", "review my changes", "review this PR", "找 bug", "审查代码". Reports blockers (critical/major) and notes (minor/nit) with evidence; never rewrites code.
- ▌ Git Release 2 · znlgisPrepare a tagged release with release notes, a SemVer version bump, and a gh release command. Use when cutting a release, drafting a changelog, tagging a version, or the task mentions "release", "changelog", "version bump", "tag", or "publish a new version".
- ▌ Office Docs 2 · znlgis bundleRead and write Microsoft Word (.docx) and Excel (.xlsx) files by converting to/from plain text or Markdown. Use when the task mentions reading a Word/Excel document, extracting text from .docx/.xlsx, creating a .docx/.xlsx, or "读 Word", "读 Excel", "生成 docx", "写 xlsx". Pure-Python via bundled scripts; no MS Office or MCP required.
- ▌ Vision Prep 2 · znlgis bundlePreprocess large images and PDF pages before sending them to a vision model. Use when the task mentions reading a large image, a screenshot with small text, a PDF page, or "大图看不清", "PDF 里的图片", "识别 PDF", "图片文字太小". DeepSeek vision downscales each image to ~800x800 and rejects PDF input, so large images must be tiled and PDFs rasterized first.
- ▌ Spec Workflow 2 · znlgisRun a lightweight, spec-driven change workflow — proposal (WHY/WHAT), specs (WHAT), design (HOW), tasks checklist, then archive. Use when the task is a non-trivial feature or behavior change that benefits from durable, git-tracked planning artifacts, or when the request mentions "spec", "proposal", "propose a change", "spec-driven", "openspec", "design doc", "requirements", or "tasks checklist". Not for one-line fixes or pure Q&A.
- ▌ Codebase Design 2 · znlgisUse when designing architecture, choosing module boundaries, or reviewing whether a codebase's structure is sound. A shared vocabulary glossary for module/interface/depth/seam/adapter/leverage/locality.
- ▌ Diagnosing Bugs 2 · znlgisUse when debugging a bug, test failure, or unexpected behavior, before proposing fixes. Build a tight red-capable feedback loop first, then reproduce, hypothesise, instrument, fix, and clean up.
- ▌ Domain Modeling 2 · znlgisUse when a project's domain language is fuzzy, terms are used inconsistently, terminology is drifting, the same concepts keep being re-explained across sessions, or you need to decide whether to record an architectural decision. Owns the CONTEXT.md glossary (a shared vocabulary of domain terms) and offers ADRs only when warranted.
- ▌ Grill With Docs 2 · znlgisUse when requirements are ambiguous AND the domain language is fuzzy — compose the grilling and domain-modeling skills to converge intent while sharpening terminology.
- ▌ Opencode Config 2 · znlgisAuthor and modify OpenCode config in this repository — opencode.json, agents, skills, commands, permissions. Use when editing opencode.json, adding or changing an agent, writing a skill or command, adjusting model routing/permissions, or the task mentions "opencode config", "agent prompt", "SKILL.md", "command", or "permission".
- ▌ Remove Deadcode 2 · znlgisSafely find and delete dead code — unused files, exports, functions, variables, and imports — with verification before each removal. Use when the task mentions "dead code", "unused code", "remove slop", "clean up" (dead code cleanup), "prune", "delete unused", "orphaned files", or after a refactor leaves unused code behind. Verifies via toolchain/LSP before deleting.
- ▌ Security Review 2 · znlgisAudit code changes for security vulnerabilities before merging. Use when reviewing a diff/PR, hardening code, or the task mentions security, injection, XSS, SSRF, secrets, auth, deserialization, path traversal, or "is this safe?". Reports findings; never auto-fixes silently.
- ▌ Verify With Docs 2 · znlgisVerify a specific or fast-moving library, framework, or API against its current documentation before writing code — retrieval-first, never from memory. Use when implementing against a named dependency (especially one that changes fast or whose exact signatures matter), when unsure of an API's current shape, or when the task mentions "which version", "latest API", "did this change", "check the docs", "SDK", or a specific library/framework by name.
- ▌ Writing For Agents 2 · znlgisUse when writing or editing a document an agent consumes — a skill, an AGENTS.md / CLAUDE.md, or any doc reached by a pointer. Triggers include "write a skill", "improve this doc", "agent instructions". For opencode config mechanics use opencode-config instead.
- ▌ Resolving Merge Conflicts 2 · znlgisUse when resolving git merge/rebase conflicts. Resolve each hunk by finding primary sources (commit messages, PRs, issues) to understand original intent. Preserve both intents where possible; never invent new behavior and never --abort.
- ▌ Writing For Agents · znlgisUse when writing or editing a document an agent consumes — a skill, an AGENTS.md / CLAUDE.md, or any doc reached by a pointer. Triggers include "write a skill", "improve this doc", "agent instructions". For opencode config mechanics use opencode-config instead.
- ▌ Resolving Merge Conflicts · znlgisUse when resolving git merge/rebase conflicts. Resolve each hunk by finding primary sources (commit messages, PRs, issues) to understand original intent. Preserve both intents where possible; never invent new behavior and never --abort.
- ▌ Gh CLI · znlgisPatterns for invoking the GitHub CLI (gh v2.100.0+) from agents. Use when the task mentions GitHub, gh, pull requests/PRs, issues, releases, gists, Actions/workflow runs, forks, repo cloning, reviews, or you need exact gh commands. Covers pagination, repo targeting, search vs list, discussions, projects, rulesets, skills, and gh api fallback.
- ▌ Triage · znlgisLabel-based issue triage workflow. Use when a batch of issues needs sorting by priority/type, or the task mentions "triage", "分流", "prioritize issues", "label". Pulls issues, classifies them, and applies labels/assignees via gh.
- ▌ Codemap · znlgisGenerate a structured, hierarchical map of a repository or directory for quick orientation. Use when starting work in an unfamiliar codebase, when the task mentions "project structure", "codebase overview", "directory layout", "what does this repo contain", or when you need a bird's-eye view before diving into specific files.
- ▌ Handoff · znlgisCompact the current conversation into a handoff document for the next agent session. Use when handing off work, ending a long session, or the task mentions "handoff", "交接", "hand over", "continue in next session". References artifacts by path — never copies.
- ▌ Reflect · znlgisReview recent work to identify recurring friction and propose minimal, durable improvements to the opencode config. Use when the user says "reflect", "what can we improve", "review our setup", "optimize the config", or after a series of related sessions reveals a pattern worth codifying.
- ▌ Grilling · znlgisUse when requirements are ambiguous before planning or implementing — ask ONE question at a time, prefer multiple choice, until intent is clear. Triggers include "grill", "interview", ambiguous requirements, clarifying questions.
- ▌ Simplify · znlgisBehavior-preserving code simplification — reduce complexity without changing what the code does. Use when the task mentions "simplify", "reduce complexity", "too clever", "hard to read", "reduce nesting", or after a feature lands and the code needs polishing. Oracle analyzes (read-only), light-orchestrator applies the edits.
- ▌ Wait What · znlgisUse when a user message is confusing or doesn't land — restate it in one sentence to confirm before acting. Triggers include "wait what", unclear requests, ambiguous instructions.
- ▌ Git Master · znlgisAdvanced Git operations — rebase, squash, fixup, blame, bisect, reflog, code archaeology (git log -S/-G), worktrees. Use when the task mentions rebase, squash, bisect, blame, reflog, fixup, finding deleted code, tracing commit history, cleaning up a branch, or recovering lost work.
- ▌ To Tickets · znlgisBreak a spec or plan into trackable GitHub issues. Use when a plan/spec needs splitting into work items, or the task mentions "tickets", "工单", "break into issues", "分解任务". Emits one issue per independently completable unit with acceptance criteria.
- ▌ Code Review · znlgisLightweight single-pass code review for a diff/branch/PR. Use when reviewing changes, checking a PR, or the task mentions "code review", "review my changes", "review this PR", "找 bug", "审查代码". Reports blockers (critical/major) and notes (minor/nit) with evidence; never rewrites code.
- ▌ Git Release · znlgisPrepare a tagged release with release notes, a SemVer version bump, and a gh release command. Use when cutting a release, drafting a changelog, tagging a version, or the task mentions "release", "changelog", "version bump", "tag", or "publish a new version".
- ▌ Office Docs · znlgis bundleRead and write Microsoft Word (.docx) and Excel (.xlsx) files by converting to/from plain text or Markdown. Use when the task mentions reading a Word/Excel document, extracting text from .docx/.xlsx, creating a .docx/.xlsx, or "读 Word", "读 Excel", "生成 docx", "写 xlsx". Pure-Python via bundled scripts; no MS Office or MCP required.
- ▌ Vision Prep · znlgis bundlePreprocess large images and PDF pages before sending them to a vision model. Use when the task mentions reading a large image, a screenshot with small text, a PDF page, or "大图看不清", "PDF 里的图片", "识别 PDF", "图片文字太小". DeepSeek vision downscales each image to ~800x800 and rejects PDF input, so large images must be tiled and PDFs rasterized first.
- ▌ Spec Workflow · znlgisRun a lightweight, spec-driven change workflow — proposal (WHY/WHAT), specs (WHAT), design (HOW), tasks checklist, then archive. Use when the task is a non-trivial feature or behavior change that benefits from durable, git-tracked planning artifacts, or when the request mentions "spec", "proposal", "propose a change", "spec-driven", "openspec", "design doc", "requirements", or "tasks checklist". Not for one-line fixes or pure Q&A.
- ▌ Codebase Design · znlgisUse when designing architecture, choosing module boundaries, or reviewing whether a codebase's structure is sound. A shared vocabulary glossary for module/interface/depth/seam/adapter/leverage/locality.
- ▌ Diagnosing Bugs · znlgisUse when debugging a bug, test failure, or unexpected behavior, before proposing fixes. Build a tight red-capable feedback loop first, then reproduce, hypothesise, instrument, fix, and clean up.
- ▌ Domain Modeling · znlgisUse when a project's domain language is fuzzy, terms are used inconsistently, terminology is drifting, the same concepts keep being re-explained across sessions, or you need to decide whether to record an architectural decision. Owns the CONTEXT.md glossary (a shared vocabulary of domain terms) and offers ADRs only when warranted.
- ▌ Grill With Docs · znlgisUse when requirements are ambiguous AND the domain language is fuzzy — compose the grilling and domain-modeling skills to converge intent while sharpening terminology.
- ▌ Opencode Config · znlgisAuthor and modify OpenCode config in this repository — opencode.json, agents, skills, commands, permissions. Use when editing opencode.json, adding or changing an agent, writing a skill or command, adjusting model routing/permissions, or the task mentions "opencode config", "agent prompt", "SKILL.md", "command", or "permission".
- ▌ Remove Deadcode · znlgisSafely find and delete dead code — unused files, exports, functions, variables, and imports — with verification before each removal. Use when the task mentions "dead code", "unused code", "remove slop", "clean up" (dead code cleanup), "prune", "delete unused", "orphaned files", or after a refactor leaves unused code behind. Verifies via toolchain/LSP before deleting.
- ▌ Security Review · znlgisAudit code changes for security vulnerabilities before merging. Use when reviewing a diff/PR, hardening code, or the task mentions security, injection, XSS, SSRF, secrets, auth, deserialization, path traversal, or "is this safe?". Reports findings; never auto-fixes silently.
- ▌ Verify With Docs · znlgisVerify a specific or fast-moving library, framework, or API against its current documentation before writing code — retrieval-first, never from memory. Use when implementing against a named dependency (especially one that changes fast or whose exact signatures matter), when unsure of an API's current shape, or when the task mentions "which version", "latest API", "did this change", "check the docs", "SDK", or a specific library/framework by name.
- ▌ Opengis Skills · znlgis bundleUse when AI coding assistant needs GIS/CAD/C#/AI/IoT/3D domain expertise for 75 open-source projects. One-stop skill index with tag-based search and on-demand loading for GDAL, GeoServer, QGIS, PostGIS, JTS, CesiumJS, FreeCAD, OpenSCAD, OCCT, NPOI, SqlSugar, Furion, Dify, SuperSplat, Go and more.
- ▌ 3d Skills · znlgisUse when working with 3D Gaussian Splatting (3DGS), .ply model cleanup/compression/publishing, interactive 360-degree panorama visualization and virtual tours, AEC/BIM 3D data processing, or CSG solid modeling. Index of 5 skills: SuperSplat, Photo-Sphere-Viewer, Ara3D-SDK, Elements, and OpenCSG.NET.