preview
/preview
Tworzy interaktywny podgląd HTML propozycji, planu, briefu lub specyfikacji i zapisuje go w lokalnej bibliotece Preview Library, a na wyraźną prośbę publikuje go online.
- Autor
- hanamizuki ↗
- Repozytorium
- solopreneur ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 32
- Skrypty
- 27
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 27 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: assets/comment-overlay.js, assets/preview-shell.js, scripts/build-library.mjs, scripts/config-migrate.mjs, scripts/config-resolve.mjs, scripts/deploy-library.mjs, scripts/deploy-share.mjs, scripts/deploy.sh, scripts/preflight.sh, scripts/reserve-local-output.mjs, scripts/resolve-delivery.mjs, scripts/resolve-provenance.mjs, scripts/setup.mjs, scripts/vercel-protect.mjs, tests/build-library.test.mj
Co robi i kiedy
Tworzy interaktywny podgląd HTML propozycji, planu, briefu lub specyfikacji i zapisuje go w lokalnej bibliotece Preview Library, a na wyraźną prośbę publikuje go online.
Oryginalny opis (EN)
Create an interactive HTML preview of any proposal, plan, idea, doc, brief, or spec and land it in the browsable local Preview Library by default (opens under file:// with a catalog sidebar and in-page comments); an explicitly temporary ask produces one self-contained HTML on the Desktop instead, and only an explicit request for Vercel, online deployment, cross-device access, or external sharing publishes the private Vercel Library or an isolated Share deployment. Use WHENEVER the user wants something visualized, made into a webpage, made interactive, shared for human review, or asks for chart
Jak działa
- Delivery mode gate
- Outcome the user is looking for
- Library workflow (default)
- Vercel workflow (Claude Code)
- Ephemeral workflow
- Legacy / escape hatch
- The Library comment overlay (what the user sees)
- What not to do
- Files in this skill
Podgląd SKILL.md
---
name: preview
description: Create an interactive HTML preview of any proposal, plan, idea, doc, brief, or spec and land it in the browsable local Preview Library by default (opens under file:// with a catalog sidebar and in-page comments); an explicitly temporary ask produces one self-contained HTML on the Desktop instead, and only an explicit request for Vercel, online deployment, cross-device access, or external sharing publishes the private Vercel Library or an isolated Share deployment. Use WHENEVER the user wants something visualized, made into a webpage, made interactive, shared for human review, or asks for charts / diagrams / calculators they can click through. ALWAYS use this skill for - make a preview / give me a preview / turn this into a webpage / visualize this / make it interactive / do a review / share for review / make a calculator page / make me a chart / make me a diagram / render this as HTML / make this reviewable / build a quick page / interactive proposal. Preferred over a markdown wall of text for human review.
---
# preview
## Delivery mode gate
This is the first action. Decide the delivery mode **before** reading Preview
Library config, running Vercel preflight/setup, creating files, using the
network, or making any other state change:
- Choose `vercel` only when the user explicitly asks for **Vercel**, an
**online deployment**, **cross-device access**, or **external sharing**.
- Choose `ephemeral` only for explicitly temporary work — "quick look",
"看完就丟", "just drop it on my Desktop" — or when the user names the
output path themselves.
- Choose `library` for everything else. `library` is the default; a request
such as "give me a link" still means a clickable local `file://` link.
Misrouting is asymmetric — a real deliverable sent to a throwaway file is
lost after the look, while a throwaway in the Library is one extra catalog
row — so ambiguity always lands in the Library.
Run the side-effect-free resolver from this skill directory with no argument
for `library`, or with exactly one flag for the explicit intents above:
```bash
node scripts/resolve-delivery.mjs [--ephemeral | --vercel]
```
Follow only the workflow it prints. On a Codex host (`CODEX_THREAD_ID` set),
`--vercel` fails closed before any network or state change. Stop immediately,
repeat the resolver's Codex Phase 1 local-only limitation, and do not substitute
a local artifact for the explicitly requested deployment. Claude Code may
continue through the existing Vercel workflow. `library` and `ephemeral` are
pure local file operations, available on Claude Code and Codex alike.
Turn any proposal / plan / idea into interactive HTML and hand the user a link
they can open. Library delivery writes into the content root and returns a
`file://` link into the freshly rebuilt local library. Explicit remote delivery
publishes the existing private Library; an external one-off link uses Share
(same Vercel project, Preview environment only — never promotes Library
production).
## Outcome the user is looking for
A link they can open and try. Not a markdown wall and not a screenshot.
Library delivery returns an absolute `file://` Markdown link to the item's
built page (catalog sidebar included). Ephemeral delivery returns an
absolute-path link to one standalone file. Explicit Vercel delivery returns
the existing Library or Share URL.
## Library workflow (default)
This workflow is available on Claude Code and Codex and is the default.
Deep reference (schema, setup, deploy internals): `../../shared/config.md`, relative to this skill inside an installed package (canonical source: `src/solopreneur/shared/config.md`).
### 1. Resolve Library config
Config is **path-scoped**, not git-remote-scoped. From the content path (or cwd when creating new work), walk up for the nearest **`.solopreneur.json`** that contains a `preview` block. Full resolution order and rules: `config-resolve.mjs` / `shared/config.md`.
```bash
# Inspect what the tools will use (anchor at the content path or cwd)
node scripts/config-resolve.mjs --from "$CONTENT_OR_CWD" # see script --help for flags
```
- Relative `root` is resolved against the **config file's directory**, not git root.
- Nested `.solopreneur.json` fully replaces a parent `preview` block (no deep merge).
- **Never hardcode** project names like personal fleet projects in this skill. Examples use placeholders only (`my-private-previews`).
**No v2 config resolves** (mode `none` or `legacy`): library mode is
unavailable here — say so in one line and deliver through the Ephemeral
workflow instead. Creating a new content root stays an explicit setup action
(`setup.mjs`, Vercel-oriented — **do not invent projects** or silently create
roots). Legacy `solopreneur.json` cascades still work for the escape hatch;
prefer migrating with `config-migrate.mjs` when the user is ready, and never
silently rewrite their legacy file.
### 2. Decide content + create / update item
**Self-assess ambiguity** before writing: only ask which deliverable if ≥2 separable topics, bare "preview" after a wide discussion, or multiple candidate artifacts. Otherwise state what you are previewing in one line and proceed.
#### Layout (v2)
```text
<root>/ # preview.root from resolved config
├── active/<id>/
│ ├── index.html
│ ├── preview.json
│ └── …assets (relative only)
├── archive/<id>/
│ └── …
└── library/ # generated local library (gitignored, never edited)
```
- **New work** → `active/<id>/` with `index.html` + `preview.json`.
- **Same work continues** → **same `id`**, same directory. When content or display metadata actually changes: `revision` += 1, refresh `updatedAt` and `provenance.lastUpdatedBy`. Unchanged re-publish and Share do **not** bump revision.
- `id`: lowercase slug `[a-z0-9-]+`, unique across all included collections.
- Collection is the **directory** (`active` vs `archive`); do not duplicate status in metadata.
#### Update routing / duplicate guard
Prefer, in order: preview id from URL / Share or archive request → caller-given id → `sourceRef` in metadata. Title similarity alone never auto-merges. Same id or same `sourceRef` → treat as update candidate. Fork only when the user says so.
#### `preview.json` (required fields)
Write a sidecar in the Library source tree only — **never deploy raw `preview.json`**; the builder projects an allowlist into `directory.json`:
```json
{
"schemaVersion": 1,
"id": "2026-07-25-short-slug",
"title": "Human title",
"createdAt": "2026-07-25T10:00:00+08:00",
"updatedAt": "2026-07-25T12:00:00+08:00",
"revision": 1,
"entry": "index.html",
"provenance": {
"createdBy": { "agent": "Builder Claude", "platform": "claude", "sessionTitle": "optional" },
"lastUpdatedBy": { "agent": "Builder Claude", "platform": "claude", "sessionTitle": "optional" }
}
}
```
- Required: `id`, `title`, `createdAt`, `updatedAt`, `revision`, and provenance parties' `agent` + `platform`.
- `sessionTitle` only when known — **never invent**.
- Optional: `project` (label only), `sourceRef` (workspace-relative stable ref, not absolute paths), `tags`.
- `entry` v1 must be `index.html`.
- Schema: `scripts/preview-schema.json`.
### 3. Write HTML
Start from `assets/template.html` (placeholders `{{TITLE}}` / `{{DATE}}` / `{{LEAD_PARAGRAPH}}` / `{{AUTHOR_OR_CONTEXT}}`).
**The builds inject** shared `comment-overlay.js` and `preview-shell.js` — the local library build and the Vercel publish alike. You may still reference `./comment-overlay.js` in the template for raw-source review; the builder rewrites it to the shared asset. Prefer not treating per-item overlay copies as the durable happy path.
**Contract (v1 static):** single `index.html`, relative assets only. No root-relative `/assets/...`, no SPA history fallback, no entry outside the item dir. Read `references/libs.md` before Alpine / Chart.js / Mermaid.
**Form follows content** (calculator, doc, charts, etc.) — same guidance as before.
**Full-bleed slides:** wrap in `<main class="doc">`, set `body.cmt-full-bleed` when needed (see template comments).
### 4. Build the local library
After content is ready (and preferably committed when the content root is git-backed):
```bash
node scripts/build-library.mjs --local --from "$PATH_UNDER_ROOT"
# machine-readable:
node scripts/build-library.mjs --local --json --from "$PATH_UNDER_ROOT"
```
- Rebuilds the whole catalog in a temporary tree and swaps it into
`<root>/library/` — generated output, never edited, never committed. A
failed build leaves the previous library untouched, and re-running is the
recovery. Concurrent builds of one root are serialized by a lock; if a
build was hard-killed, the next one refuses to start and names the stale
lock file to delete.
- First run on a root appends `/library/` + `/library.*` to the content root's
`.gitignore` and reports it — commit those lines with the content. The glob
covers the build's swap siblings (`library.tmp`, `library.bak`,
`library.lock`); untracked build output would otherwise dirty the root and
trip the deploy fetch-guard.
- The built pages render under `file://` with the full Library UX: catalog
sidebar, provenance footer, comment overlay. Comments persist per item in
that browser's `localStorage` (this machine only — export markdown if they
matter elsewhere).
- Return a clickable Markdown link to the item's built page:
`[Open preview](file:///…/<root>/library/p/<id>/index.html)` — and mention
the library home `<root>/library/index.html` when useful. Run `open` only
when the user explicitly asks.
- **Active-length hint:** if Active has **≥ 15** items (or many look clearly
stale), mention once that the user can open the sidebar **Manage mode**,
multi-select, and copy archive instructions — **never block** the build.
### 5. Archive / restore (from Manage mode)
Sidebar **Manage mode** copies a structured block (agent contract):
```text
## library archive request
library: <label>
exported: <ISO timestamp>
archive(active → archive):
- <id> — <title>
restore(archive → active):
- <id> — <title>
(給 agent:對每個 id 做 mv <root>/<from>/<id> <root>/<to>/<id>,全部完成後重新發布 library。)
```
When the user pastes this:
1. For each archive id: `mv <root>/active/<id> <root>/archive/<id>` (keep id).
2. For each restore id: reverse.
3. **One** rebuild after all moves: `build-library.mjs --local`, plus one
`deploy-library.mjs` republish when the Library is also published on Vercel.
4. Do **not** delete unless the user confirms item-by-item (delete is out of the Manage UI).
### 6. Feedback loop (comments + visible diffs)
Keep the existing comment + revision workflow:
1. User highlights, comments, exports markdown (`## comments on: …`).
2. On each revision round: flatten prior `<del>` / `<ins>`, apply new changes as visible diff, refresh a top `revision-log` callout, rebuild the local library (same id, revision +1 when content changed); republish Vercel only when that is where the user reviews.
3. Comments are per-preview-id (`preview_comments_v3:<id>`) in the browser that made them. The local library and a Vercel deployment are **different origins** — comments do not travel between them, or across Share origins. Export if they matter.
See "The comment overlay" below for UX detail.
## Vercel workflow (Claude Code)
This is the existing Library v2 publish path. Enter it only after the delivery
resolver prints `vercel`. Content rules are the Library workflow's steps 1–3 —
the same content root, items, and HTML feed both renderings. Legacy
three-bucket / `deploy.sh` is an escape hatch only (see below).
### 1. Preflight FIRST
**Always run `bash scripts/preflight.sh` before drafting HTML.** It checks Vercel CLI + auth.
- **Pass:** one short line (`vercel CLI ready, proceeding…`) and continue.
- **Fail:** do not dump stderr and stop. Ask whether to set up Vercel now (`npm i -g vercel` / `vercel login`), view HTML locally only, or cancel. Re-run preflight until pass or the user chooses local-only / cancel.
**No v2 config found:** run first-run setup — **do not invent projects**.
```bash
node scripts/setup.mjs
# optional: --project my-private-previews --team <teamId>
```
Setup proposes **one private target**, creates dirs only after confirm, and fail-closes if protection cannot be verified. It never auto-creates three Hana buckets.
### 2. Publish the Library
```bash
node scripts/deploy-library.mjs --from "$PATH_UNDER_ROOT"
# machine-readable:
node scripts/deploy-library.mjs --json --from "$PATH_UNDER_ROOT"
```
- Full snapshot of included collections → stable protected entry.
- Report **stable URL** + **immutable URL** + resolved project from the tool output.
- **Do not** use `deploy.sh --bucket keep` for Library content (pollutes Library production history).
- Empty library publish is refused (would wipe the catalog).
- Private targets fail closed on protection (anonymous entry must not be 200).
### 3. Share (external, optional)
The page **Share…** control only builds a copyable JSON request (no token, no deploy). Example:
```json
{
"schemaVersion": 1,
"kind": "preview-share-request",
"previewId": "<id>",
"revision": 4,
"contentHash": "sha256:<hash>",
"url": "<current library item URL>",
"access": "project-members"
}
```
`access`: `project-members` (default) or `anyone-with-link`.
When the user pastes a request (or asks to share an id):
```bash
# request on stdin, or --request <file>
node scripts/deploy-share.mjs --from "$PATH_UNDER_ROOT" --request - <<'EOF'
{ ...share request JSON... }
EOF
```
- Validates id / revision / contentHash against the Library item — **mismatch fail-closed** (no silent wrong version).
- Same Vercel project; **never** `--prod` / promote; Library production unchanged.
- Artifact is root `/` for that item only (no catalog / other `/p/` / raw `preview.json`).
- List / revoke: `deploy-share.mjs --list` / `--revoke` (see script usage; shareable-link secret may be required to revoke).
## Ephemeral workflow
Enter only when the resolver prints `ephemeral` — explicitly temporary work or
a user-named output path — or as the stated fallback when no v2 config
resolves in library mode. The artifact joins no catalog and carries no shell
or overlay chrome.
1. **Choose one output file.** A user-specified path wins. For temporary work
with no path, use `~/Desktop/<safe-slug>.html`, where the slug is lowercase
ASCII `[a-z0-9-]`, repeated hyphens are collapsed, and an empty result falls
back to `preview`. Resolve the final path to an absolute path.
2. **Refuse silent overwrite.** Unless the user explicitly asked to update or
replace that exact file, atomically reserve the target after the delivery
mode is decided:
```bash
node scripts/reserve-local-output.mjs "$ABSOLUTE_TARGET"
```
Use only the absolute path it prints. An existing target is preserved and
receives a collision-free sibling such as `<safe-slug>-2.html`.
3. **Write exactly one self-contained HTML file.** Write into the reserved file
(or the explicitly approved replacement). Put all CSS in `<style>` and
all necessary JavaScript in inline `<script>` blocks. Use inline SVG or data
URIs for required images. The file must render directly under `file://`
without a server, build step, external stylesheet/script/module, CDN,
runtime fetch, or relative asset. Omit JavaScript when HTML/CSS is enough.
`assets/template.html` is a Library-oriented visual reference only: its CDN
and `comment-overlay.js` references must not appear in an ephemeral artifact.
4. **Keep ephemeral delivery isolated.** Create no `preview.json`, write no
`.solopreneur.json` / `solopreneur.json`, run no `setup.mjs`,
`preflight.sh`, or deploy script, create no `.vercel`, and make no
Vercel/network calls. Config reading is not part of this workflow either —
the no-config Library fallback has already done its one read by the time it
lands here. The output HTML is the only delivery artifact.
5. **Verify and hand off.** Confirm the file exists, contains its required
inline CSS/JS, and has no runtime asset dependency. Return a clickable
absolute-path Markdown link such as `[Open preview](/absolute/path/file.html)`.
Run `open` only when the user explicitly asks to open it.
Wanting to keep an ephemeral page later is not a feature — move it into
`active/<id>/`, add a `preview.json`, rebuild the library. Ordinary file
operations, on request.
---
## Legacy / escape hatch
Use only when there is **no** v2 Library config, or for living-spec / slides / explicit migration rollback.
### `deploy.sh` (arbitrary directory)
```bash
scripts/deploy.sh <path-to-dir>
# optional: PREVIEW_PROJECT=... or --bucket default|keep|public
```
Prints one URL to stdout. Buckets (`default` / `keep` / `public`) live in legacy `solopreneur.json`. **Not** the default for new `/preview` work when a Library config resolves.
- **default (scratch)** — disposable URLs.
- **keep** — long-lived per-page project; do not use against a Library production project.
- **public** — external readers; re-read for secrets before deploy; skips SSO.
Path probing + `solopreneur.json` helpers for legacy flat `docs/preview/<date>-<slug>/` dirs remain valid for this escape hatch only. Prefer `active/<id>/` whenever v2 applies.
---
## The Library comment overlay (what the user sees)
Margin-style annotations (Google Docs / Medium-like), identical in the local
library and on Vercel:
- Highlight → `+ comment` → note → yellow marker + gutter card; stored in `localStorage` for the review session.
- Desktop: margin cards; Mobile: bottom sheet + list FAB.
- `export comments` → markdown with quotes + context.
- On pages with `<del>` / `<ins>`: `Clean` / `Show edits` toggle (defaults to showing edits).
- Detached comments (anchor text gone) still listed, not silently dropped.
- Write failures (quota / blocked storage) must surface visibly with export escape hatch.
Agent revision rules:
1. Flatten previous round (`delete` old `<del>`, unwrap old `<ins>`).
2. Apply this round as `<del>` / `<ins>` only — never silent replace.
3. Rewrite the top `revision-log` callout for this round only.
4. Rebuild the local library; redeploy Vercel only if still reviewing there (or legacy deploy only if still on escape hatch).
---
## What not to do
- **Don't** enter the Vercel workflow without explicit Vercel / online /
cross-device / external-share intent; "give me a link" remains local.
- **Don't** route ambiguous work to ephemeral — explicit temporary intent or
a user-named path only.
- **Don't** create `preview.json`, write config, run setup/preflight/deploy,
or use the network in ephemeral mode.
- **Don't** commit or hand-edit `<root>/library/` — generated output; commit
items + `preview.json` (+ the `.gitignore` line when first added) instead.
- **Don't** put CDN or relative runtime dependencies in an ephemeral artifact.
- **Don't** silently overwrite an ephemeral HTML file or run `open` without an
explicit request.
- **Don't** teach three-bucket promote as the default when v2 config exists.
- **Don't** invent Hana project names or absolute machine paths in config examples.
- **Don't** bump revision on no-op republish or Share-only deploys.
- **Don't** share a hash-mismatched revision (fail closed).
- **Don't** delete Library items from the Manage UI path without explicit per-item confirm.
- **Don't** write multi-file React apps for this skill — single `index.html` + assets.
- **Don't** let diff markup accumulate across rounds.
- **Don't** put secrets in preview HTML or comments (the Library is private but not a vault; the local library is plain files on disk).
---
## Files in this skill
| Path | Role |
|------|------|
| `scripts/resolve-delivery.mjs` | Side-effect-free library / ephemeral / Vercel gate |
| `scripts/reserve-local-output.mjs` | Atomic no-overwrite ephemeral path reservation |
| `scripts/preflight.sh` | Vercel CLI + auth |
| `scripts/config-resolve.mjs` | Path-scoped v2 + legacy resolve |
| `scripts/config-migrate.mjs` | Legacy → v2 proposal + write |
| `scripts/setup.mjs` | First-run private target |
| `scripts/build-library.mjs` | Scan collections → staging; `--local` swaps `<root>/library/` |
| `scripts/deploy-library.mjs` | Staged Library publish |
| `scripts/deploy-share.mjs` | Single-item Share Preview |
| `scripts/deploy.sh` | Legacy arbitrary-dir deploy |
| `scripts/preview-schema.json` | `preview.json` schema |
| `scripts/resolve-provenance.mjs` | Provenance display shape |
| `assets/template.html` | HTML starter |
| `assets/comment-overlay.js` | Comments + diff toggle |
| `assets/preview-shell.js` | Sidebar, Manage, Share, footer |
| `assets/library-index.html` | Library home template |
| `references/libs.md` | Alpine / Chart.js / Mermaid recipes |
Pliki w paczce (32)
- SKILL.md 21 KB
- assets/comment-overlay.js 70 KB
- assets/library-index.html 10 KB
- assets/preview-shell.js 49 KB
- assets/template.html 18 KB
- references/libs.md 6 KB
- scripts/build-library.mjs 68 KB
- scripts/config-migrate.mjs 48 KB
- scripts/config-resolve.mjs 26 KB
- scripts/deploy-library.mjs 54 KB
- scripts/deploy-share.mjs 65 KB
- scripts/deploy.sh 12 KB
- scripts/preflight.sh 2 KB
- scripts/preview-schema.json 4 KB
- scripts/reserve-local-output.mjs 1 KB
- scripts/resolve-delivery.mjs 2 KB
- scripts/resolve-provenance.mjs 8 KB
- scripts/setup.mjs 38 KB
- scripts/vercel-protect.mjs 20 KB
- tests/build-library.test.mjs 61 KB
- tests/comment-overlay.test.mjs 5 KB
- tests/config-migrate.test.mjs 54 KB
- tests/config-resolve.test.mjs 28 KB
- tests/delivery-mode.test.mjs 5 KB
- tests/deploy-library.test.mjs 57 KB
- tests/deploy-share.test.mjs 64 KB
- tests/preview-shell-boot.test.mjs 2 KB
- tests/preview-shell-local-boot.test.mjs 3 KB
- tests/preview-shell.test.mjs 12 KB
- tests/resolve-provenance.test.mjs 11 KB
- tests/setup.test.mjs 30 KB
- tests/vercel-protect.test.mjs 20 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · hanamizuki/solopreneur | 100 | MIT |
| windmill-labs/windmill | 100 | Apache-2.0 |
| lodev09/react-native-true-sheet | 100 | MIT |
| jisuzzzz/haechi | 100 | MIT |
| ialameh/sift-coder | 100 | MIT |
| jongwony/epistemic-protocols | 95 | MIT |
| SayandipBagchi/release-notes-plugin | 90 | MIT |
Identyczna treść występuje jeszcze w 2 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 3b0b75104d89 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100vercel-deploy-preview
Tworzy i zarządza wdrożeniami preview Vercel dla gałęzi i pull requestów, w tym udostępnianiem adresów podglądu. - 100vercel-deploy-preview
Tworzy wdrożenie preview Vercel dla pull requesta, do testowania zmian przed produkcją lub udostępniania adresu podglądu interesariuszom. - 100pinwall
Publikuje strony HTML, witryny i dokumenty Markdown na serwerze przeglądów Pinwall, zwraca link i obsługuje komentarze recenzentów. - 100vercel-deploy
Wdraża aplikacje i strony na Vercel na prośbę o deploy, link do wdrożenia lub wdrożenie preview. - 100vercel-deploy
Wdraża aplikacje i strony na Vercel na prośbę o deploy, link do wdrożenia lub wdrożenie preview. - 100single-html-document
Tworzy jednoplikowe dokumenty HTML z treścią, CSS i JavaScriptem w środku, np. interaktywny raport lub wyjaśnienie.