skills.rest
mgreenly
mgreenlyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugger

Guide debugging decisions for the ikigai TUI platform with a decision-tree workflow.

Updated Jun 3, 2026
Search Tags:#debugging#troubleshooting#constraints#decision-tree#tty#ikigai
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill debugger-mgreenly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/debugger
Command: npx skills add https://github.com/mgreenly/ikigai --skill debugger-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ikigai debugging can be fragile without a clear strategy and constraints. This guide provides a structured approach for diagnosing issues in the ikigai TUI app, including its critical /dev/tty constraint and common failure modes.

Core Features & Use Cases

  • Clear articulation of the critical constraint and its implications for tooling and automation.
  • A concise mapping of build modes (debug, release, sanitize) and their expected behavior.
  • A practical decision-tree workflow to guide issue isolation and debugging steps.

Quick Start

Identify the current failure mode and follow the decision tree to isolate the issue in ikigai.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I debug the ikigai TUI app when it fails to start?▼

To debug the ikigai TUI app, identify the current failure mode and follow a structured decision-tree workflow to isolate the issue, clarifying runtime behavior and guiding troubleshooting steps during crashes or misconfigurations.

What is the /dev/tty dependency constraint in ikigai?▼

The /dev/tty constraint is a critical requirement for the ikigai TUI platform dictating terminal interaction. Documenting this constraint is essential to understand its implications for tooling and automation.

How do debug, release, and sanitize build modes affect ikigai runtime behavior?▼

Build modes in ikigai map specific expected behaviors: debug for development, release for production, and sanitize for memory checks. Understanding these outcomes is required to reason about runtime failures and diagnose misconfigurations.

Can I use standard automation tooling to run the ikigai TUI without a terminal?▼

Running ikigai without standard terminal access is problematic due to the critical /dev/tty dependency. You must account for this constraint when configuring tooling and automation to prevent failures or misconfigurations.

What's the best way to isolate misconfigurations in an ikigai TUI application?▼

The best way to isolate ikigai misconfigurations is using a structured decision-tree workflow. This method enforces documenting critical constraints and build mode outcomes to systematically reason about runtime failures.

Related Skills

Explore More Software Engineering Skills→
multicammulticam

debugger

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

Community
Advanced
LdotJdotLdotJdot
45

csharp

Plan and execute C#/.NET project changes with static validation.

Community
Advanced
stillwater-scstillwater-sc
500

build-test

Build and test CMake targets with gcc and clang compilers.

Official
Advanced
pluginagentmarketplacepluginagentmarketplace
6

debugging

Guide C++ bug reproduction, isolation, and correction with GDB, LLDB, and sanitizers.

Community
Advanced