debugger

Diagnose ikigai TUI startup and runtime failures with a decision tree.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/multicam/ikigai-rev --skill debugger-multicam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/debugger
Command: npx skills add https://github.com/multicam/ikigai-rev --skill debugger-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to debugging ikigai, a TUI application with a strict terminal constraint. It helps engineers reproduce, triage, and resolve startup and runtime issues quickly by defining fixed rules and processes.

Core Features & Use Cases

  • Clearly defined constraints and build modes for ikigai development.
  • A decision-tree guide to triage bugs (startup failures, runtime crashes, and behavioral quirks).
  • Best practices, cautions, and failure-mode guidance to reduce debugging time.

Quick Start

Validate the /dev/tty constraint by reproducing a minimal startup sequence and observing the failure mode.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I debug ikigai startup failures when the terminal requires /dev/tty?

Debug ikigai startup failures by reproducing a minimal startup sequence to validate the /dev/tty constraint and observe the failure mode. Use the structured decision tree to triage terminal-specific issues and determine the exact investigation steps.

What is the best way to troubleshoot runtime crashes in a TUI application?

Troubleshoot TUI runtime crashes by applying a structured decision-tree guide to triage behavioral quirks. Define fixed rules and processes to quickly reproduce, diagnose, and resolve runtime issues within the terminal interface.

How do ikigai build modes affect debugging and runtime behavior?

Build modes affect debugging by changing runtime behavior across the ikigai platform. Validate the active build mode against defined constraints to quickly triage behavioral quirks and isolate startup or runtime failures during development.

Why does my ikigai TUI debugger fail to start in a constrained terminal environment?

Your ikigai TUI debugger fails to start because the strict terminal constraint requires /dev/tty access. Reproduce a minimal startup sequence to validate this constraint and observe the failure mode to guide your investigation.

Can I use standard debugging strategies for ikigai behavioral quirks across different build modes?

You can debug ikigai behavioral quirks across build modes by following defined constraints and a decision tree. This structured approach standardizes triage for runtime crashes and startup failures, ensuring consistent investigation steps.

What limitations should I check when troubleshooting ikigai terminal constraints?

Check limitations by validating the /dev/tty constraint, which is strict for the ikigai TUI. Review best practices, cautions, and failure-mode guidance to reduce debugging time and avoid terminal access issues.