eventmodeling-storyboarding-events
Storyboarding Events
Interview Phase (Optional)
When to Interview: Skip if the user has already specified: existing UI patterns or mockups to reference, critical data fields, and UI/UX preferences. Interview when these details haven't been discussed or when the user wants guidance on storyboarding depth.
Interview Strategy: Clarify UI needs, data priorities, and existing patterns to guide storyboard design. This ensures mockups capture all necessary fields without over-designing.
Critical Questions
When UI design guidance is needed:
-
Current UI State (Impact: Determines if you're designing from scratch or enhancing existing)
- Question: "Do you have: (A) Existing UI/wireframes to reference, (B) Rough sketches, (C) Starting from scratch?"
- Why it matters: Existing UI provides constraints and patterns; starting fresh allows more design freedom
- Follow-up triggers: If (A) → ask to share; if (C) → ask about platform/technology
-
Most Critical Data Fields (Impact: Determines storyboard focus and detail level)
- Question: "Which data fields are most important for users to see? (e.g., order status, payment confirmation, tracking info)"
More from trogonstack/agentskills
diataxis-organize-docs
Reorganize documentation into the Diataxis framework structure. Splits existing docs into tutorials, how-to guides, reference, and explanation sections.
45datadog-design-dashboard
>-
36diataxis-gen-readme
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
31nats-design-subject
>-
30gh-enrich-pr-description
Enrich GitHub PR descriptions with root-cause context, related issues/PRs, and CC mentions. Use when creating or editing a PR, when a PR has an empty or sparse description, or when the user asks to improve a PR description.
26ask-question
>-
23