This page is a test area for all UI components used across the Skill & Mobil platform. It includes buttons, forms, modals, sliders, accordions, and other interactive elements. Each component is displayed with its default state and a few variations, so you can see how they look and behave. It's mainly for developers and designers to check consistency, but if you're curious about what the app's building blocks look like, this is the place.

You can interact with them, but it's not a functional app. For example, you can click a button to see its hover or active state, type in an input field, or open a modal. However, none of these actions will save data or trigger real workflows. The page is purely for visual and behavioral testing, so feel free to play around, but don't expect any backend logic to run.

It's primarily for the development and design teams. The page acts as a living style guide and QA checklist. If you're a regular user, you likely won't need to visit it. But if you're a tester, a new developer, or someone auditing the UI, you'll find it useful to verify that every component matches the design specs and works correctly across different screen sizes.

Sometimes it's accidentally left public, but often it's intentional. Making it public lets third-party auditors, accessibility testers, or even potential partners see the UI quality without needing login access. It also helps with SEO testing or just transparency. In this case, it's part of a broader test suite, so having it publicly accessible means anyone can verify the components without setting up a full dev environment.

Yes, the page is designed to be responsive. You'll see components like hamburger menus, bottom sheets, and touch-friendly sliders that are specifically for mobile. If you resize your browser or open it on a phone, the components will adapt—buttons stretch, grids collapse, and modals become full-screen. This is crucial for testing how the Skill & Mobil app feels on smaller screens, so it's all covered here.

It's updated whenever a new component or a change to an existing one is pushed to the development branch. That means it can be ahead of the live app or behind it, depending on the release cycle. So, don't use it as a source of truth for what's currently in production. Instead, treat it as a preview of upcoming UI changes or a snapshot of the latest dev work. For stable info, check the actual app.