Przejdź do treści
Biblioteka skilli
Programowanie · Analiza

typescript-engineer

/typescript-engineer

Pomaga projektować ścisłe typy i diagnozować błędy kompilatora: wnioskowanie, generyki, typy warunkowe i deklaracje.

Repozytorium
vosslab-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
22.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
27
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga projektować ścisłe typy i diagnozować błędy kompilatora: wnioskowanie, generyki, typy warunkowe i deklaracje.

Oryginalny opis (EN)

Use when strict TypeScript type design or compiler diagnosis is central, including inference, generics, mapped or conditional types, branded types, overloads, declarations, or module-boundary contracts.

Jak działa

  1. Overview
  2. Workflow
  3. Design defaults
  4. Task routes
  5. Browser-game boundary
  6. Review output
  7. Verification and return
Sekcje z nagłówków SKILL.md, w oryginale · 83 linii, 508 słów
Podgląd SKILL.md
---
name: typescript-engineer
description: Use when strict TypeScript type design or compiler diagnosis is central, including inference, generics, mapped or conditional types, branded types, overloads, declarations, or module-boundary contracts.
---

# TypeScript engineer

## Overview

Apply TypeScript-specific judgment to compiler diagnosis, type-level design, public contracts, and
strict-safety refactoring. Use the target repository's rules, configuration, dependencies, and
front-door commands as authority.

## Workflow

1. Classify the project as greenfield or improve-existing and follow
   [`references/project_workflow.md`](references/project_workflow.md).
2. Reproduce the current diagnostic or capture the repository's focused type-check baseline. Record
   the exact diagnostic text when compilation is failing.
3. Classify the task with [`references/task_selection.md`](references/task_selection.md), then use
   [`references/topic_index.md`](references/topic_index.md) to load only the matching rule guides.
4. Identify the owner of each runtime value, validator, schema, DTO, domain model, storage shape, and
   exported type before changing a boundary.
5. Implement the smallest type design that proves the intended contract while preserving runtime
   behavior unless the user requested behavior changes.
6. Run the target repository's owned type-check or test front door and compare it with the baseline.

## Design defaults

- Keep one responsibility per file and co-locate private helper types with their implementation.
- Promote a type to shared ownership only when multiple modules need the same stable contract.
- Separate runtime behavior, runtime validation, and type-level helpers when they change for
  different reasons.
- Derive types from schemas, clients, or constants when a source of truth exists.
- Use a narrow `export type` boundary and avoid deep barrel chains.
- Prefer clear generics and utility types before conditional, mapped, recursive, or template-literal
  machinery.
- Contain unavoidable assertions inside brand constructors, proven type guards, or documented
  boundary adapters.
- Cap recursive type complexity where the compiler's work would become unstable.

For shared or exported contracts, read
[`references/modular-type-design.md`](references/modular-type-design.md). For strictness policy,
read [`references/strict-mode-flags.md`](references/strict-mode-flags.md).

## Task routes

- Audit or sweep: [`references/checklist.md`](references/checklist.md)
- Compiler diagnostic: [`references/error-diagnosis.md`](references/error-diagnosis.md)
- Remove `any` or narrow `unknown`: [`references/type-narrowing.md`](references/type-narrowing.md)
- Generic design: [`references/generics-basics.md`](references/generics-basics.md)
- Conditional or mapped design: [`references/conditional-types.md`](references/conditional-types.md)
  and [`references/mapped-types.md`](references/mapped-types.md)
- Branding or nominal identity: [`references/opaque-types.md`](references/opaque-types.md)
- Overloads: [`references/function-overloads.md`](references/function-overloads.md)
- Type-level regression examples: [`references/smell-test-examples.md`](references/smell-test-examples.md)

The topic index routes to the remaining focused guides for array access, `as const`, assertion
functions, builders, deep inference, `infer`, template literals, and utility types.

## Browser-game boundary

For browser games, simulations, save files, entity identities, coordinates, events, replay, seeds,
or migrations, read [`references/game-type-patterns.md`](references/game-type-patterns.md). During a
parallel game build, answer one bounded shared-type or boundary question and return a typed stub the
caller can import. Use [`references/divergence-map.md`](references/divergence-map.md) to discover
consumer-owned command and configuration differences rather than embedding a fixed command catalog.

## Review output

Organize a requested review under Type Safety, Module Boundaries, Compile-Time Errors, and Type-Level
Tests. Keep runtime, framework, performance, and general security findings with their owning
workflows unless they directly explain a type contract failure.

## Verification and return

Use [`references/testing_and_oracles.md`](references/testing_and_oracles.md) for proof strategy. Add
positive type assertions and intentional negative cases when the repository supports them. Return:

- the proposed contract or implemented change;
- the exact repository-owned verification command and its result;
- files changed, each tied to the requirement it satisfies;
- failures, warnings, or skipped checks with their scope.

Report completion only when the relevant compiler or test evidence is available, or state clearly
why the check could not run.
Pliki w paczce (27)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • references/array-index-access.md 1 KB
  • references/as-const-typeof.md 1 KB
  • references/assertion-functions.md 1 KB
  • references/builder-pattern.md 1 KB
  • references/checklist.md 3 KB
  • references/conditional-types.md 1 KB
  • references/deep-inference.md 1 KB
  • references/divergence-map.md 2 KB
  • references/error-diagnosis.md 1 KB
  • references/function-overloads.md 1 KB
  • references/game-type-patterns.md 6 KB
  • references/generics-basics.md 1 KB
  • references/infer-keyword.md 1 KB
  • references/mapped-types.md 1 KB
  • references/modular-type-design.md 5 KB
  • references/opaque-types.md 2 KB
  • references/project_workflow.md 5 KB
  • references/smell-test-examples.md 2 KB
  • references/strict-mode-flags.md 2 KB
  • references/task_selection.md 5 KB
  • references/template-literal-types.md 1 KB
  • references/testing_and_oracles.md 4 KB
  • references/topic_index.md 5 KB
  • references/type-narrowing.md 1 KB
  • references/utility-types.md 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · vosslab/vosslab-skills100MIT
heyAyushh/stacc90MIT
heyAyushh/stacc90MIT

Migawka bazy z 13.11.2026 · wersja paczki 2f22af1b46b2 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90typescript-type-system
    Pomaga pracować z systemem typów TypeScript: tryb strict, złożone typy, generyki, type guards i konfiguracja kompilatora.
  • 100typescript-advanced-types
    Pomaga w złożonym systemie typów: generyki, typy warunkowe, mapowane, literały szablonów i typy narzędziowe.
  • 100typescript-type-hardening
    Naprawia błędy typów i wnioskowania w TypeScript oraz mechanizmy typów: generyki, infer, mapped types i branded types.
  • 95typescript-advanced-types
    Prowadzi przez system typów TypeScript: generyki, typy warunkowe, mapowane, literały szablonowe i typy pomocnicze do budowy aplikacji bezpiecznych typowo.
  • 95typescript-advanced-types
    Prowadzi przez system typów TypeScript: generyki, typy warunkowe, mapowane, literały szablonowe i typy pomocnicze do budowy aplikacji bezpiecznych typowo.
  • 95typescript-advanced-types
    Prowadzi przez system typów TypeScript: generyki, typy warunkowe, mapowane, literały szablonowe i typy pomocnicze do budowy aplikacji bezpiecznych typowo.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.