TypeScript and JavaScript Engineering Profile
Use this profile only after repository discovery identifies the stack. Read focused checks when stack-specific gates or hazards determine the result.
Workflow
- Discover
package.json, the matching lockfile, workspace configuration, tsconfig files, runtime targets, and repository scripts.
- Follow repository-defined commands and pinned tool versions before suggesting defaults.
- Review idiomatic design and material hazards, especially implicit
any, unsafe assertions, nullability, promise loss, module-system mismatches, environment boundaries, prototype pollution, serialization, and client-server contract drift.
- Select proportionate gates from the selected package manager's repository scripts for formatting, linting, type checking, tests, builds, and dependency or vulnerability review.
- Review compatibility across Node and browser targets, module format, package exports, TypeScript version, generated types, API schemas, bundlers, and lockfile changes.
- Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.
Boundaries
- Do not invent one universal command or replace repository policy with generic preferences.
- Do not install, upgrade, publish, deploy, apply, or mutate shared state merely to run a gate.
- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.
- Separate static review, executed checks, build evidence, provider state, and live behavior.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.
Example
Synthetic example; not an observed client result.
Input: A TypeScript cast suppresses a possible undefined value at runtime.
Output: The cast changes type checking, not runtime behavior. Trace the absent-value path and test the intended fallback or error.
1---2name: stack-typescript-javascript3description: "Reviews TypeScript and JavaScript changes when async code, modules, types, dependencies, or builds need focused checks; uses repository runtimes, lockfiles, and commands."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/stack-typescript-javascript7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-stacks"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# TypeScript and JavaScript Engineering Profile1617Use this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when stack-specific gates or hazards determine the result.1819## Workflow20211. Discover `package.json`, the matching lockfile, workspace configuration, `tsconfig` files, runtime targets, and repository scripts.222. Follow repository-defined commands and pinned tool versions before suggesting defaults.233. Review idiomatic design and material hazards, especially implicit `any`, unsafe assertions, nullability, promise loss, module-system mismatches, environment boundaries, prototype pollution, serialization, and client-server contract drift.244. Select proportionate gates from the selected package manager's repository scripts for formatting, linting, type checking, tests, builds, and dependency or vulnerability review.255. Review compatibility across Node and browser targets, module format, package exports, TypeScript version, generated types, API schemas, bundlers, and lockfile changes.266. Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.2728## Boundaries2930- Do not invent one universal command or replace repository policy with generic preferences.31- Do not install, upgrade, publish, deploy, apply, or mutate shared state merely to run a gate.32- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.33- Separate static review, executed checks, build evidence, provider state, and live behavior.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.4041## Example4243Synthetic example; not an observed client result.4445Input: A TypeScript cast suppresses a possible undefined value at runtime.4647Output: The cast changes type checking, not runtime behavior. Trace the absent-value path and test the intended fallback or error.