vice-sources

Build reactive Android screen state models with ViceSource.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/eygraber/jellyfin-kmp --skill vice-sources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vice-sources
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/vice-sources
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill vice-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create ViceSource models for screen business logic and reactive state management.

Core Features & Use Cases

  • Reactive screen modeling: Build and expose UI state from repositories.
  • Composable integration: Wire models into compositors to drive UI.
  • Testing patterns: Validate state with moleculeFlow and Turbine.

Quick Start

Define a ViceSource UserModel and wire it into a UserCompositor to drive reactive UI from repository data.

Frequently Asked Questions about vice-sources

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

FAQPage Schema
How do I build reactive screen state models for Android UI?

Wire repository data into a UserCompositor to drive reactive Android UI. This approach uses ViceSource to build screen models that expose UI state and handle asynchronous operations.

How do I test reactive UI state streams in Android?

Validate reactive UI state streams using moleculeFlow combined with Turbine. This pattern tests real-time state updates and asynchronous operations emitted by ViceSource screen models.

Can I use ViceSource with Jetpack Compose for state management?

Yes, ViceSource supports Compose integration by wiring models into compositors. This drives reactive UI updates directly from repository data transformations within your Android screen architecture.

What is the best way to expose UI state from repositories in Android?

Create a ViceSource UserModel to transform repository data and feed it into a UserCompositor. This handles asynchronous operations and manages real-time UI state updates efficiently.

Do I need a specific architecture pattern to handle asynchronous operations in reactive UI?

Use a screen-based UI architecture relying on repository data transformation. ViceSource builds reactive screen state models that support real-time updates and asynchronous operations within this pattern.