What problem does it solve? Choosing and implementing the correct endpoint shape in a Jac server is error-prone: developers misuse walker:pub for simple RPC calls, hit 404/405 errors from missing entry-module imports, and mishandle the response envelope, auth visibility, and file uploads. ## Core Features & Use Cases - Endpoint shape selection: Explains when to use def:pub functions versus walker:pub walkers based on whether the endpoint actually traverses the graph. - REST surface reference: Documents /walker/<name>, /function/<name>, the standard response envelope, @restspec custom routes and methods, and multipart file uploads with UploadFile. - Pitfall guidance: Covers async endpoints, volatile _jac_id values, keyword-argument walker spawns, and the 404/405 import-registration failure mode. - Use Case: When adding a new typed CRUD endpoint to a Jac server module, use this Skill to write it as a def:pub with an explicit return type and register its name in the entry module import so it serves correctly. ## Quick Start Add a public typed list endpoint to my Jac server module and make sure it is reachable over REST.