> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/concepts/designing.md). # Designing ## Essentials All exercises need to consider SME - **Story, Mechanics and Environment**. Use the Canvas in AXS to see these at a glance so you know they’re all considered together. ## Participatory Storytelling A character in a story overcomes challenges to discover themselves. In a crisis exercise, the player is the character – they must overcome challenges to believe in themselves and believe in the process (or reform it). Think in terms of distinctive events which are moments in the exercise: one event = one serial.
### Players need to do stuff Exercises are **participatory** – we need to remember that we need to get players **doing something**, not passively reading. A common mistake is to publish a lot of content and have players read too much. Use the diagram below to consider possible player activities as a means to achieve your training objectives. --- # 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://helpdocs.conducttr.com/concepts/designing.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.