501 Muse Tips, Open-Sourced

Wed, 07 Oct 2026 00:00:00 GMT

I recently scoured the web for Muse (Meta’s personal AI assistant) tips — English and Chinese sources: X, Reddit, YouTube, V2EX, blogs, and reviews. Deduplicated, polished, and organized into ten categories: 501 tips total, now an open-source repo.

Repo

👉 https://github.com/styrigx/muse-playbook

Ten categories

Prompting (53): how to talk to Muse so it gets it right the first time — delegation mindset, asking formulas, stop conditions for long tasks
Productivity (62): reminders, email triage, docs and spreadsheets, meetings, creator ops, small-business use
Coding (22): writing code, debugging, GitHub integration, PR review workflows
Learning (14): languages, exam prep, micro-learning, tutor-style companionship
Writing (23): newsletters, social posts, podcasts, video, editing and proofreading
Daily life (110): saving money, travel, shopping comparisons, food and chores, social gifting — the breakout category
Research (34): hands-on price comparisons, price tracking, sourcing, verification methods
Creative fun (35): image prompt structures, podcasts, video, games, playful tricks
Hidden features (108): Soul, memory, permissions and safety, chat operations, hardware, quota and invites
Advanced (39): building connectors by talking, hooks automation, multi-agent setups, safety red lines

Notes

Every tip is one actionable sentence; ones marked “self-reported” are unverified community claims
Collected in October 2026 — Muse ships fast, some entries may go stale; trust the app UI
PRs and issues welcome — tell me what’s missing or wrong

Migrating the Blog from Hugo to Navfolio: Full Notes

Wed, 07 Oct 2026 00:00:00 GMT

The blog has a new theme. Moved from Hugo + PaperMod to Astro + Navfolio. Writing down the whole process — why, how, and what broke along the way.

Why switch

PaperMod is great: light, fast, minimal. But after a while it felt like just a blog theme — post list plus post pages, nothing else.

Navfolio is different. It’s a personal dashboard: avatar, motto, nav cards, writing stats, heatmap, all on one screen. The blog is one module of it. That’s closer to what I want — a blog isn’t just a place for posts, it’s a foothold on the internet.

One clarification: the portal and the blog are two sites, two repos. The portal comes later; this post is about the blog only.

Migration rule #1: keep the URLs

This was the most important constraint. Old posts lived at /post/<slug>/, and Giscus binds comments by pathname — meaning as long as the new site serves identical article URLs, old comments carry over automatically. No database migration needed.

So the first job was making sure the new theme could route articles as /post/<slug>/ with trailing slashes, then verifying every URL, Chinese and English.

Bilingual setup

Chinese is default at root /; English under /en/. Details:

Auto-redirect on first visit by browser language, crawlers excluded (or search indexing gets messy)
Manual choice remembered via localStorage
Language switch jumps to the translation — on a Chinese post, hitting EN goes to that post’s English version; falls back to homepage only if no translation exists
Split search indexes with Pagefind, one per language, so Chinese searches don’t surface English results

Homepage: the version I rejected

First attempt was a plain blog homepage — title plus post list. I rejected it myself: too far from the official demo’s dashboard look.

The redo used the official components directly: ProfileCard, IntroCard, NavigationCard, ConnectCard, BlogHeatmap, arranged as the dashboard. Two sets of copy, Chinese and English.

One bug in between: the title rendered as “Hi, Hi, I’m Sloan Sloan Gray” — greeting duplicated the title. Fixed.

Fonts: WenKai + Maple Mono

Chinese in LXGW WenKai, English and UI in Maple Mono monospace. That’s the theme’s “paper + typewriter” feel — the literary Kai-style Chinese against monospace techiness fits the “take it apart, put it back together” motto.

Technical note: the WenKai TTF is several MB; the build subsets it to used characters only, so loading is fine. WenKai ships a single Regular weight, so bold Chinese is synthesized by the browser — acceptable at these sizes, not worth chasing.

Verdict: once fonts look good and recognizable, stop. Beyond that lies madness.

Avatar: centered crop

Using my own photo. First crop was face-tracked; I rejected it for a centered square crop extending from the middle outward. Person in the center, stable composition.

Favicon: the SGX monogram

Started with no idea — generated options: a serif S, an ink dot, folded paper. Landed on SGX: initials of Sloan Gray, also the core of styrigx. Name and handle in three letters.

A few rounds: serif S was too plain; an interlocked S/G/X geometric mark had style but was unreadable at small sizes; final version thickened the strokes and separated the letters — legibility and design balanced. Sage green to match the theme.

One gotcha: the theme prefers favicon.svg, and my placeholder SVG was showing in browser tabs instead of the final interlocked PNG. Deleted the SVG so browsers fall back to PNG.

The end year is automatic — computed from the build date, rolls forward on every deploy. One caveat: it’s build-time, not runtime. A year with zero deploys would show a stale year, but publishing posts triggers builds anyway.

The “Recently” module

The official demo’s about page has a “Recently” section. The theme ships a DoingCard component — just unconfigured and unwired.

I added 5 items in each language, all real: blog migration, portal theme hunt, Muse playbook, invite-code board, S26 upgrade plan. Future updates just edit the doing list in config.

Deploy: push and forget

Used to be manual wrangler uploads, disconnected from GitHub. Now back to the Hugo-era fully automatic flow:

Source in styrigx/styrigx-blog, main branch
On push, GitHub Actions builds (deps, font subsetting, Pagefind index) and deploys to Cloudflare Pages via wrangler
Write a post or tweak config, push, done

Pitfalls worth noting

NAVFOLIO_CONTENT_SOURCE=docs is a landmine. The theme’s workflow sets it, making builds use demo content over yours. Delete it if you deploy via Actions.
Wrangler env vars. Direct-deploy scripts must preserve proxy vars and cert vars, or npm stalls and wrangler can’t connect.
TOML sub-table ordering. [params.xxx] sub-tables must come after sibling plain keys, or later keys get swallowed — once cost me the comment section.
Don’t touch Giscus params. repo_id, category_id — change those and old comments stop matching. Migrate URL structure, leave comment config alone.
Build-time vs runtime year. The footer year is computed at build time. Knowing that ends the confusion about why “automatic” still depends on deploys.

Whole migration done in a day: plan in the morning, content in the afternoon, homepage and icons in the evening, live by night. https://blog.styrigx.com runs this now.

Next: a new theme for the portal. The blog stays put.

Launched a Muse Invite-Code Sharing Site

Sun, 27 Sep 2026 00:00:00 GMT

Shipped a small project today: a community Muse invite-code board.

What it does

🎲 Draw one: one click, get a random invite code contributed by the community
📮 Contribute: have a spare code? Submit it for others
👍 Feedback: got a working code? Mark it “works” to help the next person
🧹 Auto-cleanup: codes flagged invalid 3 times get hidden automatically

How it’s built

Frontend: single HTML file, editorial paper aesthetic, Chinese/English bilingual
Backend: Cloudflare Worker API
Storage: Supabase for the code table, Cloudflare KV for rate limiting, messages, and recent draws
Draw logic: weighted rotation, least-drawn codes first

Link

👉 https://muse-invite.styrigx.com/

Come grab a code, or contribute one. Suggestions welcome — just reach out.

Styrigx (English)