Sign in Get started

toml-files - Skill - OpenSmartRoute

Skillv1.0.0

toml-files

globs: *.toml ---

by GuavaPay(0) 0 installs

Free

Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

About

Instruction file imported from GuavaPay/myguava-business-payment-sdk-android (.cursor/rules/toml-files.mdc). Copyright stays with the author.

globs: *.toml

TOML Files (.toml) Rules

File Structure

TOML files in project are primarily for dependency and version management, structured in three main blocks:

Block Organization

[versions] - Version declarations
[libraries] - Library dependency definitions
[plugins] - Plugin declarations

Naming Conventions

Use semantic naming with hyphens (-) as separators
Group related dependencies by functional area
Example: android-application, androidx-core-ktx, compose-ui

Naming Impact on Usage

Naming directly affects Gradle accessor syntax:

[plugins]
android-application = { id = "com.android.application", version.ref = "agp" }

Results in: alias(libs.plugins.android.application)

Version References

All related dependencies should reference version declarations
Use version.ref = "version-key" for consistency
Group versions logically (e.g., all Compose versions together)

Best Practices

Group related versions and libraries together
Use consistent naming patterns within functional groups
Reference versions from [versions] block rather than hardcoding
Keep version declarations at the top for easy maintenance
Use descriptive but concise naming that reflects the library's purpose

Use it

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

guavapay-myguava-business-payment-sdk-android-toml-files-rule.ocm.jsonjson

{
  "ocm": "1",
  "id": "guavapay-myguava-business-payment-sdk-android-toml-files-rule",
  "kind": "skill",
  "name": "toml-files",
  "description": "globs: *.toml ---",
  "publisher": "GuavaPay",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-cursor-rules"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "globs: *.toml ---"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-cursor-rules",
      "repository": "https://github.com/GuavaPay/myguava-business-payment-sdk-android",
      "path": ".cursor/rules/toml-files.mdc",
      "ref": "a54101addc6d566def7272c287937e27317c7bf6",
      "url": "https://github.com/GuavaPay/myguava-business-payment-sdk-android/blob/a54101addc6d566def7272c287937e27317c7bf6/.cursor/rules/toml-files.mdc",
      "key": "GuavaPay/myguava-business-payment-sdk-android/.cursor/rules/toml-files.mdc"
    }
  },
  "instructions": "---\nglobs: *.toml\n---\n\n# TOML Files (.toml) Rules\n\n## File Structure\nTOML files in project are primarily for dependency and version management, structured in three main blocks:\n\n### Block Organization\n- `[versions]` - Version declarations\n- `[libraries]` - Library dependency definitions  \n- `[plugins]` - Plugin declarations\n\n## Naming Conventions\n- Use semantic naming with hyphens (`-`) as separators\n- Group related dependencies by functional area\n- Example: `android-application`, `androidx-core-ktx`, `compose-ui`\n\n### Naming Impact on Usage\nNaming directly affects Gradle accessor syntax:\n```t",
  "cost": {
    "context_tokens": 320
  }
}

Fetch it by URL: GET /api/v1/registry/guavapay-myguava-business-payment-sdk-android-toml-files-rule/manifest?version=1.0.0