creating-julia-app
Use when you create a CLI written in Julia packages or MCP servers
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when you create a CLI written in Julia packages or MCP servers
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when you run tests
Use when you need the latest stable JuliaLang version number (e.g., to fill `VERSION=` in an install script) instead of hard-coding a value
Use when your machine does not have JuliaLang runtime
Use when you write a Julia package
Use when you add tests for Julia packages
Use when you create a JuliaLang package
| name | creating-julia-app |
| description | Use when you create a CLI written in Julia packages or MCP servers |
Apps are Julia packages that are intended to be run as "standalone programs" (by e.g. typing the name of the app in the terminal possibly together with some arguments or flags/options). This is in contrast to most Julia packages that are used as "libraries" and are loaded by other files or in the Julia REPL.
A Julia app is structured similar to a standard Julia library with the following additions:
A @main entry point in the package module (see the Julia help on @main for details)
An [apps] section in the Project.toml file listing the executable names that the package provides.
A very simple example of an app that prints the reversed input arguments would be:
# src/MyReverseApp.jl
module MyReverseApp
function (@main)(ARGS)
for arg in ARGS
print(stdout, reverse(arg), " ")
end
return
end
end # module
# Project.toml
# standard fields here
[apps]
reverse = {}
The empty table {} is to allow for giving metadata about the app.
After installing this app one could run:
$ ~/.julia/bin/reverse some input string
emos tupni gnirts
directly in the terminal. See the following link to learn more: