Asd Ste100
danyuchn/asd-ste100-skill
A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…
Quarkus code style conventions: formatting, visibility, naming, logging, and general style rules for the Quarkus codebase.
Install Coding Style
$ npx skills add quarkusio/quarkus --skill coding-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install quarkusio/quarkus coding-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/coding-style .claude/skills/coding-style && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "coding-style" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-style into .claude/skills/coding-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add quarkusio/quarkus --skill coding-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install quarkusio/quarkus coding-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/coding-style .agents/skills/coding-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coding-style" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-style into .agents/skills/coding-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarkusio/quarkus --skill coding-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install quarkusio/quarkus coding-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/coding-style .cursor/skills/coding-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "coding-style" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-style into .cursor/skills/coding-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/quarkusio/quarkus.git --path .agents/skills/coding-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add quarkusio/quarkus --skill coding-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install quarkusio/quarkus coding-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/coding-style .gemini/skills/coding-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "coding-style" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-style into .gemini/skills/coding-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install quarkusio/quarkus coding-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add quarkusio/quarkus --skill coding-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/coding-style .github/skills/coding-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "coding-style" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-style into .github/skills/coding-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarkusio/quarkus --skill coding-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install quarkusio/quarkus coding-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarkusio/quarkus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/coding-style .opencode/skills/coding-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "coding-style" agent skill from https://github.com/quarkusio/quarkus/tree/main/.agents/skills/coding-style into .opencode/skills/coding-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
coding-style- GitHub stars
- 16k
- Token cost
- ~789 tokens
- SKILL.md length
- 347 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Quarkus code style conventions: formatting, visibility, naming, logging, and general style rules for the Quarkus codebase.
- Tasks that involve Plain language and style rules
- SKILL.md covers Formatting, Visibility, Naming and General Style, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Coding Style is an agent skill from quarkusio/quarkus. Quarkus code style conventions: formatting, visibility, naming, logging, and general style rules for the Quarkus codebase.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Plain language and style rules. It works with Java. The repository describes itself as: Quarkus: Supersonic Subatomic Java. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Plain language and style rules
Example prompts
- “/coding-style”
What it can do on your machine
Read from SKILL.md and the folder at commit 8e813fd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Coding Style loads about 789 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 347 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from quarkusio/quarkus at commit 8e813fd, republished under its Apache-2.0 licence (© quarkusio). 347 words, ~789 tokens.
Download SKILL.mdSave it as
.claude/skills/coding-style/SKILL.md (or your agent's skills folder).- name
- coding-style
- description
- Quarkus code style conventions: formatting, visibility, naming, logging, and general style rules for the Quarkus codebase.
Coding Style
Formatting
- Quarkus uses 4-space indentation (no tabs)
- The project enforces formatting via
formatter-maven-pluginandimpsort-maven-plugin, let the formatting plugins do their work, never use-Dno-format - Formatter config:
independent-projects/ide-config/src/main/resources/eclipse-format.xml - Run
./mvnw process-sourceson your module to auto-format before committing - The build will fail on formatting violations
- Imports are sorted and organized automatically; do not manually organize imports
Visibility
- Prefer package-private (default) visibility for internal implementation classes
- Use
publicfor user-facing API and for classes/methods that need to be accessed across packages (e.g., processors, recorders, build items). Prefer package-private for purely internal implementation details - Use
protectedwhen designing for extension/subclassing - Internal classes should go in
.internalor.implsub-packages (e.g.,io.quarkus.<ext>.runtime.internal)
Naming
- Deployment processors:
<Feature>Processor.java - Recorders:
<Feature>Recorder.java - Build items:
<Description>BuildItem.java - Config interfaces:
<Feature>Config.javaor<Feature>BuildTimeConfig.java/<Feature>RuntimeConfig.java - Artifact IDs:
quarkus-<name>(runtime),quarkus-<name>-deployment(deployment) - Package root:
io.quarkus.<extension-name>(hyphens become underscores)
General Style
- No
@authortags in Javadoc — Git history tracks authorship - No wildcard imports
- Never use fully-qualified class names inline — always add an
importstatement instead - Avoid
staticimports except for well-known patterns (e.g., test assertions) - Minimize lambdas and streams in runtime code — reduces memory footprint for native
- Prefer descriptive method and variable names over comments
- Update existing code comments if your changes make them invalid
- Never remove existing code comments that are still valid
- Keep methods focused and short; extract when complexity warrants it
- Use
Optionalfor API return types that may be absent. In internal hot runtime code paths, direct null checks are acceptable for performance - Commits should be atomic and semantic — properly squash before submitting PRs. This helps during bisects and makes it easier to revert changes when needed
- Don't use deprecated methods or classes in new code
Logging
- Use JBoss Logging (
org.jboss.logging.Logger) as the logging API - Do NOT use
System.out.printlnorSystem.err.println - Do NOT use SLF4J, java.util.logging, or Log4j directly in Quarkus core/extension code
Extension Descriptions
Extension descriptions (in runtime/pom.xml or quarkus-extension.yaml) should:
- Be short (no hover required)
- Describe the function, not the technology
- Start with an action verb, unconjugated (
Connect foo, notConnects foo) - Not mention "Quarkus" or "extension"
- Not repeat the extension name
© quarkusio, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/coding-style of quarkusio/quarkus.
Open the folder on GitHubat commit 8e813fd
Compare with similar skills
Coding Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Coding Style this skillquarkusio/quarkus | 16k | — | ~789 | Automated safety check: Pass | Apache-2.0 | |
| Asd Ste100danyuchn/asd-ste100-skill | 3.9k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None | |
| PgjevrealZachi/pg-jev | 1k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Defensive Writing Editorlennney/stop-that-shit | 2.5k | 1 repos | ~902 | Automated safety check: Pass | MIT |
Similar skills
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Pgjev
realZachi/pg-jev
Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
C Code Style
MaJerle/c-code-style
Write, edit, or review C (and C-compatible header) code according to C coding style rules, then check and run clang-format to enforce formatting.
More from quarkusio/quarkus
All 12 skills in this repoManage Deprecations
quarkusio/quarkus
Maintain @Deprecated code in the Quarkus codebase: remove code that has been deprecated for more than 12 months, add the @Deprecated annotations that were missed when a related element was…
Building And Testing
quarkusio/quarkus
How to build and test Quarkus: Maven commands, build flags, incremental builds, justfile aliases, and important build rules.
Building Docs
quarkusio/quarkus
How to build, preview, and verify Quarkus documentation locally: root Maven build, docs rebuild, Roq dev server preview.
Classloading And Runtime Dev
quarkusio/quarkus
Quarkus split classloading model, runtime-dev module wiring, conditional dependencies, and common classloading mistakes.
Converting Recorders To Services
quarkusio/quarkus
Step-by-step guide for converting Quarkus extensions from the legacy @Record/@Recorder pattern to the ServiceRegistrar service system.
Creating Extensions
quarkusio/quarkus
How to create a new Quarkus extension: full module layout, package naming, artifact naming, dependency rules, and Dev UI setup.
Related
Works with
Categories
Questions about Coding Style
What does Coding Style do?
Quarkus code style conventions: formatting, visibility, naming, logging, and general style rules for the Quarkus codebase. Coding Style is an agent skill from quarkusio/quarkus. Quarkus code style conventions: formatting, visibility, naming, logging, and general style rules for the Quarkus codebase.
When should I use Coding Style?
Coding Style fits situations like: tasks that involve Plain language and style rules.
How do I install Coding Style in Claude Code?
Run `npx skills add quarkusio/quarkus --skill coding-style -a claude-code`. Or copy the skill folder (.agents/skills/coding-style in quarkusio/quarkus) into .claude/skills/coding-style in your project. Claude Code loads it when a task matches its description.
How do I install Coding Style in Codex?
Run `npx skills add quarkusio/quarkus --skill coding-style -a codex`. Or copy the skill folder (.agents/skills/coding-style in quarkusio/quarkus) into .agents/skills/coding-style in your project. Codex loads it when a task matches its description.
Can I use Coding Style in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add quarkusio/quarkus --skill coding-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coding-style, .gemini/skills/coding-style, .github/skills/coding-style and .opencode/skills/coding-style in your project.
What does Coding Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Coding Style is instructions for the agent only.
Does Coding Style access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Coding Style safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Coding Style use?
Coding Style is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Coding Style use?
About 789 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Coding Style?
Skills that share tags, products or a category with Coding Style: Asd Ste100 (danyuchn/asd-ste100-skill, 3.9k stars), Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars), Technical Writing Standard (cursor/plugins, 10k stars) and Pgjev (realZachi/pg-jev, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Coding Style?
quarkusio (a GitHub organization) maintains it in quarkusio/quarkus, which has 15,929 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 6, 2026.
Source: quarkusio/quarkus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.