> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/supercarrier-pro/supercarriers/included-ships/independence-class-litoral-combat-ship.md). # Independence-Class Litoral Combat Ship ## Description The Independence-class littoral combat ships (LCS) are a class of small surface vessels operated by the United States Navy. Designed for operations near shore (littorals), these ships are part of the Navy's strategy to have more versatile, modular, and nimble vessels for missions including mine countermeasures, anti-submarine warfare, and surface warfare. The Independence class is noted for its distinctive trimaran hull design, which provides exceptional stability and speed, and allows for the operation of small boats and unmanned vehicles in various conditions. ## Locations [Worldwide Locations](/supercarrier-pro/supercarriers/worldwide-locations.md) --- # 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://docs.miltechsimulations.com/supercarrier-pro/supercarriers/included-ships/independence-class-litoral-combat-ship.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.