What problem does it solve? Teams building CRM or marketplace cabinets often split one person into duplicate accounts per role, leak internal operator data to members, or hide critical status blockers. This Skill provides a structured workflow to design cabinet UX where one canonical identity holds multiple roles with safe visibility boundaries. ## Core Features & Use Cases - Role Capability Matrix: Map capabilities and visibility boundaries for investor, seller, operator, moderator, and admin roles using a canonical single-identity model. - Role Journeys & Status Design: Build step-by-step journeys per role and merge them into one cabinet surface with explicit status, safe explanation, next action, and last-updated blocks. - Anti-Pattern Validation: Check designs against common failures such as duplicate accounts per role, raw payload exposure on member endpoints, and unexplained disabled states. - Use Case: When designing a marketplace where a user can be both investor and seller, use this Skill to define one account with role-aware modules, safe access-request statuses, and role-by-role QA evidence. ## Quick Start Ask the AI to design the cabinet UX for a marketplace where one user can be both investor and seller, using the role matrix, journeys, and anti-pattern references.
