> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/competitive-concepts/wcp-cc-2026/overview-and-features.md).
# Overview and Features
A Competitive Concept (aka CC) is a robot specifically engineered to be a valuable asset to any alliance; strives to be the most well-rounded robot on the team able to do everything. The WestCoast Products CC robot is designed with the intent of showing teams what is possible for high-level play and what some of the top 8 seeds will accomplish throughout a match.
{% hint style="danger" %}
This Build Guide is intended as a general guideline. The WCP CC was designed with care and with reference to the basic rules outlined in the 2026 FRC Game Manual. However, teams are responsible for ensuring full compliance with all rules, and any necessary modifications must be made accordingly.
{% endhint %}
{% hint style="info" %}
This Build Guide will continue to be under development for the 2026 Season and will be updated as the season progresses.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.wcproducts.com/welcome/competitive-concepts/wcp-cc-2026/overview-and-features.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
