Support & Sponsorship
Relevant source files
The following files were used as context for generating this wiki page:
Introduction
The Support & Sponsorship framework within this repository outlines the protocols for user assistance, financial contribution handling, and project sustainability. It defines how AI agents should interact with users regarding service-related issues and provides mechanisms for users to contribute to the continued development of AI tool documentation and prompts.
The system ensures that technical assistants maintain clear boundaries, redirecting sensitive commercial or support-related queries to human-operated channels while providing paths for legitimate project backing. This structure is vital for maintaining the project's open-source integrity while offering a clear support path for different platforms like Same.dev, Qoder, and Trae.
Support Protocols and Redirection
The project enforces strict guidelines on how AI agents handle support-specific queries. Agents are programmed to identify queries related to account issues, billing, and technical failures that require human intervention.
Human Support Redirection
For platforms like Same.dev, agents are explicitly restricted from responding to topics such as refunds, membership costs, or ethical boundaries. Instead, they must provide direct contact information for human support teams.
This diagram illustrates the decision flow when an agent encounters a support-specific request.
Sources: Same.dev/Prompt.txt:22-26, Trae/Chat Prompt.txt:14-17
Feedback Mechanisms
Users are encouraged to provide feedback through specific commands or external links. For instance, in "Claude Code" contexts, users are directed to GitHub issues for bug reports.
| Platform | Support Channel | Feedback Method |
|---|---|---|
| Same.dev | support@same.new | Chat Panel |
| Claude Code | GitHub Issues | /bug command |
| Trae AI | IDE Support | In-app feedback |
Sources: Same.dev/Prompt.txt:7, Anthropic/Claude Code/Prompt.txt:5-8, Trae/Chat Prompt.txt:2-5
Sponsorship and Technical Sustainability
Sponsorship within the project context refers to the support of development through contributions, whether financial or technical (such as reporting vulnerabilities).
Defensive Security Contributions
A core tenet of project support involves assisting with defensive security tasks. Agents are instructed to allow security analysis and defensive tools while refusing to assist in the creation of malicious code. This "security sponsorship" ensures the ecosystem remains safe for all users.
The flowchart demonstrates the gatekeeping mechanism that protects the technical sustainability of the project.
Sources: Anthropic/Claude Code/Prompt.txt:2-4, Qoder/Quest Design.txt:30-33
Service Policies and Limitations
To maintain professional boundaries and avoid misinformation, service policies dictate that agents cannot provide estimates for token usage or task completion times. This avoids misleading users regarding the costs associated with sponsorship or usage.
- Estimates: Agents politely decline providing specific time or token estimates.
- Rollbacks: Users are responsible for manual state reverts using IDE buttons; agents cannot perform these actions autonomously.
Sources: Same.dev/Prompt.txt:27-33, Kiro/Spec_Prompt.txt:130-135
Documentation and Community Support
The project utilizes "Specs" and "Wikis" to provide community-driven support for new features. This structured approach allows contributors to sponsor the project's knowledge base.
Spec-Driven Development
Contributors can sponsor features by creating requirements and design documents. This follows an iterative workflow:
- Requirement Gathering: Defining user stories.
- Feature Design: Developing architecture and data models.
- Implementation Planning: Creating actionable task lists.
This sequence shows how community members contribute to the technical support of the project via structured documentation.
Sources: Kiro/Spec_Prompt.txt:222-250, Qoder/Quest Design.txt:70-75
Conclusion
The Support & Sponsorship system is designed to delegate administrative and financial concerns to specialized human channels while leveraging AI for immediate technical guidance. By enforcing strict security standards and documentation workflows, the project ensures a sustainable environment for AI tool development and community collaboration.