Run any Skill in Manus with one click

nodejs-typescript-conventions

Stars4

Forks1

UpdatedMay 6, 2026 at 18:27

Enforces TypeScript-only source, npm for scripts and deps, ESM import and export defaults, async await over raw then chains, no any types, minimal let usage, private or readonly class fields, functional collection helpers. Do not use for plain JavaScript codebases or non-npm package managers.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rodrigobranas

rodrigobranas/f_ia_m1_3

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	nodejs-typescript-conventions
description	Enforces TypeScript-only source, npm for scripts and deps, ESM import and export defaults, async await over raw then chains, no any types, minimal let usage, private or readonly class fields, functional collection helpers. Do not use for plain JavaScript codebases or non-npm package managers.

Node.js, JavaScript, and TypeScript conventions

Procedures

When writing or modifying application TypeScript

Author runtime and shared source strictly in TypeScript.
Use npm exclusively for installs and script execution (npm install, npm run build). Do not introduce alternate package managers for those roles.
When libraries omit types, prefer @types/<package> where published on DefinitelyTyped; rely on bundled types when shipped (Vitest includes types).
Before finishing edits, validate type correctness via the project toolchain (npm run build / tsc / editor diagnostics as applicable).
Prefer const bindings; reserve let for genuine reassignment and never declare with var.
Declare class fields private, readonly, or both unless a deliberate public surface is mandated by the dependency graph.
Prefer immutable chain helpers (filter, map, reduce, find) over manual for / while loops for collection transforms.
Prefer arrow functions for short pure operations and lexical this where stylistically consistent with surrounding modules.
Sequence asynchronous operations with async / await instead of chaining bare .then trees for primary control flow.
Ban any; supply concrete interfaces or type aliases covering inputs and outputs.
Replace CommonJS imports with ESM syntax (import / export); disallow require and module.exports in TypeScript modules.
Export a single default when the module exposes exactly one principal symbol; otherwise use named exports with consistent barrel ergonomics.

Error Handling

When async awaits risk unhandled rejection, propagate errors to callers or map them to domain-safe results following service-layer norms.
When dependency scripts assume another package manager, align documentation and CI to npm-first flows before branching tooling.

More from this repository

same repository

code-standards-en

rodrigobranas/f_ia_m1_3

Specifies English identifiers, casing conventions, verb-led functions, parameterized objects over long arg lists, CQS separation, guarded early returns, split boolean-flag behaviors, sizing limits for methods and classes, minimal comments. Do not use when localized naming is required by product policy.

2026-05-064

express-rest-http

rodrigobranas/f_ia_m1_3

Maps Express endpoints to REST-ish resources with POST action verbs for mutations, mandatory security middleware, canonical status codes, OpenAPI documentation, pagination limit and offset, partial field queries, native fetch for outbound HTTP. Do not use when replacing Express with another server framework.

2026-05-064

react-frontend-conventions

rodrigobranas/f_ia_m1_3

Constrains functional React with TypeScript and Tailwind: local state colocation, explicit props instead of spreads, Context for cross-cutting state, useMemo for heavy derivations, use-prefixed hooks, component tests. Do not use for class components, styled-components, or non-Tailwind styling stacks.

2026-05-064

repo-folder-structure

rodrigobranas/f_ia_m1_3

Defines hybrid feature-based frontend layout under src plus backend controllers-services-data layering and HTTP flow direction. Applies when creating routes, pages, features, or backend modules for consistency. Do not use for monorepo-wide policies outside this template or frameworks that forbid this layout.

2026-05-064

skill-best-practices

rodrigobranas/f_ia_m1_3

Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.

2026-05-064

vitest-testing

rodrigobranas/f_ia_m1_3

Guides Vitest-based unit and integration tests with vi mocks, Arrange-Act-Assert, fake timers for Date, HTTP endpoint integration tests without supertest, use-case and domain coverage. Do not use for Jest-centric projects or Sinon as primary mocking.

2026-05-064

name	nodejs-typescript-conventions
description	Enforces TypeScript-only source, npm for scripts and deps, ESM import and export defaults, async await over raw then chains, no any types, minimal let usage, private or readonly class fields, functional collection helpers. Do not use for plain JavaScript codebases or non-npm package managers.

Node.js, JavaScript, and TypeScript conventions

Procedures

When writing or modifying application TypeScript

Author runtime and shared source strictly in TypeScript.
Use npm exclusively for installs and script execution (npm install, npm run build). Do not introduce alternate package managers for those roles.
When libraries omit types, prefer @types/<package> where published on DefinitelyTyped; rely on bundled types when shipped (Vitest includes types).
Before finishing edits, validate type correctness via the project toolchain (npm run build / tsc / editor diagnostics as applicable).
Prefer const bindings; reserve let for genuine reassignment and never declare with var.
Declare class fields private, readonly, or both unless a deliberate public surface is mandated by the dependency graph.
Prefer immutable chain helpers (filter, map, reduce, find) over manual for / while loops for collection transforms.
Prefer arrow functions for short pure operations and lexical this where stylistically consistent with surrounding modules.
Sequence asynchronous operations with async / await instead of chaining bare .then trees for primary control flow.
Ban any; supply concrete interfaces or type aliases covering inputs and outputs.
Replace CommonJS imports with ESM syntax (import / export); disallow require and module.exports in TypeScript modules.
Export a single default when the module exposes exactly one principal symbol; otherwise use named exports with consistent barrel ergonomics.

Error Handling

When async awaits risk unhandled rejection, propagate errors to callers or map them to domain-safe results following service-layer norms.
When dependency scripts assume another package manager, align documentation and CI to npm-first flows before branching tooling.