Run any Skill in Manus with one click

tsz-emit

Stars443

Forks8

UpdatedJune 2, 2026 at 05:23

Write better tsz JavaScript and declaration emit code. Use when changing crates/tsz-emitter, emit transforms, DTS output, source maps, helper scheduling, temp/hoist planning, target/module output, or emit parity tests.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mohsen1

mohsen1/tsz

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	tsz-emit
description	Write better tsz JavaScript and declaration emit code. Use when changing crates/tsz-emitter, emit transforms, DTS output, source maps, helper scheduling, temp/hoist planning, target/module output, or emit parity tests.

TSZ Emit

Use for JS/DTS emit, transforms, helpers, temp/hoist planning, target/module output, source maps, and emit parity tests.

Start

Read AGENTS.md and docs/plan/ROADMAP.md for durable emit/DTS work.
Inspect overlapping emit PRs/issues.
Name the failure family: target gate, module/export schedule, helper, temp/ hoist, region transform, printer layout, DTS nameability/portability, source maps, or parser recovery.
State: When <syntax/output context>, tsc emits X; tsz emits X through <owner>.

Architecture

Emit is OUTPUT: no checker/solver semantic validation in emitter code.
Prefer planned facts before writing text: target/module facts, helper needs, temp reservations, hoists, prologues, exports, resource/disposable regions.
Keep direct-to-target emit; do not introduce an ESNext -> ... -> ES5 pipeline.
No semantic output surgery with replace, replacen, or replace_range. Data cleanup is fine for escaping, source-map paths, numeric separators, and path normalization.
DTS should use declaration summaries/structured emission, not late string rewrites.

Hot Checks

Use writer/list/token/source-map helpers; add delimiter helpers when they prevent real mistakes.
Target/module policy belongs in target/module facts or emit-plan-like owners, not random printer branches.
Every function-like body needs temp scope and hoist strategy. Bypasses of emit_block must still handle function-body flags and insertion points.
Check adjacent shapes: arrows, declarations, expressions, methods, accessors, constructors, async/generator wrappers, static blocks, namespaces/modules, parameter prologues, ES2015+ and relevant legacy targets.

Verification

No full emit/conformance/fourslash locally.

scripts/emit/run.sh --filter=<family> --js-only --verbose --json-out=/tmp/<name>.json
scripts/emit/run.sh --filter=<family> --dts-only --verbose --json-out=/tmp/<name>.json
cargo nextest run -p tsz-emitter <test-or-family>

PR body: AgentName, failure family, structural rule, owner layer, why no semantic validation/output surgery, targeted verification, unsupported shapes.

More from this repository

same repository

tsz-architecture

mohsen1/tsz

Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code. Use when planning semantic fixes, moving logic across query boundaries, handling architecture guard failures, ratcheting boundary debt, or reviewing changes for solver-first and no hardcoding rules.

2026-06-02443

tsz-ci-pr

mohsen1/tsz

Drive TSZ GitHub PRs through review, CI, and the merge queue. Use when checking PR status, debugging failing GitHub Actions, deciding whether a PR is WIP, marking draft PRs ready, enqueueing or verifying the queue, landing a PR, or interpreting TSZ CI gates.

2026-06-02443

tsz-conformance

mohsen1/tsz

Triage and maintain TSZ diagnostic conformance. Use when investigating conformance regressions, accepted-regression drift, fingerprint-only failures, issue creation from conformance data, or focused parity fixes that must preserve the conformance gate.

2026-06-02443

tsz-disk-cache-hygiene

mohsen1/tsz

Prevent TSZ machines and worktrees from running out of disk while preserving useful build caches. Use before creating worktrees, running large builds/tests, diagnosing low disk, cleaning artifacts, deciding whether to delete caches, or recovering space without slowing future Rust/TypeScript builds.

2026-06-02443

tsz-iteration-audit

mohsen1/tsz

Audit TSZ repo iteration speed and quality. Use when asked to deep-dive repo health, identify avoidable delays, improve agent workflows, reduce CI/PR churn, add guardrails, choose skills to install or create, or turn recurring TSZ process failures into focused tooling/docs PRs.

2026-06-02443

tsz-performance-engineering

mohsen1/tsz

Use when planning, implementing, reviewing, or interpreting TSZ performance work, including benchmark regressions, cache/residency changes, timing claims, perf counters, hotspot investigations, OOM/timeout/stack-overflow blockers, or optimization PR evidence.

2026-06-02443

name	tsz-emit
description	Write better tsz JavaScript and declaration emit code. Use when changing crates/tsz-emitter, emit transforms, DTS output, source maps, helper scheduling, temp/hoist planning, target/module output, or emit parity tests.

TSZ Emit

Use for JS/DTS emit, transforms, helpers, temp/hoist planning, target/module output, source maps, and emit parity tests.

Start

Read AGENTS.md and docs/plan/ROADMAP.md for durable emit/DTS work.
Inspect overlapping emit PRs/issues.
Name the failure family: target gate, module/export schedule, helper, temp/ hoist, region transform, printer layout, DTS nameability/portability, source maps, or parser recovery.
State: When <syntax/output context>, tsc emits X; tsz emits X through <owner>.

Architecture

Emit is OUTPUT: no checker/solver semantic validation in emitter code.
Prefer planned facts before writing text: target/module facts, helper needs, temp reservations, hoists, prologues, exports, resource/disposable regions.
Keep direct-to-target emit; do not introduce an ESNext -> ... -> ES5 pipeline.
No semantic output surgery with replace, replacen, or replace_range. Data cleanup is fine for escaping, source-map paths, numeric separators, and path normalization.
DTS should use declaration summaries/structured emission, not late string rewrites.

Hot Checks

Use writer/list/token/source-map helpers; add delimiter helpers when they prevent real mistakes.
Target/module policy belongs in target/module facts or emit-plan-like owners, not random printer branches.
Every function-like body needs temp scope and hoist strategy. Bypasses of emit_block must still handle function-body flags and insertion points.
Check adjacent shapes: arrows, declarations, expressions, methods, accessors, constructors, async/generator wrappers, static blocks, namespaces/modules, parameter prologues, ES2015+ and relevant legacy targets.

Verification

No full emit/conformance/fourslash locally.

scripts/emit/run.sh --filter=<family> --js-only --verbose --json-out=/tmp/<name>.json
scripts/emit/run.sh --filter=<family> --dts-only --verbose --json-out=/tmp/<name>.json
cargo nextest run -p tsz-emitter <test-or-family>

PR body: AgentName, failure family, structural rule, owner layer, why no semantic validation/output surgery, targeted verification, unsupported shapes.