skills.rest
Zelenov
ZelenovCOMMUNITY
Explore all skills by this author →
Website𝕏@zelenovGitHub

iced-elm-architecture

Organize iced Rust UI projects with Elm-style architecture patterns.

1|Updated Jan 23, 2026
Search Tags:#architecture#front-end#rust#state-management#modular#ui-patterns#iced
One-click install
npx skills add https://github.com/Zelenov/frename --skill iced-elm-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iced-elm-architecture
Source: https://github.com/Zelenov/frename/tree/main/.cursor/skills/iced-elm-architecture
Command: npx skills add https://github.com/Zelenov/frename --skill iced-elm-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies an Elm-style architecture for iced-based Rust UI development, providing a clear pattern for organizing features, messages, and state to reduce coupling and improve maintainability.

Core Features & Use Cases

  • Feature-based structure: each UI feature lives in its own folder with mod.rs, messages.rs, state.rs, and view.rs, enabling isolated development and easier testing.
  • Message-driven updates: updates flow through a consistent path using Task::done and subscriptions to drive reactive UI.
  • UI/core separation: keeps domain logic in core and UI orchestration in the app layer, with a store-based approach to persistence and a generic Directory-like abstraction for state.

Quick Start

Create a new iced-based Rust project and begin wiring features as described to implement Elm-style architecture.

Frequently Asked Questions about iced-elm-architecture

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

FAQPage Schema
How do I structure a Rust desktop UI project using Elm architecture with iced?▼

To structure a Rust desktop UI project with Elm architecture in iced, you organize features into isolated folders containing mod, messages, state, and view files to reduce coupling and improve maintainability.

What is the best way to manage state in iced Rust applications?▼

The best way to manage state in iced Rust applications is using Elm-style message-driven updates that flow through a consistent path with Task::done and subscriptions to drive reactive UI and deterministic state.

Can I separate domain logic from UI orchestration when building iced Rust apps?▼

Yes, you can separate domain logic from UI orchestration in iced Rust apps by keeping domain rules in a core layer and UI orchestration in the app layer, utilizing a store-based approach for persistence.

Does Elm-inspired architecture work for modular interactive desktop UIs in Rust?▼

Elm-inspired architecture works for modular interactive desktop UIs in Rust by enabling isolated feature development, easier testing, and deterministic state management across components through message passing.

Why does my iced Rust UI feature have high coupling and poor maintainability?▼

Your iced Rust UI feature has high coupling because it lacks an Elm-style structure that isolates features into dedicated folders for messages, state, and views to enforce modular boundaries.

Related Skills

Explore More Software Engineering Skills→
ewe-studiosewe-studios
1

Rust Directory and Configuration

Set up Rust toolchains, Cargo configurations, and project directory structures.

Official
Advanced
danielsogldanielsogl
39

angular-signals

Migrate Angular component state from BehaviorSubject to signals.

Community
Advanced
EojEdredEojEdred

bridge-dev

Scaffold a Rust pallet-bridge for cross-chain transfers between Flare and Partition chains.

Community
Intermediate
manutejmanutej

elm-development

Enforces TEA architecture and strong typing for Elm front-ends with JavaScript interop support.

Community
Intermediate