Expand description
§CVKG Agentic Development Guidelines (v1.3)
All AI agents contributing to this crate MUST follow ALL eight rules:
── Karpathy Guidelines (1–4) ────────────────────────────────────────────
- THINK FIRST — State assumptions. Surface ambiguity. Push back on complexity.
- STAY SIMPLE — Minimum code. No speculative features. No unasked-for abstractions.
- BE SURGICAL — Touch only what’s required. Own your orphans. Don’t improve neighbors.
- VERIFY GOALS — Turn tasks into checkable criteria. Loop until they pass. Never commit broken.
── CVKG Extended Protocols (5–8) ──────────────────────────────────────── 5. TRIPLE-PASS — Read the target, its surrounding context, and its full call graph at least THREE TIMES before making any edit or revision. 6. COMMENT ALL — Every major pub fn, unsafe block, and non-trivial algorithm in every .rs/.ts/.h/.wgsl file MUST have a descriptive doc comment. Comments describe WHY and WHAT CONTRACT, not HOW mechanically. 7. MONITOR LOOPS — Check every tool call / command for progress every 30 seconds. After 3 consecutive identical failures, stop, write BLOCKED.md, and move to unblocked work. Never silently accept a broken state. 8. HARDWARE VERIFIED — NEVER declare success based on mock data/rendering for native crates. Any change to input, rendering, or lifecycle MUST be verified via physical loopback (e.g., cargo run -p berserker) and signal path tracing.
Sources: Karpathy: https://github.com/multica-ai/andrej-karpathy-skills CVKG Extended: Section 14 of the CVKG Design Specification (v1.3) Platform-native widget delegation using winit and AccessKit
This crate provides platform-specific rendering backends for native desktop targets
Structs§
- Native
Asset Manager - A concrete AssetManager for native desktop targets that loads from the local filesystem.
- Native
Renderer - Native renderer backend implementing the Renderer trait. It wraps a shared SurtrRenderer for high-performance GPU drawing.