@jini-ai/agent-plugins 0.6.16 → 0.6.19

package/slide-design/skills/slide-design/references/storyline.md

@@ -0,0 +1,118 @@
+# Storyline
+
+Decide what the deck says before deciding how it looks.
+
+## The deck message
+
+Resolve the audience's intended outcome before outlining. Then write one sentence a listener
+could repeat to a colleague afterwards: "<what is true> so <what we should do>". Stuck? Ask the
+user what the audience should decide or do next, and build the sentence from that answer.
+Every slide either supports this sentence or leaves the deck.
+
+## Structure by deck type
+
+| Type | Goal | Structure | Typical size |
+|---|---|---|---|
+| Investor pitch | Win belief and an investment | Problem → why now → solution → proof (demo, traction) → market → business model → team → ask | 10–15 slides |
+| Sales pitch | Win a deal | Their problem → cost of doing nothing → solution → proof (demo, customer results) → plan and price → ask. Market, model and team only if the buyer asks | 6–12 slides |
+| Talk | Change how people think | Hook → one big idea → 3 parts, each with a story or example → recap → call to action | 1 slide per 1–2 min, image-led |
+| Teaching | People can do something new | Goals → what they know already → concept → worked example → practice or check → recap | One concept per slide |
+| Update | Show status and get help | Status in one line → what changed → metrics vs. plan → risks → asks and next steps | 5–10 slides |
+| Report | Share findings people read alone | Summary → findings ranked by importance, each with evidence → implications → method and appendix | Denser; read, not presented |
+| Decision | Get a yes on a choice | Summary (recommendation, reasons, ask) → options compared → evidence for the choice → risks and mitigations → plan and cost → ask | 1 summary + 5–12 body + appendix |
+
+Mixed cases: pick the type that matches the goal, then borrow sections. A pitch to a committee is
+a decision deck with pitch proof.
+
+## Answer first
+
+Use for update, report and decision decks, and any busy audience.
+
+1. Put the message on top.
+2. Ask "why?" or "how?" of it. The answers are 2–5 supporting points.
+3. Check the points:
+   - No overlaps: each fact belongs under exactly one point.
+   - No gaps: together the points are enough to carry the message.
+   - Same kind: all reasons, all steps, or all parts. Don't mix.
+4. Repeat for each point until each leaf fits one slide.
+5. Order the points on purpose: by importance, by time, or by the parts of a whole. Say which.
+
+Talks and teaching decks may build up to the answer instead. Still say early where you're going.
+
+## The opening
+
+Four moves, one or two slides or the speaker's first minute:
+
+- **Context** — something the audience already accepts.
+- **Tension** — what changed, broke, or is at stake.
+- **Question** — the question that tension raises.
+- **Answer** — the deck message.
+
+For executives or skeptics, lead with the answer and give the context after. For a story-led
+talk, open on the tension.
+
+## Titles
+
+- The title is the takeaway: the claim the slide's evidence supports. Test it: could someone in
+  the room disagree? A label like "Churn" gives nothing to disagree with.
+  - Weak: "Churn". Better: "Churn fell by a third after the onboarding rollout".
+- Aim for 8–15 words, at most 2 lines. Be specific: numbers, names, dates.
+- Topic words ("Background", "Results") are labels, not titles. If you need one, set it as a
+  small kicker above the title.
+- **Title chain test:** read only the titles, in order. They should read like a short memo. If a
+  title doesn't follow from the one before, reorder, merge, or add a bridge slide.
+- Allowed exceptions (review honours them too): an image-only talk slide whose point the speaker
+  says aloud; section dividers; questions as titles in teaching decks.
+
+## Summary slide
+
+Decision and report decks get one right after the title slide:
+
+- what we found or recommend, in one sentence;
+- 3–4 findings or reasons, one sentence each, and what they imply;
+- the ask (a decision, budget, people, a date) when the deck seeks action. Decision decks always
+  do; a report that only informs ends on implications.
+
+A reader who stops here should still get the point. Talks and teaching decks use an agenda or
+"what you'll learn" slide instead.
+
+## Outline first
+
+Before any design, write the titles-only outline:
+
+```
+1. Title — <deck title>, <presenter>, <date>
+2. <takeaway title> — evidence: <what the slide will show>
+3. ...
+N. Closing — <message restated>, <ask>
+```
+
+Check it: is the message clear, does the chain read, is there one point per slide, does the count
+fit the time? Changing an outline takes minutes; changing finished slides takes hours.
+
+## Agenda and section dividers
+
+Only for decks over about 15 slides or 20 minutes. The agenda lists the 3–5 top-level points in
+the same words the dividers use.
+
+## Closing slide
+
+Don't end on "Questions?" or "Thank you" alone. The last slide carries:
+
+- the message, restated in one line;
+- the ask or next step: who does what, by when;
+- where to reach you or find the material.
+
+Leave it on screen during questions. The appendix comes after it.
+
+## Speaker notes
+
+- Every presented slide gets notes: 40–120 words, about 30–60 seconds spoken.
+- First line: the slide's point in one sentence.
+- Then where to look first and what it means, in spoken sentences, not bullets.
+- End with a one-line bridge to the next slide.
+- Put caveats and data definitions here when they don't fit on the slide.
+- Read-alone decks may skip notes, but then each slide must stand on its own: fully labelled
+  charts with sources, and the word budget in `layout-and-style.md`.
+- A deck that is both presented and read: build the read version, then present it with builds or
+  a trimmed copy.

package/stripe/plugin.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "stripe",
+  "version": "0.1.0",
+  "description": "Connects the site to Stripe through the payments-stripe provider in @jini-ai/provider-plugins. Installation alone does not enable or configure the provider.",
+  "author": "Jini",
+  "license": "Apache-2.0",
+  "extensions": {
+    "tovu": {
+      "id": "jini/stripe",
+      "displayName": "Stripe",
+      "providerPlugin": "payments-stripe",
+      "provides": [
+        "payments"
+      ]
+    }
+  },
+  "keywords": [
+    "stripe",
+    "payments-stripe"
+  ]
+}

package/supabase/mcp.json

@@ -0,0 +1,26 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
+  "mcpServers": {
+    "supabase": {
+      "type": "streamable-http",
+      "url": "https://mcp.supabase.com/mcp?features=account,database,development,docs,debugging",
+      "tovuAuthMode": "oauth",
+      "tovuTokenAuth": {
+        "helpUrl": "https://supabase.com/dashboard/account/tokens",
+        "probeUrl": "https://api.supabase.com/v1/projects",
+        "importFromEnv": "TOVU_SUPABASE_MCP_ACCESS_TOKEN",
+        "retiredEnv": ["TOVU_SUPABASE_MCP_ENABLED", "TOVU_SUPABASE_MCP_PROJECT_REF", "TOVU_SUPABASE_MCP_ALLOWED_TOOLS",
+                       "TOVU_SUPABASE_MCP_FEATURES", "TOVU_SUPABASE_MCP_PACKAGE", "TOVU_SUPABASE_MCP_CONNECT_TIMEOUT_MS",
+                       "TOVU_SUPABASE_MCP_CALL_TIMEOUT_MS", "TOVU_SUPABASE_MCP_MAX_RESULT_BYTES"]
+      },
+      "tovuDefaultTools": {
+        "allow": ["list_organizations", "get_organization", "list_projects", "get_project", "get_cost", "confirm_cost",
+                  "create_project", "pause_project", "restore_project", "list_tables", "list_extensions", "list_migrations",
+                  "apply_migration", "execute_sql", "get_advisors", "query_logs", "get_project_url", "get_publishable_keys",
+                  "generate_typescript_types", "search_docs"],
+        "write": ["confirm_cost", "create_project", "pause_project", "restore_project"]
+      },
+      "tovuRenamedTools": { "get_logs": "query_logs" }
+    }
+  }
+}

package/supabase/plugin.json

@@ -0,0 +1,78 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "supabase",
+  "version": "1.1.0",
+  "description": "Gives this site a hosted database (Supabase) for sign-ups, forms and app data, set up from chat with no setup steps for the person. Use it whenever someone says they need a database, want to store data, or want sign-ups or form entries saved. Always start with agent_plugin_connect { pluginId: \"supabase\" }: it shows a sign-in card (the person signs in or signs up at Supabase themselves), turns the connection on, and returns once connected. Then follow the supabase skill: find or create the database, handle Supabase's free limit of two active databases, and speak in plain words only.",
+  "author": "Tovu",
+  "license": "Apache-2.0",
+  "extensions": {
+    "tovu": {
+      "maturity": "soon",
+      "summary": "Gives your site a database for sign-ups and form entries. You sign in to Supabase and the assistant sets up the rest.",
+      "id": "tovu/supabase",
+      "provides": [
+        "database:supabase"
+      ],
+      "credentialCards": [
+        {
+          "target": "supabase-sign-in",
+          "title": "Connect Supabase",
+          "label": "Supabase account",
+          "category": "general",
+          "intro": "Connect Supabase to set up and work with this site’s database.",
+          "usedFor": [
+            "Finds your accounts and databases",
+            "Reads the selected database",
+            "Sets up databases and applies database changes you approve"
+          ],
+          "keyHint": "Review the account and project access requested on the Supabase sign-in page.",
+          "saveKind": "oauth",
+          "saveTarget": "supabase",
+          "permissions": "Allows the connected tools to discover your organizations and projects and work with the selected database. Creating, pausing or restoring a project and running database changes require the applicable tool permissions.",
+          "baseUrl": "https://mcp.supabase.com"
+        },
+        {
+          "target": "supabase",
+          "title": "Connect Supabase with an access token",
+          "label": "Supabase account",
+          "category": "general",
+          "intro": "Use this fallback only when browser sign-in cannot start. The token connects the Supabase account, not a site mailer or a project’s public API.",
+          "usedFor": [
+            "Finds your accounts and databases",
+            "Reads the selected database",
+            "Sets up databases and applies database changes you approve"
+          ],
+          "keyHint": "Use a Management API personal access token, not an anon or service-role key. Discovery: Organizations, Projects (account-wide), Organization Settings and Project Settings → Read. Database tools: Database, Migrations, API Keys, Advisors and Logs → Read. Add Organization Projects → Read-write only to create a project, Project Settings → Read-write to pause/restore, and Migrations → Read-write to apply migrations. Tool write grants are still required separately.",
+          "saveKind": "agent-plugin-token",
+          "helpUrl": "https://supabase.com/dashboard/account/tokens",
+          "helpLabel": "Create a personal access token",
+          "baseUrl": "https://api.supabase.com"
+        }
+      ]
+    }
+  },
+  "keywords": [
+    "supabase",
+    "database",
+    "db",
+    "i-need-a-database",
+    "store-data",
+    "save-data",
+    "data",
+    "signups",
+    "sign-ups",
+    "forms",
+    "form-entries",
+    "backend",
+    "app-data",
+    "postgres",
+    "postgresql",
+    "sql",
+    "tables",
+    "connect",
+    "sign-in",
+    "login",
+    "setup",
+    "database:supabase"
+  ]
+}

package/supabase/skills/supabase/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: supabase
+description: Set up a hosted database (Supabase) for this site from chat. Start with agent_plugin_connect, then find or create the database, handle Supabase's free limit of two active databases (reuse, pause, or paid), and say everything in plain words. Small database changes (make a table, add or change rows) run from chat with execute_sql, after the person confirms each one.
+---
+
+# Supabase database
+
+## Connection card
+
+Choose the card yourself from its `usedFor` list. Reuse a saved key or working sign-in for that
+task. Never offer a replacement unless the person asks.
+
+`agent_plugin_connect {pluginId:"supabase"}` shows the plugin’s own **Connect Supabase** sign-in card, including what it connects and the permissions involved. Only if browser sign-in cannot start, open `credential_save {kind:"plugin-provider",target:"supabase"}` for the plugin’s access-token fallback. It links to personal access token creation, explains Management API permissions, probes the token and saves it on the MCP connection; it never saves a project anon or service-role key.
+
+The person wants somewhere to keep data (sign-ups, form entries, app data). Get them a working
+database with as few words and choices as possible. They should never need to learn a new idea.
+
+## Rules for everything you say
+
+Write every message in plain, short sentences. Lines quoted below as `> ...` are what the person
+reads; say them in your own words if needed, but keep them this simple.
+
+**Never say** any of these words or ideas to the person: token, access token, OAuth, MCP, plugin,
+scope, allowlist, read-only, region, org or organization id, project ref, API key, service role,
+tool names. Never show a key or password. Call the Supabase project "your database".
+
+Links: always markdown links to `https://` pages, one per message at most.
+
+Never loop. If a step fails twice, stop and use `references/failure-modes.md`.
+
+## Step 1. Connect (always first)
+
+Call `agent_plugin_connect { pluginId: "supabase" }` before any Supabase tool, every time, even if
+you think it is already connected (it returns at once when it is).
+
+It shows the person a card with a sign-in button. Before or with it, say:
+
+> Let's set up your database. It's free and takes about two minutes. You'll sign in to Supabase,
+> the database service this site uses. No account yet? Choose **Sign up** there (GitHub or email). If it
+> asks which team to use, pick any.
+
+The person signs up for their own Supabase account; you never make one for them and never ask for
+their email or password.
+
+- Result `{ status: "connected" }`: go to Step 2. (It also returns this at once when the person
+  added a Supabase key while creating the site; say nothing about a sign-in then.)
+- It fails with an error (sign-in could not start): see "Sign-in won't start" in
+  `references/failure-modes.md`.
+- Result `{ status: "waiting-for-sign-in" }`: see `references/failure-modes.md`.
+
+## Step 2. Find their account and databases
+
+1. Call `mcp__supabase__list_organizations`. Normally there is one; use it. If there are several,
+   ask with `assistant_ask_choice` using their names.
+2. Call `mcp__supabase__list_projects`. Keep the ones in that organization.
+3. If they already have databases, ask with `assistant_ask_choice`:
+   - **Make a new database** (first option, recommended)
+   - **Use "<name>"** for each existing one
+
+   If they pick an existing one, go to Step 5 (if its status is `INACTIVE` it is asleep: see
+   `references/failure-modes.md`).
+
+## Step 3. Check the free limit and the price
+
+Supabase's free plan allows **two active databases** per account. `mcp__supabase__get_cost` can't
+see the free limit (it says $0 even when the account is full), so count first:
+
+- From Step 2's list, count databases whose status is not `INACTIVE` (active or starting).
+- If the count is 2 or more and the cost below is $0, the account is at the free limit: skip
+  creating and go straight to **At the free limit** below.
+
+Call `mcp__supabase__get_cost { type: "project", organization_id }`.
+
+- $0: say nothing about money.
+- More than $0 (a paid account): ask with `assistant_ask_choice`:
+  - **Create it ($<amount>/<recurrence>)**, using the exact numbers returned
+  - **Cancel**
+
+  Only on **Create it**, call `mcp__supabase__confirm_cost` with the same `type`, `recurrence` and
+  `amount`, and keep the returned id for Step 4.
+
+## Step 4. Create the database
+
+Call `mcp__supabase__create_project` with:
+- `name`: short and lowercase, from the site's name or what they are building (never ask);
+- `organization_id` from Step 2;
+- `region`: nearest to the person, from the table below (default `us-east-1`);
+- `confirm_cost_id` from Step 3 when there was one.
+
+| Person is in | region |
+|---|---|
+| US East, Canada East, or unknown | `us-east-1` |
+| US West | `us-west-1` |
+| Canada | `ca-central-1` |
+| South America | `sa-east-1` |
+| UK, Ireland | `eu-west-2` |
+| Western / Central Europe | `eu-central-1` |
+| Nordics | `eu-north-1` |
+| India | `ap-south-1` |
+| Southeast Asia | `ap-southeast-1` |
+| Japan | `ap-northeast-1` |
+| Korea | `ap-northeast-2` |
+| Australia, New Zealand | `ap-southeast-2` |
+
+If it fails with an error containing
+"maximum limits for the number of active free plan projects", the account is at the free limit: go
+to **At the free limit**.
+
+Then say:
+
+> Creating your database... this usually takes 1-2 minutes.
+
+Call `mcp__supabase__get_project` to check its status, at most 10 times in one reply. Ready when the
+status is `ACTIVE_HEALTHY`. Still not ready after that:
+
+> Your database is still being made. Say "check" in a minute and I'll look again.
+
+## Step 5. Ready
+
+> Your database is ready ✓ [Open it in Supabase →](https://supabase.com/dashboard/project/<id>)
+
+(`<id>` is the project's `id` from Supabase; it goes only in the link, never in the text.)
+
+Then offer one useful next step, for example showing them where their data will appear.
+
+## Changing data or tables
+
+For a small change the person asks for (make a table, add a column, add, change or delete rows), use
+`mcp__supabase__execute_sql` on the database they chose, with one short SQL statement per call. Use
+`mcp__supabase__apply_migration` only if they ask for a tracked schema change.
+
+1. Say in one plain sentence what will change, and show the SQL in a code block:
+   > I'll make a table called "signups" with an id column. This is the SQL:
+2. Call the tool right away. Do NOT ask first with `assistant_ask_choice` or in words ("Shall I
+   run this?"): the host's own approval card is the confirmation, and asking twice is annoying. The
+   person sees the card with the exact SQL and **Allow** / **Allow for this chat** / **Cancel**;
+   nothing runs until they allow it. Keep to one change per call. A card marked as able to delete
+   data is expected for these tools.
+3. After it runs, check the result (for example `mcp__supabase__list_tables`) and say what changed
+   in plain words.
+
+If the result says they cancelled, say:
+
+> OK, I didn't change anything.
+
+Do not try the same change again unless they ask. If the card expired, say it timed out and ask if
+they still want it. Never delete a table or data they did not name. For a change that deletes data,
+say plainly what will be lost in step 1; the approval card is still the only question you ask.
+
+## At the free limit
+
+Ask with `assistant_ask_choice` (one option per active database for the first two):
+
+- **Use "<name>"**: continue at Step 5 with that database.
+- **Pause "<name>" to free a space**: call `mcp__supabase__pause_project` on it, say
+  > "<name>" is paused. Its data is kept, and you can wake it up later.
+  then go back to Step 4.
+- **Get a paid database**: say
+  > Supabase's free plan allows two active databases. To add another, upgrade your Supabase plan
+  > here, then say "done". [See plans and prices →](https://supabase.com/dashboard/org/<organization id>/billing)
+
+  On "done", go back to Step 3: `get_cost` now shows the price, so the person sees
+  **Create it ($<amount>/<recurrence>)** before anything is charged.
+
+This site never takes payment itself; upgrading happens on Supabase's own page.
+
+## When something goes wrong
+
+Use `references/failure-modes.md`: one plain sentence for each case, and what to do next.

package/supabase/skills/supabase/references/failure-modes.md

@@ -0,0 +1,101 @@
+# Supabase: when something goes wrong
+
+Each case: what you notice, what to tell the person (plain words, at most one link), and what to
+do. Never paste Supabase's raw error text. Never retry more than once on your own.
+
+## Sign-in not finished
+
+`agent_plugin_connect` returned `{ status: "waiting-for-sign-in" }` (nobody finished within a few
+minutes, which is normal during a new sign-up).
+
+> Still waiting for you to sign in to Supabase. Use the sign-in button above, then say "done".
+
+On "done" (or "I'm back"), call `agent_plugin_connect { pluginId: "supabase" }` once more. Never call
+it again on your own.
+
+## Sign-in won't start
+
+`agent_plugin_connect` failed with an error instead of showing the sign-in card. Say:
+
+> Sign-in isn't working right now, so let's use a key instead. [Make a key on Supabase →](https://supabase.com/dashboard/account/tokens)
+> Then paste it in the box below.
+
+Call `credential_save { kind: "plugin-provider", target: "supabase" }` once. It shows the box and waits. On
+`{ saved: true }` go to Step 2. On `reason: "invalid"`: "That key didn't work. Make a new one and try
+again." Never ask for the key in chat.
+
+## They said no at Supabase
+
+The person says they declined, cancelled, or closed the Supabase page.
+
+> Supabase wasn't connected. You can try again whenever you like.
+
+Stop. Start again at Step 1 only if they ask.
+
+## At the free limit
+
+`mcp__supabase__create_project` fails with an error containing
+"maximum limits for the number of active free plan projects", or two databases are already active
+on a free account. Use the skill's
+**At the free limit** section: offer to use one, pause one, or get a paid database.
+
+## The database is asleep
+
+A database they picked has status `INACTIVE` (Supabase puts free databases to sleep after a week
+without use).
+
+> That database is asleep. Waking it up now, about a minute.
+
+Call `mcp__supabase__restore_project`, then check with `mcp__supabase__get_project` (at most 10
+times) until it is `ACTIVE_HEALTHY`.
+
+## Creating failed
+
+`mcp__supabase__get_project` shows `INIT_FAILED`.
+
+> Supabase couldn't finish creating the database. Want me to try again?
+
+On yes, go back to the skill's Step 4 once. Never remove or pause anything to fix this.
+
+## They cancelled a change
+
+The card showed the SQL and they clicked Cancel (the result says `cancelled`). Nothing ran.
+
+> OK, I didn't change anything.
+
+Don't retry it on your own. If they want a different change, show the new SQL first.
+
+## A change to data or tables failed
+
+`execute_sql` returned an error (a typo, a table that already exists, a missing table). Nothing was
+changed. Say what went wrong in one plain sentence, show the corrected SQL, and ask before trying
+again. For a big or risky change, offer the table editor instead:
+[Open it in Supabase →](https://supabase.com/dashboard/project/<id>/editor)
+
+## Connection stopped working
+
+A Supabase call says the connection "is disconnected", "expired" or "was revoked", or fails with
+401.
+
+Call `external_mcp_reauth_prompt` for `supabase`, and say:
+
+> Your Supabase connection stopped working. Sign in again to keep going.
+
+After they sign in, retry the step once.
+
+## Supabase is down or busy
+
+A timeout, a connection error, a 5xx, or 429 (too many requests).
+
+> Supabase isn't responding right now. Try again in a few minutes.
+
+At most one retry later in the same conversation, never in a loop.
+
+## A Supabase step is refused by the host
+
+A call is refused as not allowed (for example `not-in-operator-allowlist`). This means the
+connection's permissions were changed by someone on this site.
+
+> That step isn't turned on for this site. An admin can turn it on in this site's settings.
+
+Do not retry it.

package/ui-ux-design/CHANGELOG.md

@@ -0,0 +1,28 @@
+# @jini-ai/agent-plugins/ui-ux-design
+
+## 0.6.19
+
+- Publishes in place as the `@jini-ai/agent-plugins/ui-ux-design` subpath; the wrapper and assembler are retired.
+- One shared copy across hosts: the skills carry the newer AI-Dev-Shop sync (c10abee: UI loop,
+  Chrome mobile matrix, animation and kUInetic references), the host card summary and Jini's search
+  keywords. Host chat rules are replaced by host-neutral tool-use wording; hosts add their own at
+  delivery. Inner plugin version 0.6.2 (above the 0.6.0 hosts seeded earlier).
+
+## 0.6.17
+
+### Patch Changes
+
+- Version bump only.
+
+## 0.6.15
+
+### Minor Changes
+
+- Breaking package-surface change for the fixed 0.6.15 release: remove the bundled
+  ui-ux-design files and wildcard export from @jini-ai/agent-plugins. Hosts must
+  explicitly install @jini-ai/agent-plugins/ui-ux-design and resolve its ./plugin.json
+  export, stage that payload and seed through the existing Agent Plugin lifecycle.
+  The lifecycle implementation remains in @jini-ai/agent-plugins. Inner plugin
+  version 0.4.6, deterministic packing, digest selection and operator activation
+  decisions are preserved. Host wording reconciliation and cutover follow later.
+