Claude Skills by amosshadowy76

Extract, define, organize, and maintain reusable app product rules for software projects. Use when Codex should turn repeated UX or product decisions into durable rules, create or update files like APP_RULES.md, APP_RULES_TEMPLATE.md, PRODUCT_PRINCIPLES.md, or FEATURE_RULES.md, separate universal principles from project-specific behavior, review whether a feature violates existing rules, or help a team build a reusable product-method framework that can be reused across multiple apps.

Validate end-to-end product meaning across a user flow after UI or interaction changes. Use when Codex needs to verify that entry copy, user choices, runtime state, persistence, recovery, history, and return-entry surfaces still describe the same thing; when checking whether a fix only made screens look consistent or truly made behavior and product semantics line up; or when turning product review findings into a path-based acceptance pass. Often pair with product-ui-consistency-review-core o...

Review product screens for structural, semantic, interaction, and visual consistency in a project-agnostic way. Use when Codex needs to compare sibling pages, identify a shared page skeleton, detect whether a difference is intentional or drift, recommend the smallest coherent fix, review repeated blocks or flows across multiple screens, or perform reusable UI consistency reviews across different apps without relying on domain-specific labels or product-specific terminology.

Review product screens for structural, semantic, and interaction inconsistencies in domain-specific or already-familiar product families. Use when Codex is working in a product that already has repeated page skeletons, stable in-domain terminology, known recurring card roles, or specialized flow patterns, and the review should use those domain concepts instead of a fully generic consistency framework.