LLM Agent Integration
LimeLink publishes an LLM-friendly documentation index at:
https://limelink.org/llms.txt
Give this single URL to an AI coding assistant, name your target platform and desired route behavior, and ask it to follow the linked current guides. From this entry point, the agent can discover the maintained instructions needed for every currently supported LimeLink deep-link workflow across web, iOS, Android, React Native, and Flutter—including direct links, Universal/App Links, eligible deferred journeys, verification, and troubleshooting.
Before generating setup code, confirm the host: RN requires New Architecture interoperability with Hermes and does not run in Expo Go; Flutter requires Flutter 3.44+/Dart 3.12+. Both wrappers depend on native SDK 1.0.1, while Flutter's package is 1.0.0. Request the relevant Android Application/Activity or iOS AppDelegate/SceneDelegate context without secrets. Follow one native lifecycle owner and one manual deferred navigation owner; register listeners early because errors/not-found are not replayed.
The index is the discovery layer: platform guides describe implementation, while the API, MCP, and Terraform provide separate, versioned automation paths. You do not need to collect individual guide URLs before starting.
Supported code workflows
- Flutter: install
limelink_flutterand follow the Flutter SDK guide. - React Native: install
@limelink/react-nativeand follow the React Native SDK guide. - iOS: use SwiftPM or CocoaPods with the iOS SDK guide.
- Android: use the public Maven artifact with the Android SDK guide.
- MCP: connect
@limelink/mcp0.1.0so an agent can read credential-free documentation, select profiles, discover Projects and Custom Domains, create Links, and retrieve or resolve them by suffix or URL through six registered tools. Configure API access withLIMELINK_PROFILES_FILEas described in the MCP Server guide. - Terraform: use
hellovelop/limelink0.3.1to manage Project, Application, and Custom Domain resources. Link is available only through the read-only UUID lookup data source; follow configuration, scope, import, and schema links in the Terraform guide.
llms.txt supplies context; it does not execute mutations or guarantee generated code. Review the selected guide, tool arguments, and generated changes before applying them.
Example Workflow
curl -fsSL https://limelink.org/llms.txt -o /tmp/limelink-docs.txt
Attach /tmp/limelink-docs.txt using the context-file feature supported by your chosen assistant, then ask for a specific task without secrets. For example:
Using the LimeLink React Native 1.0.1 guide from this index, show the
Community CLI initialization and Universal/App Link verification steps.
Use PROJECT_UUID as a placeholder and do not invent API-key configuration.
Give the agent MCP when it should operate LimeLink directly through the six documented tools.
Safe Context
Include:
- target platform and SDK version
- links to the relevant LimeLink guide
- your own non-secret app configuration requirements
Never include:
X-API-KEYvalues- one-time credential secrets
- access tokens
- production tenant, user, payment, or Paddle data
Verification
AI-generated code may be incomplete or stale. Confirm package versions, API fields, error handling, and platform setup against the linked guide and your installed dependencies before shipping.