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

# Spaghetti Code

Though I do use JS in automating part of my workflow, I'm not really a developer. Since win32.run doesn't conform to any architectural pattern (I honestly don't know about this stuff), its codebase is a mess. 

\**One quick disturbing spoile*r: sometimes you see camelCase, the other times it's snake\_case. I don't know what I was thinking. Truely sorry for that.

In case you already have an up & running webapp (website) and want to run it on win32.run, please read [3rd-party apps](/developers/3rd-party-apps.md) section for integration, so you don't have to deal with this dirty codebase.

But if you're interested in expanding or customizing win32.run, this section will try to explain some parts of my spaghetti code.


---

# 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.win32.run/developers/spaghetti-code.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.