Delegate independent tasks to specialized agents working concurrently with isolated context.
Afferent Reactive Universe Levels
afferent-reactive-universe-levels
Fix universe level mismatch errors when defining Lean 4 structures containing Reactive.Event or Reactive.Dynamic types in Afferent/Canopy widgets. Use when: (1) compiler error "Type 1 of sort Type 2 but expected Type of sort Type 1", (2) WidgetM won't accept your result structure, (3) structure c...
SKILL.md
Full skill instructions
Afferent Reactive Universe Levels
Problem
When creating Canopy widgets that return structures containing Reactive.Event Spider α or
Reactive.Dynamic Spider α fields, the compiler reports universe level mismatches like:
Application type mismatch: The argument MyResult has type Type 1 of sort Type 2
but is expected to have type Type of sort Type 1 in the application WidgetM MyResult
Context / Trigger Conditions
- Defining a new Canopy widget in
Afferent/Canopy/Widget/ - Widget returns a result structure containing
Reactive.EventorReactive.Dynamic - Error occurs at function signature like
def myWidget (...) : WidgetM MyResult - Identical pattern works in other widget files (e.g., ListBox.lean)
Solution
The open statements must appear BEFORE any structure definitions that use reactive types.
Broken pattern:
namespace Afferent.Canopy
open Afferent.Arbor hiding Event
/-- This structure ends up in Type 1 -/
structure MyResult where
onClick : Reactive.Event Spider Unit
/-! ## Reactive Section -/
open Reactive Reactive.Host -- Too late!
open Afferent.Canopy.Reactive
def myWidget : WidgetM MyResult := ... -- Error: Type 1 vs Type
Fixed pattern:
namespace Afferent.Canopy
open Afferent.Arbor hiding Event
open Reactive Reactive.Host -- Before structure!
open Afferent.Canopy.Reactive
/-- Now correctly in Type 0 -/
structure MyResult where
onClick : Reactive.Event Spider Unit
def myWidget : WidgetM MyResult := ... -- Works
Verification
After reordering, rebuild with ./build.sh. The universe error should disappear and
the widget should compile successfully.
Example
From Toolbar.lean - the working structure:
namespace Afferent.Canopy
open Afferent.Arbor hiding Event
open Reactive Reactive.Host
open Afferent.Canopy.Reactive
structure ToolbarResult where
onAction : Reactive.Event Spider String
def toolbar (actions : Array ToolbarAction) (theme : Theme)
(variant : ToolbarVariant := .filled) : WidgetM ToolbarResult := do
...
Notes
- This affects the
Spidertimeline type resolution - The
hiding EventonAfferent.Arboris necessary because Arbor has its own Event type - Compare with working files like
ListBox.leanorDropdown.leanwhich have opens at the top - Pure WidgetBuilder functions (not WidgetM) don't have this issue since they don't return reactive types
References
- Afferent/Canopy/Widget/Data/ListBox.lean - working example pattern
- Afferent/Canopy/Widget/Input/Dropdown.lean - working example pattern
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
