Real Questions
Examples from real development sessions: choices, blockers, and checkpoint decisions.
Which dialog types should we test next?
Confirmation
Multiple choice
Questions
Text input
⏎ confirm Esc cancel S snooze
Testing the newly built history feature
?
Confirmation
This is a test confirmation dialog. Does the history feature work correctly?
⏎ confirm Esc cancel S snooze
Validating new functionality
✎
Input
What improvements would you like to see in the history detail view?
i dont see new history showing up
⏎ confirm Esc cancel S snooze
Bug report via free-form text
Which reflection approach would you prefer?
CSS gradient (simple fade)
DOM duplicate with perspective
No reflection (cleaner look)
⏎ confirm Esc cancel S snooze
Designing the homepage dialog gallery
For the text info below covers - should it also be reflected?
Cover only (simpler)
Cover + text (full reflection)
No reflection at all
⏎ confirm Esc cancel S snooze
Refining the visual design
What version for this release?
1.3.3 (patch - bug fix)
1.4.0 (minor - new feature)
2.0.0 (major - breaking change)
⏎ confirm Esc cancel S snooze
Semantic versioning decision
What should replace the emoji icons?
SVG icons from icon library
Custom designed icons
Remove icons entirely
⏎ confirm Esc cancel S snooze
UI simplification choice
How should we structure the single source of truth for releases?
releases.json feeds everything
Separate files synced manually
Git tags as source
⏎ confirm Esc cancel S snooze
Documentation architecture decision
How should we handle the CHANGELOG.md vs releases.json redundancy?
Auto-generate CHANGELOG.md from releases.json
Keep both, manual sync
Remove CHANGELOG.md entirely
⏎ confirm Esc cancel S snooze
Eliminating manual synchronization
Choose your Slack authentication method
xoxc/xoxd - Extract tokens from browser
xoxp - Create Slack app with User OAuth
xoxb - Bot token (limited to invited channels)
⏎ confirm Esc cancel S snooze
Configuring Slack MCP integration
The changes add "feedback with partial answers". Should we add test cases for this?
Yes, comprehensive tests
Yes, basic smoke tests
No, skip for now
⏎ confirm Esc cancel S snooze
Test coverage prioritization
Where should the invite link be displayed?
Below room code (always visible)
In a collapsible panel
Both places
⏎ confirm Esc cancel S snooze
UI placement for multiplayer game
What should the playlist manager do?
Admin UI to create/edit playlists
Import from Spotify API
Auto-generate from music library
⏎ confirm Esc cancel S snooze
Planning new feature scope
2 of 3
Which linting/formatting tool?
1 Run verification before commit?
2 Tool: ESLint+Prettier / Biome / None
3 Pre-commit hooks: lefthook / husky / none
⏎ confirm Esc cancel S snooze
Project setup configuration wizard
?
Confirmation
Biome crashes on some Svelte files (known bug). Should I exclude .svelte files and use svelte-check instead?
⏎ confirm Esc cancel S snooze
Workaround for tooling limitation
How should agents communicate their project context to the app?
New MCP tool parameter on all calls
Environment variable at startup
Use process.cwd() automatically
⏎ confirm Esc cancel S snooze
Simplifying the integration
Which feedback service should I set up?
GitHub Issues link (simplest)
Formspree (email notifications)
Custom backend with database
⏎ confirm Esc cancel S snooze
User feedback infrastructure
How should the feedback form appear?
Floating button + modal
Link in footer/menu
Dedicated page/route
⏎ confirm Esc cancel S snooze
User feedback mechanism design
When clients don't pass project_path, what should happen?
Show badge with "Unknown Project"
No badge (opt-in only)
Use current directory as fallback
⏎ confirm Esc cancel S snooze
Default behavior for optional parameter
914 files changed - mostly artist images + playlists. How to proceed?
One big commit (faster)
Smart-commit: separate by type
Manual review: commit selectively
⏎ confirm Esc cancel S snooze
Large changeset organization
What's your primary goal for the redesign?
Polished product (Linear, Notion, Raycast)
Keep terminal aesthetic but modernize
Minimal/brutalist design
⏎ confirm Esc cancel S snooze
Design direction for app refresh
Color scheme direction?
Light by default with dark mode support
Dark by default with light mode
Only dark mode (no light mode)
⏎ confirm Esc cancel S snooze
Accessibility and user preference
The current app has terminal gimmicks: boot sequence, scanlines, ASCII art. Which to keep?
Keep ALL — it's the brand
Keep SOME — tasteful nods
Remove ALL — clean slate
⏎ confirm Esc cancel S snooze
Stripping away skeuomorphism
For Svelte 5 component libraries, which direction?
shadcn-svelte — best polished look
Skeleton v3 — full design system
Bits UI — headless primitives only
⏎ confirm Esc cancel S snooze
Component library selection
?
Confirmation
For the conversation viewer you want: compact density, collapsible tool calls, card-based messages. Is that right?
⏎ confirm Esc cancel S snooze
Confirming UX requirements
You have 5 drafts, but 3 are "Untitled". Which should I create short.io links for?
Only the 2 titled drafts
All 5 drafts (I'll rename later)
None (I'll do it manually)
⏎ confirm Esc cancel S snooze
Batch operation scoping
Typography direction?
Sans-serif (Inter, SF Pro)
Keep monospace but refined
Mix: sans for UI, mono for code
⏎ confirm Esc cancel S snooze
Balancing personality with polish
2 of 3
How do you like the new history detail view?
1 Feature quality
2 Navigation ease
3 Overall satisfaction
⏎ confirm Esc cancel S snooze
Multi-question feedback collection
← Scroll to see more real questions →