Agent skill

Rezi Debug Rendering

Debug rendering and layout issues in Rezi apps. An agent skill from RtlZeroMemory/Rezi.

Apache-2.0Auto-check passedDevelopment

Install Rezi Debug Rendering

skills CLI

$ npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install RtlZeroMemory/Rezi rezi-debug-rendering --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/RtlZeroMemory/Rezi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/rezi-debug-rendering .claude/skills/rezi-debug-rendering && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "rezi-debug-rendering" agent skill from https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering into .claude/skills/rezi-debug-rendering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rezi-debug-rendering", 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

$skill-installer install https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering

Type 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.

skills CLI

$ npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install RtlZeroMemory/Rezi rezi-debug-rendering --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RtlZeroMemory/Rezi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/rezi-debug-rendering .agents/skills/rezi-debug-rendering && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rezi-debug-rendering" agent skill from https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering into .agents/skills/rezi-debug-rendering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rezi-debug-rendering", 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.

skills CLI

$ npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install RtlZeroMemory/Rezi rezi-debug-rendering --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RtlZeroMemory/Rezi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/rezi-debug-rendering .cursor/skills/rezi-debug-rendering && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rezi-debug-rendering" agent skill from https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering into .cursor/skills/rezi-debug-rendering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rezi-debug-rendering", 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

$ gemini skills install https://github.com/RtlZeroMemory/Rezi.git --path .codex/skills/rezi-debug-rendering

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install RtlZeroMemory/Rezi rezi-debug-rendering --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RtlZeroMemory/Rezi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/rezi-debug-rendering .gemini/skills/rezi-debug-rendering && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "rezi-debug-rendering" agent skill from https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering into .gemini/skills/rezi-debug-rendering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rezi-debug-rendering", 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.

GitHub CLI

$ gh skill install RtlZeroMemory/Rezi rezi-debug-rendering

Installs 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).

skills CLI

$ npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/RtlZeroMemory/Rezi.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/rezi-debug-rendering .github/skills/rezi-debug-rendering && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "rezi-debug-rendering" agent skill from https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering into .github/skills/rezi-debug-rendering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rezi-debug-rendering", 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.

skills CLI

$ npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install RtlZeroMemory/Rezi rezi-debug-rendering --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RtlZeroMemory/Rezi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/rezi-debug-rendering .opencode/skills/rezi-debug-rendering && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rezi-debug-rendering" agent skill from https://github.com/RtlZeroMemory/Rezi/tree/main/.codex/skills/rezi-debug-rendering into .opencode/skills/rezi-debug-rendering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rezi-debug-rendering", 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: rezi-debug-rendering
GitHub stars: 675
Token cost: ~991 tokens
SKILL.md length: 379 words
Files: 1
Skills in repo: 10
Repo updated: Jun 17, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Debug rendering and layout issues in Rezi apps. An agent skill from RtlZeroMemory/Rezi.

Works in 9 steps: Enable profiling → Check VNode tree structure — ensure no… → Check widget IDs — must be unique across… → …
Has layout problems
SKILL.md covers When to use, Source of truth, Debugging steps and Common causes
Calls node; needs ZRUI_DUPLICATE_KEY

What it does

Rezi Debug Rendering is an agent skill from RtlZeroMemory/Rezi. Debug rendering and layout issues in Rezi apps. Use when UI looks wrong, has layout problems, or renders unexpectedly.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. The repository describes itself as: Build TypeScript TUI backed by fast native rendering engine. The licence is Apache-2.0.

When your agent uses it

Has layout problems
Renders unexpectedly

Example prompts

“/rezi-debug-rendering”

Requirements

A credential in ZRUI_DUPLICATE_KEY
Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash(REZI_PERF=1 *)

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

Enable profiling
Check VNode tree structure — ensure no missing children or null nodes
Check widget IDs — must be unique across the entire tree. Duplicate IDs cause unpredictable behavior
Check nesting depth
Check key props on list items — missing keys cause full re-render and lost state
Inspect with test renderer
Review layout props: width, height, flex, p, gap, align
If animation is involved, verify
Read enriched runtime errors carefully

What it can do on your machine

Read from SKILL.md and the folder at commit 671a8a2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Glob
- Grep
- Bash(REZI_PERF=1 *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
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 these keys or tokens, usually read from environment variables:
- ZRUI_DUPLICATE_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rezi Debug Rendering loads about 991 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 379 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~35
When it runs · the whole SKILL.md, loaded when a task matches: ~991

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from RtlZeroMemory/Rezi at commit 671a8a2, republished under its Apache-2.0 licence (© RtlZeroMemory). 379 words, ~991 tokens.

Download SKILL.mdSave it as .claude/skills/rezi-debug-rendering/SKILL.md (or your agent's skills folder).

name: rezi-debug-rendering
description: Debug rendering and layout issues in Rezi apps. Use when UI looks wrong, has layout problems, or renders unexpectedly.
allowed-tools: Read, Glob, Grep, Bash(REZI_PERF=1 *)
user-invocable: true
argument-hint: [symptom-description]
metadata.short-description: Debug rendering

When to use

Use this skill when:

UI does not look right or has layout problems
Widgets overlap, disappear, or have wrong dimensions
Unexpected re-renders or flicker
Performance issues during rendering

Source of truth

packages/core/src/app/widgetRenderer.ts — full render pipeline
packages/core/src/app/__tests__/widgetRenderer.transition.test.ts — transition behavior expectations
packages/core/src/runtime/commit.ts — VNode → RuntimeInstance tree
packages/core/src/layout/ — layout engine
packages/core/src/renderer/renderToDrawlist/ — draw operations
packages/core/src/widgets/composition.ts — animation hook implementations
packages/core/src/ui/ — design tokens, recipes, and capability tiers

Debugging steps

Enable profiling:

bash

REZI_PERF=1 REZI_PERF_DETAIL=1 node your-app.js

Check VNode tree structure — ensure no missing children or null nodes
Check widget IDs — must be unique across the entire tree. Duplicate IDs cause unpredictable behavior
Check nesting depth:
- Warning at 200 levels
- Fatal at 500 levels
- Flatten unnecessary wrapper nodes
Check key props on list items — missing keys cause full re-render and lost state

Inspect with test renderer:

typescript

const r = createTestRenderer({ viewport: { cols: 80, rows: 24 } });
const result = r.render(myView(state));
console.log(result.toText());  // see actual output
result.findById("my-widget");  // locate specific nodes

Review layout props: width, height, flex, p, gap, align
If animation is involved, verify:
- container widgets (ui.box, ui.row, ui.column, ui.grid) use transition with expected properties (position, size, opacity)
- properties: [] is not accidentally disabling tracks
- opacity stays within [0..1]
- exitTransition exists on nodes that should animate out before removal
- keyed re-entry behavior is intentional (same key cancels in-flight exit)
- exiting nodes are expected to be render-only (not focusable/hit-testable)
- animation hooks are not conditionally called
Read enriched runtime errors carefully:
- ZRUI_DUPLICATE_ID now includes both conflicting widget kinds + ctx.id() guidance
- ZRUI_DUPLICATE_KEY includes the duplicate key and parent context
- ZRUI_INVALID_PROPS includes prop name, widget kind, and expected type
- ZRUI_UPDATE_DURING_RENDER includes guidance to move updates into event handlers/effects

Show full SKILL.md (131 more words)Show less

Common causes

Symptom	Likely cause
Widget not visible	Missing from VNode tree, or zero width/height
Overlapping widgets	Wrong container type (use `column`/`row` not `box`)
Content truncated	Fixed width too small, missing `flex`
Flicker/full re-render	Missing `key` on list items
Transition not animating	`transition` missing, wrong `properties`, or no actual value delta
Opacity animation looks wrong	`opacity` outside `[0..1]` (clamped) or `properties` excludes `opacity`
Exit animation not visible	Missing `exitTransition`, zero/invalid duration, or node has no stable key
Exit node still interactive	Exit nodes are render-only; focus/hit-test should come from active tree only
Crash on deep tree	Nesting depth > 500
DS styling not applied	DS styling is automatic with `ThemeDefinition`; check semantic tokens/theme activation (no `dsVariant` required)
Wheel scrolling not working	Ensure the container uses `overflow: "scroll"` and content exceeds viewport size

Files

Just SKILL.md in .codex/skills/rezi-debug-rendering of RtlZeroMemory/Rezi.

Open the folder on GitHubat commit 671a8a2

Compare with similar skills

Rezi Debug Rendering 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.

Rezi Debug Rendering compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rezi Debug Rendering this skillRtlZeroMemory/Rezi	675	—	~991	Automated safety check: Pass	Apache-2.0	3 mo ago
Trellis Session Insightmindfold-ai/Trellis	15k	4 repos	~1.7k	Automated safety check: Pass	AGPL-3.0	9 days ago
Native Data FetchingCherryHQ/cherry-studio-app	4k	6 repos	~2.9k	Automated safety check: Notes	MIT	today
Debugging Executionsn8n-io/n8n	207k	—	~2.6k	Automated safety check: Pass	Custom licence	today
Aoti Debugpytorch/pytorch	104k	1 repos	~1.7k	Automated safety check: Pass	Custom licence	today
Herdr Throwaway Reproductionherdrdev/herdr	43k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
15k GitHub starsUsed in 4 repos~1.7k tokens
DevelopmentAuto-check passed
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
4k GitHub starsUsed in 6 repos~2.9k tokens
DevelopmentAuto-check: notes
Debugging Executions
n8n-io/n8n
Official
Debug failed or wrong-output workflow executions using executions tools.
207k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
104k GitHub starsUsed in 1 repo~1.7k tokens
DevelopmentAuto-check passed
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
43k GitHub stars~2.4k tokensUpdated today
DevelopmentAuto-check passed
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
258 GitHub starsUsed in 51 repos~2.4k tokens
DevelopmentAuto-check passed

Questions about Rezi Debug Rendering

What does Rezi Debug Rendering do?

Debug rendering and layout issues in Rezi apps. An agent skill from RtlZeroMemory/Rezi. Rezi Debug Rendering is an agent skill from RtlZeroMemory/Rezi. Debug rendering and layout issues in Rezi apps.

When should I use Rezi Debug Rendering?

Rezi Debug Rendering fits situations like: has layout problems; renders unexpectedly.

How do I install Rezi Debug Rendering in Claude Code?

Run `npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a claude-code`. Or copy the skill folder (.codex/skills/rezi-debug-rendering in RtlZeroMemory/Rezi) into .claude/skills/rezi-debug-rendering in your project. Claude Code loads it when a task matches its description.

How do I install Rezi Debug Rendering in Codex?

Run `npx skills add RtlZeroMemory/Rezi --skill rezi-debug-rendering -a codex`. Or copy the skill folder (.codex/skills/rezi-debug-rendering in RtlZeroMemory/Rezi) into .agents/skills/rezi-debug-rendering in your project. Codex loads it when a task matches its description.

Can I use Rezi Debug Rendering 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 RtlZeroMemory/Rezi --skill rezi-debug-rendering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rezi-debug-rendering, .gemini/skills/rezi-debug-rendering, .github/skills/rezi-debug-rendering and .opencode/skills/rezi-debug-rendering in your project.

What does Rezi Debug Rendering need to run?

Going by SKILL.md and its folder, Rezi Debug Rendering needs the command-line tools its instructions call (node) and credentials named ZRUI_DUPLICATE_KEY. Our summary lists: A credential in ZRUI_DUPLICATE_KEY. Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash(REZI_PERF=1 *).

Does Rezi Debug Rendering 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 Rezi Debug Rendering 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. Review the folder before installing.

What licence does Rezi Debug Rendering use?

Rezi Debug Rendering is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rezi Debug Rendering use?

About 991 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rezi Debug Rendering?

Skills that share tags, products or a category with Rezi Debug Rendering: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rezi Debug Rendering?

RtlZeroMemory (a GitHub user) maintains it in RtlZeroMemory/Rezi, which has 675 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on June 17, 2026.

Source: RtlZeroMemory/Rezi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Rezi Debug Rendering

Install Rezi Debug Rendering

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

When to use

Source of truth

Debugging steps

Common causes

Files

Compare with similar skills

Similar skills

Trellis Session Insight

Native Data Fetching

Debugging Executions

Aoti Debug

Herdr Throwaway Reproduction

Systematic Debugging

More from RtlZeroMemory/Rezi

Rezi Add Widget

Rezi Create Screen

Rezi Data Table

Rezi Forms

Rezi Keybindings

Rezi Modal Dialogs

Questions about Rezi Debug Rendering

Install Rezi Debug Rendering

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

When to use

Source of truth

Debugging steps

Common causes

Files

Compare with similar skills

Similar skills

More from RtlZeroMemory/Rezi

Related

Questions about Rezi Debug Rendering