trace

Trace data flow across Python, Rust, and GLSL layers in the Puree engine.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace data flow through the Puree engine for a specific feature or behavior. Use to understand how a CSS property, event, or render feature works end-to-end across Python, Rust, and GLSL layers.

Core Features & Use Cases

  • Identify the Trace Target: define the feature to trace (CSS property flow, event routing, render path, layout flow, hot reload flow, component flow) and map its data movement.
  • Read Each Layer: identify entry points, transformations, outputs, key variables, and edge cases across all engine layers.
  • Document the Full Path: produce a comprehensive trace showing inputs, transformations, and outputs across layers to map the complete data journey.
  • Identify Extension Points: note where changes could be made to add properties or adjust behavior at any layer.
  • Report: provide a complete, text-based flow diagram and per-layer details with file paths, line numbers, and data transformations.

Quick Start

Choose a trace target (e.g., CSS property flow, event routing, or render path) and document its end-to-end data path across Python, Rust, and GLSL.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I trace data flow across Python, Rust, and GLSL engine layers?

Tracing data flow across Puree engine layers involves mapping a specific feature's entry points, transformations, and outputs across Python, Rust, and GLSL to produce a complete text-based path trace with file paths and line numbers.

What is the best way to trace CSS property flow through a rendering engine?

Tracing CSS property flow through the Puree engine maps the end-to-end data movement of layout steps and render paths, documenting key variables and edge cases across all engine layers to show the complete data journey.

How does event routing work across multiple engine layers in Puree?

Event routing in Puree works by passing data through defined entry points and transformations across Python, Rust, and GLSL layers. Tracing this flow documents the complete event path and identifies where changes can adjust behavior.

Can I trace render paths spanning Python, Rust, and GLSL codebases?

Yes, you can trace render paths spanning Python, Rust, and GLSL codebases. The trace identifies each layer's inputs, transformations, and outputs, providing a comprehensive flow diagram and per-layer details for the complete render path.

How do I identify extension points for engine features across different layers?

Identifying extension points involves tracing the target feature's data flow across all Puree engine layers. The resulting trace notes exactly where changes could be made to add properties or adjust behavior at any specific layer.

What does a complete Puree engine data flow trace report include?

A complete Puree engine data flow trace report includes a full text-based flow diagram and per-layer details. It documents entry points, transformations, outputs, file paths, line numbers, and data transformations for the traced feature.