ui-core

Guide UI-core integration by defining logic boundaries and message routing for TagList, FileWorkspace, and AppDatabase.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Zelenov/frename --skill ui-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-core
Source: https://github.com/Zelenov/frename/tree/main/.claude/skills/ui-core
Command: npx skills add https://github.com/Zelenov/frename --skill ui-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI-heavy features often cross UI state and core logic, creating unclear ownership and brittle boundaries. This guide helps teams decide where logic belongs, how to wire UI actions to core operations, and how to coordinate file workspace with TagList and AppDatabase.

Core Features & Use Cases

  • Provides a clear boundary between UI state management and core data handling for new features.
  • Describes when to place logic in the UI layer vs the core, and how to connect messages to core operations.
  • Use case: designing a feature that touches both UI state and core data to ensure consistent data flow and testability.

Quick Start

Use ui-core to determine if a new feature's logic belongs in UI state management or core data handling before implementation.

Frequently Asked Questions about ui-core

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

FAQPage Schema
How do I decide where feature logic belongs between UI state and core data?

To decide where feature logic belongs between UI state and core data, evaluate whether the logic manages presentation or handles data persistence. Place presentation rules in UI state and route data operations to core layers for testability.

What is the best way to wire UI actions to core data operations?

The best way to wire UI actions to core data operations is by routing messages through explicit boundaries connecting UI state management directly to core data handling, ensuring consistent data flow and predictable behavior across feature implementation.

How do I coordinate FileWorkspace with TagList and AppDatabase components?

Coordinate FileWorkspace with TagList and AppDatabase by establishing clear boundaries for data flow and message routing. Ensure UI components interact with core data through consistent operations that maintain safe data access and testability.

When do I need to define explicit boundaries for frontend-backend integration?

Define explicit boundaries for frontend-backend integration when new UI components interact with core data structures like TagList, FileWorkspace, or AppDatabase. This prevents unclear ownership and brittle boundaries in features crossing UI state and core logic.

Does separating UI state from core data handling improve feature testability?

Separating UI state from core data handling improves feature testability by ensuring consistent data flow and predictable behavior. Clear ownership boundaries allow isolated testing of core data operations independently from UI presentation logic.