metabench
9 verified skills
docs/agi/skills/ui-pick-prompting
# Skill: ui-pick-prompting ## Scope Use the ui-pick tool to present structured choices to the user. **Does:** - Show GUI picker with options. - Wait for user selection. - Return structured result (selection, cancelled, etc.). **Does Not:** - Handle complex multi-step wizards. - Manage state between prompts. ## Inputs - Options array (strings or objects with label/value/description). - Theme (optional): `wlilo` (dark) or `bright` (light). ## Procedure ### Via HTTP (Current Session) ```power
tools
docs/agi/skills/autonomous-ui-inspection
# Skill: autonomous-ui-inspection ## Scope Use this skill for **reliable, agent-friendly UI inspection**: - Visual: Screenshots via browser tools. - Numeric: Bounding boxes, styles, overflow detection. **Does:** - Capture screenshots of rendered UI. - Extract layout metrics for validation. - Provide evidence for UI changes. **Does Not:** - Make styling changes (that's a separate task). - Run full E2E test suites. ## Inputs - URL or HTML file path. - "Ready" selector (e.g., `.control-loaded`)
tools
docs/agi/skills/theme-system-integration
# Skill: theme-system-integration ## Scope Add theme support to existing controls or integrate theming into new features. **Does:** - Define params schemas for controls - Register variants in the variant registry - Integrate `resolve_params` for merge priority - Add CSS variable hooks and data attributes - Test theme inheritance and override behavior **Does Not:** - Create controls from scratch (see jsgui3-control-creation skill) - Handle runtime theme switching animations ## Inputs - Contro
development
docs/agi/skills/browser-verification
# Skill: browser-verification ## Scope Use browser subagents to verify UI rendering, capture evidence, and document visual results. **Does:** - Launch demo servers and verify they're running - Navigate browser to check rendered output - Capture screenshots and recordings for documentation - Inspect DOM structure and CSS computed styles - Verify console for errors **Does Not:** - Replace unit tests (use both) - Handle complex user interaction flows (see e2e testing) ## Why Browser Verificatio
development
docs/agi/skills/lab-experimentation
# Skill: lab-experimentation ## Scope Use lab experiments to answer "how should we do this?" questions about jsgui3 behavior. **Does:** - Run existing lab experiments to confirm behavior. - Create minimal new experiments when behavior is unknown. - Promote stable findings into Skills/Patterns. **Does Not:** - Replace unit tests (labs are for exploration). - Cover production deployment scenarios. ## Lab Structure ``` lab/ ├── experiments/ # Individual experiments │ └── 001-topic-
testing
docs/agi/skills/session-discipline
# Skill: session-discipline ## Scope Maintain structured notes across agent sessions to ensure continuity and knowledge transfer. **Does:** - Initialize session folders with standard structure. - Track active work, findings, and follow-ups. - Enable future agents to resume work seamlessly. **Does Not:** - Persist state between AI context windows (that's the purpose of the docs). - Replace version control (still commit changes). ## Session Structure Each session lives in `docs/sessions/<date
testing
docs/agi/skills/jsgui3-control-creation
# Skill: jsgui3-control-creation ## Scope Create new UI controls following jsgui3 patterns, conventions, and theme system integration. **Does:** - Scaffold new control class files. - Apply correct naming conventions (Camel_Case for classes, snake_case for methods). - Set up SSR-safe guards. - Integrate with theme system using `themeable` mixin. - Create accompanying SASS/CSS with CSS variable hooks. - Generate TypeScript declaration files (.d.ts). **Does Not:** - Handle complex data binding (
development
docs/agi/skills/typescript-types
# Skill: typescript-types ## Scope Create and maintain TypeScript declaration files (.d.ts) for jsgui3-html components. **Does:** - Generate .d.ts files for controls and modules - Define interfaces for specs, params, and return types - Update package.json exports for TypeScript consumers - Maintain backward compatibility with JavaScript users **Does Not:** - Convert source files to TypeScript - Add runtime type checking - Handle complex generic patterns ## Inputs - File or module to type (e.
development
docs/agi/skills/inheritance-debugging
# Skill: inheritance-debugging ## Scope Debug constructor inheritance issues where subclass properties are accessed before initialization. **Does:** - Diagnose "undefined is not iterable" and NaN calculation errors - Fix super() initialization order problems - Add fallback defaults in render methods - Verify fixes with incremental testing **Does Not:** - Cover general JavaScript debugging - Handle non-inheritance related bugs ## Context In jsgui3 controls, a common pattern is: 1. Base class
development