[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXZ7T2DFG9GYG6453WX2GF":3,"skill-same:01M6BXZ7T2DFG9GYG6453WX2GF":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":48,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6BXZ7T2DFG9GYG6453WX2GF","studio-typescript",null,"Use when building, checking, linting, formatting, or configuring a TypeScript project with @jterrazz\u002Ftypescript, such as build\u002Fdev\u002Fstart\u002Fmutation, a failing `typescript check` pass, the kind and platform of `studio.config.ts`, its presets and tool settings, the derived editor files, the baseline (`.studio\u002Fbaseline.json`), writing a rule with `@jterrazz\u002Ftypescript\u002Frules`.","jterrazz\u002Fpackage-typescript","jterrazz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F18480834?v=4","01M6BXZ37DPSKSVP6HRWNQQX76","Jean-Baptiste Terrazzoni","01M6BXZ3C7453E0F4T57B303HD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fskills\u002Fstudio-typescript\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38],"typescript","studio typescript","writing","editor","config","dev","start","baseline","tool","json","2026-11-10 10:12:30",false,"---\nname: studio-typescript\ndescription: Use when building, checking, linting, formatting, or configuring a TypeScript project with @jterrazz\u002Ftypescript, such as build\u002Fdev\u002Fstart\u002Fmutation, a failing `typescript check` pass, the kind and platform of `studio.config.ts`, its presets and tool settings, the derived editor files, the baseline (`.studio\u002Fbaseline.json`), writing a rule with `@jterrazz\u002Ftypescript\u002Frules`.\n---\n\n# @jterrazz\u002Ftypescript\n\nOne devDependency that builds, checks, lints and formats a project. The manual is the package's `docs\u002F`, read from the install (`node_modules\u002F@jterrazz\u002Ftypescript\u002Fdocs\u002F`) or from this repository when the toolchain itself is the change. This page decides what to run and which page to open; the page owns the rule.\n\n## What to run\n\n| Gesture                  | When                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |\n| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| `typescript fix`         | before every commit: lint fixes, formatting, `.gitignore`, spellings, empty directories                                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| `typescript check`       | the gate: every pass in parallel, then the drift report; a tree already proven green answers from `.artifacts\u002Fproven\u002F` and runs nothing, `--cold` runs it (`docs\u002Freference\u002Fquality-checks.md`, A tree proven green)                                                                                                                                                                                                                                                                                                            |\n| `typescript test`        | the `make test` recipe: the project's `test` script over the test files the change reaches by the last mutation record, every file where it cannot tell (`docs\u002Freference\u002Fquality-checks.md`, The test files a change reaches), answered from its proof like `check`                                                                                                                                                                                                                                                            |\n| `typescript build`       | what the manifest publishes into `dist\u002F`: ESM + types, CJS where a target is `.cjs`                                                                                                                                                                                                                                                                                                                                                                                                                                            |\n| `typescript mutation`    | Stryker over a sandbox copy; fails on a mutant a test runs and lets live (the module tests over the change, then the whole suite over what they let live and the changed lines; domain at zero survivors, glue at its bar; the text of a file `typescript.mutation.presentation` declares never mutated; `--since`, `--mutate`, `--report html` for the HTML report a person browses; its test runners sized from the machine, `TYPESCRIPT_CAPACITY` to give it one); a survivor to answer: `docs\u002Fguides\u002Ftriage-a-survivor.md` |\n| `typescript doctor`      | first read after a bump: installed tools against the declared ranges, then every setting beside the file it comes from                                                                                                                                                                                                                                                                                                                                                                                                         |\n| `typescript baseline`    | a bump lands red: record today's counts, exact; `fix` lowers one that fell                                                                                                                                                                                                                                                                                                                                                                                                                                                     |\n| `typescript docs-layout` | a repository with no npm project: the manual's shape, alone                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| `typescript gate-lock`   | before an install or a pack: refuses while a running gate holds the checkout, naming its pid                                                                                                                                                                                                                                                                                                                                                                                                                                   |\n| `typescript rehearse`    | before a tag: the gate on Linux, in Docker, on a fresh clone of the branch, as the runner runs it (`docs\u002Freference\u002Fcommands.md`)                                                                                                                                                                                                                                                                                                                                                                                               |\n\n`typescript \u003Ccommand> --help` prints a command's flags and runs nothing; a flag it does not read, or one given twice, is refused before anything is written (`docs\u002Freference\u002Fcommands.md`).\n\nA project declares its `kind` (`library`, `api`, `cli`, `website`, `mobile`) and its `platform` (`node`, `bun`, `react`, `next`, `astro`, `expo`) in `studio.config.ts`, `defineConfig({ kind, platform })`; the profile, the tsconfig preset and every law follow. A monorepo is no kind: its root `package.json` lists `workspaces`, is `private`, and its `studio.config.ts` holds the repository's settings and no kind, or is absent; each member declares its own. `oxlint.config.ts`, `oxfmt.config.ts` and `tsconfig.json` are derived (the first two hand their own `import.meta.url` to `oxlintConfig` \u002F `oxfmtConfig`), and `typescript fix` writes them; every tool setting lives in `studio.config.ts`, and no `knip.json`, `tsdown.config.ts` or `stryker.config.*` is kept. A repository root also owes a `Makefile` of six gestures and a `docs\u002F` manual its `CLAUDE.md` routes to. The whole wiring, from an empty folder to a green run, is `docs\u002Fstart\u002Fgetting-started.md`.\n\n## What a failing pass means\n\nEvery pass that ran prints a `RUN` header and one verdict with its seconds; a pass that did not apply prints nothing. The run's last line names the first failing pass and its first finding, and `.artifacts\u002Fgate\u002Fverdict.json` holds every pass's status for a reader that should not parse the log, for `check`, `fix` and `mutation` alike (`docs\u002Freference\u002Fquality-checks.md`, The verdict file). Each rule id below is explained in `docs\u002Freference\u002Fquality-checks.md`, under the pass's own section. On a GitHub runner the run prints a line per pass, each finding as rule and place, found, `fix` and `read`, and an annotation each (`docs\u002Freference\u002Fquality-checks.md`, On a GitHub runner).\n\n| Pass                             | It failed because                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |\n| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Config (one file)                | `studio.config.ts` declares no valid kind and platform, a derived file says something else (`typescript fix`), a tool keeps its own config, the manifest does not match the kind, or a `src\u002Fstandard\u002F` computes                                                                                                                                                                                                                                                                                                                       |\n| TypeScript Check                 | tsc 7 refused a type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |\n| Oxlint Check                     | a rule fired that `.studio\u002Foxlint-suppressions.json` does not hold: fix it, or `typescript baseline`; a recorded count fell: `typescript fix`; an oxlint rule is left in `.studio\u002Fbaseline.json` (`baseline-moved-to-oxlint`): `typescript baseline`; a directive suppresses nothing (`Unused oxlint-disable directive`, `reportUnusedDisableDirectives`): delete it; a `@ts-ignore` or an undescribed `@ts-expect-error` (`typescript\u002Fban-ts-comment`)                                                                               |\n| Oxfmt Check                      | a file is not formatted: `typescript fix`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |\n| Gitignore (artefacts)            | an artefact is named or committed outside `.artifacts\u002F\u003Ctool>\u002F`                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| Knip (unused code)               | a file, export or dependency nothing uses                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |\n| a preset's label                 | a preset's checks refused, `@jterrazz\u002Ftest`'s conventions among them; the preset's own manual owns the id                                                                                                                                                                                                                                                                                                                                                                                                                             |\n| Docs (layout)                    | the repository's `docs\u002F` breaks the manual's spine, or holds a generated `reference\u002F`                                                                                                                                                                                                                                                                                                                                                                                                                                                 |\n| Publish (packaging)              | the `exports` map promises a file the tarball does not carry, or a shipped file is compiled from test material                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| Architecture (layer map)         | an import crosses a layer of a preset (the standard's `lint\u002F` direction included), of `typescript.architecture` or of the project's own `.dependency-cruiser.*` (`architecture\u002F\u003Cname>`, at its line); a recorded `architecture\u002F\u003Cname>` count grew (`typescript baseline`) or fell (`typescript fix`); the map does not load or has nothing to cruise                                                                                                                                                                                  |\n| Astro (check + format)           | `astro check` or prettier refused a `.astro` file                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |\n| Suppressions (directives)        | a lint directive is misspelled or unreasoned                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |\n| Comments (styles, scripts, YAML) | a comment of a style sheet, a script, a Makefile, a Dockerfile or a YAML file states no kind: give it one, or delete it by hand, since `typescript fix` deletes no comment                                                                                                                                                                                                                                                                                                                                                            |\n| Markdown (prose)                 | rumdl refused a page (`markdown\u002Flink-resolves` a missing link, `MD051` a missing anchor, `MD040` a fence with no language: `typescript fix`), a page cites a path that is gone, a block runs past its limit, a skill's frontmatter is no YAML or lacks its name or description (`markdown\u002Fskill-frontmatter-reads`: quote the value holding `: `), or its prose punctuates with a dash (`markdown\u002Fprose-has-no-dash`: rewrite the sentence; an author's text kept as written sits under a root declared `{ reason, verbatim: true }`) |\n| Names (tree)                     | a directory is not kebab-case, a name says nothing, names a construct (`types.ts`), is written in half, a skill holds more than its `SKILL.md`, a root sits outside the spine undeclared, `studio.config.ts` does not load, an entry is not named for its subpath, an `index` publishes nothing, a `.bin` publishes no bin, a published subpath has no source, the `Makefile` misses one of the six gestures, or a directory is empty: `typescript fix`                                                                               |\n| Secrets (credentials)            | a committed line looks like a live credential                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |\n\nThe drift report closes the run, and refuses nothing: a rule set apart already carries its reason in `typescript.oxlint`.\n\n## Before writing\n\n- A file is named for its subject in the domain: never `types.ts`, `utils.ts`, `constants.ts`, nor a `*.types.ts` suffix. An `index` is an entry the package publishes, named `index[.\u003Csubpath>][.browser].ts` for its subpath, and a bin `\u003Ccommand>.bin.ts`, named for the command it publishes. `.bin` marks only a published bin, and a program the package does not publish is named for what it runs (`docs\u002Freference\u002Fquality-checks.md`, The entry grammar).\n- A file holds 300 lines and a function 60; a `*.spec.ts` is `@jterrazz\u002Ftest`'s `spec-file-within-line-limit`, at 400 (`docs\u002Freference\u002Flint-presets.md`).\n- The default is no comment: a name carries the meaning. A comment that stays opens with its kind (`invariant:`, `hazard:`, `outside:` or `value:`) or fails `jterrazz-typescript\u002Fcomment-states-its-kind`, which you settle by hand, since `typescript fix` deletes no comment; an exported symbol's hover is one `\u002F** ... *\u002F` paragraph above it, wrapped with no blank line, which its block tags (`@param`, `@example`) may follow on lines of their own. A style sheet's, a script's, a Makefile's, a Dockerfile's and a YAML file's comments are held to the same kinds by the Comments pass. A comment longer than the function it sits on fails `jterrazz-typescript\u002Fcomment-no-longer-than-its-function` (`docs\u002Freference\u002Flint-presets.md`, A comment states its kind).\n- A suppression carries its reason: `\u002F\u002F oxlint-disable-next-line \u003Crule> -- why`, and `@ts-expect-error` with a description.\n- Every artefact lives under `.artifacts\u002F\u003Ctool>\u002F`; `dist\u002F` is the product, not an artefact.\n- What knip cannot trace goes under `typescript.knip`, each name mapped to its reason.\n- The API is the types: there is no generated reference, and `docs\u002F` never holds one.\n- A repository root holds `src\u002F`, `lint\u002F`, `specs\u002F`, `docs\u002F`, `skills\u002F`; any other root folder fails Names (tree) unless the ecosystem imposes it (`bin\u002F`, `public\u002F`, `app\u002F`...) or `studio.config.ts` declares it under `typescript.roots` with a reason.\n- A `lint\u002F` holds at its root the modules that compose it (its entries, its bins, what `src\u002F` reads) and three folders: `consumer\u002F` and `self\u002F` hold declarations alone, and `kit\u002F` holds the code that runs them (`docs\u002Freference\u002Fquality-checks.md`, The lint tree).\n- A repository's root `Makefile` answers `make install`, `build`, `lint`, `fix`, `test` and `check`; a workspace member owes none of them.\n- `studio.config.ts` holds what the project is, its presets and its exceptions, each with its reason, and nothing derivable: a module loaded by path is built by its name (`instrumentation.ts`, `*.worker.ts`, `*.global-setup.ts`, a `*.cli.ts` into `.artifacts\u002Fdev\u002F`), and kind and platform defaults are the standard's (`docs\u002Freference\u002Fbuilding.md`, What the manifest does not name).\n- What a package holds a project to reaches it through the preset the project lists under `presets` in `studio.config.ts`, after the standard the declaration derives; the project's own layers, roots and name rules go in its `typescript` section, and a preset's law is set aside only under `optOuts`, with its reason (`docs\u002Freference\u002Fconfiguration.md`, Presets).\n- A rule a package writes for its consumers is written with `@jterrazz\u002Ftypescript\u002Frules` (`docs\u002Freference\u002Frules-kit.md`).\n- A local `compilerOption` is a smell: the preset is where the fix belongs.\n\n## The page to read next\n\n| Question                                                                                                                         | Page                                                      |\n| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |\n| what the toolchain is, and the map of the manual                                                                                 | `README.md`, then `docs\u002FREADME.md`                        |\n| the four ideas: declaration, settings file, two commands, baseline                                                               | `docs\u002Fconcepts\u002Fideas.md`                                  |\n| wiring a project from an empty folder to a green `check`, `.artifacts\u002F`                                                          | `docs\u002Fstart\u002Fgetting-started.md`                           |\n| `studio.config.ts`, kind and platform, a preset, the merge order, an opt-out, a rule set apart, a tsconfig preset                | `docs\u002Freference\u002Fconfiguration.md`                         |\n| a failing pass, a rule id, the baseline                                                                                          | `docs\u002Freference\u002Fquality-checks.md`                        |\n| a lint rule, a profile, how the config merges, knip                                                                              | `docs\u002Freference\u002Flint-presets.md`                          |\n| `build`, `start`, `dev`, `tsc`, an entry the manifest does not name                                                              | `docs\u002Freference\u002Fbuilding.md`                              |\n| a bump landed red                                                                                                                | `docs\u002Fguides\u002Fadopt-a-stricter-release.md`                 |\n| proving a release on a project before it is published: the tarball install, no `install-links`                                   | `docs\u002Fguides\u002Finstall-an-unreleased-build.md`              |\n| which number moves on a release                                                                                                  | `docs\u002Fguides\u002Frelease.md`                                  |\n| writing a rule, a check or its page with the kit                                                                                 | `docs\u002Freference\u002Frules-kit.md`                             |\n| changing the toolchain itself: its layers, its loop                                                                              | `docs\u002Fconcepts\u002Farchitecture.md`, `docs\u002Fguides\u002Fdevelop.md` |\n| how this toolchain proves itself, and the rules it keeps for its own suite (this repository alone; the install ships without it) | `docs\u002Fguides\u002Ftest.md`                                     |\n","# @jterrazz\u002Ftypescript\n\nOne devDependency that builds, checks, lints and formats a project. The manual is the package's `docs\u002F`, read from the install (`node_modules\u002F@jterrazz\u002Ftypescript\u002Fdocs\u002F`) or from this repository when the toolchain itself is the change. This page decides what to run and which page to open; the page owns the rule.\n\n## What to run\n\n| Gesture                  | When                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |\n| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| `typescript fix`         | before every commit: lint fixes, formatting, `.gitignore`, spellings, empty directories                                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| `typescript check`       | the gate: every pass in parallel, then the drift report; a tree already proven green answers from `.artifacts\u002Fproven\u002F` and runs nothing, `--cold` runs it (`docs\u002Freference\u002Fquality-checks.md`, A tree proven green)                                                                                                                                                                                                                                                                                                            |\n| `typescript test`        | the `make test` recipe: the project's `test` script over the test files the change reaches by the last mutation record, every file where it cannot tell (`docs\u002Freference\u002Fquality-checks.md`, The test files a change reaches), answered from its proof like `check`                                                                                                                                                                                                                                                            |\n| `typescript build`       | what the manifest publishes into `dist\u002F`: ESM + types, CJS where a target is `.cjs`                                                                                                                                                                                                                                                                                                                                                                                                                                            |\n| `typescript mutation`    | Stryker over a sandbox copy; fails on a mutant a test runs and lets live (the module tests over the change, then the whole suite over what they let live and the changed lines; domain at zero survivors, glue at its bar; the text of a file `typescript.mutation.presentation` declares never mutated; `--since`, `--mutate`, `--report html` for the HTML report a person browses; its test runners sized from the machine, `TYPESCRIPT_CAPACITY` to give it one); a survivor to answer: `docs\u002Fguides\u002Ftriage-a-survivor.md` |\n| `typescript doctor`      | first read after a bump: installed tools against the declared ranges, then every setting beside the file it comes from                                                                                                                                                                                                                                                                                                                                                                                                         |\n| `typescript baseline`    | a bump lands red: record today's counts, exact; `fix` lowers one that fell                                                                                                                                                                                                                                                                                                                                                                                                                                                     |\n| `typescript docs-layout` | a repository with no npm project: the manual's shape, alone                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| `typescript gate-lock`   | before an install or a pack: refuses while a running gate holds the checkout, naming its pid                                                                                                                                                                                                                                                                                                                                                                                                                                   |\n| `typescript rehearse`    | before a tag: the gate on Linux, in Docker, on a fresh clone of the branch, as the runner runs it (`docs\u002Freference\u002Fcommands.md`)                                                                                                                                                                                                                                                                                                                                                                                               |\n\n`typescript \u003Ccommand> --help` prints a command's flags and runs nothing; a flag it does not read, or one given twice, is refused before anything is written (`docs\u002Freference\u002Fcommands.md`).\n\nA project declares its `kind` (`library`, `api`, `cli`, `website`, `mobile`) and its `platform` (`node`, `bun`, `react`, `next`, `astro`, `expo`) in `studio.config.ts`, `defineConfig({ kind, platform })`; the profile, the tsconfig preset and every law follow. A monorepo is no kind: its root `package.json` lists `workspaces`, is `private`, and its `studio.config.ts` holds the repository's settings and no kind, or is absent; each member declares its own. `oxlint.config.ts`, `oxfmt.config.ts` and `tsconfig.json` are derived (the first two hand their own `import.meta.url` to `oxlintConfig` \u002F `oxfmtConfig`), and `typescript fix` writes them; every tool setting lives in `studio.config.ts`, and no `knip.json`, `tsdown.config.ts` or `stryker.config.*` is kept. A repository root also owes a `Makefile` of six gestures and a `docs\u002F` manual its `CLAUDE.md` routes to. The whole wiring, from an empty folder to a green run, is `docs\u002Fstart\u002Fgetting-started.md`.\n\n## What a failing pass means\n\nEvery pass that ran prints a `RUN` header and one verdict with its seconds; a pass that did not apply prints nothing. The run's last line names the first failing pass and its first finding, and `.artifacts\u002Fgate\u002Fverdict.json` holds every pass's status for a reader that should not parse the log, for `check`, `fix` and `mutation` alike (`docs\u002Freference\u002Fquality-checks.md`, The verdict file). Each rule id below is explained in `docs\u002Freference\u002Fquality-checks.md`, under the pass's own section. On a GitHub runner the run prints a line per pass, each finding as rule and place, found, `fix` and `read`, and an annotation each (`docs\u002Freference\u002Fquality-checks.md`, On a GitHub runner).\n\n| Pass                             | It failed because                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |\n| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Config (one file)                | `studio.config.ts` declares no valid kind and platform, a derived file says something else (`typescript fix`), a tool keeps its own config, the manifest does not match the kind, or a `src\u002Fstandard\u002F` computes                                                                                                                                                                                                                                                                                                                       |\n| TypeScript Check                 | tsc 7 refused a type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |\n| Oxlint Check                     | a rule fired that `.studio\u002Foxlint-suppressions.json` does not hold: fix it, or `typescript baseline`; a recorded count fell: `typescript fix`; an oxlint rule is left in `.studio\u002Fbaseline.json` (`baseline-moved-to-oxlint`): `typescript baseline`; a directive suppresses nothing (`Unused oxlint-disable directive`, `reportUnusedDisableDirectives`): delete it; a `@ts-ignore` or an undescribed `@ts-expect-error` (`typescript\u002Fban-ts-comment`)                                                                               |\n| Oxfmt Check                      | a file is not formatted: `typescript fix`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |\n| Gitignore (artefacts)            | an artefact is named or committed outside `.artifacts\u002F\u003Ctool>\u002F`                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| Knip (unused code)               | a file, export or dependency nothing uses                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |\n| a preset's label                 | a preset's checks refused, `@jterrazz\u002Ftest`'s conventions among them; the preset's own manual owns the id                                                                                                                                                                                                                                                                                                                                                                                                                             |\n| Docs (layout)                    | the repository's `docs\u002F` breaks the manual's spine, or holds a generated `reference\u002F`                                                                                                                                                                                                                                                                                                                                                                                                                                                 |\n| Publish (packaging)              | the `exports` map promises a file the tarball does not carry, or a shipped file is compiled from test material                                                                                                                                                                                                                                                                                                                                                                                                                        |\n| Architecture (layer map)         | an import crosses a layer of a preset (the standard's `lint\u002F` direction included), of `typescript.architecture` or of the project's own `.dependency-cruiser.*` (`architecture\u002F\u003Cname>`, at its line); a recorded `architecture\u002F\u003Cname>` count grew (`typescript baseline`) or fell (`typescript fix`); the map does not load or has nothing to cruise                                                                                                                                                                                  |\n| Astro (check + format)           | `astro check` or prettier refused a `.astro` file                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |\n| Suppressions (directives)        | a lint directive is misspelled or unreasoned                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |\n| Comments (styles, scripts, YAML) | a comment of a style sheet, a script, a Makefile, a Dockerfile or a YAML file states no kind: give it one, or delete it by hand, since `typescript fix` deletes no comment                                                                                                                                                                                                                                                                                                                                                            |\n| Markdown (prose)                 | rumdl refused a page (`markdown\u002Flink-resolves` a missing link, `MD051` a missing anchor, `MD040` a fence with no language: `typescript fix`), a page cites a path that is gone, a block runs past its limit, a skill's frontmatter is no YAML or lacks its name or description (`markdown\u002Fskill-frontmatter-reads`: quote the value holding `: `), or its prose punctuates with a dash (`markdown\u002Fprose-has-no-dash`: rewrite the sentence; an author's text kept as written sits under a root declared `{ reason, verbatim: true }`) |\n| Names (tree)                     | a directory is not kebab-case, a name says nothing, names a construct (`types.ts`), is written in half, a skill holds more than its `SKILL.md`, a root sits outside the spine undeclared, `studio.config.ts` does not load, an entry is not named for its subpath, an `index` publishes nothing, a `.bin` publishes no bin, a published subpath has no source, the `Makefile` misses one of the six gestures, or a directory is empty: `typescript fix`                                                                               |\n| Secrets (credentials)            | a committed line looks like a live credential                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |\n\nThe drift report closes the run, and refuses nothing: a rule set apart already carries its reason in `typescript.oxlint`.\n\n## Before writing\n\n- A file is named for its subject in the domain: never `types.ts`, `utils.ts`, `constants.ts`, nor a `*.types.ts` suffix. An `index` is an entry the package publishes, named `index[.\u003Csubpath>][.browser].ts` for its subpath, and a bin `\u003Ccommand>.bin.ts`, named for the command it publishes. `.bin` marks only a published bin, and a program the package does not publish is named for what it runs (`docs\u002Freference\u002Fquality-checks.md`, The entry grammar).\n- A file holds 300 lines and a function 60; a `*.spec.ts` is `@jterrazz\u002Ftest`'s `spec-file-within-line-limit`, at 400 (`docs\u002Freference\u002Flint-presets.md`).\n- The default is no comment: a name carries the meaning. A comment that stays opens with its kind (`invariant:`, `hazard:`, `outside:` or `value:`) or fails `jterrazz-typescript\u002Fcomment-states-its-kind`, which you settle by hand, since `typescript fix` deletes no comment; an exported symbol's hover is one `\u002F** ... *\u002F` paragraph above it, wrapped with no blank line, which its block tags (`@param`, `@example`) may follow on lines of their own. A style sheet's, a script's, a Makefile's, a Dockerfile's and a YAML file's comments are held to the same kinds by the Comments pass. A comment longer than the function it sits on fails `jterrazz-typescript\u002Fcomment-no-longer-than-its-function` (`docs\u002Freference\u002Flint-presets.md`, A comment states its kind).\n- A suppression carries its reason: `\u002F\u002F oxlint-disable-next-line \u003Crule> -- why`, and `@ts-expect-error` with a description.\n- Every artefact lives under `.artifacts\u002F\u003Ctool>\u002F`; `dist\u002F` is the product, not an artefact.\n- What knip cannot trace goes under `typescript.knip`, each name mapped to its reason.\n- The API is the types: there is no generated reference, and `docs\u002F` never holds one.\n- A repository root holds `src\u002F`, `lint\u002F`, `specs\u002F`, `docs\u002F`, `skills\u002F`; any other root folder fails Names (tree) unless the ecosystem imposes it (`bin\u002F`, `public\u002F`, `app\u002F`...) or `studio.config.ts` declares it under `typescript.roots` with a reason.\n- A `lint\u002F` holds at its root the modules that compose it (its entries, its bins, what `src\u002F` reads) and three folders: `consumer\u002F` and `self\u002F` hold declarations alone, and `kit\u002F` holds the code that runs them (`docs\u002Freference\u002Fquality-checks.md`, The lint tree).\n- A repository's root `Makefile` answers `make install`, `build`, `lint`, `fix`, `test` and `check`; a workspace member owes none of them.\n- `studio.config.ts` holds what the project is, its presets and its exceptions, each with its reason, and nothing derivable: a module loaded by path is built by its name (`instrumentation.ts`, `*.worker.ts`, `*.global-setup.ts`, a `*.cli.ts` into `.artifacts\u002Fdev\u002F`), and kind and platform defaults are the standard's (`docs\u002Freference\u002Fbuilding.md`, What the manifest does not name).\n- What a package holds a project to reaches it through the preset the project lists under `presets` in `studio.config.ts`, after the standard the declaration derives; the project's own layers, roots and name rules go in its `typescript` section, and a preset's law is set aside only under `optOuts`, with its reason (`docs\u002Freference\u002Fconfiguration.md`, Presets).\n- A rule a package writes for its consumers is written with `@jterrazz\u002Ftypescript\u002Frules` (`docs\u002Freference\u002Frules-kit.md`).\n- A local `compilerOption` is a smell: the preset is where the fix belongs.\n\n## The page to read next\n\n| Question                                                                                                                         | Page                                                      |\n| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |\n| what the toolchain is, and the map of the manual                                                                                 | `README.md`, then `docs\u002FREADME.md`                        |\n| the four ideas: declaration, settings file, two commands, baseline                                                               | `docs\u002Fconcepts\u002Fideas.md`                                  |\n| wiring a project from an empty folder to a green `check`, `.artifacts\u002F`                                                          | `docs\u002Fstart\u002Fgetting-started.md`                           |\n| `studio.config.ts`, kind and platform, a preset, the merge order, an opt-out, a rule set apart, a tsconfig preset                | `docs\u002Freference\u002Fconfiguration.md`                         |\n| a failing pass, a rule id, the baseline                                                                                          | `docs\u002Freference\u002Fquality-checks.md`                        |\n| a lint rule, a profile, how the config merges, knip                                                                              | `docs\u002Freference\u002Flint-presets.md`                          |\n| `build`, `start`, `dev`, `tsc`, an entry the manifest does not name                                                              | `docs\u002Freference\u002Fbuilding.md`                              |\n| a bump landed red                                                                                                                | `docs\u002Fguides\u002Fadopt-a-stricter-release.md`                 |\n| proving a release on a project before it is published: the tarball install, no `install-links`                                   | `docs\u002Fguides\u002Finstall-an-unreleased-build.md`              |\n| which number moves on a release                                                                                                  | `docs\u002Fguides\u002Frelease.md`                                  |\n| writing a rule, a check or its page with the kit                                                                                 | `docs\u002Freference\u002Frules-kit.md`                             |\n| changing the toolchain itself: its layers, its loop                                                                              | `docs\u002Fconcepts\u002Farchitecture.md`, `docs\u002Fguides\u002Fdevelop.md` |\n| how this toolchain proves itself, and the rules it keeps for its own suite (this repository alone; the install ships without it) | `docs\u002Fguides\u002Ftest.md`                                     |\n",{"name":5,"description":7},"main","6a164554d127adbbcb508d0e4a3db3c5487790bd","skills\u002Fstudio-typescript","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript","https:\u002F\u002Fjterrazz.com","https:\u002F\u002Fgithub.com\u002Fjterrazz","Ideas to explore. Tools to build. A world to see differently.","2026-11-10 20:28:24",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add jterrazz\u002Fpackage-typescript --skill studio-typescript",{"tool":58,"command":59},"bunx","bunx skills add jterrazz\u002Fpackage-typescript --skill studio-typescript",{"tool":61,"command":62},"pnpm","pnpm dlx skills add jterrazz\u002Fpackage-typescript --skill studio-typescript","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fskills\u002Fstudio-typescript\u002FSKILL.md",true,[],[67,74,80,85,90,96],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":39},"01M6BXZN6ZH0NP6AP2ACVMT6FH","shop","Use when working on the shop.","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fspecs\u002Flint\u002Fnames\u002F__fixtures__\u002Fspine\u002Fskills\u002Fshop\u002FSKILL.md",[],[69],{"skillNo":75,"name":76,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":39},"01M6BXZKRNDEQGKA90D4KQB25D","x","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fspecs\u002Flint\u002Fnames\u002F__fixtures__\u002Flint-tree\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":81,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":39},"01M6BXZJAWWQFTRJV5JBGVNJM6","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fspecs\u002Fcli\u002Fcheck\u002F__fixtures__\u002Fmarkdown\u002Fskill-routes\u002Fskills\u002Fshop\u002FSKILL.md",[],[69],{"skillNo":86,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":39},"01M6BXZGV76FFZXEHX6M8VZZN1","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fspecs\u002Fcli\u002Fcheck\u002F__fixtures__\u002Fmarkdown\u002Fskill-references\u002Fskills\u002Fshop\u002FSKILL.md",[],[69],{"skillNo":91,"name":69,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":39},"01M6BXZF4ED25PJNPGBV6JH79E","Use when: an order is placed.","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fspecs\u002Fcli\u002Fcheck\u002F__fixtures__\u002Fmarkdown\u002Fskill-frontmatter\u002Fskills\u002Fshop\u002FSKILL.md",[],[69],{"skillNo":97,"name":98,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":39},"01M6BXZD0RJ81TXJATQ5CYW4PC","returns","https:\u002F\u002Fgithub.com\u002Fjterrazz\u002Fpackage-typescript\u002Fblob\u002Fmain\u002Fspecs\u002Fcli\u002Fcheck\u002F__fixtures__\u002Fmarkdown\u002Fskill-frontmatter\u002Fskills\u002Freturns\u002FSKILL.md",[],[98]]