# Use App Requirements Doc

## Purpose

You can use the app requirements document to store context for that Deplyr AI should be aware of between edits. 

## Usage Tips

* Add in the purpose of your app.
* Write down the colors you want to use throughout your app.
* Write the integrations used in your app.
* If you have complex interactions like autosaving or debounced fuzzy searching, add that into your requirements doc.

## Example

Here's an Example requirements doc.

```
Product Requirements Document: Inventory Management App

Goal
*   Provide a user-friendly interface for managing inventory items.
*   Enable users to quickly add new items with relevant details.
*   Offer a visually appealing and modern design.

Core Product Requirements and Features

*   Add Inventory Item Form:
    *   Fields:
        *   Product Name (text input, required)
        *   Listed Price (number input, required, step 0.01)
        *   Sale Price (number input, step 0.01)
        *   Description (textarea, readonly, background grayed out)
        *   Sold (select input)
    *   Functionality:
        *   Form submission to add a new item to the inventory.
*   Modern UI Styling:
    *   Gradient background.
    *   Rounded corners on elements (form, inputs, buttons).
    *   Improved spacing between form elements.
    *   Refined typography.
    *   Enhanced button styling with gradient and hover effects.
```


---

# 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://deplyr.gitbook.io/docs/how-to-guides/use-app-requirements-doc.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.