What problem does it solve? Fullstack Jac apps split code across server endpoints and client components, and wiring them together incorrectly causes silent failures: 405 errors from unregistered endpoints, unresolved Vite imports, un-awaited RPC promises, and stale cached reads. This Skill codifies the exact rules for connecting main.jac, server modules, and client modules so the pieces register and communicate correctly. ## Core Features & Use Cases - Entry module wiring: Register def:pub endpoints and walkers via plain imports in main.jac, and mount the client with def:pub app and [serve] base_route_app. - Two call styles: Choose between function RPC (await save_profile(...)) and walker spawn (root spawn add_task(title=t)), with the argument and return-value rules for each. - Boundary import rules: Apply sv import correctly in client modules, avoid it in main.jac, and understand the 60-second reader cache plus write-then-refetch mutation pattern. - Use Case: You add a new def:pub endpoint to a server module but the client gets 405 Method Not Allowed; this Skill tells you the name must join the entry module's import list and how to verify drift with jac check. ## Quick Start Ask the agent to scaffold the main.jac entry for a new fullstack Jac app with one server endpoint and a client component that calls it.
