> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/readme/design.md). # Design Cortex XSIAM design guidance for content and Marketplace packs. Cortex XSIAM provides out-of-the-box content that contain most of the functionality you need. However, it also supports creating custom content, enabling you to develop unique functions to meet any specific need. You can create individual content items (playbooks, integrations, etc.) for your own use or create content packs that can be contributed to Marketplace. Content packs include one or more content items, and facilitate integrating various data sources by packaging together predefined configurations such as parsers, rules, and dashboards, improving the accuracy and efficiency of security threat identification and analysis. All content contributed to Marketplace must be within a content pack. Before you begin to create content packs for contribution, you need to understand your goals, and review the design guidelines. Careful attention to the design process ensures that you achieve your desired use case and that the different components of your content pack function correctly together. During the design process, we recommend the following stages: * Understand your use case. * Identify which components you need to achieve your use case, such as playbooks, integrations, incident fields, etc. Determine what content, if any, you can reuse from existing content packs. * Review [documentation best practices](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/documentation/documentation-best-practices.md). While you do not need to complete your entire design before you begin coding, we recommend you return regularly to the design stage throughout the development process, to review whether you are achieving your use case, if your components have changed, and to verify you are implementing best practices. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/readme/design.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.