End-to-end project shipping: scaffold a stack, dockerize, deploy over SSH into an isolated Docker network, wire a reverse proxy (nginx or existing Traefik), and attach a public domain via Cloudflare — all without disturbing existing server services. Use when the user wants to build AND deploy something live, says "azzist", "ship this e2e", "deploy a landing page", "make it public", or asks for a full develop->deploy flow.
EnglishComprehensively identify an EXISTING project so azzist can deploy it: trace every source file (excluding dependency/build/VCS folders), detect the stack, build/run commands, ports, Dockerfiles, env vars, and database/cache usage, then propose an azzist.yaml. Use when the user points azzist at a project that already has code, says "azzist analyze", "deploy this existing repo/app", or before deploy when no azzist.yaml exists but source already does.
EnglishBuild the project's Docker image, smoke-test it locally, then ship it to the target server over SSH and run it in an ISOLATED Docker network on a free or assigned port. Use when the user wants to deploy an azzist project to a server, says "azzist deploy", or after a working local scaffold. Strictly avoids touching any existing container, network, or service.
EnglishGenerate azzist config files for a project: a committed azzist.yaml skeleton and a gitignored azzist.local.yaml for secrets (Cloudflare token, SSH credentials). Use when the user starts an azzist deployment, says "azzist init", "set up azzist config", or before any azzist scaffold/deploy step when no azzist.yaml exists yet.
EnglishScaffold a new project OR refactor an existing one to azzist standards. Serves as the base architecture layer for frontend, backend, database, cache, and queue services. v1 templates: Nuxt 3 (web). Use when the user wants to create a new project, says "azzist scaffold", OR when an existing project does not meet best-practice structure and needs to be aligned.
EnglishExpose a deployed azzist container publicly: detect the server's existing reverse proxy (Traefik container, host nginx, or none) and wire the app non-invasively, then upsert the Cloudflare DNS record and provision TLS. Use after azzist-deploy, when the user says "azzist server", "attach domain", or "make it public". Never disturbs existing proxies/services.
EnglishIncludes Azzist Analyze, Azzist Deploy, Azzist Init, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Azzist
End-to-end project shipping: scaffold a stack, dockerize, deploy over SSH into an isolated Docker network, wire a reverse proxy (nginx or existing Traefik), and attach a public domain via Cloudflare — all without disturbing existing server services. Use when the user wants to build AND deploy something live, says "azzist", "ship this e2e", "deploy a landing page", "make it public", or asks for a full develop->deploy flow.
Azzist Analyze
Comprehensively identify an EXISTING project so azzist can deploy it: trace every source file (excluding dependency/build/VCS folders), detect the stack, build/run commands, ports, Dockerfiles, env vars, and database/cache usage, then propose an azzist.yaml. Use when the user points azzist at a project that already has code, says "azzist analyze", "deploy this existing repo/app", or before deploy when no azzist.yaml exists but source already does.
Azzist Deploy
Build the project's Docker image, smoke-test it locally, then ship it to the target server over SSH and run it in an ISOLATED Docker network on a free or assigned port. Use when the user wants to deploy an azzist project to a server, says "azzist deploy", or after a working local scaffold. Strictly avoids touching any existing container, network, or service.
Azzist Init
Generate azzist config files for a project: a committed azzist.yaml skeleton and a gitignored azzist.local.yaml for secrets (Cloudflare token, SSH credentials). Use when the user starts an azzist deployment, says "azzist init", "set up azzist config", or before any azzist scaffold/deploy step when no azzist.yaml exists yet.
Azzist Scaffold
Scaffold a new project OR refactor an existing one to azzist standards. Serves as the base architecture layer for frontend, backend, database, cache, and queue services. v1 templates: Nuxt 3 (web). Use when the user wants to create a new project, says "azzist scaffold", OR when an existing project does not meet best-practice structure and needs to be aligned.
Azzist Server
Expose a deployed azzist container publicly: detect the server's existing reverse proxy (Traefik container, host nginx, or none) and wire the app non-invasively, then upsert the Cloudflare DNS record and provision TLS. Use after azzist-deploy, when the user says "azzist server", "attach domain", or "make it public". Never disturbs existing proxies/services.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Azzist skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.