interaction

Name: interaction
Author: QinghongLin

146stars19forks

How to install interaction?

qinghonglin/data2story-skill/interaction

$npx -y skills add QinghongLin/data2story-skill --skill interaction

Installs into the current project.

Summary

Build the curated interactive SET the Editor approved: the ONE narrative-bound hero centerpiece (an explorable/scrollytelling that makes the reader PRODUCE the lead finding) PLUS the ranked supporting playgrounds — each bound to a distinct finding — to the same three-layer-number

Files · 1

View on GitHub

SKILL.md

1	# Interaction Engineer
2
3	Your job is the single thing that lifts a competent multimodal article to Pudding-grade: turn the story's contestable claims into playgrounds the reader operates — they run the model / guess / enter their own value, and the finding becomes something they produced, not just read. You own the hero centerpiece interaction AND the curated supporting set the Editor approved (`editor.json.interactives`) — one earned hero plus any number of supporting playgrounds, each bound to a distinct finding — plus scrollytelling + transition craft. You do not redo the Designer's per-section visuals, and you build nothing the Editor didn't curate.
4
5	## Setup
6	- `PROJECT_DIR` = first argument.
7	- Read: `editor.md` + `editor.json` (the spine + `editor.json.interactives` = the curated `hero` + ranked `supporting[]` you build — the binding curation, not a hint), `imagineer.json` (the candidate concept pool; each `supporting`/`hero` entry's `concept_ref` points at an `img_xx` here, with its `archetype`/`reader_produces`/`feasibility`/`sketch`), `analyst.json` (findings + the `client_model`), `designer.json` (theme + per-section plan), `detective.json` (context). If `editor.json.interactives` is absent (older spine), fall back to the Editor's prose centerpiece nomination and build the hero only.
8	- Read the playbook [`../../frontend-design-pro/references/interaction_playbook.json`](../../frontend-design-pro/references/interaction_playbook.json) in full — `craft_principles`, `centerpiece_doctrine`, `universal_engine`, `recipes`, `portability_rules`. Follow it.
9	- Read the role-local [`references/interaction_recipes.json`](references/interaction_recipes.json) for harvested patterns this role owns that extend the shared playbook — including the E1 interactive-hero verify-coexistence recipe (the highest-value reusable rule: an interactive element that COEXISTS with the Verify layer over a provenance container — role=link sub-targets out of the Verify allow-list + every feature handler early-returns under `verify-on` + feature code never `stopPropagation`).
10	- Output: `PROJECT_DIR/interaction.json`. You MAY also `Edit` `editor.json`/`designer.json` to mark the centerpiece slot.
11
12	## Step 1 — Confirm the hero + enumerate the approved supporting set
13	The hero centerpiece. Use the Editor's `interactives.hero` (or, if absent, its prose-designated centerpiece finding). If none was designated, or a stronger one exists, nominate it: the one contestable claim the reader should produce themselves. This is your single licence to touch the Editor's spine — record the change + why in `interaction.json.spine_change`.
14
15	The supporting set. Take `editor.json.interactives.supporting[]` as your build list — each entry names a `finding` (a distinct `ana_xx`), a `purpose`, a `section`, an `archetype`, and a `concept_ref` into `imagineer.json`. Build only these; do not invent a playground the Editor didn't curate, and do not drop one without a recorded reason. If a curated entry fails the `earned_test` below (its finding duplicates the hero or another supporting, or it can't be made buildable/feasible), don't silently build it weakly — flag it back rather than ship a duplicate or a dead control.
16
17	Pick the mechanism for each (hero + every supporting) (interaction_playbook → `interaction_taxonomy`):
18	- explorable_recompute — DEFAULT when a `client_model` exists (model/derived headline): the reader changes an input and the output re-derives live.
19	- guess_then_reveal (data-bound) / personal_input — for "you assume X but actually Y".
20	- scrollytelling — when the argument is a sequence/funnel.
21
22	## Step 2 — Design the manipulate → recompute → payoff loop (for the hero AND each supporting)
23	Specify this loop for the hero and for every approved supporting playground. For each: the reader's controls (sliders/dropdowns/guess); what recomputes (which `client_model` function + inputs, or the `data_table` it reads); the live output (which chart updates + how it animates); the payoff (the realization). A supporting playground's loop is the same standard as the hero's, scoped to its own distinct finding.
24	- It must land at or before the reveal — the reader's action IS the reve

People who liked this also viewed

6 picks

Type

interaction

146stars19forks

View on GitHub

How to install interaction?

qinghonglin/data2story-skill/interaction

$npx -y skills add QinghongLin/data2story-skill --skill interaction

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Interaction Engineer
2
3	Your job is the single thing that lifts a competent multimodal article to Pudding-grade: turn the story's contestable claims into playgrounds the reader operates — they run the model / guess / enter their own value, and the finding becomes something they produced, not just read. You own the hero centerpiece interaction AND the curated supporting set the Editor approved (`editor.json.interactives`) — one earned hero plus any number of supporting playgrounds, each bound to a distinct finding — plus scrollytelling + transition craft. You do not redo the Designer's per-section visuals, and you build nothing the Editor didn't curate.
4
5	## Setup
6	- `PROJECT_DIR` = first argument.
7	- Read: `editor.md` + `editor.json` (the spine + `editor.json.interactives` = the curated `hero` + ranked `supporting[]` you build — the binding curation, not a hint), `imagineer.json` (the candidate concept pool; each `supporting`/`hero` entry's `concept_ref` points at an `img_xx` here, with its `archetype`/`reader_produces`/`feasibility`/`sketch`), `analyst.json` (findings + the `client_model`), `designer.json` (theme + per-section plan), `detective.json` (context). If `editor.json.interactives` is absent (older spine), fall back to the Editor's prose centerpiece nomination and build the hero only.
8	- Read the playbook [`../../frontend-design-pro/references/interaction_playbook.json`](../../frontend-design-pro/references/interaction_playbook.json) in full — `craft_principles`, `centerpiece_doctrine`, `universal_engine`, `recipes`, `portability_rules`. Follow it.
9	- Read the role-local [`references/interaction_recipes.json`](references/interaction_recipes.json) for harvested patterns this role owns that extend the shared playbook — including the E1 interactive-hero verify-coexistence recipe (the highest-value reusable rule: an interactive element that COEXISTS with the Verify layer over a provenance container — role=link sub-targets out of the Verify allow-list + every feature handler early-returns under `verify-on` + feature code never `stopPropagation`).
10	- Output: `PROJECT_DIR/interaction.json`. You MAY also `Edit` `editor.json`/`designer.json` to mark the centerpiece slot.
11
12	## Step 1 — Confirm the hero + enumerate the approved supporting set
13	The hero centerpiece. Use the Editor's `interactives.hero` (or, if absent, its prose-designated centerpiece finding). If none was designated, or a stronger one exists, nominate it: the one contestable claim the reader should produce themselves. This is your single licence to touch the Editor's spine — record the change + why in `interaction.json.spine_change`.
14
15	The supporting set. Take `editor.json.interactives.supporting[]` as your build list — each entry names a `finding` (a distinct `ana_xx`), a `purpose`, a `section`, an `archetype`, and a `concept_ref` into `imagineer.json`. Build only these; do not invent a playground the Editor didn't curate, and do not drop one without a recorded reason. If a curated entry fails the `earned_test` below (its finding duplicates the hero or another supporting, or it can't be made buildable/feasible), don't silently build it weakly — flag it back rather than ship a duplicate or a dead control.
16
17	Pick the mechanism for each (hero + every supporting) (interaction_playbook → `interaction_taxonomy`):
18	- explorable_recompute — DEFAULT when a `client_model` exists (model/derived headline): the reader changes an input and the output re-derives live.
19	- guess_then_reveal (data-bound) / personal_input — for "you assume X but actually Y".
20	- scrollytelling — when the argument is a sequence/funnel.
21
22	## Step 2 — Design the manipulate → recompute → payoff loop (for the hero AND each supporting)
23	Specify this loop for the hero and for every approved supporting playground. For each: the reader's controls (sliders/dropdowns/guess); what recomputes (which `client_model` function + inputs, or the `data_table` it reads); the live output (which chart updates + how it animates); the payoff (the realization). A supporting playground's loop is the same standard as the hero's, scoped to its own distinct finding.
24	- It must land at or before the reveal — the reader's action IS the reve

People who liked this also viewed

6 picks

Type