Container Native Deployment

Community

rrezartprebreza

container-native-deployment

Use when packaging Spring Boot 4 as an OCI image, JVM container, AOT application, or GraalVM native executable. Covers buildpacks, layers, runtime hints, probes, security, and verification.

Overview

Publisher	rrezartprebreza
Repository	`spring-boot-skills`
Skill name	`container-native-deployment`
Stars	322
Forks	52
Bundled files	3
License	MIT
Links	Skill source Repository

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.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by rrezartprebreza on GitHub. Read the source before you install it.

Installation

Install the Container Native Deployment AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/container-native-deployment
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/container-native-deployment

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/rrezartprebreza/spring-boot-skills.git /tmp/spring-boot-skills
mkdir -p .claude/skills
cp -r /tmp/spring-boot-skills/skills/spring-boot-4/container-native-deployment .claude/skills/container-native-deployment

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Container Native Deployment 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 Container Native Deployment 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 Container Native Deployment 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.

Container and Native Deployment

Choose JVM, AOT cache, checkpoint/restore, or native from measured requirements.

Container image

Prefer Boot build-image tasks with Cloud Native Buildpacks for standard services.
Preserve dependency, loader, snapshot, and application layers for cache reuse.
Pin compatible builder/run image families and promote immutable digests.
Run as non-root and use a read-only filesystem where possible.
Inject secrets at runtime; never copy credentials into a build context or image layer.
Configure graceful shutdown and platform termination timing together.

Runtime behavior

Verify JVM memory and CPU ergonomics under real container limits.
Expose Actuator liveness and readiness probes separately.
Use a startup probe for expensive initialization.
Keep writable paths explicit and bounded.

Native image and AOT

Use GraalVM 25 or newer with Boot 4 native build support.
Register narrow RuntimeHints for reflection, resources, serialization, JNI, or proxies.
Respect the closed-world model: runtime bean topology and classpath cannot change.
Review profile and conditional-bean behavior during AOT processing.
Run native integration tests against the produced executable.

Supply chain

Generate an SBOM, scan the final image, and regularly rebuild on patched run images.
Sign and attest release images where the delivery platform supports it.

Examples

See examples/good-dockerfile and examples/bad-dockerfile.

The good example uses Boot's jarmode=tools extraction in a builder stage. A normal Maven package does not create target/dependencies/ or target/application/ directories by itself.

Official sources

Container images: https://docs.spring.io/spring-boot/reference/packaging/container-images/
Dockerfiles and layer extraction: https://docs.spring.io/spring-boot/reference/packaging/container-images/dockerfiles.html
Native images: https://docs.spring.io/spring-boot/reference/packaging/native-image/

Gotchas

Agent assumes a passing JVM suite proves native compatibility - run the actual native executable.
Agent adds broad reflection metadata - use the smallest runtime hints possible.
Agent bakes secrets into layers - inject them only at runtime.
Agent makes liveness depend on remote systems - use readiness for traffic dependencies.
Agent selects native only for fashion - benchmark startup, memory, throughput, and build time.
Agent copies nonexistent target/dependencies directories - extract the packaged jar in a builder stage.

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 Container Native Deployment AI skill do?

Use when packaging Spring Boot 4 as an OCI image, JVM container, AOT application, or GraalVM native executable. Covers buildpacks, layers, runtime hints, probes, security, and verification.

Why use Container Native Deployment on TypingMind?

Because you install it once and use it with any model. Container Native Deployment 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 Container Native Deployment in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/rrezartprebreza/spring-boot-skills/tree/main/skills/spring-boot-4/container-native-deployment. 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 Container Native Deployment?

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 Container Native Deployment?

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

Is the Container Native Deployment AI skill free?

Yes. It is published on GitHub by rrezartprebreza under the MIT license. 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

Diagnosing Bugs

mattpocock

CommunityPopular

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

E2e Testing

Patrones de pruebas E2E con Playwright, Page Object Model, configuración, integración CI/CD, gestión de artefactos y estrategias para pruebas inestables.

Eval Harness

Framework formal de evaluación para sesiones de Claude Code que implementa principios de desarrollo orientado a evals (EDD)

Tdd Workflow

Usar este skill al escribir nuevas funcionalidades, corregir bugs o refactorizar código. Aplica el desarrollo guiado por pruebas con 80%+ de cobertura incluyendo pruebas unitarias, de integración y…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Container and Native Deployment

Container image

Runtime behavior

Native image and AOT

Supply chain

Examples

Official sources

Gotchas

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now