Give your AI assistant access to the documentation
If you use an AI coding assistant — GitHub Copilot, Claude Code, Cursor, Windsurf, or a self-hosted LLM — you can give it access to the full Citrix SecurSpaces™ documentation so it can answer SecurSpaces-specific questions accurately and help you with SecurSpaces tasks.
The documentation is served directly from your SecurSpaces instance, so this works the same way in air-gapped and internet-connected environments. All documentation fetches stay on your network, and the documentation always matches your deployed SecurSpaces version.
Overview
The documentation is published in an AI-readable format based on the llms.txt standard. Two files make this possible:
-
llms.txt— a structured index of every documentation page, so your AI assistant can discover what is available and fetch the right page. -
llms-full.txt— the complete documentation corpus in a single file, for ingestion into a context window or a retrieval-augmented generation (RAG) system.
Which source to use
Both files are available from two places. Prefer the first if you have a SecurSpaces deployment.
| Source | URL | Use it when |
|---|---|---|
| Your SecurSpaces instance | https://<your-securspaces-url>/docs/llms.txt |
You have access to a deployment. The documentation matches your deployed version, fetches stay on your network, and it works in air-gapped environments. |
| The public copy | https://assets.sds.citrix.com/llms.txt |
You have no deployment to point at, or your tool cannot reach one. Always the latest published documentation, which may be ahead of your version. |
The public copy indexes the same pages on docs.citrix.com, so it needs outbound internet access. Use the
instance-hosted copy where you can: it cannot drift from the platform you are actually running.
This guide walks through:
- Verifying the documentation is available from your SecurSpaces instance.
- Adding SecurSpaces context to your AI assistant.
- Testing that your assistant uses the documentation.
Before you begin
- Know your SecurSpaces instance URL — the URL you use to log in to the SecurSpaces console (for example,
https://sds.mycompany.internal). - Use an AI assistant that supports system prompts or custom instructions.
Step 1: Verify the documentation is available
In your browser, navigate to:
https://<your-securspaces-url>/docs/llms.txt
<!--NeedCopy-->
You should see a structured list of SecurSpaces documentation pages. If this page loads, you are ready to continue.
If it does not load, contact your platform administrator. If you have no SecurSpaces instance to point at,
use https://assets.sds.citrix.com/llms.txt instead and substitute that URL wherever this guide refers to
your instance.
Step 2: Add SecurSpaces context to your AI assistant
Add the following snippet to your AI assistant’s system prompt or custom instructions. Replace <your-securspaces-url> with your actual SecurSpaces instance URL.
You have access to documentation for Citrix SecurSpaces, the cloud development environment I work in. In SecurSpaces, my code, IDE, and developer tools run in a remote, containerized workspace that I access from a browser or over SSH — not on my local machine.
This workspace IS a SecurSpaces workspace. Treat any reference to "my/this workspace," "my environment," "this machine/container," or my dev tooling as referring to SecurSpaces — even when I don't say "SecurSpaces" explicitly.
Documentation sources:
- Documentation index: https://<your-securspaces-url>/docs/llms.txt
- Full documentation corpus: https://<your-securspaces-url>/docs/llms-full.txt
How to answer SecurSpaces questions:
- Fetch the index first to find relevant pages, then fetch the specific page(s) for detailed answers. For a clearly SecurSpaces-related question, prefer this documentation over general knowledge.
- Cite the specific doc page(s) you used (title or URL) so I can verify the source. If you did not consult the docs for a SecurSpaces answer, say so.
- SecurSpaces workspaces are ephemeral. When advising on installing tools or changing the environment, check what persists and recommend an approach that survives workspace restarts.
Accuracy and uncertainty:
- Base SecurSpaces-specific answers on the fetched documentation. Clearly separate what the docs confirm from your own general knowledge or inference.
- If the documentation does not cover the question, or covers it only
partially, say so explicitly rather than filling the gap with assumptions.
- Do not invent SecurSpaces features, configuration options, URLs, CLI commands, API fields, or version numbers. If you are not certain a detail is in the docs, state your uncertainty and point me to the docs index or my platform administrator instead of guessing.
- This documentation matches my deployed SecurSpaces version. If your general
knowledge conflicts with it, the documentation wins. Flag any behavior that may depend on version, configuration, or admin-controlled settings.
- If you cannot reach the documentation URLs, tell me the fetch failed and do not answer SecurSpaces-specific questions from memory alone.
<!--NeedCopy-->
Where to add this snippet
| AI Tool | Where to add |
|---|---|
| GitHub Copilot (VS Code) | Settings → Copilot → Custom Instructions, or .github/copilot-instructions.md in your repo |
| Claude Code | Add to CLAUDE.md in your project root, or ~/.claude/CLAUDE.md for global |
| Cursor | Settings → Rules for AI, or .cursorrules file in your repo |
| Windsurf | Settings → Cascade → Rules |
| Self-hosted LLM (Ollama, etc.) | Modelfile SYSTEM directive, or pass as a system message in your client |
Step 3: Test it
Ask your AI assistant a clear SecurSpaces-specific question, for example:
“How do I configure a workspace template in SecurSpaces?”
The assistant should fetch the documentation and provide a specific answer with SecurSpaces terminology and concrete steps.
Troubleshooting
| Symptom | Possible cause | What to do |
|---|---|---|
https://<your-securspaces-url>/docs/llms.txt does not load |
Wrong instance URL, or docs endpoint not reachable from your network | Confirm the URL you use to log in to the SecurSpaces console. If it still fails, contact your platform administrator. |
| The assistant answers from general knowledge instead of the docs | Snippet not applied, or the tool does not auto-fetch URLs | Confirm the snippet is saved in the correct location for your tool. Ask the assistant to fetch the documentation index first. |
| The assistant reports it cannot reach the documentation URLs | Air-gapped tool without network access to the SecurSpaces instance | Ensure the AI tool runs where it can reach your SecurSpaces instance URL, or use llms-full.txt as pasted context. |
| You have no SecurSpaces instance to point the assistant at | Evaluating, or working outside a deployment | Use the public copy at https://assets.sds.citrix.com/llms.txt and https://assets.sds.citrix.com/llms-full.txt. |
Related information
- Run AI coding agents in workspaces — how agents are governed when they run inside a workspace, and what your administrator sets up for them