> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/landing-page/landing-page-en/design/components.md).
# Toss Design System (TDS)
TDS is short for Toss Design System. It is the design system used across the Toss community, and the common design language that makes up Toss products, as well as a developer tool. TDS helps designers, developers, planners, and other roles collaborate using the same standards.
### TDS Benefits
* It can provide users with a consistent product experience.
* Designers can focus on solving problems rather than implementing UI.
* Developers can build 3 to 5 times faster than when creating custom UI themselves.
***
### Notes on using TDS
To use TDS safely and correctly, please review the information below first.
#### License information
{% hint style="info" %}
If you use this UI Kit, the [license terms](https://developers-apps-in-toss.toss.im/design/prepare/figma-ui-license)are considered accepted.
{% endhint %}
1. **Intellectual property rights:** All rights to all materials provided by Toss through the Apps in Toss (Appintoss) service, including intellectual property rights, belong to Toss. Partners may use these materials only within the scope of using the Apps in Toss service.
2. **Scope of usage rights:** Toss's permission to use TDS is a limited right for providing the Apps in Toss service. You cannot obtain deliverables or additional rights beyond this scope.
3. **Compliance obligations and actions in case of violations:** Partners must comply with this guide and relevant laws and regulations. If they fail to do so, Toss may suspend the provision of the Apps in Toss service or take other necessary measures.
***
### Component list
We introduce 11 core TDS components most frequently used in Apps in Toss. Click each component to see detailed usage instructions and examples.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developers-apps-in-toss.toss.im/landing-page/landing-page-en/design/components.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
.webp?alt=media&token=a6d87c01-7360-42f8-9d8f-8402bba4ecc3){kind=link}
