How do I install the Write Viewmodel skill?

Run npx skillmds@latest add igorescodro/write-viewmodel in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Write Viewmodel safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write Viewmodel?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Write Viewmodel free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Write Viewmodel?

igorescodro (@igorescodro) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Write Viewmodel by igorescodro — Agent Skill

Name: Write Viewmodel
Author: igorescodro

Write Viewmodel

Use when writing a new ViewModel or modifying an existing one in the Alkaa project. Triggers on tasks like "add a ViewModel", "create VM for X screen", "implement state handling", or "connect use case to UI".

igorescodro feb833b 2 files · 6.4 KB Updated Sep 17, 2026

File contents

Write ViewModel

Overview

ViewModels in Alkaa bridge domain use cases and Compose UI via cold flows and sealed state classes. They contain no business logic — only orchestration, mapping, and scope management.

Structure

Sealed State Class — data object for stateless states, data class for states with data, ImmutableList for list payloads → see references/CODE_PATTERNS.md
Flow Exposure — Cold Flow<ViewState> by default; hot StateFlow only when multiple collectors share the same stream → see references/CODE_PATTERNS.md
Use Case Injection — Inject use cases as constructor parameters; never repositories or other ViewModels → see references/CODE_PATTERNS.md
Coroutine Scope — applicationScope for DB mutations that survive ViewModel destruction; viewModelScope for UI-bound work → see references/CODE_PATTERNS.md
Mappers — Dedicated mapper class injected as constructor param; never map inline → see references/CODE_PATTERNS.md

For unit test setup and fake patterns → see references/CODE_PATTERNS.md and the write-unit-tests skill.

Scope Rules

Situation	Scope
DB insert / update / delete	`applicationScope.launch { }`
Network call that should persist	`applicationScope.launch { }`
Debounced UI updates	`viewModelScope`
Short-lived UI-bound work	`viewModelScope`

Common Mistakes

Mistake	Fix
Calling repository directly	Wrap in a use case first
Exposing `StateFlow` for a screen-scoped stream	Return cold `Flow<ViewState>`
Mapping models inline in ViewModel	Create a `XxxMapper` class
Using `viewModelScope` for DB writes	Use `applicationScope.launch { }`
Depending on another ViewModel	Extract shared logic into a use case
Testing with mocks	Write a `XxxFake` that implements the use case interface

Related Skills

Fake patterns and test structure → use write-unit-tests skill
Composable and screen wiring → use write-composable skill

---name: write-viewmodeldescription: Use when writing a new ViewModel or modifying an existing one in the Alkaa project. Triggers on tasks like "add a ViewModel", "create VM for X screen", "implement state handling", or "connect use case to UI".---# Write ViewModel## OverviewViewModels in Alkaa bridge domain use cases and Compose UI via cold flows and sealed state classes. They contain no business logic — only orchestration, mapping, and scope management.## Structure1. **Sealed State Class** — `data object` for stateless states, `data class` for states with data, `ImmutableList` for list payloads → see `references/CODE_PATTERNS.md`2. **Flow Exposure** — Cold `Flow<ViewState>` by default; hot `StateFlow` only when multiple collectors share the same stream → see `references/CODE_PATTERNS.md`3. **Use Case Injection** — Inject use cases as constructor parameters; never repositories or other ViewModels → see `references/CODE_PATTERNS.md`4. **Coroutine Scope** — `applicationScope` for DB mutations that survive ViewModel destruction; `viewModelScope` for UI-bound work → see `references/CODE_PATTERNS.md`5. **Mappers** — Dedicated mapper class injected as constructor param; never map inline → see `references/CODE_PATTERNS.md`For unit test setup and fake patterns → see `references/CODE_PATTERNS.md` and the `write-unit-tests` skill.## Scope Rules| Situation | Scope ||-----------|-------|| DB insert / update / delete | `applicationScope.launch { }` || Network call that should persist | `applicationScope.launch { }` || Debounced UI updates | `viewModelScope` || Short-lived UI-bound work | `viewModelScope` |## Common Mistakes| Mistake | Fix ||---------|-----|| Calling repository directly | Wrap in a use case first || Exposing `StateFlow` for a screen-scoped stream | Return cold `Flow<ViewState>` || Mapping models inline in ViewModel | Create a `XxxMapper` class || Using `viewModelScope` for DB writes | Use `applicationScope.launch { }` || Depending on another ViewModel | Extract shared logic into a use case || Testing with mocks | Write a `XxxFake` that implements the use case interface |## Related Skills- **Fake patterns and test structure** → use `write-unit-tests` skill- **Composable and screen wiring** → use `write-composable` skill

Frequently asked questions