PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Write human-facing TileLang design documents for proposed or completed kernel implementations.
Install Writing Tilelang Design Docs
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-design-docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tilelang/writing-tilelang-design-docs .claude/skills/writing-tilelang-design-docs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-tilelang-design-docs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docs into .claude/skills/writing-tilelang-design-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-design-docs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-design-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tilelang/writing-tilelang-design-docs .agents/skills/writing-tilelang-design-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-tilelang-design-docs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docs into .agents/skills/writing-tilelang-design-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-design-docs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-design-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tilelang/writing-tilelang-design-docs .cursor/skills/writing-tilelang-design-docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-tilelang-design-docs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docs into .cursor/skills/writing-tilelang-design-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-design-docs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sablin39/tilelang-cuda-skills.git --path skills/tilelang/writing-tilelang-design-docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-design-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tilelang/writing-tilelang-design-docs .gemini/skills/writing-tilelang-design-docs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-tilelang-design-docs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docs into .gemini/skills/writing-tilelang-design-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-design-docs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-design-docsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tilelang/writing-tilelang-design-docs .github/skills/writing-tilelang-design-docs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-tilelang-design-docs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docs into .github/skills/writing-tilelang-design-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-design-docs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-design-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tilelang/writing-tilelang-design-docs .opencode/skills/writing-tilelang-design-docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-tilelang-design-docs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-design-docs into .opencode/skills/writing-tilelang-design-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-design-docs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-tilelang-design-docs- GitHub stars
- 145
- Token cost
- ~2.2k tokens
- SKILL.md length
- 980 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- None found
At a glance
Write human-facing TileLang design documents for proposed or completed kernel implementations.
- Explaining an algorithm
- SKILL.md covers Establish the document state, Write for a human reviewer, Choose Markdown or interactive… and Choose visuals by review…, plus 3 more sections
- Runs Python scripts from its folder; calls python
- Execution mapping
What it does
Writing Tilelang Design Docs is an agent skill from sablin39/tilelang-cuda-skills. Write human-facing TileLang design documents for proposed or completed kernel implementations. Use when explaining an algorithm, execution mapping, memory flow, pipeline, tensor lifetimes, compiler evidence, tradeoffs, validation, or measured results to a reviewer.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/design-doc-template.md`, `references/tensor-lifetime-format.md` and `scripts/render_tensor_lifetimes.py`).
It sits in Development, covering Architecture decision records. The repository describes itself as: Skills for writing tilelang and debugging with CUDA toolkits.
When your agent uses it
- Explaining an algorithm
- Execution mapping
- Tensor lifetimes
- Compiler evidence
Example prompts
- “/writing-tilelang-design-docs”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 502a514. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Tilelang Design Docs loads about 2.2k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 980 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 980 words (~2,216 tokens).
“Create a document a person can review without reading the implementation first. Explain the problem, the selected design, why it should work, and what evidence supports it. Use a professional, approachable tone and visuals that make the kernel's execution and…”
- name
- writing-tilelang-design-docs
Files
SKILL.md and 4 other files (scripts, references) in skills/tilelang/writing-tilelang-design-docs of sablin39/tilelang-cuda-skills.
- SKILL.md
- references/design-doc-template.md
- references/interactive-design-doc-template.html
- references/tensor-lifetime-format.md
- scripts/render_tensor_lifetimes.py
Open the folder on GitHubat commit 502a514
Compare with similar skills
Writing Tilelang Design Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Tilelang Design Docs this skillsablin39/tilelang-cuda-skills | 145 | — | ~2.2k | Automated safety check: Pass | None | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Architecture DecisionDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Architecture Decision
Donchitos/Claude-Code-Game-Studios
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
More from sablin39/tilelang-cuda-skills
All 10 skills in this repoTorch Profiling Tilelang Programs
sablin39/tilelang-cuda-skills
Inspect a PyTorch baseline with torch.compile graphs/code and torch.profiler before drafting a custom kernel, then compare TileLang and PyTorch timelines, forward/backward regions, and allocations.
Cuda
sablin39/tilelang-cuda-skills
Draft, debug, and measure CUDA kernels and host launch workflows.
Debugging Tilelang Programs
sablin39/tilelang-cuda-skills
Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures.
Designing With Tilefoundry
sablin39/tilelang-cuda-skills
Describe model or operator HIR with TileFoundry, inspect topology and placement, run static cost analysis, visualize authored dataflow, and check a runtime implementation against its evaluator.
Profiling Tilelang Programs
sablin39/tilelang-cuda-skills
Measure TileLang kernel and workflow performance, choose benchmark or timeline tools, and compare implementations fairly.
Optimizing Tilelang Programs
sablin39/tilelang-cuda-skills
Tune a correct TileLang kernel using measured bottlenecks, tile sizes, layouts, pipelining, fusion, and autotuning.
Related
Categories
Questions about Writing Tilelang Design Docs
What does Writing Tilelang Design Docs do?
Write human-facing TileLang design documents for proposed or completed kernel implementations. Writing Tilelang Design Docs is an agent skill from sablin39/tilelang-cuda-skills. Write human-facing TileLang design documents for proposed or completed kernel implementations.
When should I use Writing Tilelang Design Docs?
Writing Tilelang Design Docs fits situations like: explaining an algorithm; execution mapping; tensor lifetimes; compiler evidence.
How do I install Writing Tilelang Design Docs in Claude Code?
Run `npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a claude-code`. Or copy the skill folder (skills/tilelang/writing-tilelang-design-docs in sablin39/tilelang-cuda-skills) into .claude/skills/writing-tilelang-design-docs in your project. Claude Code loads it when a task matches its description.
How do I install Writing Tilelang Design Docs in Codex?
Run `npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a codex`. Or copy the skill folder (skills/tilelang/writing-tilelang-design-docs in sablin39/tilelang-cuda-skills) into .agents/skills/writing-tilelang-design-docs in your project. Codex loads it when a task matches its description.
Can I use Writing Tilelang Design Docs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-design-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-tilelang-design-docs, .gemini/skills/writing-tilelang-design-docs, .github/skills/writing-tilelang-design-docs and .opencode/skills/writing-tilelang-design-docs in your project.
What does Writing Tilelang Design Docs need to run?
Going by SKILL.md and its folder, Writing Tilelang Design Docs needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Writing Tilelang Design Docs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Tilelang Design Docs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Writing Tilelang Design Docs use?
No licence was found for Writing Tilelang Design Docs or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Tilelang Design Docs use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.
What are the alternatives to Writing Tilelang Design Docs?
Skills that share tags, products or a category with Writing Tilelang Design Docs: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Tilelang Design Docs?
sablin39 (a GitHub user) maintains it in sablin39/tilelang-cuda-skills, which has 145 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 15, 2026.
Source: sablin39/tilelang-cuda-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.