instant_explore

Use when the user wants to plan or refresh the daily place-story Reels calendar — deciding which 景點 to feature each day/week, rebalancing the theme mix after a metrics review, doing the period-end 檢核 (e.g. 8/3), or when lorescape-metrics IG analysis finishes and next period's selection is due. Triggers on 「規劃景點 calendar」「排 Reels 景點」「下週/下月選點」「調整題材配比」「月底檢核」. Local, read-only on Supabase; writes only marketing/content-calendar/.

Lorescape 每月行銷月報 — 從 lorescape-metrics 累積的 data/metrics CSV 讀取最近 30 天資料、對比前月，輸出策略學習與下月計畫。Use when "monthly audit", "monthly marketing review", "monthly report", "executive marketing review", "month-end audit", "月報", "本月數據", "月度審計", "月度行銷檢查", or any request for a 30-day marketing audit for Lorescape.

Lorescape 每週行銷週報 — 從 lorescape-metrics 累積的 data/metrics CSV 讀取最近 7 天資料、對比前週，輸出健康評分與行動清單。Use when "weekly audit", "weekly marketing review", "weekly check-in", "weekly scorecard", "what changed this week", "Friday marketing review", "每週審計", "本週數據", "週報", "每週行銷檢查", or any request for a recurring 7-day marketing audit for Lorescape.

Use when producing the daily-story reel/video for a Lorescape place — the place-photo, aspect-switching, narration-text style rendered locally (NOT Google Flow). Triggers on 「產每日故事影片」「做 reel / 短影片」「不要用 flow 做影片」「把今天的故事做成影片」, and lorescape-manual-daily-story's post-publish video step. Covers preparing the story, condensing narration, rendering, and muxing BGM.

Use when the user wants to update Lorescape's accumulating daily metrics — Google Search Console search traffic, GA4 landing + app traffic, Instagram account reach/followers, per-post IG/Reels insights, Reels 24h/48h/7d insight snapshots from IG App screenshots, RevenueCat subscription/revenue snapshot, or App Store / Play downloads & ratings. Triggers on 「產品數據報告」「這週/這月數據」「抓 GSC / 搜尋流量」「GA4 / landing / App 流量」「IG 數據 / 觸及」「每則貼文 / 貼文成效」「reel 洞察 / 截圖數據」「訂閱 / 營收 / MRR / RevenueCat」「App 下載 / 評分」. Sources via API (GSC / GA4 / IG / RevenueCat / App Store Connect / Play reports bucket)；Reels 快照另由使用者提供 IG App 洞察截圖. Accumulates into in-repo CSVs (data/metrics/*.csv, gitignored), one file per source. Local, read-only, does not touch the server.

Use when the user starts the day's work on Lorescape — 「開工」「開始今天的工作」「先處理 scheduler」「今天要做什麼」/lorescape-scheduler — to read SCHEDULE.md, verify from artifacts which routine items are already done, list today's todos, and drive them in order by invoking each item's skill.

Use when the user wants to manually generate, review, regenerate, or publish a Lorescape daily story (the server's 08:00 cron is paused via DAILY_STORY_ENABLED=0), pick the next place from daily_story_places, fix/overwrite a specific date's daily story in Supabase, gather Unsplash photos of the place, resolve a missing cover image, or — only after the user publishes — render the daily-story reel of the place (place photos + aspect-switching + narration text, locally via Remotion — NOT Google Flow; via the lorescape-daily-reel skill).

Use when debugging the Lorescape daily-story pipeline — diagnosing today's review/publish state, why an IG post didn't go out, scheduler or timezone drift, what commit is deployed on the VPS, mismatches between Supabase rows and the Discord review message, or inspecting sync tables (journey_entries / quick_guide_entries / trips / saved_locations). Strictly read-only.

Use when the user wants to publish a wander-style (dark photo-overlay, person-narrative) IG carousel for a Lorescape daily story — e.g. 「今天用 wander 風格發」,「做 wander 圖組」,「茜茜公主那種風格」. Covers writing the 7–9 slide beats, rendering, local preview, and sending for Discord review. Photos default to the day's marketing/outputs/daily_image/<date>/ pool; a user-provided folder can override. This is the FIXED carousel style for daily stories (since 2026-07-06) — lorescape-manual-daily-story Step 8b runs this flow after every publish.

Use when the user wants to manually publish a specific day's finished video from marketing/outputs/daily_video/<date>/ to Instagram Reels using the local IG token in publisher/.env — e.g. "發布某天的影片到 IG reels", "把今天的影片發到 Reels", "publish reel for 2026-06-22". Local-only, does not touch the server's scheduled publish job.

Lorescape 留存與流失分析 — GA4 留存報表 + RevenueCat 訂閱生命週期、每日故事推播習慣養成、App 推播 win-back 策略。Use when "retention", "reduce churn", "keep customers", "churn analysis", "churn prevention", "win-back", "customer lifetime value", "留存", "流失", "訂閱流失", "用戶留存", "推播策略", "每日故事推播", or any request to analyze or improve Lorescape user retention.

lorescape.app 落地頁文案撰寫與審查 — 為 lorescape.app（Next.js 雙語落地頁）產生完整頁面文案，或審查現有文案，依 MARKETING.md 的 value prop 與 differentiators 對應到 dictionaries.ts 的雙語結構（zh/en）。CTA = App Store / Google Play 下載。Use when "landing page", "落地頁", "LP 文案", "hero section", "write landing page copy", "review landing page", "改落地頁", "App Store CTA", or any request to write or review lorescape.app page copy. Descriptions trigger bilingual output (English + zh-TW).

lorescape.app 技術 SEO 審計 — 對 lorescape.app（Next.js 雙語落地頁）執行完整技術 SEO 稽核，含可抓取性、索引、Core Web Vitals、結構化標記、內部連結、行動裝置 UX、雙語內容品質。產出優先修復清單。Use when "SEO audit", "technical SEO", "site audit", "crawl issues", "indexation problems", "why aren't we ranking", "SEO health check", "SEO 稽核", "排名問題", "搜尋流量", or any request to diagnose SEO issues on lorescape.app. Descriptions trigger bilingual output (English + zh-TW).

Lorescape 內容品質檢查 — 對內容執行完整品質關卡。評分 Four U's（Unique/Useful/Ultra-specific/Urgent），檢查禁用字與 AI slop，執行語氣 regex，對搜尋內容跑 SEO lint。Use when "score this", "quality check", "run quality gates", "check this content", "four u's score", "banned word check", "SEO lint", "品質檢查", "跑 gate", "禁用字檢查", "Four U 分數", or any request to validate content quality before publishing.

Use when driving, automating, or inspecting a running Flutter app in debug mode via the `marionette` CLI — tapping buttons, entering text, pressing keys, swiping/scrolling, taking screenshots, recording video, reading logs, listing interactive widgets, or triggering hot reload/restart against a live VM service URI. Trigger whenever the user wants to interact with or test a Flutter app that's already running (e.g. "tap the submit button", "screenshot the app", "what's on screen", "scroll to X", "record a demo video"), even if they don't say "marionette" by name.

Use when writing or modifying Flutter widget tests under frontend/test/ in this project - covers BDD naming, pump helpers, fake-over-mock, interaction-over-static-render, router testing, i18n handling, and when to prefer a widget test over a controller/notifier test.