Skip to content
Skills Library
Design & UX · Building & coding

artifacts

/artifacts

Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or when they paste a Ryugi Cloud link (…/a/…) to read, including during brainstorming.

Author
innei ↗
Repository
ryugi ↗
Licence
MIT
Last repository change
14.11.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
10
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 14.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or when they paste a Ryugi Cloud link (…/a/…) to read, including during brainstorming.

Original author description

Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or when they paste a Ryugi Cloud link (…/a/…) to read, including during brainstorming.

How it works

  1. Read a Ryugi Cloud link
  2. Reading CLI output
  3. Pick the type
  4. Before writing
  5. Creative work
  6. Pick the artifact
  7. Start the server and get the link
  8. Share a link
  9. Auto-publish
  10. Directory
Original SKILL.md headings · 250 lines, 1,926 words
SKILL.md preview
---
name: artifacts
description: Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or when they paste a Ryugi Cloud link (…/a/…) to read, including during brainstorming.
---

# Artifacts

Artifacts are pages your human partner opens in their browser while you
work: an artboard of mockups to choose from and comment on, a document to
read and comment on, or one HTML page to click and tune. You write files
into the project; a local server shows each artifact at its own link and
updates it the moment a file changes. They look, then answer on the page or
in the terminal.

**Use this app for every artifact** — even when your harness offers its own
artifact or publishing tool, including one named `Artifact` or a hosted
canvas. When they want a link that opens outside this machine, publish it to
Ryugi Cloud (see Share a link).

## Read a Ryugi Cloud link

When your human partner pastes a Ryugi Cloud link (`https://ryugi.innei.dev/a/<id>`,
or `/a/<id>` on another Ryugi Cloud host), run this with `app/` in this skill's directory:

```bash
node app/ryugi.cjs get <link>
```

The page is an app shell; `get` reads its content with this machine's Cloud
sign-in and prints an outline, not the files. Follow the printed `Details`
or `More` command; they keep the captured version and page scope. `--block ID`
reads one complete block, `get <link> --source` prints pure LiteXML, and
files need `--download --out NEW_DIRECTORY`. Exit code 2 requires human
action: follow the printed login or upgrade link.

## Reading CLI output

Read the default **Brief** output directly. The first line names the
command, the artifact and what needs doing
(`Comment list: document/plan · 3 to apply`). Each collection follows as a
title line with its counts, then one line per record that needs action: the
id first, then its state and value in words
(`days · submitted → 45 (recommended)`). Records that need nothing are only
counted; `--all` lists them. The last lines are the commands to run next:
`Next`, `Read`, `More`, `Acknowledge`, `Details`. If a format configuration
overrides Brief, add `--format brief` for that call.

- Run the printed `Read`, `More` and `Acknowledge` commands as printed; they
  keep the snapshot, project, artifact and receipt.
- Acknowledge only after reading and using all the evidence the `Read`
  delivered. A preview has no receipt, later replies stay unread, and ack
  never resolves or decides anything.
- Each type's guide says which comment sections to read and how to apply
  answers, choices and verdicts.
- Exit codes: 0 success, 1 failure, 2 human action, 3 validation issues, 4
  incomplete evidence, 5 partial completion, 130/143 interrupted. Inspect the
  reported effects before retrying an unknown write.

Select `--format json` only when code such as `jq` parses the output, and read
its `data` envelope (`.data.url`).

## Pick the type

| What is being decided                                                                                        | Type                       | Read before writing                                                      |
| ------------------------------------------------------------------------------------------------------------ | -------------------------- | ------------------------------------------------------------------------ |
| Architecture, engineering design, a review, report, proposal or walkthrough                                  | `document`                 | `document.md`                                                            |
| Structure still taking shape — parts, modules, roles, who talks to whom — or they want to draw it themselves | `whiteboard`               | `whiteboard.md`                                                          |
| One surface or one dimension — a component, type scale, background, motion                                   | `html`                     | `html.md`, `ui.md` for components                                        |
| A business space — several screens, dimensions, states or questions at once                                  | `artboard`                 | `artboard.md`; `artboard-prototype.md` for playable boards or parameters |
| Whether a built change matches what was approved, when they ask you to verify it                             | `artboard`, a verify group | `artboard.md`                                                            |
| What you proved by running it: output, numbers, what is deployed, and what you did not verify                | `verify`                   | `verify.md`                                                              |
| Nothing to see                                                                                               | text                       |                                                                          |

Draw on a whiteboard while the parts and arrows are themselves the question;
once the structure is settled and the reasons need writing, it is a document
that references the whiteboard. Explaining a structure that already exists is
a document; working one out together, even starting from existing code, is a
whiteboard. UI screens and user flows stay on an artboard.

A control does not make it an artboard: one surface, however tunable, is
`html`. The artboard is for several dimensions at once; one group is one
dimension. "HTML" or "page" names the medium, not the type.

## Before writing

The type column is a gate, not a menu: open that doc first, in a command of
its own. Read alongside other files, a harness's output cap can cut it off
midway. `html` also reads `ui.md` — its controls are `<ryugi-…>`; artboard
boards use plain HTML, CSS and JavaScript, including their own event
handlers. Verify against the doc — ids, `ryugi-change`, restored state — not
just that it renders.

## Creative work

For UI mockups, landing and marketing pages, visual direction exploration and interface critique, use ryugi:interface-craft to inform choices; it adds no approval gate. Pure documentation, precise cosmetic edits and non-UI visualizations do not require it.

Load the project's design system (tokens, components, type) before the first
frame; if it has none, say which type, scale and palette you are using. Use
real copy and data, never lorem ipsum. An `html` page shows both themes
when the product has them, and the states the decision touches.

For preview icons, read [icons.md](./icons.md). When implementing the
approved design, map its actions to the app's existing business icons;
the preview glyphs are visual references.

## Pick the artifact

Each artifact is `<project>/.ryugi/artifacts/<type>/<id>/`. The id is
lowercase letters, digits and hyphens, named after the topic
(`arrow-tuner`, `header-nav`).

- Same topic: keep the same artifact and change it in place.
- New topic: a new id, and so a new link.
- Your human partner can override either.

## Start the server and get the link

Paths below are relative to this skill's directory: resolve `app/` to its
absolute path before running them. Every artifacts command uses the launcher.

```bash
node app/ryugi.cjs start --background --project-dir /path/to/project --artifact html/arrow-tuner
# Server: RUNNING
# Project: /path/to/project
# Artifact: html/arrow-tuner
# Open: https://ryugi.innei.dev/a/…
# Local: http://localhost:27319/html/…
# Cloud: live_link_reserved
```

- Give them the `Open` URL exactly as printed. `Cloud: live_link_reserved` is a
  live link reservation, not a completed publication; `local_only` is a local link.
  A separate `Local` URL is the fallback. Keep the full URL, including `?key=`.
- Follow printed warnings and actions for quota, sign-in or upgrades.
- Run `start` before the first file of a new artifact, so the page is open while
  you write. Run it again only right before sharing a link, for that artifact.
  `Server: RUNNING · reused` means it reused the running server and its port.
- One server serves all projects and remains running between sessions. Each run
  registers your project.
- The browser opens once the first artifact is ready enough to show. Use
  `--no-open` for headless use and still share the `Open` URL.
- `node app/ryugi.cjs stop` stops the server for every project; files stay.

**Launching by harness.** Use `--background` for a completed startup result in
Claude Code, Codex and ordinary shells. A foreground server uses `--foreground`
with the harness's background-shell mechanism; wait for `Server: RUNNING` and
`Open` before sharing the link.

**Remote or containerized setups:** use `--host 0.0.0.0 --url-host HOST` with
an address the human partner's browser can reach. Non-loopback local links
require the full printed key-bearing URL.

## Share a link

Publish when they want a link that works outside this machine. The server must
be running.

```bash
node app/ryugi.cjs publish --project-dir /path/to/project --artifact html/arrow-tuner --public
# Publish: PUBLISHED · html/arrow-tuner
# ID: …
# URL: https://ryugi.innei.dev/a/…
# Visibility: public (requested)
```

- First publication: use `--public` for someone else to open it; use `--private`
  for only the signed-in owner.
- To update the same publication, omit both visibility flags. Explicit flags
  change access only when your human partner requests that change.
- Share the printed `URL`. Publishing again replaces what the same link shows.
- Publishing also publishes what the artifact references, following references
  of references: everything never published goes out at the same visibility,
  and everything already published but changed here is updated. `References`
  lists each one with its state. A private one stays private and visitors see
  a locked label; its `Next` line is the command that makes it public, for
  your human partner to decide. `--no-refs` publishes only this artifact.
- Exit code 2 with `E_LOGIN_REQUIRED`: give them the printed login link, wait for
  sign-in, then retry. `E_PLAN_LIMIT` gives the reason and an upgrade link.
- Exit code 1: fix the reported cause. Exit code 5: inspect the retained URL and
  per-target effects before retrying a partial publication.
- `--unpublish` deletes the Cloud copy, `--list` shows a bounded account page,
  and `--delete <cloud-id>` removes the named copy.

## Auto-publish

When your human partner is signed in and auto-publish is on, every artifact
changed during your turn is published as a private copy when the turn ends
(Claude Code only; elsewhere, publish when asked). `config` prints
whether it is on.

- Do not run `publish` to keep a private copy current; the turn end does it.
- They want to look from their phone or another machine: give them
  the `Open` URL from `start`. It is live while this computer is on, and shows
  the last published copy when it is off. Or ryugi.innei.dev, which lists
  every copy once they sign in there.
- Someone else will open it: `--public`, as in Share a link.
- An unpublished artifact stays out of auto-publish until it is published by
  hand.
- When asked to put the auto-publish question to them, ask once and run
  `config --auto-publish on` or `off` with their answer. Their project-only
  choice: add `--project`.

## Directory

```
<project>/.ryugi/artifacts/
  artboard/<id>/       canvas.json + pages/ (you write); comments.json (server only)
  document/<id>/       doc.xml + assets/ (you write); comments.json (server only)
  html/<id>/           index.html + its files        (you write)
  whiteboard/<id>/     scene.excalidraw, pages.json + pages/ (you and the server); comments.json (server only)
  verify/<id>/         report.xml + evidence/ (you write); comments.json (server only)
  .state/              the server writes; never edit
```

- Keep each artifact self-contained: everything it uses lives inside its
  own directory and is referenced relatively. Copy screenshots in; never
  point at absolute paths.
- `.state/` keeps itself out of git. By default `.ryugi/.gitignore` keeps
  only documents in git; changing that is your human partner's call: leave
  `.gitignore` alone.

## After every change

1. Write the files with your file-writing tool.
2. Run `check` after your last write. It waits until the server has checked
   that write, then reports warnings, pending work and browser evidence; no
   sleep or `checkedAt` comparison is needed.

   ```bash
   node app/ryugi.cjs check --project-dir /path/to/project --artifact artboard/settings-nav
   # Check: INCOMPLETE · artboard/settings-nav
   # Browser: not run
   # Pending: browser_not_run
   ```

   Fix every warning. For `html` this includes `runtime: …` lines: errors
   the page threw in their browser. They only count once the new version
   has loaded there: while a `Browser: not run` or `Browser: unknown` line
   shows, an empty list means "not run yet", not "no errors".

   A `W_MODULES` line asks you to tag the artifact with the business module
   it serves: read `modules.md` and do what the line says before you report.
   No such line, nothing to do.

3. Tell them what changed and give the link. Questions, choice groups and verify
   groups use their page controls; discussion can continue in the terminal.
   For a document, an `html` page or static boards, send that
   message as soon as `check` is clean; screenshots or browser checks of
   your own come after it, reported in the next message. Playable boards
   follow `artboard.md`.

When the conversation moves on, leave the artifact as it is; it's the
record of what was explored.
Files in this package (10)
  • SKILL.md 13 KB
  • artboard-prototype.md 9 KB
  • artboard.md 23 KB
  • document.md 17 KB
  • html.md 3 KB
  • icons.md 2 KB
  • modules.md 3 KB
  • ui.md 12 KB
  • verify.md 7 KB
  • whiteboard.md 11 KB

Versions

RepositoryScoreLicence
This page · innei/ryugi95MIT
innei/ryugi100MIT
yusixian/anjian100MIT
allenai/asta-plugins100Apache-2.0
yusixian/anjian95MIT
yusixian/anjian95MIT
innei/ryugi95MIT
innei/ryugi90MIT
innei/ryugi90MIT

Database snapshot: 13.11.2026 · package version 98e2dfd53340 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100claude-design-brief
    Generate paste-ready prompts for Claude Design (the artifact / design-canvas tool at claude.ai, NOT Claude Code) that are committed enough to skip its Q&A loop and start drawing on message one. Use when the user wants hi-fi mockups, an interactive prototype, multiple directions…
  • 100interface-craft
    Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.
  • 90explore-design-directions
    Develop and compare materially different UI/UX directions, choose the smallest decision-useful artifact, and present a recommendation for human selection. Use when a material design choice remains open; route explicit prototype, mockup, or design-lab work to prototype-design-directions.
  • 100stitchflow
    Turn briefs, mockups, and product context into Stitch UI screens, design systems, variants, prototypes, Tailwind-friendly HTML, and screenshots. Use when the user wants to explore a screen, edit an existing Stitch project, compare visual directions, build a multi-screen…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.