> For the complete documentation index, see [llms.txt](https://resources.viewrail.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.viewrail.com/install/signature-cable-railing/tension-kit-installs.md). # Tension Kit Installs Choose the install page that matches your run. Start with the run type. Then match the hardware at each end. ### Level runs * [Level Tension Kit to Level Tension Kit](/install/signature-cable-railing/tension-kit-installs/level-to-level.md) — Use this for a level run with tension kits on both ends. * [Inside Post Mount Kit to Level Tension Kit](/install/signature-cable-railing/tension-kit-installs/inside-post-mount-to-level.md) — Use this for a level run with an inside post mount on one end. ### Angle runs * [Angle Tension Kit to Angle Tension Kit](/install/signature-cable-railing/tension-kit-installs/angle-to-angle.md) — Use this for an angled run with angle kits on both ends. * [Inside Post Mount Kit to Angle Tension Kit](/install/signature-cable-railing/tension-kit-installs/inside-post-mount-to-angle.md) — Use this for an angled run with an inside post mount on one end. ### Installation order Use [Post Order of Installation](/install/signature-cable-railing/post-order-of-installation.md) to confirm where to start on your run before installing cable hardware. --- # 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://resources.viewrail.com/install/signature-cable-railing/tension-kit-installs.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.