> For the complete documentation index, see [llms.txt](https://annarbor.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annarbor.worldiaday.org/people/krysta-stone.md).
# Krysta Stone
Krysta has been a practitioner of design thinking for over 17 years and applies her information architecture, UX strategy & research, and product management expertise to crafting user-centered digital experiences. Working with clients in industries ranging from financial services, to healthcare, to cultural institutions, she has a passion for influencing the way people interact with technology and savors the challenge of breaking complex information into simple interactions. Currently the Director of User Experience at Perficient/Digital, Krysta’s a travel, comedy, and food enthusiast and holds a Master of Science in Information degree from the University of Michigan.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://annarbor.worldiaday.org/people/krysta-stone.md?ask=&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 `automate deployments from our CI pipeline` 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.