diagnose

Diagnose and fix Puree engine bugs across subsystems during Blender addon development.

20|2|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/nicolaiprodromov/puree --skill diagnose-nicolaiprodromov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/nicolaiprodromov/puree/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/nicolaiprodromov/puree --skill diagnose-nicolaiprodromov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically diagnose and fix bugs in the Puree engine. This skill targets framework-level issues, not user YAML/SCSS problems.

Core Features & Use Cases

  • Classify symptoms and identify the likely subsystem (render, layout, text, image, event, hot reload) to guide debugging.
  • Trace data flow from input to output to locate where issues originate and what data is incorrect.
  • Add diagnostic output and structured logging to observe runtime behavior and verify fixes.
  • Fix and verify by applying minimal changes, then re-run quick tests and hot-reload cycles to ensure stability.
  • Common root causes include misaligned data, layout inconsistencies, or stale caches that require targeted fixes.

Quick Start

Describe the observed symptom and apply the diagnose workflow to identify the subsystem and implement a fix.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug framework-level bugs in the Puree engine during Blender addon development?

To debug Puree engine framework bugs during Blender addon development, classify the observed symptom to identify the affected subsystem, trace data flow to locate the issue's origin, and add diagnostic output to verify the fix.

What is the best way to diagnose hot-reload issues in a Blender addon?

The best way to diagnose Blender addon hot-reload issues is to apply a structured workflow that isolates the hot-reload subsystem, adds structured logging to observe runtime behavior, and verifies stability through quick hot-reload cycles.

How do I trace data flow to find layout inconsistencies in the Puree engine?

Trace data flow in the Puree engine by following the input-to-output path within the layout subsystem to locate where misaligned data or stale caches originate, then apply minimal changes to resolve the inconsistency.

When should I use structured diagnostic output for Puree engine bugs?

Use structured diagnostic output for Puree engine bugs when you need to observe runtime behavior across event or image subsystems, allowing you to verify applied minimal changes and ensure framework stability during hot-reload cycles.

Can I use this diagnostic workflow for user YAML or SCSS problems in the Puree engine?

No, this diagnostic workflow targets framework-level issues across render, layout, text, image, event, and hot-reload subsystems, and does not apply to user YAML or SCSS problems within the Puree engine.