floatty-architect

Guide architecture decisions for SolidJS, Yjs, and Rust services.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/float-ritual-stack/floatty --skill floatty-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: floatty-architect
Source: https://github.com/float-ritual-stack/floatty/tree/main/.claude/skills/floatty-architect
Command: npx skills add https://github.com/float-ritual-stack/floatty --skill floatty-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Floatty-Architect provides structured architectural guidance to help engineers review, plan, and audit Floatty's architecture across the SolidJS frontend, Yjs CRDT backend, and Rust services. It clarifies how to apply established patterns, detect architectural anti-patterns, and reason about complex interactions such as CRDT synchronization, PTY lifecycles, and IPC.

Core Features & Use Cases

  • Mode-aware guidance for Feature Guidance, Bug Review, and Architecture Exploration.
  • Documentation of established Floatty patterns (Two-Lane Event System, Origin-Tagged Transactions, Terminal Lifecycle Outside SolidJS, Ref-Counted Observers, Defensive Disposal).
  • Handoff prompts and investigation templates to accelerate AI-assisted coding reviews and architectural audits.

Quick Start

Describe the architecture challenges you want to solve and specify the required patterns to apply; I will generate a targeted architecture plan and a concrete handoff prompt.

Frequently Asked Questions about floatty-architect

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

FAQPage Schema
How do I architecture plan features for a SolidJS frontend and Yjs CRDT backend?

Architecture planning for a SolidJS frontend and Yjs CRDT backend is guided by mode-aware feature planning that proposes and validates established patterns like the Two-Lane Event System. It generates actionable handoff prompts for AI coding agents to accelerate implementation.

What is the Two-Lane Event System pattern in CRDT synchronization?

The Two-Lane Event System is an established architectural pattern for managing CRDT synchronization and complex interactions. It separates event processing to clarify data flow between the SolidJS frontend, Yjs backend, and Rust services during feature planning.

How do I review code for architectural anti-patterns in a Tauri application?

Code review for architectural anti-patterns in a Tauri application uses a dedicated Bug Review mode to detect violations. It enforces explicit mode detection and adherence to established patterns like Origin-Tagged Transactions and Defensive Disposal.

Does this architecture guidance work with Rust services and PTY lifecycles?

Architecture guidance for Rust services and PTY lifecycles is fully supported through pattern documentation like Terminal Lifecycle Outside SolidJS. It helps reason about complex interactions including IPC and CRDT synchronization across the stack.

Can I generate handoff prompts for AI coding agents from architecture audits?

Handoff prompts for AI coding agents are generated directly from architecture audits and feature planning. The guidance produces investigation templates and concrete prompts that validate patterns like Ref-Counted Observers for downstream implementation.

When should I not use Origin-Tagged Transactions for CRDT state management?

Origin-Tagged Transactions should be reconsidered when architecture exploration reveals they conflict with existing PTY lifecycles or IPC patterns. Constraint detection during code reviews identifies when established patterns fail to fit specific feature requirements.