dashboard-chat-best-practices
FeaturedApply dashboard-grade chat UX patterns in the Eve chat template. Use when changing Next.js Cache Components/PPR behavior, static shell layout, Suspense bootstrap boundaries, theme hydration, auth display hydration, signed-in/signed-out static shell behavior, optimistic messages, streaming row identity, composer/sidebar interactions, thinking/tool rendering, responsive styling, visual polish, or Vercel dashboard chat comparisons.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- thedotmack
- Repository
- thedotmack/claude-mem
- Created
- 1 years ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
eve-chat-template-eve
Work safely on Eve-specific internals in the Eve chat template. Use when changing the Eve agent, withEve routes, eveChannel auth, useEveAgent, ClientSession/SessionState, persisted event logs, stream/resume behavior, connection authorization, Vercel Connect MCP connections, local Eve tools, or upstream Eve API assumptions.
conversational-ui-restraint
Build or review a chat/copilot/assistant interface — message list, composer, streaming responses, conversation sidebar, canvas/side-panel for structured output. Trigger for "make this chat UI look like ChatGPT/Claude", "为什么我的 对话界面看起来很乱", "streaming response feels janky", "conversation sidebar needs work", "this looks AI-generated", or when reviewing a chat/assistant screen before shipping it. This is a DIFFERENT problem than dense dashboards — a chat UI's job is to get out of the way of the content, not to show more data per screen (use `terminal-software-design` for tables/dashboards/data grids, not this). Do NOT trigger to invent a generic app aesthetic from a blank slate (use `ui-ux-pro-max`) or for landing pages. Portable: self-contained prose, no script dependency — works pasted into any assistant.
dashboard-design
Anti-slop dashboard skill for SaaS app UI. Admin panels, analytics, CRM, data tables, app shells that read as real daily-use software. Project-first component retrieval, strict visual QA, zero placeholder data.