> For the complete documentation index, see [llms.txt](https://docs.coreframework.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreframework.com/navigating-the-ui/breakpoints.md). # Breakpoints Editing breakpoints could not be any more simple! We have made it super easy to add/edit classes and variables on literally any breakpoint, all within a few easy clicks! ## Video Overview {% embed url="" %} When you are editing on any breakpoint, the editing window will have a green border to indicate that you are indeed editing on a breakpoint and not editing on "All Breakpoints".

Editing on a breakpoint will turn the editing window green for easy

### Adding New Breakpoints To add a new breakpoint of your choice, simply click on the "Add new media query" button. This will bring up a mini modal where you can select your min-width and max-width values:

### Adding Classes to Breakpoints You will notice that each tab will be empty by default. Simply navigate through each tab to add classes/selectors along with their properties and values, and these will be applied to the break point you're currently on. Simple! Then once again, go through the tabs to add your necessary classes along with their properties and values for your specific breakpoints. --- # 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.coreframework.com/navigating-the-ui/breakpoints.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.