TAHAI operational skins · product direction
Skins are operational. Period. The goal is not another coat of paint. It is a browser surface you can shape around how you learn, create, compare, plan, and get things done.
The idea behind the skin
“Skin is the operational layer for our bodies’ interaction with the external world. Do more than change the look, redefine your operational layer.”
A TAHAI skin should shape your interaction with the web: the way it looks, the way your space is arranged, and the way your chosen tasks flow. The design belongs to you. Permission to act on a website remains a separate decision.
This is the model we are building toward. The existing v1 package stays compatible as an appearance-only foundation; operational capabilities require the expanded format and runtime.
Colors, artwork, typography, spacing, and visual identity. Personal expression remains part of the experience—not its ceiling.
Live page panes, panels, command placement, and responsive layouts, with keyboard access and a clear way to recover.
Your named activities, start surfaces, workspace templates, and useful commands. Work Modes belong inside the broader operational design.
Your instructions, inputs, steps, checkpoints, and reviewed actions, with clear progress and safe pause, resume, and recovery.
Explicit grants for requested browser or website operations. Installing artwork or a layout must not authorize private-data access, sending, publishing, or account changes.
The creator experience we are building toward
The goal is local creation, use, and file sharing without requiring a TAHAI account. Connected services still have their own authentication and permission requirements.
For everyone
A classroom, a personal planning space, a shopping comparison, a research desk, a creative studio, an accessible focus environment, or an operations console. The websites and services are yours to choose. TAHAI services are optional—not the definition of what a skin can do.
Explore everyday possibilities →The public creator kit includes starter artwork, supported appearance fields, a sample skin, an offline color Studio, and build instructions. It does not yet provide the complete operational surface editor, workflow runtime, custom widgets, or external action system described above.
The kit is hosted on GitHub. It is a creator resource, not a browser installer. Check your installed browser’s skin-format support before importing a package.
Read the included README and authoring documentation before editing the starter.
Use the supplied fields and artwork rules. Do not add operational fields and expect v1 to execute them.
Follow the kit’s tooling and retain the original starter so you can compare and recover your changes.
Check import, appearance, preview, and reset using a browser version that supports the format.
Control is part of the design
The expanded operational model must keep the browser’s address, identity, permission, and security controls recognizable and reachable. It must let you review requested capabilities, revoke access, and return to a safe layout.
Sharing a skin must not silently share signed-in sessions, workspace URLs, entered values, credentials, or private run history. A rollback restores a design; it cannot automatically undo an action already taken on a website.
Follow the work
Operational skins are the product direction, not a claim that the whole system has shipped. Current v1 creator resources, development source, and published browser packages have different capabilities. Check the version you install.
Share a use case, a creator idea, or a reproducible issue—without including private data.
Share your feedback ↗