with one click
create
Instantiate the rust-axum-template into a new project
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Instantiate the rust-axum-template into a new project
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a GitHub issue on the rust-axum-template repo from a description or current conversation context
Squash-merge the open PR, pull master, and reset dev branch
Start the dev server in the background, or restart it if already running
Show current branch, working tree status, and any open PR
Stop the running dev server
| name | create |
| description | Instantiate the rust-axum-template into a new project |
| allowed-tools | Bash, AskUserQuestion, Read |
Parse $ARGUMENTS for the following values. Arguments may be passed positionally
(/create my-app github.com acme) or as key=value pairs
(/create app=my-app git_username=acme). Skip prompts for any value already provided.
app=): Project name (alphanumeric and hyphens only)git_forge=): Git forge domain (default: github.com)git_username=): Git forge username or org namedeps_target=): Dependency install target (default: bin-deps)Only ask about template repo and branch if the user mentioned them:
https://github.com/EnigmaCurry/rust-axum-template.gitmasterCheck for nix-shell. If nix-shell is on $PATH, all bash commands in the
steps below MUST be run inside nix-shell. Use nix-shell --run "<command>" for
each bash invocation. The repo's shell.nix provides all required build tools
(cargo, node, pnpm, just, pkg-config, openssl, etc.) and configures environment
variables automatically. Do NOT install packages individually via nix profile install.
For any required value not provided via arguments, ask the user with AskUserQuestion:
github.com (Recommended) and codeberg.org as optionsgit remote get-url origin as default, with "Enter a different username" as the second optionAsk whether to:
setup.sh here) (Recommended)If creating a new directory (option b):
NEW_DIR="../${APP}"
git clone --branch "${TEMPLATE_BRANCH}" "${TEMPLATE_REPO}" "${NEW_DIR}"
Then run setup.sh from inside that directory.
Run setup.sh non-interactively (remember: wrap in nix-shell --run if nix is available):
cd "${PROJECT_DIR}"
DEPS_TARGET="${DEPS_TARGET}" APP="${APP}" GIT_FORGE="${GIT_FORGE}" GIT_USERNAME="${GIT_USERNAME}" bash setup.sh
Verify the build succeeded:
just test
All tests should pass. If they fail, diagnose and fix before continuing.
Report success and remind the user to:
LICENSE.txtjust run help to verify the build