Metadata-Version: 2.5
Name: ion-sh
Version: 0.1.0
Summary: Ion: the tools that walk each project from its birth to its light. Installs them, keeps them up to date, runs them.
Project-URL: Homepage, https://github.com/antoine-tena/ion
Author: antoine-tena
License-Expression: MIT
Keywords: claude-code,developer-tools,installer,ion,web-studio
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Operating System :: MacOS
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python :: 3.14
Requires-Python: >=3.14
Description-Content-Type: text/markdown

# ion

The tools that walk each project from its birth to its light. The ion is the client's project:
born in the studio, carried by the tools, guarded, given a shape, seen, lasting. Each tool walks
it through one step of that journey.

```sh
uv tool install ion-sh
ion add                # asks which tools to install
ion add repo host      # or name them; `all` for every published one
ion list               # the family by stage, and what is installed (`--json` for a script)
ion upgrade            # every installed tool, and ion itself
ion remove repo        # asks first; `--yes`, `--dry-run`
ion host domain check  # runs a tool: hands over to `ion-host domain check`
```

Each tool is its own package on PyPI, `ion-<tool>`, installed as its own uv tool with its own
command `ion-<tool>`. No plain word lands on the PATH, so no tool can clash with a system command
(`host`, `render`): `ion <tool> …` runs it, the way `git lfs` runs `git-lfs`.

**Sun**: the studio itself, where every project is born.

| Tool | Role |
|---|---|
| `sell` | prospecting: finding the next clients, the first contact |
| `count` | the studio's books: accounting, cash, what is owed |
| `hire` | the team: roles, access, welcoming a newcomer |

**Flare**: the storm that can hit a project on the way.

| Tool | Role |
|---|---|
| `rescue` | incidents: from the alert to the post-mortem |

**Wind**: the workshop, the tools that carry the know-how to every repo.

| Tool | Role |
|---|---|
| `repo` | technique: code, tests, CI, updates, working with Claude |
| `render` | templates: render, then update without overwriting (Rust) |
| `score` | sourced rules and their score |
| `learn` | rereads sessions and pours their lessons into the right tool |

**Shield**: what guards a client project and lets it shine.

| Tool | Role |
|---|---|
| `deal` | business: client file, quotes, contracts, legal duties |
| `host` | hosting and operations: servers, domains, DNS, mail, backups |
| `secure` | security: audits, secrets |

**Sky**: where the project takes its shape and colours.

| Tool | Role |
|---|---|
| `design` | design: visual identity, layout, typography, motion |
| `media` | raw media: photos, videos and logos, sorted, with their rights |

**Aurora**: the moment the public sees it.

| Tool | Role |
|---|---|
| `words` | words: site copy, docs, announcements |
| `launch` | launch: announcement, listings, first visibility |

**Afterglow**: what stays and pays once it is launched.

| Tool | Role |
|---|---|
| `maintain` | upkeep of delivered sites: updates, small requests |
| `measure` | what a site brings: audience, conversions |
| `show` | client stories: testimonials, case studies, portfolio |

A tool joins PyPI with its first release; `ion list` says which ones are there. Until then, a
tool already published under its earlier name installs from it (`keramos-hearth`,
`keramos-grog`), and `ion <tool>` runs its earlier command (`kiln`, `hearth`, `grog`).
