> For the complete documentation index, see [llms.txt](https://help.getskatter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getskatter.com/tutorials/parking-lots.md).

# Quick tip : Parking lots

You can create parametric parking lots using Curve Hosts.

![](https://s3.amazonaws.com/helpscout.net/docs/assets/59565b230428637ff8d43431/images/59b8433e042863033a1cc956/file-Al6Z7PJRnH.png)

Here is the skp file:  [parking.skp](http://forums.getskatter.com/uploads/default/original/1X/bc3e4f87f1804b26d4f5c00cd66ff7f152d34276.skp) \
Right-click on the cars group, then “Edit Skatter group”

The important steps:

* Make sure the axes of the car component are on the middle bottom of the car
* Create a line that goes through the middle of the spots. You may need to divide the line in at least 3, to group it. There is a small bug in Skatter that tend to make a loop if only two lines are connected. Check the groups containing the lines to see what I mean.
* Use Grid distribution, with the width of a parking spot as the Spacing X
* Then add some random rotation for a little bit of diversity

You can of course use as many different car components as you want.


---

# 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://help.getskatter.com/tutorials/parking-lots.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.