# Resources

For SF.gov usage and mechanics, see [our style guide](https://app.gitbook.com/@sfdigitalservices/s/style-guide).

Anything we don’t have in the guide we default to the [AP Stylebook](https://apstylebook.com/). If you don’t have access to it, check it [a copy from the SFPL](https://sfpl.bibliocommons.com/v2/record/S93C3826084) or email <webmaster@sfgov.org>.

We would like to thank:

[City of Oakland Style Guide](https://docs.google.com/document/d/1pOhZdKAyO_82BKspgiklE8pv962t3X2e3NA9hC4-jGg/edit#heading=h.2uwiwibyiti3) by the Oakland Design League&#x20;

We stole much of our guide from Oakland's excellent guide

The UK government’s [Content design: planning, writing and managing content](https://www.gov.uk/guidance/content-design)


---

# 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://sfdigitalservices.gitbook.io/style-guide/resources.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.
