# libs

It's a good convention to put applications-specific libraries into the directory matching the application name. This provides enough organization for small to mid-size applications(Crema is using this) like below.<br>

```
crema-4.x/
├── apps/
│   ├── source/
│   ├── source-e2e/
│   ├── adminapp/
│   └── adminapp-e2e/
├── libs/
│   ├── constants/
│   ├── context/
│   ├── helpers/
│   ├── hooks/
│   ├── services/
│   ├── source/
│   │   ├── feature-main/
│   │   ├── ui-table/
│   │   └── utils-testing/
│   ├── adminapp/
│   │   ├── feature-main/
│   │   ├── feature-login/
│   │   ├── ui/
│   │   └── utils-testing/
│   └── shared/
│       ├── ui/
│       └── utils-testing/
├── tools/
├── nx.json
├── package.json
└── tsconfig.base.json
```

\
For larger projects, it is a good idea to group libraries into application sections like below

```
crema-4.x/
├── apps/
│   ├── source/
│   ├── source-e2e/
│   ├── adminapp/
│   └── adminapp-e2e/
├── libs/
│   ├── constants/
│   ├── context/
│   ├── helpers/
│   ├── hooks/
│   ├── services/
│   ├── source/
│   │    ├── registration/
│   │    │   ├── feature-main/
│   │    │   ├── feature-login/
│   │    │   ├── ui-form/
│   │    │   └── utils-testing/
│   │    ├── search/
│   │    │   ├── feature-results/
│   │    │   └── utils-testing/
│   │    └── shared/
│   │        └── ui/
│   ├── source/
|   └── shared/
│       ├── ui/
│       └── utils-testing/
├── tools/
├── nx.json
├── package.json
└── tsconfig.base.jso
```


---

# Agent Instructions: 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:

```
GET https://docs.cremawork.com/v-4/overview/folder-structure/libs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.