Coding & Development / Debugging
Rubber Duck
/RubberTry it in
When to reach for this
Writing, reviewing and debugging code in plain language.
- First drafts of a function, class or script
- Reading an error message and working out the actual cause
- Reviewing a diff, a design doc or a pull request
- Area
- Debugging
- Effort
- No blanks to fill
- Difficulty
- easy
- Niche
- 8 commands here
Closest commands in the same niche
Fresh and trending
Ordered by the catalogue's own addedAt and popularity fields — not by live traffic, which SlashAI never sees. Some addedAt values in the source data sit in the future, so treat “newest” as newest-in-catalogue rather than as a verified publication date.
Hashtags
What it does
Interrogate your reasoning with pointed questions until the bug surfaces.
How to use
Describe the bug, what you already tried, and what you believe is happening — the questions attack that belief.
Example
/Rubber Bug: state resets on route change Belief: the provider remounts Tried: memoising the provider, logging in useEffect
Run it in
Paste the command, then attach the file or text on the same message - it handles mixed input well.
How did this land?
Only you see this — stored on this devicePaste this command into your AI tool, then come back and say how it went. Your answer stays in this browser — SlashAI has no server and no account, so there is nothing to send it to and nobody who would read it.
You might also like
/DebugQuery
Diagnose the failure and propose a minimal fix for a database query — e.g. a 30-line PostgreSQL query joining orders.
/DebugComponent
Diagnose the failure and propose a minimal fix for a UI component — e.g. a React `<PricingTable />` component with three tier props.
/DebugScript
Diagnose the failure and propose a minimal fix for a script — e.g. a Python script that renames 10.
/DebugApi
Diagnose the failure and propose a minimal fix for an API endpoint — e.g. a `POST /api/orders` Express handler with Stripe integration.