Start with route-specific docs at /docs before escalating a product-usage question. Use /support/faq for operational help outside the docs tree, /feedback when the product itself should improve, and the /profile account center for most logged-in account questions.

Identify the layer before you ask the question. Most confusion comes from mixing public browsing, logged-in account settings, provider integrations, platform API keys, and challenge workflows together. Once you know which layer you are in, the answer is usually much easier to find.

General questions

These questions help orient new users before they decide whether to go deeper into challenges, skills, prompts, or workspace flows.

Account and subscription

Most account issues are really route-discovery issues. The main thing to know is which profile surface owns which type of change.

Challenges and learning

Challenge questions usually come from deciding whether to browse, start locally, or create something new. These answers focus on that decision point.

AI tools and integrations

The most common tool confusion is about provider credentials versus platform auth. Keep that distinction clear and the rest of the tool model gets much simpler.

Support and escalation

When the product really is stuck, use the route that matches the type of issue. That keeps support requests actionable instead of vague.

Use support for operational issues and feedback for product gaps. If the problem is billing, account access, deletion, or something specific to your setup, use support. If the problem is that a product surface should work better, use the feedback route so the team can treat it as a product improvement. Open feedback.

If the issue still feels ambiguous, inspect whether auth, integrations, or the route itself is failing. That one distinction usually separates user action from actual product bug. It also makes a bug report much easier to reproduce and fix.