vibeSpatial

PROACTIVELY USE THIS SKILL when the user says "commit", "land", "land this", "ship it", "done", "wrap up", "let's finish", or any intent to commit work. This is the ONLY user entrypoint for the commit workflow — do not invoke $pre-land-review directly for commits. Orchestrates the full landing flow: pre-land review, staging, review marker, and git commit.

PROACTIVELY USE THIS SKILL when wiring a new operation into the vibeSpatial Python dispatch stack — adding a public API method, connecting to GeometryArray, writing or updating the owned dispatch helper, handling CPU fallback observability, coercing GeometryArray or OwnedGeometryArray inputs, or extending DeviceGeometryArray surfaces. This is the Python-side complement to $new-kernel-checklist (which covers the kernel itself). Trigger on: "wire dispatch", "add API", "add method", "GeometryArray", "DGA method", "CPU fallback", "dispatch wrapper", "public API", "coerce", "OwnedGeometryArray".

The review gate that must pass before any commit lands. Called automatically by the $commit skill — do NOT invoke directly when the user says "commit", "land", "ship it", etc. (use $commit instead). Invoke directly only when you want to run the review without committing, or when another skill references it. This is a MANDATORY gate — do not create a git commit without completing this checklist.

PROACTIVELY USE THIS SKILL when wiring a new operation into the vibeSpatial Python dispatch stack — adding a public API method, connecting to GeometryArray, writing or updating the owned dispatch helper, handling CPU fallback observability, coercing GeometryArray or OwnedGeometryArray inputs, or extending DeviceGeometryArray surfaces. This is the Python-side complement to /new-kernel-checklist (which covers the kernel itself). Trigger on: "wire dispatch", "add API", "add method", "GeometryArray", "DGA method", "CPU fallback", "dispatch wrapper", "public API", "coerce", "OwnedGeometryArray".

PROACTIVELY USE THIS SKILL to find relevant files and documentation before starting any work. Use it instead of exploring the codebase manually. Trigger on: any new task, request, question, bug, feature, investigation, or when you need to find code, docs, tests, scripts, kernels, configs, ADRs, architecture docs, or understand how something works. Also trigger on: "where is", "find", "how does", "what file", "which module", "show me", "look up", "search for", "navigate to", "open", "locate", "explore", "investigate", "understand", "learn about", "read about", "check", "review", "audit", "debug", "fix", "modify", "update", "add", "implement", "create", "write", "build", "refactor", "test", "benchmark", "profile", "optimize". This is the fastest way to find anything in the repo — always prefer it over manual grep/glob exploration.

PROACTIVELY USE THIS SKILL when the user provides a PRD, spec, requirements doc, or tasklist and wants end-to-end execution with minimal check-ins. Trigger on: "autonomous mode", "own this", "own this end-to-end", "enact this PRD", "implement all of this", "here are the requirements", "no check-ins unless blocked", or similar. Treat the provided PRD or tasklist as the mandate. Execute through implementation, verification, profiling, docs, and landing when requested. Only interrupt for true external blockers such as missing secrets, required sandbox or network approval, destructive irreversible actions not already authorized, or contradictory requirements.

Use this skill to optimize existing CUDA/NVRTC kernel code, CuPy operations, CCCL primitive usage, or GPU dispatch logic in src/vibespatial/. Unlike gpu-code-review (which flags issues) and cuda-writing (which guides new code), this skill reads existing code and produces concrete rewrites with measured justification. Invoke on pre-existing kernel files to bring them up to NVIDIA best-practice performance standards.

PROACTIVELY USE THIS SKILL when writing, modifying, or reviewing GPU kernels, CUDA/NVRTC kernel source, CCCL primitive usage, device memory management, stream-based pipelining, or any GPU dispatch logic in src/vibespatial/. Covers kernel lifecycle, ADR-0033 tier system, stream overlap patterns, warp-level intrinsics, count-scatter patterns, precompilation (ADR-0034), precision dispatch (ADR-0002), and GPU saturation techniques.

Use this skill to verify GIS correctness of spatial operations, check predicate semantics, validate geometry conventions (winding, closure, DE-9IM), understand edge cases (degenerate geometries, null/empty handling), or answer "does this make sense?" questions about spatial algorithms. This is the domain knowledge oracle for autonomous agents working on vibeSpatial. Trigger on: "is this correct", "should this return", "what does X mean in GIS", "DE-9IM", "winding", "orientation", "edge case", "degenerate", "predicate semantics", "topology", "validity".

PROACTIVELY USE THIS SKILL when reviewing GPU kernel code, CUDA/NVRTC source, CuPy operations, CCCL primitive usage, device memory management, stream-based pipelining, or any GPU dispatch logic. This skill contains quantitative thresholds, anti-pattern detection rules, and architecture-specific guidance for A100, H100, RTX 3090, and RTX 4090 GPUs. Use it to catch performance regressions, memory management issues, synchronization bugs, and precision problems before they land.

PROACTIVELY USE THIS SKILL when adding a new GPU kernel, NVRTC kernel, CCCL primitive wrapper, or any new GPU-dispatched operation to src/vibespatial/. This checklist ensures every registration, warmup, caching, precision, dispatch, test, benchmark, and documentation step is completed. The CUDA-focused worker sub-agent and gpu-code-review skill should reference this checklist. Trigger on: "new kernel", "add kernel", "implement kernel", "write kernel", "create kernel", "new GPU operation", "add GPU", "scaffold kernel".

PROACTIVELY USE THIS SKILL whenever you are writing, modifying, reviewing, or adding a GPU kernel, CUDA kernel, NVRTC kernel source, or any computation in src/vibespatial/ that touches coordinate data on the GPU. This includes work on bounds, distance, point-in-polygon, binary predicates, segment intersection, spatial indexing, overlay, clip, buffer, constructive ops, dissolve, or any new kernel. ADR-0002 requires dual-precision dispatch (fp32/fp64) via PrecisionPlan. This skill contains the full compliance procedure, the precision infrastructure API, kernel-class-specific implementation patterns, and the current compliance status of every kernel file.

Use this skill to optimize existing CUDA/NVRTC kernel code, CuPy operations, CCCL primitive usage, or GPU dispatch logic in src/vibespatial/. Unlike gpu-code-review (which flags issues) and cuda-writing (which guides new code), this skill reads existing code and produces concrete rewrites with measured justification. Invoke on pre-existing kernel files to bring them up to NVIDIA best-practice performance standards.

PROACTIVELY USE THIS SKILL whenever you are writing, modifying, reviewing, or adding a GPU kernel, CUDA kernel, NVRTC kernel source, or any computation in src/vibespatial/ that touches coordinate data on the GPU. This includes work on bounds, distance, point-in-polygon, binary predicates, segment intersection, spatial indexing, overlay, clip, buffer, constructive ops, dissolve, or any new kernel. ADR-0002 requires dual-precision dispatch (fp32/fp64) via PrecisionPlan. This skill contains the full compliance procedure, the precision infrastructure API, kernel-class-specific implementation patterns, and the current compliance status of every kernel file.

PROACTIVELY USE THIS SKILL when the user says "commit", "land", "land this", "ship it", "done", "wrap up", "let's finish", or any intent to commit work. This is the ONLY user entrypoint for the commit workflow — do not invoke /pre-land-review directly for commits. Orchestrates the full landing flow: pre-land review, staging, review marker, and git commit.

The review gate that must pass before any commit lands. Called automatically by the /commit skill — do NOT invoke directly when the user says "commit", "land", "ship it", etc. (use /commit instead). Invoke directly only when you want to run the review without committing, or when another skill references it. This is a MANDATORY gate — do not create a git commit without completing this checklist.

PROACTIVELY USE THIS SKILL when reviewing GPU kernel code, CUDA/NVRTC source, CuPy operations, CCCL primitive usage, device memory management, stream-based pipelining, or any GPU dispatch logic. This skill contains quantitative thresholds, anti-pattern detection rules, and architecture-specific guidance for A100, H100, RTX 3090, and RTX 4090 GPUs. Use it to catch performance regressions, memory management issues, synchronization bugs, and precision problems before they land.

Use this skill to verify GIS correctness of spatial operations, check predicate semantics, validate geometry conventions (winding, closure, DE-9IM), understand edge cases (degenerate geometries, null/empty handling), or answer "does this make sense?" questions about spatial algorithms. This is the domain knowledge oracle for autonomous agents working on vibeSpatial. Trigger on: "is this correct", "should this return", "what does X mean in GIS", "DE-9IM", "winding", "orientation", "edge case", "degenerate", "predicate semantics", "topology", "validity".

PROACTIVELY USE THIS SKILL to find relevant files and documentation before starting any work. Use it instead of exploring the codebase manually. Trigger on: any new task, request, question, bug, feature, investigation, or when you need to find code, docs, tests, scripts, kernels, configs, ADRs, architecture docs, or understand how something works. Also trigger on: "where is", "find", "how does", "what file", "which module", "show me", "look up", "search for", "navigate to", "open", "locate", "explore", "investigate", "understand", "learn about", "read about", "check", "review", "audit", "debug", "fix", "modify", "update", "add", "implement", "create", "write", "build", "refactor", "test", "benchmark", "profile", "optimize". This is the fastest way to find anything in the repo — always prefer it over manual grep/glob exploration.

PROACTIVELY USE THIS SKILL when adding a new GPU kernel, NVRTC kernel, CCCL primitive wrapper, or any new GPU-dispatched operation to src/vibespatial/. This checklist ensures every registration, warmup, caching, precision, dispatch, test, benchmark, and documentation step is completed. The cuda-engineer agent and gpu-code-review skill should reference this checklist. Trigger on: "new kernel", "add kernel", "implement kernel", "write kernel", "create kernel", "new GPU operation", "add GPU", "scaffold kernel".

PROACTIVELY USE THIS SKILL when writing, modifying, or reviewing GPU kernels, CUDA/NVRTC kernel source, CCCL primitive usage, device memory management, stream-based pipelining, or any GPU dispatch logic in src/vibespatial/. Covers kernel lifecycle, ADR-0033 tier system, stream overlap patterns, warp-level intrinsics, count-scatter patterns, precompilation (ADR-0034), precision dispatch (ADR-0002), and GPU saturation techniques.