om-system-extension

Name: om-system-extension
Availability: InStock
Author: SHGrowth

Wire UMES extension mechanisms to coordinate UI and data via the Triad pattern.

6|2|Updated Mar 27, 2026

Search Tags:#extension #modular #ui-injection #event-subscribers #api-interceptors #umes #mutation-guards

Ready to run

npx skills add https://github.com/SHGrowth/om-superpowers --skill om-system-extension

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: om-system-extension
Source: https://github.com/SHGrowth/om-superpowers/tree/main/skills/om-system-extension
Command: npx skills add https://github.com/SHGrowth/om-superpowers --skill om-system-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Extend core modules without forking source code by using the Universal Module Extension System (UMES) to safely augment existing behavior, UI, and APIs.

Core Features & Use Cases

Extend forms, tables, and API responses without changing core code.
Coordinate UI and data via the Triad pattern (enricher + widget + injection) to graft new capabilities.
Support for enrichers, widget injections, API interceptors, mutation guards, component replacements, and event subscribers.

Quick Start

Use the UMES wizard to scaffold enrichers, widgets, interceptors, guards, and subscribers, then run yarn generate and yarn dev to verify the extension in the target UI.

Frequently Asked Questions about om-system-extension

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

FAQPage Schema

What is the Triad pattern for coordinating UI and data extensions?▼

The Triad pattern coordinates UI and data when extending core modules without forking. It combines an enricher, a widget, and an injection to graft new capabilities onto existing forms, tables, and API responses.

How do I scaffold a modular plugin extension using UMES?▼

Scaffold a modular plugin extension by using the UMES wizard to generate enrichers, widgets, interceptors, guards, and subscribers. After scaffolding the defined extension directory structure, run yarn generate to register changes and yarn dev to verify the extension in the target UI.

What directory structure is required for UMES extension mechanisms?▼

The required directory structure for UMES extension mechanisms includes data/enrichers.ts, widgets/injection/, api/interceptors.ts, data/guards.ts, and subscribers/. A YAML frontmatter is also required to define the extension configuration.

Can I intercept API responses and add mutation guards to existing forms?▼

Yes, you can intercept API responses and add mutation guards to existing forms using UMES extension mechanisms. The system supports API interceptors and mutation guards to safely augment existing behavior without changing core code.

Does UMES support event subscribers and component replacements for dashboards?▼

UMES supports event subscribers and component replacements for dashboards, forms, and APIs. These extension mechanisms allow developers to safely augment existing behavior and coordinate UI changes across different module surfaces.