typescript

- Avoid explicit type annotations when TypeScript can infer - Avoid implicitly any ; explicitly type when necessary - Use accurate types: prefer Record over object or any - Prefer interface for object shapes (e.g., React props); use type for unions/intersections - Prefer as const satisfies XyzInterface over plain as const - Prefer @ts-expect-error over @ts-ignore over as any - Avoid meaningless null/undefined parameters; design strict function contracts - Prefer ES module augmentation ( declare module '...' ) over namespace ; do not introduce namespace -based extension patterns - When a type needs extensibility, expose a small mergeable interface at the source type and let each feature/plugin augment it locally instead of centralizing all extension fields in one registry file - For package-local extensibility patterns like PipelineContext.metadata , define the metadata fields next to the processor/provider/plugin that reads or writes them - Prefer async / await over callbacks or .then() chains - Prefer async APIs over sync ones (avoid *Sync ) - Use promise-based variants: import { readFile } from 'fs/promises' - Use Promise.all , Promise.race for concurrent operations where safe - Prefer object destructuring - Use consistent, descriptive naming; avoid obscure abbreviations - Replace magic numbers/strings with well-named constants - Defer formatting to tooling - Use @lobehub/ui...