JovaniPink 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,tsconfigfiles, 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.
- Separate static review, executed checks, build evidence, provider state, and live behavior.
Output
Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.