← all publishers

Tranz007

@tranz007 source repo

Report this profile Claim this profile

• 15 skills
• 0 followers
• 1 day ago last updated

1. ▌
   Pr · tranz007 bundle

   Create a high-quality pull request description for UX-related implementation that explains why the change exists, what behavior changed, design-system usage, states, accessibility, testing, risks, and what reviewers should inspect. Use when design or design-engineering work is ready to become a PR.
   0
   installs
2. ▌
   Clear · tranz007

   Rewrite UX, product, research, handoff, ticket, or engineering-facing content so it reads like a capable human practitioner wrote it. Use when generated or existing content is bloated, robotic, unclear, over-structured, audience-blind, or sounds like AI while preserving meaning, evidence strength, and uncertainty.
   0
   installs
3. ▌
   Frame · tranz007

   Turn a feature request, stakeholder request, idea, complaint, or vague design assignment into a clear UX problem frame with user outcome, evidence, constraints, assumptions, unknowns, and success signals. Use before solutioning when the real problem or reason for the work is unclear.
   0
   installs
4. ▌
   Ripple · tranz007

   Trace what else a UX, flow, component, content, or design-system change could affect. Use when a designer asks "if we change this, what else moves?", "what else could this affect?", or wants to understand downstream UX impact before committing to a change.
   0
   installs
5. ▌
   Content · tranz007

   Review and improve product UX content including labels, instructions, errors, empty states, confirmations, terminology, and content timing. Use when a designer asks whether UI copy is clear, consistent, accessible, actionable, appropriately human, or aligned with the product's established language.
   0
   installs
6. ▌
   Handoff · tranz007

   Prepare UX work for engineering by preserving user intent, behavior, states, design-system usage, accessibility requirements, dependencies, acceptance behavior, and unresolved questions. Use when a designer says "get this ready for engineering", needs a handoff, behavioral contract, implementation-ready ticket content, or wants to stop engineering from guessing.
   0
   installs
7. ▌
   Critique · tranz007

   Review and compare UX designs, flows, prototypes, specifications, or implementations against user goals, evidence, interaction behavior, accessibility, design-system fit, content, and engineering intent. Use when a designer asks for critique, comparison, tough feedback, review before approval, or wants to check whether implementation preserved the intended experience.
   0
   installs
8. ▌
   Decision · tranz007 bundle

   Recover or preserve consequential UX and architecture rationale. Use when a designer asks why something was designed a certain way, whether a choice deserves an ADR/design decision record, or wants to capture context, evidence, alternatives, rationale, consequences, and status without documenting trivial changes.
   0
   installs
9. ▌
   Setup UX · tranz007 bundle

   Set up or refresh UX Skills for a new or existing project by capturing product intent, learning users and evidence, the design system, engineering environment, accessibility expectations, terminology, and consequential decisions. Use only when the user explicitly asks to set up, initialize, connect, learn, or refresh UX Skills/project context; do not activate during ordinary UX work.
   0
   installs
10. ▌
    Challenge · tranz007

    Interrogate a UX idea, requirement, flow, feature, or design direction before execution. Use when a designer asks to be challenged, wants assumptions exposed, wants a red-team review of the premise, or needs hard questions that test whether the proposed work should exist at all.
    0
    installs
11. ▌
    Blindspots · tranz007

    Find important users, contexts, constraints, dependencies, consequences, and conditions that a design discussion has not considered at all. Use when a designer asks "what am I missing?", wants edge perspectives beyond UI states, or needs a pre-review scan for overlooked experience risks.
    0
    installs
12. ▌
    System Fit · tranz007

    Decide whether a UX need should reuse, compose, extend, or create a design-system component or pattern. Use when a designer asks whether something needs a new component, how a design fits the current system, or what design-system contribution a feature should make.
    0
    installs
13. ▌
    State Sweep · tranz007

    Find missing interface and service states such as loading, empty, partial, permission, timeout, stale data, validation, failure, interruption, and recovery. Use when a designer asks what states or edge cases are missing from a screen, component, journey, or feature.
    0
    installs
14. ▌
    Accessibility · tranz007

    Review UX design intent and available implementation evidence for accessibility barriers, inclusive interaction, WCAG or Section 508 requirements, keyboard and focus behavior, semantics, dynamic announcements, content, motion, zoom/reflow, and recovery. Use when a designer asks for an accessibility review or needs accessibility behavior defined before engineering handoff.
    0
    installs
15. ▌
    User Grounding · tranz007

    Ground UX work in actual users and evidence when who the design is for, their goals or context, or the strength of user knowledge is materially uncertain. Use when a designer asks who this is for, whether personas are useful, what research is needed, what existing research says, or when a decision depends on unsupported assumptions about users. Do not activate merely because a UX task involves users when the audience and need are already clear.
    0
    installs