design-conversational-interfaces

Designs chatbot and voice-assistant dialogue behavior including intent catalogs, turn flows, repair, and refusals.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-conversational-interfaces-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-conversational-interfaces
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/design-conversational-interfaces
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-conversational-interfaces-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI chatbots and assistants often ship with vague openers, dead-end errors, improvised refusals, and recommendations that erode trust. This Skill turns "add a chatbot" into a specified, honest, testable conversation design grounded in NN/g research and shipped conversational products. ## Core Features & Use Cases - Closed intent catalog and repair tree: Define the finite set of things the bot can do, split guide (willing-but-lost) from fallback (off-limits) misses, and route every utterance through a safety-first decision tree. - Turn spine and recommendation patterns: Design the open-converge-deliver-critique-close flow with one question per turn, gated follow-ups, one confident pick plus a named runner-up, and re-ranking instead of restarts. - Trust, safety, and memory dosing: Pre-author verbatim refusal and safety deferral lines, set the five NN/g chatbot dimensions deliberately, and cap memory-initiated proactivity for persistent companion bots. - Use Case: Designing a guided-selling assistant for a retail site — produce a Conversation Spec with the intent catalog, verbatim opening line, critique vocabulary, chip set, and a golden utterance set handed to AI evals. ## Quick Start Use the design-conversational-interfaces skill to design the conversation flow for a customer support chatbot, including its intent catalog, fallback handling, and refusal scripts.

Frequently Asked Questions about design-conversational-interfaces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a chatbot conversation flow?

Start by scoping a closed world: the bot's one-sentence job, its finite capability list, and its off-limits list. Then design a five-phase turn spine — open, converge, deliver, critique loop, close — with one question per turn and every turn ending in next-step doors.

How should a chatbot handle questions it cannot answer?

Split misses into two intents: guide for willing-but-lost users, answered with warm re-orientation and real capability doors, and fallback for off-catalog or off-limits asks, answered with an honest decline plus the closest real doors. Never use a generic "I didn't understand that."

What is the difference between guide and fallback intents in chatbots?

Guide handles confused users who want to engage, with warm re-orientation and 3-4 capability doors. Fallback handles off-catalog, off-limits, or gibberish input with an honest decline. Collapsing them makes confused users feel rejected or strings along off-limits askers.

When should I not use conversational interface design?

Do not use it to decide whether chat is the right interface at all — that decision belongs to stage-interface design. It also excludes voice mechanics like barge-in and turn-taking, output enforcement machinery, and trust UI such as provenance display, which are separate concerns.

How much memory should a persistent AI companion bot use?

Limit memory-initiated follow-ups to one per session, phrased as a question rather than an assertion, and never enumerate what the bot remembers. Proactive turns must be brief, warm, and declinable, and a declined prompt is not repeated the same day.