debug-mode

Capture runtime evidence from Bun log servers to diagnose frontend UI bugs.

14|Updated Mar 6, 2026

Search Tags:#debugging #frontend #hypothesis testing #bun #runtime evidence #log server

Ready to run

npx skills add https://github.com/andrueandersoncs/debug-skill --skill debug-mode-andrueandersoncs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-mode
Source: https://github.com/andrueandersoncs/debug-skill/tree/main
Command: npx skills add https://github.com/andrueandersoncs/debug-skill --skill debug-mode-andrueandersoncs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @effect/cli, @effect/platform, @effect/platform-bun, effect, and includes scripts (resource) components.

What problem does it solve?

Debug Mode replaces guesswork with captured runtime evidence so frontend and UI bugs can be investigated without asking users to copy console output or manually reproduce every detail.

Core Features & Use Cases

Log server workflow: Starts a local Bun log server, creates sessions, and writes structured NDJSON logs to per-session files.
Evidence-driven debugging: Encourages hypothesis-based investigation for state, timing, branching, and interaction issues instead of adding ad hoc console.log statements.
Cleanup and verification: Includes commands to clear or remove session logs after reproduction and post-fix validation.
Use case: A modal fails to open, state looks wrong, or a value is unexpectedly null; the skill captures the relevant runtime path so the fix is based on logged evidence.

Quick Start

Use the debug-mode skill on the target project path to start evidence-based debugging and analyze the resulting runtime logs.

Frequently Asked Questions about debug-mode

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

FAQPage Schema

How do I debug frontend UI bugs using runtime evidence instead of guessing?▼

Debug frontend UI bugs with runtime evidence by starting a local Bun log server that captures structured NDJSON logs to per-session files. This replaces ad hoc console statements with hypothesis-based investigation for state, timing, and interaction issues.

What is the best way to find the root cause of a state or timing bug in a Bun-based app?▼

The best way to find the root cause of state or timing bugs in a Bun-based app is hypothesis-driven debugging using session-based log files. You tag hypotheses and reproduce the issue to capture the exact runtime path that triggered the unexpected behavior.

Can I use this evidence-driven debugging approach for browser and Bun workflows?▼

Yes, you can use this evidence-driven debugging approach for browser and Bun-based app workflows. It applies to state, timing, branching, and interaction issues where reproduction details and logs matter for identifying the root cause.

How do I clean up session logs after reproducing and fixing a UI bug?▼

Clean up session logs after reproducing and fixing a UI bug by running the included cleanup commands. These commands clear or remove the per-session NDJSON log files and support post-fix validation steps.

Why does my modal fail to open or show a null value unexpectedly?▼

A modal failing to open or showing an unexpectedly null value often stems from state or branching issues. Capturing the relevant runtime path with a Bun log server provides the evidence needed to base your fix on actual execution data.

Do I need Bun installed to run the log server for frontend debugging?▼

Yes, you need Bun installed to run the log server for frontend debugging. The skill relies on a Bun runtime environment and the Effect platform to start sessions, write structured NDJSON logs, and execute cleanup commands.