zo-space

Standardize zo.space page and API route creation with build and runtime debugging.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ankitjh4/skill-builder --skill zo-space-ankitjh4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zo-space
Source: https://github.com/ankitjh4/skill-builder/tree/main/zo-space
Command: npx skills add https://github.com/ankitjh4/skill-builder --skill zo-space-ankitjh4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents broken zo.space page and API routes by guiding you through the platform’s architecture, route conventions, build pipeline, and common failure modes.

Core Features & Use Cases

  • Route authoring without guesswork: Create page routes (React/TSX) and API routes (Hono handlers) with the correct default exports and routing rules, including visibility behavior.
  • Build-and-runtime debugging workflow: Diagnose issues by checking route errors, understanding when Vite rebuilds all pages, and knowing how API route loading differs from page rendering.
  • Operational safety for route updates: Avoid gotchas like reserved routes, lack of hot reload, single-file page constraints, and environment-variable placement (server-side API vs client-side pages).

Quick Start

Use the zo-space skill to create or update a zo.space route by following its route-type requirements and then confirm correctness by checking get_space_errors() after the update.

Frequently Asked Questions about zo-space

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

FAQPage Schema
How do I fix route building errors in zo.space pages and Hono API endpoints?

Diagnose zo.space routing failures by verifying default exports in React pages, using app.all() for Hono API methods, and checking get_space_errors() after updates to catch build pipeline issues.

Why does Vite rebuild all my zo.space pages when I edit a single route?

Vite rebuilds all zo.space pages during updates due to single-file page constraints and lack of hot reload. Verify route correctness post-update by checking get_space_errors() for build pipeline failures.

How do I create zo.space API routes with Hono correctly?

Create zo.space Hono API routes by implementing app.all() for method handling and ensuring correct default exports. Follow SKILL-driven route visibility conventions and verify correctness using get_space_errors() after updates.

What are the limitations when updating zo.space React page routes?

zo.space React page route updates are limited by single-file constraints, lack of hot reload, and reserved routes. Place environment variables server-side for API routes and client-side for pages to avoid failures.

How do I check for zo.space route visibility and runtime errors after updates?

Verify zo.space route visibility and runtime errors using get_space_errors() after updates. This confirms correct default exports, app.all() API handling, and compliance with mandatory route conventions.