Complex capabilities need to stay within the user’s cognitive limits. Workflows, variable references, and input/output logic are intuitive to engineers, but unfamiliar to teachers. Research showed that even a simple node-based prompt workflow was already near the limit most teachers and operators could comfortably understand. Abstracting it further into Skills or configuration files would reduce both clarity and editability.

Content atomization creates a similar tension. Learning depends on context, and over-fragmentation can break continuity. I worked closely with teachers to define the minimum information each page should contain, balancing flexibility, engineering efficiency, and learning flow. The goal of design is not to remove complexity, but to keep it where users can still control it.