How do I install the Spring Boot Dev skill?

Run npx skillmds@latest add arconia-io/spring-boot-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spring Boot Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spring Boot Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spring Boot Dev free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Spring Boot Dev?

arconia-io (@arconia-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spring Boot Dev by arconia-io — Agent Skill

Name: Spring Boot Dev
Author: arconia-io

Spring Boot Dev

Build, test, and run Spring Boot applications using Arconia CLI. Use when working on a Java or Spring Boot project and you need to compile the application, run tests, start the app in development mode, build a GraalVM native executable, or run the application locally with dev services. Also use when the user asks to check if the project compiles, verify tests pass, or launch the app for local development.

arconia-io 970d3e3 3.3 KB Updated Sep 17, 2026

File contents

Spring Boot Development

Use Arconia CLI to build, test, and run Spring Boot applications. Arconia CLI auto-detects Maven or Gradle — you never specify the build tool.

Run the application in development mode

arconia dev

This starts the app with the dev Spring profile active. If the project uses Arconia Dev Services, external services (databases, message brokers, AI inference servers, etc.) are provisioned automatically — no configuration needed.

Use --test (-t) only if the project relies on Spring Boot's native Testcontainers approach (a TestApplication class in src/test). If the project uses Arconia Dev Services, plain arconia dev is correct.

arconia dev --test

Build the application

arconia build

Options:

Flag	Effect
`--clean`	Remove previous build output first
`--skip-tests`	Skip tests during the build
`--native`	Produce a GraalVM native executable instead of a JAR
`--offline`	Build without network access

Build a GraalVM native executable:

arconia build --native

Build output locations

Build type	Gradle	Maven
JVM JAR	`build/libs/`	`target/`
Native executable	`build/native/nativeCompile/`	`target/`

Run tests

arconia test

Options:

Flag	Effect
`--clean`	Clean before testing
`--native`	Run tests in GraalVM native mode
`--offline`	Test without network access

Run a specific test class:

# Gradle
arconia test -- --tests "*BookServiceTests"

# Maven
arconia test -- -Dtest=BookServiceTests

If the project uses Arconia Dev Services, integration tests automatically get external services provisioned — no @Import annotations or configuration classes required.

Pass extra arguments to the build tool

Use -- to forward arguments to the underlying Maven or Gradle command:

arconia build -- --stacktrace
arconia test -- -DmyProperty=value
arconia dev -- -Dspring.profiles.active=staging

Workflow

Start the app: arconia dev
Make changes — the app live-reloads if Spring Boot DevTools is on the classpath
Run tests: arconia test
Build the final artifact: arconia build

Gotchas

arconia build --native requires GraalVM to be installed. Native builds are significantly slower than JVM builds but produce fast-startup, low-memory binaries.
arconia dev without --test is the default and correct choice when the project uses Arconia Dev Services. Only add --test for Spring Boot's native Testcontainers approach.
All commands support --verbose (-v) for detailed output when debugging build issues.
The -- separator is required to distinguish Arconia CLI flags from build tool arguments. Everything after -- is passed directly to Maven or Gradle.

---name: spring-boot-devdescription: Build, test, and run Spring Boot applications using Arconia CLI. Use when working on a Java or Spring Boot project and you need to compile the application, run tests, start the app in development mode, build a GraalVM native executable, or run the application locally with dev services. Also use when the user asks to check if the project compiles, verify tests pass, or launch the app for local development.license: Apache-2.0---# Spring Boot DevelopmentUse Arconia CLI to build, test, and run Spring Boot applications. Arconia CLIauto-detects Maven or Gradle — you never specify the build tool.## Run the application in development mode```basharconia dev```This starts the app with the `dev` Spring profile active. If the project usesArconia Dev Services, external services (databases, message brokers, AIinference servers, etc.) are provisioned automatically — no configuration needed.Use `--test` (`-t`) only if the project relies on Spring Boot's nativeTestcontainers approach (a `TestApplication` class in `src/test`). If theproject uses Arconia Dev Services, plain `arconia dev` is correct.```basharconia dev --test```## Build the application```basharconia build```Options:| Flag | Effect ||---|---|| `--clean` | Remove previous build output first || `--skip-tests` | Skip tests during the build || `--native` | Produce a GraalVM native executable instead of a JAR || `--offline` | Build without network access |Build a GraalVM native executable:```basharconia build --native```### Build output locations| Build type | Gradle | Maven ||---|---|---|| JVM JAR | `build/libs/` | `target/` || Native executable | `build/native/nativeCompile/` | `target/` |## Run tests```basharconia test```Options:| Flag | Effect ||---|---|| `--clean` | Clean before testing || `--native` | Run tests in GraalVM native mode || `--offline` | Test without network access |Run a specific test class:```bash# Gradlearconia test -- --tests "*BookServiceTests"# Mavenarconia test -- -Dtest=BookServiceTests```If the project uses Arconia Dev Services, integration tests automatically getexternal services provisioned — no `@Import` annotations or configurationclasses required.## Pass extra arguments to the build toolUse `--` to forward arguments to the underlying Maven or Gradle command:```basharconia build -- --stacktracearconia test -- -DmyProperty=valuearconia dev -- -Dspring.profiles.active=staging```## Workflow1. Start the app: `arconia dev`2. Make changes — the app live-reloads if Spring Boot DevTools is on the classpath3. Run tests: `arconia test`4. Build the final artifact: `arconia build`## Gotchas- `arconia build --native` requires GraalVM to be installed. Native builds are significantly slower than JVM builds but produce fast-startup, low-memory binaries.- `arconia dev` without `--test` is the default and correct choice when the project uses Arconia Dev Services. Only add `--test` for Spring Boot's native Testcontainers approach.- All commands support `--verbose` (`-v`) for detailed output when debugging build issues.- The `--` separator is required to distinguish Arconia CLI flags from build tool arguments. Everything after `--` is passed directly to Maven or Gradle.

Frequently asked questions