skills.rest
Da1sypetals
Da1sypetalsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cutile-annotate

Annotate cuTile kernels with typecheck blocks for LSP inlay hints.

Updated Feb 5, 2026
Search Tags:#diagnostics#kernel development#LSP#typecheck#annotate#cuTile#inlay hints
One-click install
npx skills add https://github.com/Da1sypetals/cutile-lsp --skill cutile-annotate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cutile-annotate
Source: https://github.com/Da1sypetals/cutile-lsp/tree/main/skills/cutile_annotate
Command: npx skills add https://github.com/Da1sypetals/cutile-lsp --skill cutile-annotate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

cuTile kernel authors often lack immediate, editor-based feedback for type correctness and diagnostics. This Skill provides a structured way to annotate kernels so the LSP can generate in-editor inlay hints and warnings, speeding up development and reducing debugging cycles.

Core Features & Use Cases

  • Enables LSP-driven inlay hints and diagnostics for cuTile kernels by guiding <typecheck> blocks and enable markers.
  • Documents a repeatable workflow to annotate kernels and integrate with standard cuTile project setups.
  • Use Case: a developer iterates on a kernel, receives instant type-related feedback and shape/type validation as they code.

Quick Start

Ensure the top of the kernel file contains the enable marker (# cutile-lsp: on) and place the code region markers (# cutile-lsp: start / # cutile-lsp: end) around the kernel. Include a <typecheck> block in the kernel docstring to define parameter shapes and dtypes, so the LSP can parse and surface hints and diagnostics.

Frequently Asked Questions about cutile-annotate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get LSP inlay hints for cuTile kernels?▼

To get LSP inlay hints for cuTile kernels, add the enable marker `# cutile-lsp: on` at the top of your file and wrap kernel code with `# cutile-lsp: start` and `# cutile-lsp: end` markers to activate editor analysis.

What are inlay hints and diagnostics in cuTile kernel development?▼

Inlay hints and diagnostics in cuTile kernel development are LSP-driven editor features that provide immediate, in-editor type correctness feedback and shape validation, reducing debugging cycles during kernel authoring.

How do I define parameter shapes and dtypes for cuTile typecheck blocks?▼

To define parameter shapes and dtypes for cuTile typecheck blocks, include a `<typecheck>` block within the kernel docstring so the LSP can parse it and surface relevant hints and diagnostics.

Do I need any external dependencies to enable cuTile LSP diagnostics?▼

No external dependencies are required to enable cuTile LSP diagnostics, as the skill relies solely on standard cuTile project setups, LSP configuration, and built-in code region markers.

Why are my cuTile inlay hints not showing up during kernel authoring?▼

cuTile inlay hints may not show up if the kernel file lacks the `# cutile-lsp: on` enable marker, missing the `# cutile-lsp: start` and `# cutile-lsp: end` region markers, or lacks a `<typecheck>` block in the docstring.

Related Skills

Explore More Software Engineering Skills→
saskinosiesaskinosie
39

weaviate-local-setup

Sets up and manages a local Weaviate Docker instance with vectorizers and data persistence via Docker volumes.

Community
Advanced
AscendAscend
31

triton-operator-precision-eval

Benchmark Triton operator precision against PyTorch references and generate MERE/MARE reports.

Official
Advanced
tarrragontarrragon
1

lsp-first

Configure language servers and navigate code using LSP protocols.

Community
Intermediate
ulf1ulf1

326-numpy-unittest

Validate NumPy unit tests with numpy.testing assertions and tolerance checks.

Community
Intermediate