floatty-interactive-view

Name: floatty-interactive-view
Availability: InStock
Author: float-ritual-stack

Validate spec verbs and host dispatch wiring for interactive Floatty views.

Updated Dec 19, 2025

Search Tags:#kanban #floatty #interactive-views #door-design #spec-architecture #chirp-dispatch

Ready to run

npx skills add https://github.com/float-ritual-stack/floatty --skill floatty-interactive-view

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: floatty-interactive-view
Source: https://github.com/float-ritual-stack/floatty/tree/main/.claude/skills/floatty-interactive-view
Command: npx skills add https://github.com/float-ritual-stack/floatty --skill floatty-interactive-view

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Architectural constraints for building interactive Floatty views inside the render door, ensuring a clean separation between spec-defined verbs and host dispatch logic. It helps prevent patch-stacking and mutation-logic leaks when adding new interactive views (kanban, tree, calendar, graph) that mutate the outline.

Core Features & Use Cases

Enforces the spec-driven verb surface and host-dispatch pattern to avoid direct store mutations inside door components.
Provides a repeatable workflow for introducing interactive views that require drag, edit, or navigation, with required reads and validation steps.
Guides teams to pre-validate patterns before writing component code, reducing regressions and ensuring consistent behavior across views like kanban, tree, calendar, and graph.

Quick Start

Validate the spec surface and host dispatch pattern before implementing any new interactive view that mutates the outline.

Frequently Asked Questions about floatty-interactive-view

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

FAQPage Schema

How do I prevent direct store mutations when building interactive kanban or tree views?▼

To prevent direct store mutations in interactive views, enforce a spec-driven verb surface and route all outline changes through host dispatch wiring rather than patching state directly inside door components.

What is the required setup before coding drag or click-to-edit features for a Floatty view?▼

Before coding interactive Floatty views, you must declare verbs in the spec, verify host dispatch wiring exists, and establish a required re-projection subscription to validate the architectural pattern.

How does host dispatch wiring work for interactive calendar and graph patterns?▼

Host dispatch wiring separates spec-defined verbs from mutation logic, ensuring interactive calendar and graph patterns route outline changes through the host rather than leaking state mutations into components.

Why does my interactive view logic leak mutation patterns and cause regressions?▼

Mutation logic leaks and regressions occur when interactive views bypass spec-defined verbs and host dispatch patterns, causing patch-stacking instead of maintaining clean architectural separation during outline mutations.

Can I use this pattern for keyboard navigation and drag interactions that mutate the outline?▼

Yes, this pattern applies to any interactive view requiring drag, click-to-edit, or keyboard navigation that mutates the outline, covering kanban, tree, calendar, and graph patterns with consistent validation steps.

What's the best way to validate spec architecture before implementing interactive view components?▼

The best way to validate spec architecture is pre-validating the verb surface and host dispatch pattern before writing component code, ensuring re-projection subscriptions are established to reduce regressions across interactive views.