> For the complete documentation index, see [llms.txt](https://docs.nuken.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuken.xyz/the-menus/project-config-menu/project-details.md).

# Project details

If you want to provide additional information about your project to those who may tinker with it after you, this section of the **Project Config Menu** may be helpful.&#x20;

When you import a project that's been configured with these project details, you'll get a neat little pop-up, like this.

<figure><img src="/files/fJ2kUgWDV9BFJkM4TtY3" alt=""><figcaption></figcaption></figure>

Here are some details you can provide about your project.

> **Intended device / audience** - Who is this for? Examples of target audiences include "*computers*", "*Windows devices*", "*smartphones*" , etc.

> **Project author** - What's your name? Just write whatever you want to be called. "Anonymous" is the default if you don't type anything.

> **Shoutout message** - What would you like to say? This is an input box for whatever you'd like. You could drop a project description here, or a link. Anything really.


---

# 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.nuken.xyz/the-menus/project-config-menu/project-details.md?ask=<question>&goal=<endgoal>
```

`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.
