Three things: turn model capability into software people actually use, hand repetitive work to automation, and organise scattered information into something searchable. We own the whole chain — requirements, design, implementation, deployment and operations.
Each product gets its own domain and its own site, and every entrance starts here. They solve unrelated problems but share one engineering standard: readable interfaces, explicit boundaries, reversible releases.
Every AI competition, in one catalogue
Turns AI competition notices scattered across dozens of official sites, chat groups and newsletters into one filterable, subscribable, reminder-backed catalogue — so finding a contest stops being manual labour.
A bilingual technical guide to an open-source robot duck
A bilingual technical reference for the open-source bipedal robot Microduck: hardware specs, software architecture, the sim-to-real training pipeline and the OTA update flow — readable in Chinese, readable offline. An independent guide, not an official site.
One sentence in, an animation out
Moves "make a short animation worth watching" out of a video editor and into a browser tab. Describe the idea in one sentence and it comes back ready to publish. Rewrite the copy, change the pacing, trim the length — change that one thing without redrawing the rest.
Leave the desk, keep the session
Coding agents run on your own machine but expect you to sit beside them, waiting for a confirmation, a clarification, a yes. AgentLink brings that link to your phone: follow progress, keep typing, clear approvals — then pick up at the desk where you left off.
Upload a document, get a question bank
Material you already have — PDFs, Word files, scans, photos — is split into individual questions with options, answers and explanations in place. Then drill, sit a timed mock exam, or hand the bank to students and colleagues instead of typing it in.
Information architecture, visual systems and responsive implementation. The stack follows the goal: Vue 3, Astro, or zero-dependency native ES modules with static pre-rendering.
Node services, REST and JSON-RPC contracts, SQLite and PostgreSQL persistence. Contracts get fixed before implementation so nobody has to guess field names during integration.
Local and hosted models wired up with structured output, failure fallbacks and call-level observability. Anything solvable on-device stays on-device.
Playwright browser automation, multi-threaded scheduling, cloud instance orchestration — click-by-click workflows turned into scripts you can re-run.
Multi-source ingestion, de-duplication, incremental updates and retrieval. Agree on the definitions first; otherwise automation only produces bad data faster.
Docker Compose orchestration, a single Nginx ingress, mixed static and dynamic hosting, plus access logs, traffic reporting and event tracking.
What each layer uses today; swapped when a project needs otherwise
| Layer | Choice |
|---|---|
| Front end | Vue 3 · Vite · Astro · native ES modules with static pre-rendering |
| Back end | Node.js 22 · REST / JSON-RPC · SQLite · PostgreSQL |
| AI | Local inference (LM Studio / ONNX Runtime) · structured output · model routing |
| Automation | Playwright · multi-threaded scheduling · cloud service APIs |
| Deployment | Docker Compose · Nginx reverse proxy · read-only static mounts |
| Observability | Access logs · GoAccess traffic reports · first-party event tracking |
Whether you want a new product or want an existing workflow automated, describe the situation directly. Arriving with a concrete problem beats arriving with "we want to use AI".