Install
$ agentstack add skill-d-padmanabhan-agent-engineering-handbook-typescript-javascript Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.
Security review
⚠ Flagged1 finding(s); flagged for manual review. · v0.1.0 How review works →
- • Prompt-injection patterns
- • Secret / credential exfiltration
- • Dangerous shell & filesystem operations
- • Untrusted network calls
- • Known-malicious package signatures
- high Dangerous shell/eval execution.
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ● Dynamic code execution Used
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
TypeScript & JavaScript Development
Guiding Principles
- Type Safety: Leverage strict mode, avoid
any, use discriminated unions - Explicit Over Implicit: Prefer explicit types for clarity and maintainability
- Modern Defaults: ESM, const/let, async/await, optional chaining
- Security First: Never use
eval, sanitize HTML, validate inputs
Quick Reference
| Aspect | TypeScript | JavaScript | |--------|------------|------------| | Package Manager | pnpm preferred | pnpm preferred | | Module System | ES Modules | ES Modules + // @ts-check | | Linting | eslint --max-warnings=0 | eslint --max-warnings=0 | | Formatting | Prettier | Prettier | | Types | Strict mode | JSDoc types |
Non-Negotiables
NN-1: Validate at trust boundaries
Static types do not validate runtime data. Treat HTTP bodies, responses, webhooks, queue messages, localStorage/sessionStorage, environment variables, CLI args, and JSON files as unknown until validated with Zod or an explicit type guard.
Reject:
JSON.parse(raw) as Tawait response.json() as T- unchecked property access on remote JSON
as anyor double assertions (value as unknown as T)
NN-2: Fetch/API calls require timeout + status check + schema validation
Every service/network fetch must include a timeout, check response.ok, and validate the JSON shape before returning typed data.
import { z } from 'zod';
async function fetchJson(
url: string,
schema: z.ZodType,
options: RequestInit = {},
): Promise {
const response = await fetch(url, {
...options,
signal: options.signal ?? AbortSignal.timeout(5_000),
headers: { Accept: 'application/json', ...options.headers },
});
if (!response.ok) {
throw new Error(`request failed: HTTP ${response.status}`);
}
return schema.parse(await response.json());
}
NN-3: Production servers are hardened by default
Node/Express/Fastify services need bounded request bodies, explicit CORS, security headers, request IDs, structured logging, generic 5xx responses, and graceful shutdown. Do not use direct app.listen(...) examples for production services without retaining and closing the server.
NN-4: Package manager and runtime are pinned
Declare packageManager and Node engine policy in package.json; CI uses Corepack and the declared package manager.
{
"packageManager": "pnpm@10.0.0",
"engines": { "node": ">=22" }
}
Critical Patterns
// 1. Use strict equality
if (value === 0) { } // ✅ GOOD
if (value == 0) { } // ❌ BAD
// 2. Handle Promise rejections
fetchData().catch(err => console.error(err)); // ✅ GOOD
// 3. Optional chaining and nullish coalescing
const name = user?.profile?.name ?? 'Guest'; // ✅ GOOD
// 4. Use Set/Map for lookups
const seen = new Set(); // ✅ GOOD (O(1))
const seen = []; // ❌ BAD (O(n))
// 5. Never use eval or new Function
eval(userInput); // ❌ NEVER DO THIS
// 6. Sanitize HTML
element.textContent = userInput; // ✅ GOOD
element.innerHTML = userInput; // ❌ BAD (XSS)
TypeScript Configuration
{
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "bundler",
"strict": true,
"noImplicitAny": true,
"strictNullChecks": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"noUncheckedIndexedAccess": true,
"esModuleInterop": true,
"skipLibCheck": false
}
}
Avoid any - Use Proper Types
// ❌ BAD - Loses all type safety
function processData(data: any): any {
return data.value;
}
// ✅ GOOD - Generic type
function processData(data: T): T {
return data;
}
// ✅ GOOD - Unknown for truly unknown types
function processData(data: unknown): string {
if (typeof data === 'object' && data !== null && 'value' in data) {
return String((data as { value: unknown }).value);
}
throw new Error('Invalid data');
}
Discriminated Unions
type SuccessResponse = {
status: 'success';
data: { id: string; name: string };
};
type ErrorResponse = {
status: 'error';
error: { code: number; message: string };
};
type ApiResponse = SuccessResponse | ErrorResponse;
function handleResponse(response: ApiResponse): void {
if (response.status === 'success') {
console.log(response.data.id); // Type-safe
} else {
console.log(response.error.message); // Type-safe
}
}
Utility Types
interface User {
id: string;
name: string;
email: string;
password: string;
}
type UserUpdate = Partial; // All optional
type UserCredentials = Pick;
type UserPublic = Omit; // Exclude password
type RequiredUser = Required; // All required
type ReadonlyUser = Readonly; // Immutable
Async Patterns
// Parallel execution
const [users, products] = await Promise.all([
fetchUsers(),
fetchProducts()
]);
// Handle partial failures
const results = await Promise.allSettled([
fetchUsers(),
fetchProducts()
]);
results.forEach(result => {
if (result.status === 'fulfilled') {
console.log(result.value);
} else {
console.error(result.reason);
}
});
Security Rules (Mandatory)
- Never use
eval,new Function, or unsanitizedinnerHTML - Use
textContentfor DOM insertion - Validate and sanitize all external inputs
- Do not log secrets/tokens/PII
- Use parameterized queries; no string-built queries
- Enforce HTTPS; secure cookies (HttpOnly, SameSite)
Naming Conventions
| Type | Convention | Example | |------|------------|---------| | Functions/Variables | camelCase | fetchUserData | | Classes/Interfaces | PascalCase | UserService | | Constants | UPPERSNAKECASE | MAX_RETRIES | | Types | PascalCase | ApiResponse |
Detailed References
- TypeScript Patterns: See [references/typescript-patterns.md](references/typescript-patterns.md) for advanced types, generics, mapped types
- JavaScript Patterns: See [references/javascript-patterns.md](references/javascript-patterns.md) for JSDoc, ESM, performance
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: d-padmanabhan
- Source: d-padmanabhan/agent-engineering-handbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.