人生到處知何似,應似飛鴻踏雪泥
Tw93 · · Products

Any website can be a desktop app in seconds. Paste a link, press Create, and it gets its own window and icon.

Pake's open-source CLI, 4 years and 63.6K, stays free. The native app is one purchase for Mac, Windows and Linux, early bird still on.

pake.run/

0:51
Tw93 · · Products

Kaku is my open-source Mac terminal for AI coding.

Running several agents at once? A tab lights a dot when its agent needs you, and Cmd+J jumps straight to it. On your phone, the remote page lists every tab with its agent's status.

github.com/tw93/Kaku

Tw93 · · Products

MiaoYan is a native Markdown notebook for Mac, iPad and iPhone, light and fast. I've been building it since 2020.

It's AI friendly too. Notes are plain Markdown files, so agents can edit them, and the miao CLI lets them search, read and add notes.

miaoyan.app/

Tw93 · · AI

Here's how I keep X clean without missing the good stuff from people I follow. I gave Grok this prompt, and you can try it too:

Every evening at 8pm, put together today's highlights from the accounts I follow…Show more, plus others worth reading. Read posts only through the official X API, and skip anything covered the day before.

Format:
- Open with "Today's main threads" in 3 short sentences
- One section per person, with their name and @, and a divider between sections
- 2 to 4 points per section, each as a bold topic, then the content and a link to the original post. Use two to four sentences to cover what they said, the key details and the background
- End each section with one sentence of your own take
- Put small tools in a final "Tools" section
- About 10 to 15 sections, no em dashes, no AI tone, keep it simple and clear

Now I get this digest every day, so I scroll X less and stay a bit more focused.

Tw93 · · Products

Pake V3.18 is out. It's an open-source tool that turns any webpage into a lightweight desktop app with one command, now at 62.9K stars.

What's new:
1. The docs have their own site now, with a step-by-step getting started tutorial and pages for shortcuts, scripts and AI agents.…Show more
2. Dragging a file onto a page to upload it now always works.
3. Downloads keep their real names, so Annual Report.pdf no longer gets saved as Annual%20Report.pdf.
4. On Windows, downloads show the native WebView2 panel with progress, and a failed build no longer blocks the next one.

Thanks to the contributors whose pull requests went into this release.

github.com/tw93/Pake

Tw93 · · Learning

People often ask me how to use AI to design products that look good and don't feel like AI slop. It's not an easy question, since I'm not a professional designer, so I can only share it from a product engineer's point of view:…Show more how to make products that aren't ugly and are easy to use.

First, one premise. A good-looking design can't save a product that doesn't solve a problem. Design is the icing on the cake, not what decides whether a product succeeds. If I had to rank priorities, it would be: solves a problem > easy to use > looks good. It's like food: first don't go hungry, then get enough to eat, then eat well.

I won't say much about solving the problem, since that depends on the product itself. It solves a concrete need: someone needs it, there's a real scenario for it, and your product happens to offer a way for a person or an agent to get it done. Some problems are just bigger than others.

So how do you make a product that's easy to use and not ugly? Ha, you can walk through the list below yourself, or hand the whole thing to your agent and have it review your product's codebase.

1. Pretend you're an ordinary user who knows nothing about tech. Can they get through the main flow and come out with what they need? Find every place where they get stuck, where something isn't explained, or where one step doesn't lead naturally into the next, and fix all of it, so people can use the product without a manual. Only where that's truly impossible, add a short hint.

2. Every piece of copy should read the way native speakers of that language actually talk. Choose your words carefully instead of translating flatly. Look at how Apple, Windows and well-known websites word the same thing, and aim for copy that feels simple, clear and natural to a local.

3. Where the product itself already makes something clear, don't add text to explain it. Don't over-explain. Check every line of helper text for whether it says what it means without padding, and if the interaction or the visuals already say it, don't say it again in words.

4. When you show a number, make sure people know what it refers to, and make it easy to read for what it means. Money, metrics, distance and other units each have their own best practices. Accuracy matters a lot, so don't skip validating the data to save effort.

5. Don't keep asking users to confirm something they already chose. Ask a second time only when an action can't be undone, so the screen isn't full of confirmation dialogs. Don't splash big red areas over dangerous actions either. Think about how pleasant the product feels to use. Users aren't stupid, so don't worry too much about them making mistakes.

6. Visually, keep one accent color per page. Try to avoid orange, terracotta, and the bright corporate blue of old admin dashboards. Make every gray a warm gray, never a cold blue-gray. If you can't find a good color, look through traditional Chinese colors.

7. Use as few font sizes as possible, at most four on a page. Think about the reading rhythm of the whole page, its clarity and text contrast, and make sure it meets accessibility standards. Line height, letter spacing and paragraph spacing all need repeated tuning, while the whole system stays consistent.

8. Use italics, monospace and all caps sparingly, and only with a clear reason. No italics for helper text, monospace only for code, paths and metrics, and no all-caps text in buttons or labels. Go easy on joining things with a middle dot (·). Use one verb for one action across the whole product, and avoid verbs that push people to act, like the marketing-style "Buy now".

9. Keep buttons, spacing, corner radius, dividers, dialogs, animation and shadows consistent and restrained, so they don't get in the user's way. Nested rounded corners should be concentric: the inner radius equals the outer radius minus the padding between them, and it looks better. Pages are flat by default: no stacked shadows, no glow, no frosted glass. Shadows are only for dialogs that really float above the page, and no cards inside cards.

10. In a multilingual product, lay things out for the longest translation first, and put meaning before looks rather than changing what the text says to make it fit. You can rewrite the copy, but don't change the font size or truncate it. Check that everything displays well at different sizes on the devices your users actually use, test them all, and fix everything that looks off.

11. For a design you keep tweaking without getting it right, or one that still looks off after many rounds, ask your agent for the three options it thinks are best and pick one, then tell it to keep refining until you're happy. I like having AI put before-and-after images into one PDF, which makes comparing them much easier for me.

That's about it. One more thing matters a lot, though: your own patience and willingness to keep iterating. I'm a bit of a perfectionist, and I often go a dozen rounds with AI over a single line of copy, a color or a design until I'm happy with it. AI is smart, but you often need to ask more of it, and put in more time and patience to get a result you like. Or put another way, spend more time and look at more good design, and you can build products that are easy to use and not ugly.

Tw93 · · Thoughts

Yesterday a reader sent me a message. They study computer science, and they feel AI can now do all of their homework and papers for them. They asked whether this field still has a future, and what advice I'd give for the years ahead.…Show more

It made me think: if I could go back to my final year of college, what would I do to make the road ahead a little smoother, with fewer pitfalls? This is just my own limited view, and I'd love to hear yours.

1. I'd still choose computer science, then pick the sub-field I find most interesting, and use AI to amplify my work there as much as I can, so that right after graduating it already feels like leading a team.

2. Move to a city with a strong tech scene and plenty of tech companies, like San Francisco, New York, London or Seattle. If your degree and skills are strong enough, find a good AI company in the few blocks of San Francisco between SoMa and Mission Bay. Being that close to the AI labs will sharpen your sense of where large models are heading far more than anywhere else.

3. At work, get things done fast, and be willing to pay for good AI tokens so you can do them well and quickly. Push the projects you care about to 150%, and finish the ones you don't to a solid 80 in the least time possible. Don't waste time, so there's room left to learn more. Embrace new things eagerly, and be willing to spend money on the best AI.

4. Put half of your salary into VOO and QQQ as a regular monthly investment. You can also pick one or two tech companies you strongly believe in, like NVIDIA, Apple, or Anthropic once it goes public. Don't chase hot stocks, and don't speculate.

5. Find your partner earlier, rather than putting it off until you've been working for a few years. Watch how they handle problems and how patient they are. Look for the one who cares how you feel, stays optimistic, and stands on your side whatever happens.

6. Don't lend money to anyone, including relatives, classmates and old friends. Lending money will only weigh on you while you're young. Don't show off how much you earn, and don't spend carelessly. First grow your first pot of money to the point where you'd feel comfortable living for two years without working.

7. Keep learning, keep talking with people, and keep making fun things for the community, your circles and X. Build your GitHub and X accounts without chasing profit, so they grow into your personal brand. Always serve people assuming your users are good people.

8. Outside your main work, grow your own interests. Take some classes, whether photography, a musical instrument, sports, or even running and cycling. Life outside work won't get dull, and it gets you out and about more.

9. Health always comes first. Sleep matters, so never stay up late. Don't sit for too long, drink plenty of water, and walk more. Don't push too hard at work either. The first burst of energy fades, the second runs low, and the third is gone, so stretch out how long you can keep working.

10. In the end, find your own path to not having to clock in, as early as you can. You can still work, but you don't have to show up for a job. Earn money through your interests, expertise, strengths and what you keep learning, keep improving along the way, and enjoy making that money.

Tw93 · · Products

One more thing, Mole CLI just landed on Linux, free and open source forever, as on Mac and Windows.

27 releases and 900+ commits in the past month. Linux went from first commit to 0.4.0 in four days, with the same menu, keys and safety rules as the Mac.

github.com/tw93/Mole

Tw93 · · Products

With AI, writing code has gotten way faster, but verification is still slow, especially waiting on GitHub Actions CI. I spent this afternoon giving the CI for Mole, Kaku and Pake a full overhaul, and the results were great, so I want to share what I learned.…Show more

Just copy the prompt below and hand it to your agent, and let's see how much time it saves you.

Speed up this repo's GitHub Actions as much as possible without dropping any necessary tests or checks.

1. Start by using gh to pull the last 50 runs and split each job into three phases: queue, setup and the actual test run. Look for patterns. Often the slow part is setup, not the tests themselves.
2. When a PR gets several pushes in a row, only run the latest one and cancel the older runs with cancel-in-progress. Don't do this on main, though: every commit on main needs a complete run before a release.
3. Commits that only touch the README or docs shouldn't trigger CI, so filter them out with paths. Watch out: a required check that gets skipped stays pending and blocks the PR from merging, so plan for that up front.
4. Prefer the built-in caching in setup actions: turn on cache in setup-node, setup-go has it on by default, and use Swatinem/rust-cache for Rust. Each repo only gets 10 GB of cache, so don't put anything in there you won't actually reuse.
5. Build twice in a row locally. The second build should take almost no time. If something still takes time, something is set up wrong, like a Dockerfile that copies the whole repo before installing dependencies, or a build script watching a file that doesn't exist. Check for anything similar.
6. Download prebuilt tools instead of compiling them on the spot with go install or cargo install, which eats a lot of time.
7. Run jobs that don't depend on each other in parallel, remove needs edges that don't pass any data, and split your longest test suite across multiple machines.
8. Free accounts can run at most 5 macOS jobs at once, shared across all workflows. Move anything that doesn't care about the OS, like formatting, linting and dependency audits, over to Ubuntu.
9. Don't do the same work twice, and don't do work you don't need. If another job already ran a check, don't run it again, and a job that only builds the frontend doesn't need to pull the whole Rust cache.
10. Once you're done, push and watch how the runs actually perform. Look at the timings, find the patterns, then do another pass to catch what you missed and get it as good as it can be. Finally, show me a before and after comparison.

Tw93 · · Products

One more thing, Mole is still simple, now it's also pro.

See which app eats your bandwidth, run a speed test, and hover any tag for Wi-Fi, disk and battery internals you'll never see unless you want them. Try it via Settings > Receive beta updates.

mole.fit/releases

0:29
Tw93 · · Tools

Sharing the 6 Chrome extensions I use every day.

1. Maple Bookmarks, made by me. I keep Chrome's bookmark bar hidden and open my bookmarks in a popup with a shortcut.
2. Maple NewTab, also made by me. A minimal new tab page that replaces Chrome's default and shows a beautiful…Show more painting every day.
3. Minimal Theme for Twitter / X. Highly recommended if you spend time on X. It strips away a lot of the clutter and makes X look much nicer.
4. PWA Install Block. I really dislike the install-app button in the address bar, and this hides it.
5. uBlock Origin Lite. The best ad blocker I've used, and the lightest on performance.
6. WebRTC Control. I care about privacy, and I don't want AI to know too much about me.

Tw93 · · Life

"You've gotta touch it to believe it." Then you've gotta wipe it.

Tw93 · · Products

Kami 1.20 is out. Your AI writes the words, Kami gives them good paper.

From the last three releases: charts drawn from data and checked before delivery, product sites in the product's own color, and Chinese and Korean pages that read well on iPhone.

github.com/tw93/kami

Tw93 · · AI

I spent an afternoon turning my AI coding habits into 20 rules that you and your agent can learn from together.

Briefing
1. Stop dictating the implementation. Describe the outcome you want. Models are good enough now, so aim high and don't worry that it can't be done.…Show more
2. Give your agent the background and the goal: why it matters, who it's for, what great looks like. Then let go of the technical details.
3. Use the best model available. A weaker one just means more back-and-forth, wasted time and frustration.
4. Before adding a feature, setting or toggle, have the agent check with you first. Don't let it add features, toggles or copy nobody will use, and have it write your product rules down as it goes.
5. Think big, but have it build in the smallest usable steps and commit as you go, so you can roll back anytime.

Rules
6. Teach it how you talk: "look at" or "analyze" means read and report, "fix" or "change" means edit. Commits, releases and deletions always need your OK.
7. In AGENTS.md or CLAUDE.md, write only what it can't learn from the code, and what you've already ruled out. Never paste keys or tokens into the chat. If you do, treat them as leaked and rotate them.
8. Prompts alone won't hold hard rules. Enforce them with scripts, and only count it done when the checks actually pass.

Coding
9. Before writing code, have it explain what it will change and what that will affect, so you have the context to make the call.
10. Have it build a verification script for the project, run it at each checkpoint and show you the results. Over time, that becomes your agent's test suite.
11. Parallel agents each get their own worktree and commit only their own changes. Once everything is merged, run the full test suite.

Debugging
12. Find the cause before fixing. If two fixes fail, add logs and look at the real data instead of guessing.
13. If three fail, clear the context and start fresh with the problem, the goal and what you've already tried.

Review
14. Keep the agent that writes separate from the agent that reviews, so one doesn't bias the other.
15. Cap reviews at 3 rounds. From round two on, only review what's new.
16. The riskier the change, the deeper the check. Deletions, payments, and releases are one-way doors, so check them yourself and click through the real result.

Shipping
17. Every commit says what changed, how it was verified and how to roll it back. Your git history becomes great context for the next agent.
18. Use it yourself or give it to early testers first. Add a beta update switch so a bad release doesn't hit everyone.

Retro
19. Every production bug and user report gets a test case that runs before each release. Rerun them whenever you switch models to see if the new one holds up.
20. When fixing one thing, have it find and fix the same problem everywhere. Same for features and visual polish.

Tw93 · · Products

Mole tells you what your cleaned space would cost at Apple's storage upgrade price. I'm at $1,300 so far. Hover the Clean number at the bottom of the menu bar panel to see yours. How much have you saved?

Tw93 · · Products

Kaku shipped 9 releases in October, mostly on remote access.

Run kaku remote and your Mac's terminals, running Claude Code sessions included, open in a browser on another device, and it now works with touch, on the web page and over remote desktop.

github.com/tw93/Kaku

Tw93 · · Products

I started MiaoYan in 2020, and six years later it's on iPhone and iPad too. It's a native Markdown editor written in Swift, one App Store purchase covers Mac, iPhone and iPad with the same iCloud Drive folder, and the Mac app stays free and open source.
miaoyan.app/

Tw93 · · Products

Mole CLI just passed 72.8K stars, and October is its busiest month yet: 18 releases across Mac and Windows.

The Windows CLI now matches the Mac one, any AI agent can drive it with the official skill, and mo slim strips Intel code from universal apps.

github.com/tw93/Mole

Tw93 · · Tools

Just discovered this beautiful collection of 526 traditional Chinese colors, and I love it.

Each color has its own poetic name, inspired by nature, flowers, minerals, and centuries of Chinese culture. Such a lovely source of inspiration for design.

figma.com/design/5gJsBEyypBoGo48GFRcd4F

Tw93 · · Products

Mole got 8 pages in iCreate 182, the largest Apple magazine in the Netherlands and Belgium, from the five planets all the way down to the little mole in the menu bar.

Thank you Ward Edema and the iCreate team for going through every tab so carefully.

Tw93 · · Products

Mole for Windows is finally here, a Windows app that feels well made.

It cleans thoroughly, removes apps with their leftovers, maps your disk and shows live status, all on your PC, no ads. $15.20 at launch, $10 for Mole for Mac owners with MOLEAGAIN.

mole.fit/windows

0:55
Tw93 · · Products

Mole Mac 1.16 is a big update.

• Clean up junk from Claude Code, Codex and more
• Clear caches and logs in System Data
• Better uninstall cleanup, with 800+ apps personally tested
• Refreshed icons and friendlier wording

mole.fit/

There’s more in 1.16 than these four highlights. You can find the full release notes here mole.fit/releases

Tw93 · · Products

I resent 400+ Mole license emails, one by one. Some buyers were saving gifts; others had never received their keys.

It led to this little bit of magic: click on the website to open Mole with your key filled in. Just confirm. Coming in the next release.

mole.fit/blog/resending-mole-license-ema…

0:05
Tw93 · · Products

Kaku is an open-source Mac terminal, ready for AI coding.

Recent updates add session recovery and official Homebrew support, fix image-related typing freezes, and make tabs easier to use over remote desktop.

kaku.fun/

Tw93 · · Products

✨ To make Mole better at uninstalling apps and cleaning up leftovers, I've manually tested and checked 800 Mac apps.

This includes Adobe apps, antivirus, developer tools and AI tools. Every app has a free uninstall guide, even if you don't use Mole.

mole.fit/tested-apps

Older notes