all publishers

heyviet

@heyviet source repo

8 published skills

  1. ▌
    Wireframe · heyviet bundle
    Use when the user invokes /wireframe, asks to wireframe, sketch, or block out a screen, flow, or app before high-fidelity design or code — or when a build is jumping straight to polished UI without structural exploration, stakeholders demand pixel-perfect too early, or an existing wireframe needs review, critique, or handoff. Dispatcher that runs the full wireframe-* family and co-fires the matching design skills.
    0 installs
  2. ▌
    Wireframe Handoff · heyviet
    Use when presenting wireframes to stakeholders, clients, or executives; when wireframes are ready for build and developers need a handoff; when a developer asks "what happens when..."; when annotating behavior, states, data sources, validation, or edge cases; when built screens drift from the wireframes during development; or when deciding what to spec in the wireframe versus leave to the build team. Also fires when preparing design alternatives for a sign-off meeting.
    0 installs
  3. ▌
    Wireframe Elements · heyviet
    Use when choosing which UI component represents a need in a wireframe, tempted to invent a custom control where a standard one exists, unsure what belongs on a screen type (dashboard, list, detail, form, settings), deciding between list, table, tiles, or cards, picking horizontal vs vertical navigation, representing components at low fidelity, or consolidating repeated screens into page templates.
    0 installs
  4. ▌
    Wireframe Feedback · heyviet
    Use when requesting or giving feedback on wireframes, running or facilitating a design critique, or preparing wireframes for stakeholder review. Also fires when feedback arrives vague ('make it pop', 'I don't like it'), as solutions instead of problems ('just move it to settings'), when deciding which feedback to act on after a review, or when a review session went sideways — loud voices dominating, defensiveness, or the same debates repeating without decisions.
    0 installs
  5. ▌
    Wireframe Ideation · heyviet
    Use when starting a screen design from a blank canvas, jumping straight into one layout, or treating the first idea as the final idea — or when structure is missing before screens (no user flow, sitemap, or content inventory yet). Also fires when layout alternatives are needed, when divergent exploration should precede committing to a direction, when ideation stalls after one or two sketches, or when stakeholders debate what belongs on a page before anything is drawn.
    0 installs
  6. ▌
    Wireframe Principles · heyviet
    Use when a wireframe reads flat and everything looks equally important, when boxes or text edges are misaligned and the layout feels thrown together, when reviewers can't tell what's clickable or where to look first, when greeked/lorem text is hiding real content decisions, when color or typography starts sneaking into a wireframe, or when reviewing any wireframe's visual logic — hierarchy, alignment, clarity — before sharing it.
    0 installs
  7. ▌
    Wireframe Fundamentals · heyviet
    Use when deciding whether to wireframe or jump straight to high-fidelity design or code, choosing the right fidelity for a design artifact, or picking a wireframing tool or method. Also fires when stakeholders skip ideation and commit to the first concept, demand 'just make it look real,' polish visuals during early exploration, sign off on branding instead of structure, or when a project derails after coding starts because flaws weren't caught on paper.
    0 installs
  8. ▌
    Wireframe Collaboration · heyviet
    Use when running a team wireframing session or design-studio workshop, breaking design-by-committee gridlock, involving engineers and PMs in design (or reining in a hijack), unblocking a solo-designer bottleneck, deciding who owns which wireframing decision, structuring PM→designer→engineer handoffs, resolving cross-role design disagreements, or adapting collaborative wireframing for remote and async teams.
    0 installs