typescript-style
Apply TypeScript style rules that prefer checked literal typing with satisfies and as const satisfies over unsafe assertions. Use when writing or reviewing TypeScript or TSX code, test fixtures, typed object literals, mocks, config objects, or table-driven cases.
Informações da origem
- Repositório
- ryoppippi/dotfiles
- Última atividade na origem
- 16 de maio de 2026 às 11:57
- Idioma detectado do SKILL.md
- inglês
- Estrelas
- 266
- Forks
- 5
Opções de instalação
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Revise os arquivos de origem
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Exibindo SKILL.md
SKILL.md
Instruções da origem · Visualização somente leitura- name
- typescript-style
- description
- Apply TypeScript style rules that prefer checked literal typing with satisfies and as const satisfies over unsafe assertions. Use when writing or reviewing TypeScript or TSX code, test fixtures, typed object literals, mocks, config objects, or table-driven cases.
# TypeScript Style
## Prefer `satisfies` Over `as`
Avoid `as` type assertions and especially `as any`. Use `satisfies` when checking object literals, mocks, config objects, fixture data, and expected rows.
Bad:
```ts
const config = { port: 3000, host: 'localhost' } as ServerConfig;
const ctx = { fetchDirent: vi.fn(), addReadHistory: vi.fn() } as any;
```
Good:
```ts
const config = { port: 3000, host: 'localhost' } satisfies ServerConfig;
const ctx = { fetchDirent: vi.fn(), addReadHistory: vi.fn() } satisfies MockContext;
```
## Use `as const satisfies`
Use `as const satisfies` for static literal data when preserving exact literal values or readonly tuples helps TypeScript catch mistakes.
Good:
```ts
const ROUTES = {
home: '/',
about: '/about',
} as const satisfies Record<string, string>;
```
Good for table-driven cases:
```ts
const reportCases = [
{ type: 'daily', period: '2026-05-16' },
{ type: 'monthly', period: '2026-05' },
] as const satisfies readonly ReportCase[];
```
## Acceptable `as`
Use `as` only when `satisfies` cannot express the operation, such as narrowing data returned from an external untyped boundary or adapting to an API that requires a nominal type. Keep it local and avoid `as any`.
## Prefer `@ts-expect-error`
Use `@ts-expect-error` instead of `@ts-ignore`, and include a short explanation. `@ts-expect-error` fails when the underlying type error disappears, so stale suppressions are caught.
Bad:
```ts
// @ts-ignore
import privateApi from 'some-package/private-api';
```
Good:
```ts
// @ts-expect-error Private runtime API has no public type declaration.
import privateApi from 'some-package/private-api';
```
Ver no GitHub