Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

node-programming

Node.js and JavaScript/TypeScript development guidance for creating, modifying, reviewing, testing, packaging, and debugging backend, CLI, tooling, and full-stack code. Use when tasks involve package.json, npm, pnpm, yarn, bun, .js, .mjs, .cjs, .ts, tsconfig, Express, NestJS, Next.js API routes, Vitest, Jest, ESLint, or Node dependency management.

Exécuter dans Manus

Étoiles3

Forks0

Mis à jour1 mai 2026 à 19:23

Source

devalexandre

devalexandre/Agno-Deep-Agents

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Commande d'installation

Téléchargement

Exécuter dans Manus

Utile pourSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	node-programming
description	Node.js and JavaScript/TypeScript development guidance for creating, modifying, reviewing, testing, packaging, and debugging backend, CLI, tooling, and full-stack code. Use when tasks involve package.json, npm, pnpm, yarn, bun, .js, .mjs, .cjs, .ts, tsconfig, Express, NestJS, Next.js API routes, Vitest, Jest, ESLint, or Node dependency management.

Node Programming

Goal

Make Node.js changes that respect the project's runtime, module system, package manager, and TypeScript strictness.

Discovery

Identify the package manager from lockfiles: package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lockb.
Read package.json scripts, tsconfig*.json, lint config, test config, and framework conventions before editing.
Preserve the existing module style: ESM, CommonJS, or mixed boundaries.
Check whether the code targets Node only, browser bundles, serverless, or a full-stack framework.

Implementation

Prefer typed, explicit data flow in TypeScript; avoid weakening types with any unless the surrounding code already accepts it.
Keep async code awaitable and handle rejected promises.
Preserve environment variable conventions and validation patterns.
Avoid switching package managers or adding dependencies unless the need is clear and the existing stack supports it.
For HTTP APIs, keep route, validation, service, and test changes aligned.
For CLIs, preserve exit codes, stdout/stderr conventions, and non-interactive behavior.

Verification

Use the project's scripts first: npm test, pnpm test, yarn test, bun test, npm run lint, npm run typecheck, or npm run build.
Prefer targeted tests before full suites when the project is large.
If dependencies are missing, run syntax or TypeScript checks that are available and report the gap clearly.

Review Focus

ESM/CJS mismatches, unhandled promises, accidental browser-only or Node-only imports, broken build scripts, unsafe environment access, dependency churn, and generated lockfile noise.

Plus depuis ce dépôt

même dépôt

elixir-programming

devalexandre/Agno-Deep-Agents

Elixir development guidance for creating, modifying, reviewing, testing, and debugging Elixir and Phoenix applications. Use when tasks involve .ex or .exs files, mix.exs, Phoenix, LiveView, Ecto, OTP supervision trees, GenServer, ExUnit, mix format, mix test, migrations, schemas, contexts, or Elixir dependency management.

2026-05-013

go-programming

devalexandre/Agno-Deep-Agents

Go development guidance for creating, modifying, reviewing, testing, and debugging Go services, libraries, CLIs, and tooling. Use when tasks involve .go files, go.mod, go.work, goroutines, channels, contexts, HTTP handlers, database code, table tests, gofmt, go test, or Go module management.

2026-05-013

python-programming

devalexandre/Agno-Deep-Agents

Python development guidance for creating, modifying, reviewing, testing, packaging, and debugging Python code. Use when tasks involve .py files, pyproject.toml, requirements files, pytest, ruff, mypy, FastAPI, Django, Flask, CLIs, scripts, type hints, virtual environments, or Python dependency management.

2026-05-013

rust-programming

devalexandre/Agno-Deep-Agents

Rust development guidance for creating, modifying, reviewing, testing, packaging, and debugging Rust crates, CLIs, services, and libraries. Use when tasks involve .rs files, Cargo.toml, Cargo.lock, workspaces, ownership, lifetimes, traits, async Rust, tokio, serde, cargo fmt, cargo test, cargo clippy, or Rust dependency management.

2026-05-013

codebase-analysis

devalexandre/Agno-Deep-Agents

Analyze a codebase before changing it, infer local patterns, and choose focused implementation and verification steps.

2026-04-263

deep-agent-planning

devalexandre/Agno-Deep-Agents

Planning discipline for long-running Deep Agent tasks with delegation, task tracking, validation, and concise delivery.

2026-04-263

name	node-programming
description	Node.js and JavaScript/TypeScript development guidance for creating, modifying, reviewing, testing, packaging, and debugging backend, CLI, tooling, and full-stack code. Use when tasks involve package.json, npm, pnpm, yarn, bun, .js, .mjs, .cjs, .ts, tsconfig, Express, NestJS, Next.js API routes, Vitest, Jest, ESLint, or Node dependency management.

Node Programming

Goal

Make Node.js changes that respect the project's runtime, module system, package manager, and TypeScript strictness.

Discovery

Identify the package manager from lockfiles: package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lockb.
Read package.json scripts, tsconfig*.json, lint config, test config, and framework conventions before editing.
Preserve the existing module style: ESM, CommonJS, or mixed boundaries.
Check whether the code targets Node only, browser bundles, serverless, or a full-stack framework.

Implementation

Prefer typed, explicit data flow in TypeScript; avoid weakening types with any unless the surrounding code already accepts it.
Keep async code awaitable and handle rejected promises.
Preserve environment variable conventions and validation patterns.
Avoid switching package managers or adding dependencies unless the need is clear and the existing stack supports it.
For HTTP APIs, keep route, validation, service, and test changes aligned.
For CLIs, preserve exit codes, stdout/stderr conventions, and non-interactive behavior.

Verification

Use the project's scripts first: npm test, pnpm test, yarn test, bun test, npm run lint, npm run typecheck, or npm run build.
Prefer targeted tests before full suites when the project is large.
If dependencies are missing, run syntax or TypeScript checks that are available and report the gap clearly.

Review Focus

ESM/CJS mismatches, unhandled promises, accidental browser-only or Node-only imports, broken build scripts, unsafe environment access, dependency churn, and generated lockfile noise.