sselfie-maya-os

What problem does it solve?

This Skill enforces a canonical, Maya-first operating model to prevent divergent routes, analytics drift, and inconsistent UX decisions across product, engineering, and QA so teams ship predictable, low-risk funnel behavior.

Core Features & Use Cases

• Canonical Journey & Screen Map: Single-source-of-truth mappings from user-journey stages to routes, owners, and key behaviors to avoid alias route growth.
• Scaling Playbook: Prioritizes tool dispatcher, inline renderer, cross-session memory, funnel telemetry integrity, and API consistency to scale without increasing user complexity.
• QA & Release Gates: Prescribes build, type-check, targeted regression tests, and manual smoke checks plus analytics allowlist verification to block unsafe merges.
• Output Contract & Escalation Rules: Requires agents to name exact routes, API/event contracts, current vs target behavior, migration shims, and explicit merge risk for any change.
• Use case: Auditing a checkout regression by mapping the affected stage to the canonical route, validating telemetry contracts, running the QA checklist, and proposing the smallest safe change with an assessed merge risk.

Quick Start

Read the referenced files and produce an output that lists the affected stage, user intent, surface/tool, data reads and writes, analytics events, and a success metric.