A step-by-step guide for finding the cause of software problems. It covers gathering facts, narrowing the issue, reproducing it, and checking common categories such as rendering, state, API, type, style, and performance.

Use it to investigate errors, broken screens, stale data, failed network requests, TypeScript errors, styling problems, or slow behavior.

It prevents guesswork by turning an unclear failure into a smaller, testable problem.

debugging — Cursor rule by kubev2v

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/kubev2v/forklift-console-plugin/debugging

Clone the repo

git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 994 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00004	$0.00994
Opus 5	$0.00002	$0.00497
Sonnet 5	$0.00001	$0.00199
Haiku 4.5	$0.00000	$0.00099

Measured yesterday against content hash 1989dc1706a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debugging scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/workflows/debugging.mdc · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debugging Workflow

Invoke with: "help debug", "troubleshoot", "why isn't this working", "fix this error"

1. Understand the Problem

Gather Information

What is the expected behavior?
What is the actual behavior?
When did it start happening?
Is it reproducible? What are the exact steps?
Any error messages in the console or network tab?

Classify the Issue

Render issue: Component not displaying correctly
State issue: Data not updating or stale
API issue: Network request failing or returning wrong data
Type issue: TypeScript compilation error
Style issue: Layout or visual problem
Performance issue: Slow rendering or memory leak

2. Isolate the Problem

Check the Error Message

Read the full stack trace
Identify the file and line number
Understand what the error means

Narrow Down the Scope

Which component is affected?
Is it a rendering problem or a data problem?
Does it happen with specific data or always?
Does it happen in a specific provider type?

Reproduce Minimally

Find the simplest case that triggers the issue
Remove unrelated code/props to isolate

3. Common Issue Categories

Component Not Rendering

Check if data is loaded (loaded flag)
Check for errors (loadError)
Check conditional rendering logic
Verify props are being passed correctly
Check for early returns hiding content

State Not Updating

Check useState setter is being called
Check useEffect dependencies
Look for stale closures
Verify state is at the right component level
Check if re-render is being suppressed by memoization

API/Resource Issues

Check useK8sWatchResource configuration (GVK, namespace)
Verify the resource exists: oc get <resource> -n <namespace>
Check RBAC permissions: oc auth can-i list <resource>
Look at network tab for failed requests
Check if provider is in Ready state

TypeScript Errors

Read the error message carefully
Check type definitions in @forklift-ui/types
Verify optional chaining for nullable fields
Check import paths and aliases

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 150 lines · 4 tokens per session scan A 1989dc1706a4

Subscribe to this mod's changes

debugging is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 4 tokens to every session and 994 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Backend and APIs Debugging Research

debugging