00 Creative developer
松坂ユキ
Ideas in orbit.
Code on earth.
Independent work across Android, the web, and Linux. A few ideas, built into things you can use.
01 Projects
Five projects. Different worlds, the same curiosity. From beneath Android to a place for your words.
Index
5 entries
KernelPatch-based Android root management.
System and kernel modules, Lua plugins, and Shizuku integration in one configurable manager. Multiple home layouts, themes, and custom fonts put the interface in its owner's hands.
One Miuix interface for Android root control.
Built on KernelPatch and the APatch capability chain, Aster brings root state, superuser access, and APM / KPM modules into one interface. Protected runtime changes use a timed trial with recovery attempts before they can be kept.
A Material Design 3 blog theme, powered by Astro.
Markdown and MDX publishing, Pagefind search, and configurable personal pages in a Material Design 3 theme. The project is winding down maintenance; Shirone is the recommended successor.
An anime-inspired Material 3 Expressive blog theme.
A reading space for long-form writing and personal collections. Dynamic HCT palettes, persistent Swup navigation, and Markdown / MDX publishing sit on an Astro and Svelte foundation.
A self-contained niri and DankMaterialShell desktop.
A Wayland configuration that brings niri, DankMaterialShell, and matugen together as one deployable unit. Wallpaper-driven colors flow through the desktop and terminal, with plugin management, backups, and preserved machine-specific settings.
02 About
A short account of how the work gets made, and the three rules it keeps coming back to.
I am Matsuzaka Yuki (松坂ユキ), a student developer and administrator of LyraVoid. I work close to the machine — Android internals, the Linux desktop, and small AI tools that do one thing properly instead of five things badly.
Most of what is on this site began as something I needed and could not find: a patch, a manager, an agent, a place to keep a novel. I like building the version that fits the way I actually work, then keeping the notes in public so the next person can see where the decisions were made.
Nothing here is finished. It is all maintained.
I care about software that is calm to use: honest status, plain language, and failure modes that somebody sat down and designed.
Working rules
01 Local first.
If it can run on the machine in front of you, it should. Less to trust, less to break, and the evidence stays where you can read it.
see the figure in 01 ↘
02 Name the boundaries.
Every piece gets a job and an edge. When the edge is written down, either side of it can change without a rewrite.
the seams show in 03 ↘
03 Ship the small version.
A tool you can hold beats a plan you cannot. Everything after that is iteration, which is the part I actually enjoy.
running in 05 ↘
Still on the bench
03 Stack
An index rather than a scoreboard: the languages, surfaces, and tools the archive actually leans on, mapped back to the entries that use them.
Cross-reference
Core
The languages I reach for first, from device level code to services.
Surface
Where the work has to actually run, and keep running.
Bench
The daily bench: build, version, ship, repeat.
Open
Not a skill list. These are the things currently taking up the margin.
hover a name to find its entry
04 Archive
Prototypes, dead branches, interface studies, and small tools that never needed a name. Fewer rules here than anywhere else on the site.
Experiment log
Opened / Status
Small experiments are still on the bench. Published studies will appear here.
entries get added when something survives the first afternoon.
05 Contact
Find the code, follow the work, or start a conversation on GitHub.
cut here
Channels
From the desk of
Matsuzaka Yuki LyraVoid