typescript-dev

Enforce TypeScript strict mode, interfaces, generics, and utility types.

2|1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/Wulnut/lark_agent --skill typescript-dev-wulnut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-dev
Source: https://github.com/Wulnut/lark_agent/tree/main/.opencode/skill/typescript-dev
Command: npx skills add https://github.com/Wulnut/lark_agent --skill typescript-dev-wulnut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript 编码规范和最佳实践,帮助开发团队在类型系统、严格模式和工具类型方面保持一致性,降低潜在缺陷并提升可维护性。

Core Features & Use Cases

  • Strict type usage: 通过在对象结构中使用 interface、强调 strictNullChecks,提升类型安全性。
  • Generics & utility types: 使用泛型和工具类型(如 Pick、Omit、Partial)构建可复用组件与函数。
  • Tooling guidance: 提供启用严格模式、优先使用类型守卫、避免 any 的实践,以及常用开发工具的配置建议。

Quick Start

Start a new TypeScript project with strict mode enabled and adopt interfaces, generics, and utility types from the outset.

Frequently Asked Questions about typescript-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TypeScript strict mode and type safety in my project?

Enforce TypeScript strict mode by enabling it in tsconfig, using interfaces for object shapes, leveraging type guards, and avoiding any to ensure type safety and code maintainability.

What is the best way to use utility types like Pick and Omit for reusable generics?

Use utility types like Pick, Omit, and Partial to construct reusable generic components and functions, ensuring flexible yet strictly typed object structures across your codebase.

When should I use interfaces instead of type aliases in TypeScript?

Use interfaces for defining object shapes to improve type safety and strictNullChecks, ensuring consistent typing and maintainable code across teams and libraries.

Can I apply these TypeScript coding standards to existing *.ts and *.tsx files?

Yes, these coding standards apply to codebases using TypeScript files including *.ts, *.tsx, and *.d.ts across projects, teams, and libraries seeking consistent typing.

Why should I avoid using any in my TypeScript codebase?

Avoid using any to maintain strict type safety and leverage strictNullChecks, which reduces potential defects and improves overall code maintainability across development teams.