support

SylphxAI's avatarfrom SylphxAI

Support - help center, tickets, docs. Use when building support.

4stars🔀3forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for building modern customer support infrastructure, including help centers, ticketing systems, and documentation. Built on Next.js and Resend, it emphasizes a 'self-service first' philosophy, ensuring users find answers quickly while providing support agents with deep user context (plan, usage, and actions) to resolve complex issues efficiently and build long-term trust.

Use Cases

  • Developing a self-service help center to reduce support volume by allowing users to find answers independently.
  • Building an integrated ticketing system that automatically captures user state and recent actions for faster troubleshooting.
  • Implementing automated email workflows using Resend to manage support tickets and set clear response time expectations.
  • Creating a documentation-driven support strategy that identifies product friction points and converts common queries into permanent knowledge base articles.
namesupport
descriptionSupport - help center, tickets, docs. Use when building support.

Support Guideline

Tech Stack

  • Framework: Next.js (with Turbopack)
  • Email: Resend

Non-Negotiables

  • Self-service must be prioritized over contact forms
  • Support context must include user state (plan, usage, recent actions)
  • Response time expectations must be set and met

Context

Support is where trust is won or lost. Users who need help are often frustrated — the support experience either deepens their trust or confirms their fears.

Great support isn't just fast responses — it's making users not need support in the first place. Every support ticket is a signal that something in the product could be clearer.

Driving Questions

  • What are the most common support requests and can they be self-served?
  • What context does support need that they don't have?
  • Where does the product create confusion that leads to support tickets?
  • How would we handle a surge in support volume?
  • What would make users feel supported before they ask for help?