smithery/aztr0nutzs

netninja-gui-wireup

Verify and fix NET-NiNJA GUI wiring so every control maps to a real handler and backend action. Use when auditing UI behavior, fixing no-op buttons/tabs, or producing a control-to-handler/backend map.

Installation

$ npx skills add smithery/aztr0nutzs --skill netninja-gui-wireup

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/aztr0nutzs.

npx skills add smithery/aztr0nutzs

Browse all from smithery/aztr0nutzs

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,480 B
  • docs SUMMARY.md 227 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Netninja GUI Wireup

Goal

Ensure every GUI control is connected to a real handler and backend action, and produce a control map that shows control -> handler -> backend -> output.

Read First

  • netreaper_gui.py (primary UI)
  • netreaperguilegacy.py (legacy UI)
  • guicomponents.py, guibackendstatus.py, guitheme.py
  • Backend entrypoints: job_pipeline.py, modules/, providers/

Workflow

  1. Build a GUI control map by scanning for widget creation and signal hookups (clicked.connect, currentChanged, etc.).
  2. For each control, trace the handler to the backend call and output widget. Record gaps explicitly.
  3. Fix missing wiring: connect signals, implement handlers, or route to existing backend functions.
  4. Validate init order: ensure widgets exist before usage (e.g., navigation lists before binding signals).
  5. Remove no-op or placeholder actions, or mark as intentionally disabled with a clear message.
  6. Update UI state feedback: status chips, logs, or output panes should reflect handler results.

Output Expectations

  • A control map table with file/line references.
  • No GUI element that appears interactive but does nothing.
  • Any fixes are tied to specific files and handlers.