tumai-platform-changes

Enforce architecture rules for Tumai platform changes with UI-first workflows.

Updated Aug 27, 2026

Search Tags:#workflow #architecture #platform #catalog #governance #risk-management #ui-first

Ready to run

npx skills add https://github.com/mariasebarespersona/Tum-AI --skill tumai-platform-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tumai-platform-changes
Source: https://github.com/mariasebarespersona/Tum-AI/tree/main/.claude/skills/tumai-platform-changes
Command: npx skills add https://github.com/mariasebarespersona/Tum-AI --skill tumai-platform-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill enforces architectural governance for Tumai platform changes, ensuring reuse, UI-first flow creation, and a single source of truth before modifying catalog entries, executors, or Supabase configs.

Core Features & Use Cases

Enforces Rule 1: Marketplace-first reuse by auditing existing catalog entries before creating new nodes.
Enforces Rule 2: UI-first workflow changes, ensuring flows appear in editor canvases before backend steps.
Ensures Rule 3: Every new catalog item includes catalog entry, executor, and skill doc; validates alignment.
Provides process guidance for documenting changes in docs/context.md and following the plan.

Quick Start

Follow the rules in this skill to audit, plan, implement, and verify platform changes in the editor UI before touching backend code.

Frequently Asked Questions about tumai-platform-changes

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

FAQPage Schema

How do I enforce architecture rules for platform changes before modifying a catalog?▼

Apply governance rules to platform changes by auditing existing catalog entries first, enforcing UI-first flow creation, and validating executor alignment before modifying backend code.

How do I create a UI-first workflow in a platform editor before writing backend code?▼

Ensure UI-first workflow changes by making new flows and nodes appear on the editor canvas first, then proceeding to backend implementation and Supabase configurations.

What is the process for adding a new catalog item with an executor and skill documentation?▼

Adding a new catalog item requires creating a catalog entry, an executor, and skill documentation, then validating alignment to maintain a single source of truth.

Do I need to audit the marketplace catalog before creating new workflow nodes?▼

Yes, you must audit existing marketplace catalog entries before creating new nodes to ensure maximum reuse and prevent duplicate architecture within the platform.

Why does my platform workflow change require validation against a single source of truth?▼

Validation against the catalog as a single source of truth prevents architecture drift, ensuring centralized defaults, documented changes, and proper risk management for executor modifications.

What is the best way to document platform architecture changes for governance and risk management?▼

Document platform architecture changes by recording them in docs/context.md, following the implementation plan, and validating catalog alignment to satisfy governance requirements.