the-vm-standard

Enforce View Model architectural covenants in TypeScript codebases.

68|13|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/kriegcloud/beep-effect --skill the-vm-standard-kriegcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-vm-standard
Source: https://github.com/kriegcloud/beep-effect/tree/main/.repos/beep-effect/.claude/skills/the-vm-standard
Command: npx skills add https://github.com/kriegcloud/beep-effect --skill the-vm-standard-kriegcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a strict set of rules and conventions for View Model architecture, ensuring consistency, maintainability, and a clear separation of concerns across the codebase.

Core Features & Use Cases

  • Standardized Structure: Enforces single-file definitions, unified type/tag naming, and namespace imports.
  • Clear Responsibilities: Mandates View Models act as thin bridges, delegating business logic to services and yielding dependencies from the Effect context.
  • Robustness: Requires specific atom conventions, confinement, and dual live/test variants for reliable development and testing.
  • Use Case: When developing a new UI component, ensure its associated View Model adheres to all defined architectural covenants before integration.

Quick Start

Ensure all new View Models strictly follow the covenants outlined in the VM Standard documentation.

Frequently Asked Questions about the-vm-standard

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

FAQPage Schema
How do I enforce View Model architecture standards in a TypeScript codebase?

To enforce View Model architecture standards in a TypeScript codebase, apply structural covenants that mandate single-file definitions, unified type naming, and namespace imports to ensure consistency and separation of concerns.

What is the correct way to structure TypeScript View Models for maintainability?

Maintainable TypeScript View Models require acting as thin bridges that delegate business logic to services and yield dependencies from the Effect context, ensuring a clear separation of concerns.

How do I set up live and test variants for TypeScript View Models?

Set up live and test variants for TypeScript View Models by defining dual structural configurations within the architecture covenants, requiring specific atom conventions and confinement for reliable development and testing.

Does this View Model standard require any specific dependencies or frameworks?

The View Model standard does not require external dependencies but mandates using the Effect context for yielding dependencies, ensuring the View Model acts as a thin bridge delegating business logic to services.

When should I use View Models instead of direct state management in TypeScript?

Use View Models instead of direct state management when you need to enforce strict separation of concerns, delegating complex business logic to services while maintaining standardized structural integrity and atom conventions across your codebase.