Skip to content

Session Log — 2026-07-11

Highlights

  • OpenCode as a chat agent / MCP discussion: User asked whether an MCP could turn OpenCode into a general chat agent.
  • Built: canva-design OpenCode skill (local Canva-style generator): User wanted "more like Canva" — i.e. design generation (templates, text overlays, branded graphics), not just pixel edits.
  • Test: LEMO Instagram post: Generated an Instagram post for LEMO EGG.2B.302.CLL as a skill demo (user confirmed it was just a test, "well done").
  • Notes / follow-ups: ~ does NOT expand in the OpenCode bash tool shell — use absolute paths (/home/dini/...).
  • Edited: Shopify Import Tool V12 — added global Tags column: User wanted the v12 metafield tool (/home/dini/Downloads/work/Shopify_import_tool_V12.html) to output a Tags column.
  • Built: B-Series insert spec database → Shopify metafields → product-page spec table: Goal: turn the LEMO catalogues into a queryable insert-spec DB, store specs as Shopify metafields, and render them as a product-page spec table on lemo-test ...

Full log

Session Log — 2026-07-11

OpenCode as a chat agent / MCP discussion

  • User asked whether an MCP could turn OpenCode into a general chat agent.
  • Conclusion: OpenCode is already a general chat agent; MCPs extend capabilities (tools/data/channels), they don't change the core nature.
  • Noted available local tooling for image work: ImageMagick (convert/mogrify) and Pillow 12.3 are installed.

Built: canva-design OpenCode skill (local Canva-style generator)

User wanted "more like Canva" — i.e. design generation (templates, text overlays, branded graphics), not just pixel edits.

Researched two paths: 1. Official Canva MCP — hosted at https://mcp.canva.com/mcp, OAuth2 via mcp-remote bridge, needs a Canva account. True Canva, cloud-bound. 2. Local skill — generate designs locally, no account. Chosen by user (all design types: social posts, thumbnails/banners, flyers, quote/branded graphics).

Confirmed global skill path: ~/.config/opencode/skills/<name>/SKILL.md (name must be lowercase-hyphen, match dir).

Files created (~/.config/opencode/skills/canva-design/)

  • SKILL.md — frontmatter + workflow + dimensions catalog + render/preview commands
  • templates/ — 9 starter HTML/CSS templates:
  • social-post.html 1080×1080 · story.html 1080×1920 · linkedin-banner.html 1584×396
  • youtube-thumbnail.html 1280×720 · banner.html 1200×628 · flyer.html 1080×1350
  • quote-card.html 1080×1080 · announcement.html 1080×1080 · logo.html 600×600
  • lib/render.js — node lib/render.js <in.html> <out.png> <w> <h> [scale]; renders via cached Chromium (Playwright). Installed playwright into lib/ (browsers already cached). Default scale 2 → 2× crisp output.
  • lib/serve.js — node lib/serve.js <file> [port]; serves over localhost + opens in browser (xdg-open). For HTML previews user can refresh after edits.
  • lib/brand.json — default brand kit (colors/fonts/logo) to persist the user's brand.

Browser preview added

  • Agent cannot read images, so added serve.js to display designs in the user's browser.
  • Verified DISPLAY=:1 is set → xdg-open opens a real window. Remote note: ssh -L 8787:localhost:8787.

Verification

  • All 9 templates rendered to correct dimensions (e.g. 1080×1080 → 2160×2160 at 2×).
  • End-to-end test: custom "Summer Sale" post (orange + black) rendered successfully.

Test: LEMO Instagram post

Notes / follow-ups

  • ~ does NOT expand in the OpenCode bash tool shell — use absolute paths (/home/dini/...).
  • Could add a /design slash command and more template styles later.
  • Official Canva MCP remains an option if true Canva integration is ever wanted.

Edited: Shopify Import Tool V12 — added global Tags column

User wanted the v12 metafield tool (/home/dini/Downloads/work/Shopify_import_tool_V12.html) to output a Tags column.

Decision: a manual global Tags box (not auto-derived from metafields). User types comma-separated tags once; that value is written to the Tags column of every exported product row.

Changes made to Shopify_import_tool_V12.html

  • New #globalTags text input in the Metafields card (under the bulk-apply row).
  • New #pTags preview in the Preview card (live badge preview as you type).
  • globalTags variable, persisted to localStorage (v12_global_tags); input listener updates it + the preview live.
  • render() shows #pTags.
  • exportCSV(): header now Handle,Title,Body (HTML),Variant SKU,Tags,...; every row gets the tags value (normalized: trimmed, comma-joined).
  • Backup saved as Shopify_import_tool_V12.bak.html before editing.

Verification (headless Playwright)

  • Unit: normalization + preview correct.
  • E2E: loaded real shopify_metafield_export.csv (47 products) → 47 export rows → Tags column at index 4 (after Variant SKU) → all 47 rows contain the entered tags. PASS.

Notes

  • Tags are global (one value → all rows), per user's "on every product line" intent.
  • Out of scope (user dropped earlier idea): auto-deriving tags from Series/Size metafields.

Built: B-Series insert spec database → Shopify metafields → product-page spec table

Goal: turn the LEMO catalogues into a queryable insert-spec DB, store specs as Shopify metafields, and render them as a product-page spec table on lemo-test (Dawn theme "JBS/LEMO Customs"). Scope this pass: B Series only (K series deferred).

Data pipeline

  • Located 11 LEMO catalogue PDFs in /home/dini/vault/catalogues/; extracted all to catalogues/text/*.txt via pdftotext -layout; created catalogues/INDEX.md.
  • Learned LEMO part-number grammar: MODEL.SIZE+SERIES.INSERTCFG.HOUSING-INSULATOR-CONTACT-COLLET.CABLEØ (e.g. FGG.1B.306.CLAD62); insert-config last 2 digits = contact count.
  • Store SKU join key = LEM.<LEMO_PART_NO> (e.g. LEM.ECG1B302CLL). Inserts match LEM.<MODEL><SIZE>B<3-digit-config>...; accessories use 100/200 codes.
  • Parser /tmp/opencode/parse_bkt.py against catalogues/text/BKT_series.txt (B/K multipole table, lines 4268–4760). Fixed: XB over-match, \f line offset, missing 340+ codes, dupes.
  • Verified dataset catalogues/specs/b_series_multipole.json = 74 unique B-series multipole records; per-size counts match source exactly (0B:7,1B:10,2B:15,3B:16,4B:11,5B:13,XB:2).
  • Human reference catalogues/specs/b_series_multipole.md.

Theme rendering (local files only — NOT pushed)

  • snippets/spec-table.liquid — reads product.metafields.specs.*, renders a styled table, only shows when insert_config is set.
  • sections/main-product.liquid — added spec_sheet block: when 'spec_sheet' case in block loop + schema block def (heading setting).
  • templates/product.lemo-product.json — added a spec_sheet block instance after description (this is the template the user will use).

Metafields written (live on store, namespace specs, additive — separate from existing custom.*)

Keys: series, shell_size, insert_config, contact_count (int), contact_diameter_mm (decimal), wire_gauge_awg, rated_current_a (decimal), test_voltage_kv, termination_solder/crimp/pcb_straight/pcb_elbow (bool). Written to 7 sample 1B products: ECG1B302/304/306/308/316 CLL, EEG1B302CLL, EAG1B316CLN. Verified in API responses.

Data-integrity flag

  • Store sells LEM.ECG1B310CLL (10-pin 1B) but the catalogue B multipole table has no 1B.310 (310 exists only for 3B). Skipped — no source spec. Needs a decision (store error vs. another catalogue).

Auth / tooling blockers (important for next time)

  • Shopify MCP: get-products has limit+searchTitle but no cursor (can't paginate whole catalog); get-product-by-id needs full GID and does not return metafields. update-product DOES accept metafields[] — that's how specs were written.
  • Backup script OAuth client_credentials (clientId e677609934... + shpss_... secret) mints a 24h shpua_ token with write_themes,write_theme_code scopes.
  • BUT Shopify (2025 change) now blocks themeCreate AND themeFilesUpsert for custom-app tokens without a special exemption → cannot theme push/create themes via token.
  • shopify theme dev (CLI v4.4.0) with SHOPIFY_CLI_THEME_TOKEN got past login but rejected --store-password ("invalid") even though the storefront password moyeem is confirmed correct (curl login → 200). Known CLI quirk with token auth. Interactive OAuth login (browser) not completable headlessly.
  • Net: to run a real theme dev/push preview, do the interactive shopify theme dev login in a local fish terminal.

Preview delivered

  • Since store preview was blocked, rendered the exact snippet output with real 302 data as a standalone HTML file: catalogues/specs/spec-preview.html (also /tmp/opencode/spec-preview.html). User confirmed the look is fine.

Key files

  • /home/dini/vault/catalogues/specs/b_series_multipole.json — 74 verified B multipole records (source of truth)
  • /home/dini/vault/catalogues/specs/b_series_multipole.md — human-readable reference
  • /home/dini/vault/catalogues/specs/spec-preview.html — visual preview of the spec table
  • /home/dini/Downloads/work/dawn-theme/snippets/spec-table.liquid
  • /home/dini/Downloads/work/dawn-theme/sections/main-product.liquid (spec_sheet block)
  • /home/dini/Downloads/work/dawn-theme/templates/product.lemo-product.json (spec_sheet instance)
  • /tmp/opencode/parse_bkt.py — parser

Next steps

  • Verify the 7 on a real theme dev preview (interactive login), then bulk-write specs to all B inserts (per-size searchTitle batches via MCP update-product, or an Admin token pass).
  • Resolve 1B.310. Then extend to K series.