Replying to @strube
100% AI. I do have an academy where I share tools and any learning from my journey academy.mobayilo.com/learn/d…
1
11
Replying to @staroaeg
No. That's on purpose: no dates, no reordering. The list stays in the order you wrote it, and each line shows how long it's been there, so old things stand out. Thanks to you, the new version is all keyboard: ⌥Space from any app, type, Enter, Esc. ⌥Space🙏
2
I built Focus Zen: a simple to-do list for Mac.
One list. Nothing else.
Write it down. Check it off. Move on.
Your list never leaves your Mac. No account, no cloud, no tracking.
Free and open source, or $5 to support it.
focus.mobayilo.com
#OpenSource #Productivity
3.26 billion tokens. 25,421 requests. $2,320.79.
Not a productivity report.
For almost three weeks, I kept coming back because I was happy—building, learning, following curiosity, and teaching what I learned.
This is what joy looks like:
adusingi.com/blog/this-is-wh…
1
16
I needed a monitoring system and was excited when Basecamp open-sourced Upright. Then I saw it needed 2 GB of memory to check three things: apps online, certificates valid, servers with space.
With AI and Go, I built Indebero in half a day. It needs 512 MB.
adusingi.com/blog/more-than-…
#golang
2
2
33
I live in Japan. Almost nobody I work with does, so in June I spent half an afternoon building a small clock app to stop working out what time it is for everyone else.
Three months later it had become the page eight people use to book time with me.
adusingi.com/blog/what-time-…
2
328
Replying to @asmartbear
I know a few founders in my village in Japan who are running the same business for more than 30 years.
1
1
446
If you are looking for a quiet place to build remotely in Japan. Come say hello! We have all facilities. Coworking, cafe, nice hotel and guesthouse #buildinpublic #okayama #remotework
I keep exploring working from the terminal and would love to bring my whole workflow inside. Today I connected my music app, umuzika.com, thanks to the Subsonic API, and now I'm enjoying it with cliamp.
46
Replying to @le_chaman
viens regarder une mission japonaise sur la bouffe. Les américaines c'est rien. Les japonaise c'est une autre level
72
Replying to @tessl_io
@tessl_io watched your presentation at AIDevCon and got this output .The feedback is mostly a rubric mismatch — tessl is judging this as a model-invoked skill, but yours isn't one. Here's my read, section by section:
The Description critique (33%) is largely moot. Your skill has disable-model-invocation: true, so it only fires when you type /handoff. Everything the judge wants — "Use when..." clauses, trigger-term synonyms like "compress context", distinctiveness from summarization skills — exists to help a model decide when to auto-select a skill. Since the model never makes that decision here, stuffing the description with trigger vocabulary would add noise for zero benefit. The description's only job is to read clearly in your skill list, and it does.
The frontmatter warning is a false positive. The "unknown keys" are argument-hint and disable-model-invocation — both valid Claude Code frontmatter that tessl's schema simply doesn't know about. Don't remove them; removing disable-model-invocation would actually change behavior (the skill would start auto-triggering).
The Content critiques (73%) are a mixed bag:
- "Add a verification step to confirm the file was written" — unnecessary in Claude Code. The Write tool errors loudly on failure; a silent loss isn't a real failure mode here. This is generic-agent advice that doesn't apply to your harness.
- "Number the steps explicitly" — marginal. The skill is 13 lines of body; the sequence is obvious. Cheap to do, but I wouldn't call it a gap.
- "Add a template for the handoff document" — this is the one suggestion with real merit. Right now every handoff's structure is improvised, so docs from different sessions will look different and the reading agent can't rely on where anything is. A light skeleton (goal, current state, decisions made, open items, suggested skills, artifact references) would make outputs consistent without over-constraining. I'd keep it loose — a rigid template fights the reality that handoffs vary a lot by conversation.
So: I'd ignore the 61% score, and the one change worth making is adding a brief output skeleton to the skill body. Want me to add it?
1
26
Living in Japan, working with Africa and the West — picking a meeting time that isn't someone's 3am got old. So I built World Time 🌍.
A Three.js globe arcing between your cities, a "best overlap" planner, auto-detected location & live weather. Static on Cloudflare, no API keys.
MIT, clone it: meeting.mobayilo.com
#buildinpublic #opensource
2
43



