valley-mas-product-guard

Validate Valley MAS product behavior across creator spaces, blogs, resources, and navigation.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/muddyrain/valley-mas --skill valley-mas-product-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: valley-mas-product-guard
Source: https://github.com/muddyrain/valley-mas/tree/main/.codex/skills/valley-mas-product-guard
Command: npx skills add https://github.com/muddyrain/valley-mas --skill valley-mas-product-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protect product behavior consistency in Valley MAS when changes affect creator spaces, blogs, resources, media posts, navigation, visibility scopes, or other user-experience touchpoints.

Core Features & Use Cases

  • Guard creator spaces, blogs, resources, and media content from UX regressions when a feature update is introduced.
  • Validate visibility behavior (private/shared/public) and navigation flows (list to detail to context return) to ensure consistency.
  • Ensure previews, content cards, and detail pages match and that empty/loading/404/fallback states are reasonable.

Quick Start

Assess a proposed change for its impact on creator spaces, blogs, resources, navigation, and visibility scopes, and verify cross-view consistency.

Frequently Asked Questions about valley-mas-product-guard

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

FAQPage Schema
How do I prevent UX consistency regressions when updating product behavior?

Product behavior guardrails validate transitions from list to detail, content-card accuracy, and empty/loading/404/fallback states. They enforce checks for cross-view access, author permissions, non-misleading previews, and proper context-aware return paths to protect user experience consistency.

How do I validate visibility scopes and navigation flows for creator spaces?

Validate visibility scopes by checking private, shared, and public access behaviors across creator spaces. Verify navigation flows from list to detail pages, ensure context-aware return paths work correctly, and confirm cross-view access permissions prevent unauthorized entry.

Does this product behavior guard work for blogs, resources, and media posts?

Yes, the product behavior guard works for blogs, resources, media posts, and creator spaces. It validates content-card accuracy, ensures previews match detail pages, and checks that empty, loading, 404, and fallback states display consistently across all these content types.

What's the best way to check empty, loading, and 404 fallback states during changes?

The best way to check fallback states is to assess each proposed change against expected empty, loading, 404, and fallback behaviors. Verify that content cards and detail pages display reasonable fallback content and that previews do not mislead users when data is unavailable.

Why do I need to verify cross-view access and non-misleading previews?

You need to verify cross-view access and non-misleading previews to maintain user experience consistency. Without these checks, users may encounter broken navigation flows, unauthorized content access, or mismatched previews that do not accurately represent the actual detail page content.