mtk-agent-toolkit: Skill for Claude Code

Tech Stack: TypeScript

Overview

TypeScript/JavaScript context for the workflow skills and review agents: commands, detection markers, the data-layer and framework rules that bite (React, React Native/Expo, Next.js, Tauri, Node), settings and scan recipes. Generic framework practice is assumed, not restated. JavaScript-only projects use the same skill; the type rules become recommendations.

When To Use

Loaded automatically when the active tech stack is typescript; never invoked directly.

Build & Test Commands

setup-bootstrap writes the detected package manager to .claude/tech-stack-pm; <pm> below is that value. Detection, first match wins:

if [ -f bun.lock ] || [ -f bun.lockb ]; then echo bun
elif [ -f pnpm-lock.yaml ]; then echo pnpm
elif [ -f yarn.lock ]; then echo yarn
else echo npm   # package-lock.json, or package.json only
fi

• Install: <pm> install
• Type check (compile-equivalent): <pm> run typecheck if defined in package.json, else npx tsc --noEmit --pretty false (or tsc -b for project references)
• Build: <pm> run build (verifies full toolchain — bundler, type check, assets)
• Test (batch): <pm> test <path/to/file> or <pm> run test -- <pattern> (vitest/jest support filter flags; check package.json scripts)
• Test (full): <pm> test or <pm> run test
• Bounded output is the default. Pass --reporter=dot (vitest) or --silent (jest) where the runner supports it. Batch checkpoints run these through bash scripts/mtk-verify-run.sh --label <batch-id>-<step> -- <cmd> — the wrapper's bounded tail is the evidence, the log path is the receipt.
• Format: see ## Format Command.
• Lint: <pm> run lint if defined, else npx eslint <path> or npx biome check <path> based on project config

Tauri (when src-tauri/ exists): from src-tauri/, cargo check (fast) or cargo build, cargo test, cargo fmt, cargo clippy -- -D warnings; full app <pm> run tauri dev / <pm> run tauri build.