> For the complete documentation index, see [llms.txt](https://docs.lostage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lostage.io/welcome.md).

# Welcome to SLAG

Generating long-form fictional content with just a simple prompt.

## Overview

Development on SLAG began in December of 2024 as a way to generate an illustrated SciFi novel called *Starfall: Lost Age of Giants*. Shortly after generating the first chapter for *Starfall*, the team behind SLAG saw the potential in building a more abstract framework.\
\
Rather than create an application to generate a single literary work, we are building a system that can build *any* literary work from a single prompt. By leveraging modern LLMs (Claude Sonnet 3.5 at present), retrieval-augmented generation (RAG), and programmatic recursive-prompting, SLAG is able to develop rich stories complete with world building, character development, plot construction, and more.

At it's core, SLAG is a way of empowering anyone and everyone with the means to generate long-form fictional content for themselves and their communities.&#x20;

Together, we can make reading great again.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lostage.io/welcome.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.
