Skip to content
View karote00's full-sized avatar

Block or report karote00

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
karote00/README.md

I build systems that make complex things easier to change.

Asa Tsai · Software architect · Taipei

10+ years building frontend systems, design tools, and the architecture behind them.

I keep coming back to one question: why should adding one feature require understanding the whole application?

Years before Asyra, I proposed this direction at my previous company. It wasn't adopted, but the idea stayed with me. After leaving, I wrote it down as Communication-Driven Development (CDD): start with what needs to be communicated, and make responsibilities clear to both the system and the people building it.

Asyra grew out of those principles. I'm building it so the next person can understand, change, and extend a product without needing me beside them.

Read the CDD docs · Docs on GitHub

One foundation. Different worlds.

Asyra handles the shared infrastructure: editable state, transactions, Undo/Redo, and clear ownership. Each app brings its own rules and its own world.

Design

A canvas editor with editable vectors, Undo/Redo, and optional AI and collaboration. A working product built on the same foundation.

Asyra Design: an editable cat drawing inside the canvas editor

Try the editor · Source · Follow the architecture

Simulation

I'm starting with a robot workcell to build the architecture for a larger goal: simulating factory processes, including semiconductor fabs, to find problems before they happen on the floor. Over time, I want to bring my earthquake engineering background into building and factory safety analysis too. The current workbench explores geometry, clearance, and motion; it's an early development checkpoint.

Asyra Sim: a robot workcell in the experiment workbench

Try the workbench · Source

FieldScope

A greenhouse modeling workspace with structures, crops, and a robot concept. The scene exists; patrol and harvesting simulation are still ahead.

FieldScope: a modeled greenhouse with crop rows

Explore the greenhouse · Source

Make it easier to pick up the work.

The same question shows up in my other tools:

  • handoff-ai keeps project knowledge available across people, agents, and sessions.
  • context-rag finds the project context an agent needs for the task at hand.
  • local-leetcode-trainer brings coding practice and AI guidance into a local workflow.

I care about clear boundaries, predictable changes, and leaving enough context for whoever comes next. A good demo gets my attention. Being able to keep changing it is what makes me stay.


Taipei, Taiwan · Remote collaboration

Let's talk on LinkedIn · Read the Asyra docs

Popular repositories Loading

  1. local-leetcode-trainer local-leetcode-trainer Public

    A complete offline LeetCode practice environment with multi-language support - practice anywhere, collaborate with AI, submit with confidence

    JavaScript 59 9

  2. asyra asyra Public

    Composable framework for canvas-based, visual, and domain-driven products.

    TypeScript 46 2

  3. handoff-ai handoff-ai Public

    JavaScript 45

  4. react-board react-board Public

    Demo

    JavaScript 15 1

  5. context-rag context-rag Public

    A lightweight CLI tool for semantic search (RAG) on project context, with branch-aware caching and AI integration.

    JavaScript 7 1

  6. html-3DCube html-3DCube Public

    Demo

    JavaScript 6