Development & Writing Skills

Expert on Aptos Framework (0x1 standard library) - account, coin, fungibleasset, object, timestamp, table, event, vector, string, option, error, and other core modules.

Set up and maintain Tesseron integration in a JS/TS project. Picks the right consumer package (@tesseron/react for React, @tesseron/server for Node, @tesseron/web for any other browser context), installs it with the project's existing package manager, ensures a Standard-Schema validator is present, and inserts the canonical Tesseron API — tesseron.app(...), at least one action, at least one resource, tesseron.connect(...) — at module scope of the entry point. Also handles integration maintenance: switching consumer packages, upgrading @tesseron/ versions in lockstep, splitting a multi-surface app into multiple app.id values, or removing Tesseron. Strictly scoped to Tesseron concerns — does not create projects, scaffold build tooling, pick framework versions, or template framework-specific integration code (reactive primitives, component patterns, lifecycle hooks). Use when the user says "add tesseron", "integrate tesseron", "wire up @tesseron/web" / "/react" / "/server", "upgrade tesseron", "switch to @tesseron/react", "split this into two tesseron apps", or opens a project without @tesseron/ yet and wants to start using it.

Authoritative Tesseron documentation lookup via the @tesseron/docs-mcp MCP server. Calls searchdocs to find relevant pages and readdoc to fetch the full markdown body when the user asks precision questions about Tesseron protocol or SDK behaviour. Triggers on requests that need an exact spec, not an overview — wire format (JSON-RPC envelopes, tesseron/hello, tesseron/welcome, tesseron/resume, actions/progress, actions/cancel), transport framing, handshake and claim-code flow, session resume and resumeToken, lifecycle transitions, sampling contract, elicitation contract (ctx.confirm, ctx.elicit), progress + cancellation via AbortSignal, error codes (TesseronErrorCode, SamplingNotAvailableError, ElicitationNotAvailableError, TimeoutError, CancelledError, ResumeFailedError), capability negotiation, origin allowlist, multi-app namespacing, MCP gateway config, Standard Schema (Zod, Valibot, Typebox) integration, action-builder steps, resource read/subscribe, React hook semantics. Use phrases like "what error code does X return", "what does tesseron/hello look like", "exact handshake shape", "resumeToken flow", "gateway origin allowlist", "show me the spec for", "what fields does X accept". The framework skill handles orientation and the mental model; tesseron-docs handles chapter-and-verse questions.

Maps existing Tesseron TypeScript codebases — catalogs apps, actions, resources, context-method usage, transports, React hooks, and session-lifecycle wiring; traces how agent invocations flow through handlers into app state; returns a compact architecture summary with file:line references. Use PROACTIVELY when the user asks to "explore", "map", "understand", "analyze", "trace", or "explain how this works" in a project that imports from @tesseron/core, @tesseron/web, @tesseron/server, @tesseron/react, or @tesseron/mcp, or before extending a non-trivial Tesseron codebase. The caller should pass the scope (project root, package, or specific feature) in the invocation prompt.

Reviews Tesseron TypeScript code for framework- and protocol-specific correctness — app manifest hygiene, action/resource builder invariants, ActionContext capability checks, handler async/signal forwarding, subscriber cleanup, session resume flow, React hook registration patterns, gateway origin-allowlist sanity — using confidence-based filtering. Use PROACTIVELY after any change to Tesseron code, before commit or PR, and whenever the user asks to review, audit, check, or validate code that imports from @tesseron/core, @tesseron/web, @tesseron/server, @tesseron/react, or @tesseron/mcp. Complements generic code review by focusing only on Tesseron-specific concerns. The caller should pass the scope (diff, file paths, or module) in the invocation prompt.

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.