> For the complete documentation index, see [llms.txt](https://docs.electrik.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.electrik.dev/1.x/getting-started/directory-structure.md). # Directory Structure Electrik is a non-intrusive package. It will not interfere with your existing structure. Most of the project is based on Laravel's directory structure. You can read more about it [here](https://laravel.com/docs/9.x/structure). However, for the documentation here is how Electrik is structured: * art (contains a screenshot of the dashboard you see after logging in) * config * database/migrations * resources/views * routes * src * stubs * .gitignore * LICENSE * README.md * composer.json * composer.lock ### Art Directory Art directory contains screenshots and graphics which are used for various documentations and readme files. They are not required or used in the application anywhere. ### Config Directory For Electrik to work properly, it needs to modify some values in default configuration files like auth.php, livewire.php, etc. You can take a look at the files to understand what has changed. ### Database/Migrations Similar to configuration, Electrik also needs to modify the table structure of existing packages to make it compatible with some features of Electrik. For example, we need to add `team_id` to Cashier's subscription table to make sure it works for the team rather than a user in the system. ### Stubs Directory This directory contains stubs required for building the Electrik components --- # 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://docs.electrik.dev/1.x/getting-started/directory-structure.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.