Kotlin Java Library logo

Kotlin Java Library

Community
alexandru
kotlin-java-library

Helps agents design and review Kotlin library APIs for Java consumers. Use when building Kotlin code intended for Java callers, shaping JVM signatures with @JvmName, @JvmOverloads, @JvmStatic, @JvmField, @Throws, @JvmRecord, nullability, records, and backward/binary compatibility rules.

Overview

Publisheralexandru
Repositoryskills
Skill namekotlin-java-library
Stars
51
Forks
3
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by alexandru on GitHub. Read the source before you install it.

Installation

Install the Kotlin Java Library AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/alexandru/skills/tree/main/skills/coding/kotlin-java-library
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/alexandru/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/coding/kotlin-java-library .claude/skills/kotlin-java-library
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Kotlin Java Library in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Kotlin Java Library on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Kotlin Java Library is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Kotlin Java Library Design

Quick start

  • Read references/kotlin-java-library.md before changing public Kotlin APIs for Java consumers.
  • Design Kotlin APIs as if the primary caller is Java: explicit overloads, stable names, and predictable nullability.
  • Use JVM interop annotations (@JvmOverloads, @JvmStatic, @JvmField, @JvmName) to shape the Java surface.
  • Prefer Java-friendly top-level functions with @file:JvmName, and use @file:JvmMultifileClass when splitting across files.
  • Use fun interface for Java callbacks; avoid function types that return Unit.
  • Document checked exceptions with @Throws and return defensive copies for read-only collections.
  • Follow binary compatibility rules: add overloads or new members instead of changing published signatures.
  • Validate examples with scripts/verify-examples.java when changing the reference or public API patterns.

Workflow

  1. Identify which public APIs must be Java-friendly (constructors, factories, utilities, callbacks, records).
  2. Shape the Java surface with JVM annotations and explicit overloads.
  3. Audit public signatures for Java stability (names, nullability, overload sets, and collection exposure).
  4. Apply backward-compatibility rules before publishing; treat @PublishedApi members as public.
  5. Validate with Java call-site examples.
  6. Run jbang skills/coding/kotlin-java-library/scripts/verify-examples.java; if it fails, fix the sample or document why it cannot be tested.

Rules of thumb

  • Avoid Kotlin-only surface features in public API: default args without overloads, extension-only entry points, and name clashes.
  • Explicitly declare public return and property types.
  • Use @JvmOverloads for Java-callable optional parameters, and provide explicit overloads when behavior differs.
  • Use @JvmStatic for companion/object members meant to be static in Java.
  • Use const val for compile-time constants and @JvmField only for immutable non-const fields you want exposed as fields.
  • Use @JvmName to resolve signature clashes or to provide a stable Java name.
  • Use @JvmRecord only for new Java-record value carriers targeting JVM 16+; do not retrofit it onto published classes.
  • Avoid Nothing in public generic signatures; it becomes raw types in Java.

Output expectations

  • Offer Java-call-site examples when proposing API changes.
  • Call out binary compatibility risks and safer alternatives.
  • Include validation results for non-trivial snippets.

References

  • Load references/kotlin-java-library.md for interop details, examples, and testing prompts.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Kotlin Java Library AI skill do?

Helps agents design and review Kotlin library APIs for Java consumers. Use when building Kotlin code intended for Java callers, shaping JVM signatures with @JvmName, @JvmOverloads, @JvmStatic, @JvmField, @Throws, @JvmRecord, nullability, records, and backward/binary compatibility rules.

Why use Kotlin Java Library on TypingMind?

Because you install it once and use it with any model. Kotlin Java Library is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Kotlin Java Library in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/alexandru/skills/tree/main/skills/coding/kotlin-java-library. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Kotlin Java Library?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Kotlin Java Library?

As many as you like. As long as a model supports skills, you can use Kotlin Java Library with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Kotlin Java Library AI skill free?

It is published on GitHub by alexandru. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇