메뉴
Author or debug TypeScript transformations for cached rote responses and TypeScript flows. Use for `FlowOutput` shape, deterministic response handling, `rote deno` execution, and tests before returning to flow authoring or workspace work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | rote-typescript-transformations |
| description | Author or debug TypeScript transformations for cached rote responses and TypeScript flows. Use for `FlowOutput` shape, deterministic response handling, `rote deno` execution, and tests before returning to flow authoring or workspace work. |
All rote-<name> references in this document — including every name in the Handoff
Contract — are companion skills, never CLI commands (rote-shell is not rote shell).
Invoke them through the runtime's skill mechanism; only literal rote … commands run in a
terminal.
Use this skill when cached rote responses need TypeScript transformation or a TypeScript flow body is
being authored. rote grammar deno and rote guidance typescript essential remain the source of
truth for execution syntax and SDK import forms.
This is a helper skill, not a lifecycle owner. Return to rote-flow-authoring or rote-workspace
after the transformation is implemented and tested; do not stop here when release, index/search
verification, pending cleanup, or final presentation is still outstanding.
steps: block, through
rote deno run --allow-all.steps: through rote flow run. Raw deno skips the
effect plane and provides no presentation input; rote deno run reroutes steps: flows to the
flow runner, but do not rely on the reroute — use rote flow run directly.deno directly.~/.rote/bin/; use rote on PATH.Typical execution:
rote deno run --allow-all /absolute/path/to/main.ts [args]
Use SDK imports exactly as shown by live rote guidance. Avoid npm-style package assumptions unless the current rote version explicitly supports them.
When a transformation can be expressed clearly with jq, prefer rote query @N '<jq-filter>' -r and return
to rote-workspace. Use TypeScript when the task needs richer validation, grouping, date handling,
joins, cross-response merging, or formatting than jq should carry.
Keep transformations deterministic:
Design FlowOutput for future agents as well as humans:
summary for the short answer.data or domain-specific fields for machine-readable results.warnings for partial, skipped, or best-effort outcomes.If the transformation is part of a reusable flow, return the proposed FlowOutput shape to
rote-flow-authoring before release.
Test with representative cached data or fixture input before release. Cover no-result,
partial-result, malformed/optional fields, and at least one user-provided edge case. After changes,
rerun legacy TypeScript through rote deno run --allow-all and flows with frontmatter steps:
through rote flow run, rather than a standalone TypeScript runner.
If a cached response query fails, inspect the cached response first. If the response is an adapter error, fix the upstream call, auth, base URL, or arguments before adding transformation workaround code.
Return these fields to rote-flow-authoring or rote-workspace:
FlowOutput shape and warnings contract.rote grammar deno guidance can be checked or its blocker is known.FlowOutput shape, and transformation-specific test expectations.rote-flow-authoring for flow lifecycle/release; rote-workspace for additional
adapter calls or cached response queries; rote-command-patterns for command syntax; rote-troubleshooting
after repeated unchanged failures.rote-flow-authoring or rote-workspace with transformation path, output shape, tests,
and blockers.Use for browser automation through rote: browsing websites, attaching to active Chrome or Edge sessions, Gmail or other logged-in sites, headed/headless exploration, snapshots, readiness waits, page slices, ref rebasing, and crystallizing browser flows. Prefer rote browser primitives over direct Playwright calls.
Create, edit, test, lint, release, verify, or publish reusable rote flows. Use for reusable contract elicitation, rote-driven schema discovery, scaffold/test/release/search lifecycle, and registry handoff.
Use for CLI and shell work through rote when command output, files, logs, process state, dependency checks, mixed API/browser evidence, or crystallized CLI flows must be remembered, queried, replayed, or shared.
Use when executing a task through one installed rote adapter, especially in a delegated subagent or adapter-specific helper. Applies after the main rote skill has selected an adapter for a single-adapter workflow.
Tune an existing rote adapter — auth, base URL, write guard, sensitivity, capability index, OAuth re-auth, GraphQL field filter, policies, adapter guidance, grouping, versioning. A menu of small show → confirm → apply → re-show operations on an adapter you already created. Use when the user says "configure <adapter>", "change the base url", "re-auth notion", "rebuild the capability index", "enable an auth scheme", or "set up sensitivity / write guard". For creating a NEW adapter, use rote-adapter-create instead.
Create a rote adapter for any API — dry-run-first. Discovers the spec (built-in catalog → web search → local file), analyzes it without committing (`rote adapter new <id> <spec> --dry-run`), then pre-fills auth, base-url, and toolset choices from the analysis — asking you only where it's genuinely ambiguous. When auth is ambiguous or low-confidence, researches the provider's docs to recommend a scheme and produce setup steps (API key / OAuth2). Use when the user says "add an adapter", "connect to <API>", "create a stripe/notion/datadog adapter", "build an adapter from this OpenAPI spec". Never creates from a discovered spec without a clean dry-run first. Hands off to rote-adapter-config for tuning afterward.