Ignis

Use this skill when the current task is "developing or publishing services with Ignis", not when modifying the Ignis repository itself.

Scope of application:

Use
```
ignis-cli
```
to initialize, build, publish and deploy services
Use HTTP Router, middleware, response helper, SQLite and migration from
```
ignis-sdk
```
Write or troubleshoot
```
ignis.toml
```
Quickly get started with the minimal project structure in examples

Scope of inapplicability:

Modify source code of

ignis-cli

ignis-sdk

ignis-manifest

ignis-runtime

ignis-platform-host

Quick Process

First read
```
references/integration.md
```
to confirm the complete integration path.
If the task focuses on CLI or release deployment, continue reading
```
references/cli.md
```
.
If the task focuses on
```
ignis.toml
```
fields, default values or sample configurations, read
```
references/ignis-toml.md
```
.
If the task focuses on
```
ignis-sdk
```
API, use
```
references/ignis-sdk/index.md
```
as the entry point, and only open the currently required module or item page further.
If the task involves login or
```
[services.ignis_login]
```
, switch to the
```
ignis-login
```
skill.
If you need minimal HTTP / SQLite templates, prioritize reading the entire example projects:
```
references/examples/hello-fullstack/
```
and
```
references/examples/sqlite-example/
```
.

The currently recommended workflow is:

ignis login -> ignis project create -> ignis service new -> ignis service build -> ignis service publish -> ignis service deploy

The current CLI no longer takes local
```
dev
```
as the main workflow; build, publish and deployment are the default priorities.
Simple handlers can directly use
```
wstd::http
```
, but
```
ignis-sdk
```
is usually preferred for multi-routing, middleware, unified responses, and SQLite.
When you need to check SDK details, prioritize reading the single page generated by
```
mddoc
```
, do not infer only from summary documents.
The current public network routing model exposes services by path prefix under a project host, for example, the frontend uses
```
/
```
and the API uses
```
/api
```
, do not assume subdomains like
```
api.<project-host>
```
anymore.
The current
```
http
```
service uniformly uses the standard
```
wasm32-wasip2
```
build path, do not infer CLI behavior according to the
```
cargo-component
```
workflow anymore.
Do not guess the source of
```
ignis-sdk
```
dependencies; if the current version is not published to crates.io, use an explicit
```
path
```
or fixed
```
git
```
version.