AGENT SKILL

typescript-dev

Use before writing or explaining strict TypeScript, and before writing a bun:test file: our own types validated where data is mapped into them, narrowing instead of casting, Result instead of throwing, branded types, using for cleanup, the compiler-cost traps (interface vs intersection, const enum, tsgo), and the bun:test idiom. Triggers: writing TypeScript, idiomatic TS, type narrowing, discriminated union, branded type, Result type, parse JSON into a type, tsconfig strictness, interface vs type, const enum, tsgo, TypeScript 7, write a test in bun test, describe and it, mock in bun test, run only this test. Bun runtime APIs are bun-dev; which cases to test is software-testing.

License 许可
GPL-3.0
最近更新
2026-11-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
typescript-dev
description
Use before writing or explaining strict TypeScript, and before writing a bun:test file: our own types validated where data is mapped into them, narrowing instead of casting, Result instead of throwing, branded types, using for cleanup, the compiler-cost traps (interface vs intersection, const enum, tsgo), and the bun:test idiom. Triggers: writing TypeScript, idiomatic TS, type narrowing, discriminated union, branded type, Result type, parse JSON into a type, tsconfig strictness, interface vs type, const enum, tsgo, TypeScript 7, write a test in bun test, describe and it, mock in bun test, run only this test. Bun runtime APIs are bun-dev; which cases to test is software-testing.

03 SKILL.md 正文

Writing TypeScript

Strict TypeScript for this machine, typed with our own types: a value with rules gets a type that validates once, where outside data is mapped into it, so code past that line holds a value that cannot be invalid. The compiler and lint gate reject the rest; this skill holds the choices they cannot make. Out of scope: a tutorial, Bun APIs (bun-dev).

The gate: qsm-langdev init writes tsconfig.qsm.json and .oxlintrc.json, which require strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, verbatimModuleSyntax, ?? over ||, no any flowing into a typed value, and every promise awaited; oxfmt formats. Write against them; do not restate them in code or prose. A repository may opt into isolatedDeclarations (explicit return type on every export) and erasableSyntaxOnly (no enums, no namespaces with code, no parameter properties).

Our own types, validated at the mapping

A string that is an email, a number that is an age, an id that must not be swapped: each gets its own type, built by one parse function that is the only place the rule is written and the only cast. The mapping from unknown is where it fails, with a named error, so nothing past it re-checks.

type Email = string & { readonly __brand: "Email" };
class InvalidEmail extends Error { override readonly name = "InvalidEmail"; }
const parseEmail = (raw: unknown): Result<Email, InvalidEmail> =>
  typeof raw === "string" && /^[^@\s]+@[^@\s]+$/.test(raw)
    ? { ok: true, value: raw as Email }
    : { ok: false, error: new InvalidEmail(String(raw)) };

The record that holds the parsed fields is a plain type built from those values, never JSON.parse(raw) as User. A closed set ("free" | "pro") is a literal union checked at the same place. Parse the environment once at startup the same way.

Rules

  • Narrow with a type predicate, never cast, because a cast moves the crash to run time. Close every union with assertNever(x: never), so a missing arm is a compile error.
  • Narrow a catch binding (unknown) with instanceof Error, and rethrow with { cause: err }.
  • Return { ok: true; value } | { ok: false; error } for a failure the caller handles; throw only for what nobody can handle, because a throw is invisible in the type. Give a domain failure its own class with a name.
  • Make a state with behaviour its own type, not an enum, because an enum cannot own its transitions.
  • Use using and await using instead of try/finally for a resource with an owner.
  • Use interface ... extends over an intersection, because it is cached and gives shorter errors.
  • Never use const enum; use { Up: "Up" } as const plus (typeof X)[keyof typeof X], because esbuild, swc, Bun and tsgo cannot inline it across files.
  • Before moving to tsgo (TypeScript 7), turn on isolatedModules, because tsgo checks files in isolation and code that compiles only through tsc's cross-file inference breaks. A TS6xxx deprecation in 6.x is a blocker, and an orphaned references[] entry now errors.

Tests in bun:test

One file per unit, order-service.test.ts, with test data that shows only what matters, built by a small factory (aUser({ active: false })), because a shared twenty-field fixture breaks fifty tests at once. Whether a test is needed is software-testing.

  • Import describe, it, expect from bun:test, never rely on globals. describe names the unit, it the case as a sentence, two levels at most.
  • beforeEach builds fresh state; beforeAll only for expensive read-only setup, because mutated shared state is the first flaky test.
  • it.each with the row in the title, so the report says which input failed.
  • await expect(p).rejects.toThrow("msg"); an unawaited promise passes before it fails.
  • Pass a dependency in rather than mock.module, which replaces a module for the whole file; spyOn wraps one method, and mock.restore() goes in afterEach.
  • setSystemTime(date) around code that reads the clock, setSystemTime() after, never Bun.sleep to wait for time.
  • Run one file bun test order-service, one test bun test -t "rejects payment".

Red flags

  • When a test still passes with the code under test deleted, assert the result, because it proves nothing.
  • When a string or number carries a domain meaning past the parse, give it a type, because the next caller will pass the wrong one.

Say it in the reply

When you avoided a cast, an enum or a throw, say what replaced it, and name the one place each value is validated. For a test file: file, count, and the command that runs it.

04 同仓库更多 Skills

qsmark-labs
qsmark-labs/qsm-marketplace

worktrunk

Use when working with git worktrees or wt (worktrunk): creating, switching, merging or removing a branch workspace, configuring wt (project or personal config, workflow hooks around switch, commit and merge, commit-message generation, hook approvals), or a wt command that failed. Triggers: make a worktree for this branch, wt merge, wt remove, configure wt, .config/wt.toml, run tests before merge, install deps when a worktree is created, wt hook, wt switch does not cd, nastav wt, wt nefunguje.

★ 0
qsmark-labs
qsmark-labs/qsm-marketplace

web-ladder

Use when a task needs something the internet holds: look something up, search the web, find which page answers a question, read a page, check a library's current docs, a page that needs a browser or shows a captcha. Runs one research loop: searxng search, keywords, cases, search again up to three times, Context7 for a library, Tavily when the keywords will not come, one page in a browser, the person on a wall. Triggers: look this up, search the web, find out online, read this page, check the docs, the page is blocked, captcha, najdi na webu, otevri tu stranku. A multi-round question goes to the qsm-web:web-research agent; one tool's commands are its own skill (searxng, browserbox, opensrc).

★ 0
qsmark-labs
qsmark-labs/qsm-marketplace

searxng

Use when running a web search through the person's own SearXNG instance with qsm-web searxng: choosing a search profile or engines, the instance, time range or language, reading its JSON, a suspended engine. Triggers: search with searxng, qsm-web searxng, search profile, niche search, academic search, IT search, vyhledavaci profil, searxng is down, which engines. The research loop around it is the web-ladder skill.

★ 0
qsmark-labs
qsmark-labs/qsm-marketplace

opensrc

Use when the source code of an open-source library or repository is needed on disk to read: the docs are silent, the behaviour must be checked in code, the version the project pins. Runs qsm-web opensrc get with a package spec or a repository address. Triggers: get the source of this package, clone this library, read the library's code, qsm-web opensrc, stahni zdrojak knihovny. Library docs are the Context7 skill; the research loop is the web-ladder skill.

★ 0
qsmark-labs
qsmark-labs/qsm-marketplace

browserbox

Use when one page needs a real browser through qsm-web browserbox: content built by script, a page that blocks plain fetching, a captcha to solve or hand to the person, a scripted sequence of clicks, a login the person is present for. Triggers: open it in a browser, the page is empty without JavaScript, captcha, take over the browser, run these steps on the page, log in to this site, browserbox. When to reach for a browser at all is the web-ladder skill.

★ 0
qsmark-labs
qsmark-labs/qsm-marketplace

usage

Use when the user wants a review of how they use Claude Code, or setup hands over after a first install: review my Claude Code usage, audit my setup, what does my setup cost, where did my tokens go, clean up my Claude Code, usage report, zkontroluj moje pouzivani. One walkthrough of four stages (machine, work, habits, extensions), questions after each, then one plan. A question about one topic (which hooks are slow) goes to that topic's skill; this session's tokens alone is `/qsm-usage`.

★ 0