skills.rest
sandrasocial
sandrasocialCOMMUNITY
Explore all skills by this author →
GitHub

sselfie-maya-os

Align product behavior and telemetry across Maya-driven user journeys.

1|Updated Oct 27, 2025
Search Tags:#analytics#routing#qa#scaling#user-journey#maya#product-ops
One-click install
npx skills add https://github.com/sandrasocial/sselfie-9g --skill sselfie-maya-os
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sselfie-maya-os
Source: https://github.com/sandrasocial/sselfie-9g/tree/main/skills/sselfie-maya-os
Command: npx skills add https://github.com/sandrasocial/sselfie-9g --skill sselfie-maya-os

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about sselfie-maya-os

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

FAQPage Schema
How do I prevent analytics drift and divergent routes across product journeys?▼

Preventing analytics drift and divergent routes requires a canonical user-journey operating model that maps stages to exact routes, API contracts, and analytics events. This alignment across product, engineering, and QA ensures teams ship predictable funnel behavior.

What is a canonical screen map and when do I need it for product operations?▼

A canonical screen map is a single-source-of-truth mapping linking user-journey stages to specific routes, owners, and key behaviors. You need it when scaling checkout flows or onboarding to prevent alias route growth and inconsistent UX decisions.

How do I audit a checkout regression using user-journey definitions?▼

To audit a checkout regression, map the affected stage to the canonical route, validate telemetry contracts against the analytics allowlist, run the QA checklist, and propose the smallest safe change with an assessed merge risk.

What QA release gates should I enforce for analytics event allowlists?▼

Enforce QA release gates requiring build, type-check, targeted regression tests, and manual smoke checks. Additionally, verify the analytics event allowlist to block unsafe merges that could break funnel telemetry integrity.

Can I scale in-app UI behavior without increasing user complexity?▼

Yes, you can scale in-app UI behavior without increasing user complexity by prioritizing a tool dispatcher, inline renderer, cross-session memory, and funnel telemetry integrity. This scaling playbook maintains API consistency across expanding surfaces.

Why do agents need to name exact routes and migration shims for product changes?▼

Agents must name exact routes, API/event contracts, current vs target behavior, migration shims, and merge risk to satisfy output contracts. This explicit documentation ensures safe changes and prevents unsafe merges across Maya-driven journeys.

Related Skills

Explore More Product & Management Skills→
hongmaple0820hongmaple0820
9

ux-researcher-designer

Structure user research data into personas, journey maps, and usability frameworks.

Community
Advanced
ThalesGroupThalesGroup
19

agilab-testing

Execute targeted AGILAB tests across unit, smoke, and regression suites.

Official
Advanced
dljsjrdljsjr

tui

Guide developers in building TUI components for Sandpiper extensions.

Community
Intermediate
cloudofgeorgecloudofgeorge

plan-design-review

Assess and critique design plans across UX, feasibility, performance, accessibility, and risk.

Community
Advanced