-
-
Notifications
You must be signed in to change notification settings - Fork 34
Support.md
We provide multiple support channels to help you succeed with CursorRIPER.sigma. You can select the right channel based on your needs and the urgency level.
| Level | Description | Response Time | Availability |
|---|---|---|---|
| Community | Free community support | 24-48 hours | Best effort |
| Standard | Email support for users | 12-24 hours | Business hours |
| Priority | Dedicated support team | 4-8 hours | Extended hours |
| Enterprise | 24/7 dedicated support | 1-4 hours | Always available |
- Self-Service First - Check documentation and FAQ
- Community Support - Ask in discussions or forums
- Official Support - Contact our support team
- Escalation - Critical issues get priority handling
Best for: General questions, feature discussions, sharing experiences
Location: GitHub Discussions
Categories:
- π¬ General - General questions and discussions
- π‘ Ideas - Feature requests and suggestions
- π Q&A - Questions and answers
- π Show and Tell - Share your projects
- π’ Announcements - Official updates
Response Time: 24-48 hours (community-driven)
How to Get Better Help:
- Use clear, descriptive titles
- Provide context and examples
- Search existing discussions first
- Include relevant details (versions, error messages)
- Be patient and respectful
Best for: Bug reports, reproducible problems
Location: GitHub Issues
When to Use:
- You've found a reproducible bug
- Feature is broken or not working as documented
- Security vulnerabilities (use security template)
- Documentation issues
Response Time: 12-48 hours
Required Information:
- Framework version (
npm list @cursoriper/core) - Node.js version (
node --version) - Operating system and version
- Steps to reproduce
- Expected vs actual behavior
- Error messages and stack traces
Guidelines:
- Search previous messages before asking
- Use threads for detailed discussions
- Be respectful and patient
- Help others when you can
Best for: Technical issues, account problems, private matters
Essential Information:
Subject: [FRAMEWORK VERSION] Brief description of issue
Environment:
- Framework Version: 1.0.5
- Node.js Version: 18.17.0
- Operating System: Ubuntu 22.04
- Package Manager: npm 9.8.1
Issue Description:
- What were you trying to accomplish
- What happened instead
- Error messages (full stack traces)
- Steps to reproduce
Attempts to Resolve:
- What you've already tried
- Documentation you've consulted
- Similar issues you've found
For Performance Issues:
- System specifications (CPU, RAM, disk)
- Load characteristics (users, requests/second)
- Monitoring data, if available
- Database and cache configuration
For Security Issues:
- Do NOT include sensitive information
- Describe the vulnerability generally
- Include affected versions
- Mention any public disclosure timeline
When to Use: Production outages, security incidents, data loss
- Price: $500/month
- Response Time: 8 hours (business hours)
- Channels: Email, phone during business hours
- Coverage: Business-critical issues
- Price: $2,000/month
- Response Time: 4 hours (extended hours)
- Channels: Email, phone, dedicated Slack
- Coverage: All issues, including development help
- SLA: 99.5% response time guarantee
- Price: $5,000/month
- Response Time: 1 hour (24/7/365)
- Channels: Email, phone, dedicated hotline, on-site if needed
- Coverage: Everything + proactive monitoring
All Enterprise Plans Include:
- Priority bug fixes and feature development
- Access to beta features and early releases
- Custom documentation and training materials
- Architecture review and consultation
- Migration assistance and planning
- Dedicated support portal access
Start Here First:
- Quick Start Guide - Get up and running in 5 minutes
- FAQ - Answers to common questions
- Troubleshooting Guide - Solve common problems
- API Reference - Complete API documentation
Tutorials and Guides:
Video Resources (Coming Soon):
- Getting started video series
- Advanced feature tutorials
- Live coding sessions
- Community webinars
Community Content:
- Blog posts and articles
- Conference presentations
- Community-created tutorials
- Example projects and templates
North America:
- Hours: 6 AM - 10 PM PST (business support)
Primary Languages:
- English (native support)
How to Provide Feedback:
- Support surveys after each interaction
- Annual support review for enterprise customers
- Feedback email: feedback@cursoriper.com
- Community discussions about support experience
What We Track:
- Response and resolution times
- Issue categorization and trends
- Customer satisfaction scores
- Support channel effectiveness
- Documentation gaps and improvements
Continuous Improvement:
- Monthly support team training
- Quarterly process reviews
- Community feedback integration
- Tool and platform upgrades
Do you have a question or issue?
ββ Is it an emergency? β Emergency Support
ββ Is it a bug or security issue? β GitHub Issues
ββ Do you need quick help? β Discord/Community
ββ Is it complex or private? β Email Support
ββ Want to discuss or share? β GitHub Discussions
| Issue Type | Recommended Channel | Expected Response |
|---|---|---|
| Quick question | GitHub Discussions | Minutes to hours |
| Bug report | GitHub Issues | 12-48 hours |
| Feature request | GitHub Discussions | 24-72 hours |
| Technical issue | Email Support | 8-24 hours |
| Enterprise help | Enterprise Support | 1-8 hours |
| Emergency | Emergency Hotline | 30 minutes - 2 hours |
| Security issue | security@cursoriper.com | 2-12 hours |
Do This:
- β Search documentation and FAQ first
- β Provide complete information upfront
- β Use the most appropriate channel
- β Be specific about your environment
- β Include steps to reproduce issues
Avoid This:
- β Posting the same question in multiple channels
- β Providing vague problem descriptions
- β Using emergency channels for non-urgent issues
- β Including sensitive information in public channels
- β Demanding immediate responses
- Website: https://cursoriper.com
- Documentation: Framework Wiki
- GitHub: https://github.com/johnpeterman72/CursorRIPER.sigma
- Support operates on reduced hours during major holidays
- Emergency support remains available
- Holiday schedule published in advance
- Community channels remain active
We're here to help you succeed with CursorRIPER.sigma! Don't hesitate to reach out.
Last Updated: June 28, 2025
Framework Version: CursorRIPER.sigma v1.0+
Need immediate help? Check our FAQ or start with GitHub Discussions! π
- ποΈ Framework Overview
- π RIPER Modes
- πΎ Memory System
- π£ Symbolic Notation
- π Phase Management
- π‘οΈ Code Protection
- π Context References
- π Permission System
- π Cross-References
- πΎ Backup System
- π Mode Transitions
- πΎ Memory Management
- π‘οΈ Protection Workflow
- π Context Management
- π₯ Team Collaboration
- π£ Symbol Reference
- β¨οΈ Command Reference
- π Mode Reference
- π Permission Matrix
- π API Reference
- π Overview
- π GitHub Integration
- π Web Search
- π Browser Automation
- π³ Docker Integration
-
Installation Issues
- Node.js Version Compatibility
- Package Installation Failures
- Framework Dependencies Missing
- Database Connection Issues
- Port Conflicts
- Environment Setup Issues
- Build and Development Issues
- Framework CLI Issues
-
Configuration & Runtime Issues
- Framework Configuration Problems
- Runtime Performance Issues
- Module Loading and Plugin Issues
- Database and Storage Issues
- Memory Leaks and High Memory Usage
- High CPU Usage
-
BMAD Module Issues
- BMAD Module Initialization Problems
- Business Model Canvas Issues
- Stakeholder Management Issues
- Analytics and Reporting Issues
- Performance Optimization
-
Database & API Issues
- Database Connection Problems
- Database Migration Issues
- API Performance and Reliability Issues
- Data Consistency Issues
- Transaction Problems
-
Performance & Memory Issues
- Memory Management
- CPU Optimization
- Database Query Performance
- Caching Issues
- Resource Monitoring
-
Security & Authentication Issues
- Authentication Failures
- Authorization Problems
- JWT Token Issues
- Session Management
- CORS and Security Headers
- SSL/TLS Configuration
-
Deployment & Production Issues
- Production Deployment Failures
- Environment Configuration
- Load Balancing Issues
- Monitoring and Logging
- Backup and Recovery
When reporting issues, please include:
- Framework version (
npm list @cursoriper/core) - Node.js version (
node --version) - Operating system and version
- Error messages and stack traces
- Steps to reproduce the issue
- Configuration files (sanitized)
- Recent changes or deployments
- Technical Support: support@cursoriper.com
- Documentation: https://docs.cursoriper.com
- Community Forum: https://community.cursoriper.com