zo-space

Standardizes Zo.space route creation and debugging for SPA pages and Hono APIs.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill zo-space-uniquecrete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zo-space
Source: https://github.com/Uniquecrete/ThinkFasterv1/tree/main/Skills/zo-space
Command: npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill zo-space-uniquecrete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents broken zo.space pages and fragile API behavior by giving a single, authoritative reference for how routes are structured, built, and deployed in the Zo space runtime.

Core Features & Use Cases

  • Route creation and management workflow: Use the provided tooling to list, fetch source code, update, and delete page/API routes safely.
  • Correct implementation for page vs API routes: Know the required defaults (React component vs Hono handler), visibility rules, and method-handling behavior for APIs.
  • Build, runtime, and failure debugging guidance: Understand when Vite rebuilds will break all pages, how to check errors, and the practical restart/crash-loop workflow.
  • Standards for packages and styling: Use the pre-installed Bun/Node packages and Tailwind semantic tokens consistently to avoid runtime surprises.

Quick Start

Read this guide, then update your route using the space route update tool for the exact path and route type you are building or debugging.

Frequently Asked Questions about zo-space

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and debug zo.space routes for React pages and Hono API endpoints?

To create and debug zo.space routes, use the standardized space route update tool to define React component defaults for pages or Hono handlers for APIs, ensuring correct method handling and visibility behavior to prevent runtime misconfigurations.

Why does my Vite build break all zo.space pages at once?

Vite build failures break all zo.space pages because the update_space_route build pipeline recompiles the entire project, requiring you to check error diagnostics and resolve the failing module before restarting the deployment workflow.

What's the best way to structure Hono API routes in a Bun runtime environment?

The best way to structure Hono API routes in a Bun runtime is to export default Hono handlers with explicit method handling, adhering to the zo.space functional contract to avoid fragile API behavior and deployment failures.

Do I need to install additional packages for Tailwind styling in zo.space routes?

You do not need to install additional packages for Tailwind styling in zo.space routes because the runtime pre-installs Bun and Node packages, allowing you to consistently apply Tailwind semantic tokens without runtime surprises.

How does zo.space handle route visibility and default exports for SPA pages?

zo.space route visibility and SPA page rendering rely on default exports of React components, where the functional contract enforces specific visibility behavior rules to ensure deterministic route management across the Vite and React stack.