What problem does it solve?
Native SDK cores are restricted to a deterministic TypeScript subset, so work needing Node built-ins, regexes, JSON, Map/Set, Date, or classes cannot live in src/core.ts. This Skill guides authoring src/services modules that run ordinary static-tier TypeScript behind a typed effect boundary without breaking determinism or compiler rules.
Core Features & Use Cases
- Typed operation surface: Exported service functions become named operations with contract-encodable request/result types, called from the core through generated clients from @native-sdk/services.
- Hermetic npm vendoring: Use native vendor to install exact-version packages into src/services/vendor with hash verification and no network access at build time.
- Streaming, cancellation, and deadlines: Declare streaming operations with emit capabilities, @deadlineMs timeouts, and cooperative cancellation via ServiceCancellation tokens.
- Carrier selection and authority: Choose between the in-process thread pool and the isolated child subprocess carrier, with documented platform matrices and replay behavior.
- Use Case: Move feed-parsing logic that needs regex and JSON out of a deterministic core into src/services/feeds.ts, then call it from update via the generated feedsParse command with typed ok/err message routing.
Quick Start
Ask the assistant to add a new TypeScript service under src/services that parses data with Node built-ins and wire it into the core through the generated typed client.