the signals and their derived score are provisional and subject to change.
validate manually before sharing.
07ac1b01f7c89a6f71945f38f08dfbbea0ae8558f252d1a9418c3 months agoCo-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>8f6264deecf23 months agoCo-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com># Teksilo — Claude Code Reference
## Project Overview
Teksilo is a pure-Rust GUI framework for serious desktop applications. Architecture: retained widget tree with SwiftUI-style layout, AccessKit accessibility, wgpu rendering.
- **License:** MPL2.0 — Copyright (c) 2026-2026 FernTech, all rights reserved
- **Rust edition:** 2024 (resolver 3)
- **Author:** Cyril Jacquet
## Build Commands
```bash
cargo build # Build all crates
cargo test ---
name: teksilo
description: Build, modify, or debug a Rust desktop GUI app that DEPENDS ON the `teksilo` crate (FernTech's pure-Rust GUI framework) — questions about teksilo widgets, layout, Signal/Prop reactivity, events, theming, settings, i18n, animations, reactive data models, accessibility overrides, the `teksu!` DSL (writing a widget tree in it, translating to or from builder calls, or debugging a `teksu!` compile error), and driving or testing the running app through the automation bridge / MCP ---
name: teksilo
description: Build, modify, or debug a Rust desktop GUI app that DEPENDS ON the `teksilo` crate (FernTech's pure-Rust GUI framework) — questions about teksilo widgets, layout, Signal/Prop reactivity, events, theming, settings, i18n, animations, reactive data models, accessibility overrides, the `teksu!` DSL (writing a widget tree in it, translating to or from builder calls, or debugging a `teksu!` compile error), and driving or testing the running app through the automation bridge / MCP ---
name: extract-widget-api
description: Extract the public API and inline documentation of a type from any teksilo crate with a public API (30 of them, including teksilo-core, teksilo-tokens, teksilo-canvas and teksilo-charts; four are also mdBook-cataloged). Use when the user wants to see a type's public surface (struct, builder methods, enums, module doc) without opening the file, or asks things like "show me Button's API", "what are HStack's builder methods", "what's on ListModel", "list teksilo-widget.gitignoreunspecifieddocs/plans