Skills Directory
Claude Skills by Intense-Visions
github.com/Intense-Visions> Implement hashing, HMAC, signing, encryption, and key derivation with Node.js crypto
> Manage environment configuration with process.env, dotenv, and validation for 12-factor apps
> Handle uncaught exceptions, promise rejections, and errors across async Node.js code
> Write Node.js ES modules correctly using import.meta.url, package.json type, and CJS interop
> Use Node.js EventEmitter for typed pub-sub communication with memory leak prevention
> Structure Express applications with middleware chains, routers, and proper error handling
> Build performant APIs with Fastify using schema validation, plugins, decorators, and hooks
> Build low-level HTTP servers with Node.js http module and middleware pattern
> Perform file system operations correctly using fs.promises, path utilities, and file watching
> Profile Node.js applications using --prof, clinic.js, memory snapshots, and event loop lag
> Process large data efficiently using Node.js Readable, Writable, and Transform streams
> Test Node.js APIs and modules using supertest, nock, and test containers
> Offload CPU-intensive work to worker threads using MessageChannel and shared buffers
> Use composables, components, and utilities in Nuxt without writing any import statements
> Fetch data and coordinate async state across server and client using Nuxt's built-in composables
> Target Node.js servers, edge runtimes, static hosting, or hybrid modes using Nitro presets and route rules
> Structure applications with file-based routing, named layouts, and per-page configuration via definePageMeta
> Protect routes, redirect unauthenticated users, and transform navigation using Nuxt's layered middleware system
> Extend Nuxt at build time with defineNuxtModule — add components, imports, plugins, and server routes programmatically
> Extend the Nuxt application instance, register global services, and provide values to composables using defineNuxtPlugin
> Set page titles, Open Graph tags, canonical URLs, and structured data with useSeoMeta and useHead
> Build fully-typed server API endpoints using Nitro's event-handler model and H3 utilities
> Share reactive state across components with SSR-safe useState and Pinia store hydration
> Test Nuxt components, composables, and pages using @nuxt/test-utils with full Nuxt context including auto-imports
> Propagate trace context across service boundaries using W3C TraceContext headers and baggage
> Add custom spans, attributes, and events to business-critical code paths beyond auto-instrumentation
> Track and correlate errors across services with span exceptions, status codes, and error events
> Configure OTLP exporters to send traces, metrics, and logs to observability backends and collectors
> Correlate structured logs with distributed traces using OpenTelemetry context for unified observability
> Record application metrics with OpenTelemetry counters, histograms, and gauges for monitoring and alerting
> Integrate OpenTelemetry with NestJS using interceptors, decorators, and module-based configuration
> Add OpenTelemetry tracing to Next.js with the instrumentation hook for Server Components, API routes, and middleware
> Identify performance bottlenecks using trace analysis, histogram metrics, and span timing patterns
> Control trace volume and costs with head sampling, tail sampling, and priority-based strategies
> Initialize the OpenTelemetry Node.js SDK with resource attributes, exporters, and auto-instrumentation
> Instrument distributed traces with OpenTelemetry spans to visualize request flow across services
> Post-execution LLM-judgment: did the implementation actually satisfy its spec? Reads the spec's acceptance section, the change diff, and test output, and emits a confidence-rated `OutcomeVerdict` (`SATISFIED | NOT_SATISFIED | INCONCLUSIVE`) with a rationale and unmet criteria. Ship authority is derived in TypeScript, never trusted from the LLM: a high-confidence `NOT_SATISFIED` blocks ship; every other verdict is advisory. The harness's first blocking post-execution spec-satisfaction gate (...
> Implement authentication that resists credential stuffing, session hijacking, and token theft
> Apply cryptographic best practices for password hashing, data encryption, digital signing, and key management
> Prevent cross-site request forgery by validating request origin and requiring unpredictable tokens for state-changing operations
> Manage third-party dependency risks with auditing, lockfiles, automated scanning, and supply chain hardening
> Secure file upload endpoints against malicious files, path traversal, resource exhaustion, and code execution
> Enforce object-level authorization so users can only access resources they own or are permitted to access
> Eliminate SQL, NoSQL, and command injection by never concatenating untrusted input into queries or commands
> Implement security logging and monitoring to detect attacks, support incident response, and maintain audit trails
> Protect APIs with rate limiting, throttling, and abuse prevention to mitigate brute force, scraping, and denial of service
> Keep credentials out of code, logs, and version control by using environment variables, secrets managers, and strict access controls
> Configure HTTP security headers to protect against XSS, clickjacking, MIME sniffing, and information leakage
> Block script injection by encoding output, sanitizing HTML, and enforcing Content Security Policy
> Master HTTP browser caching — Cache-Control directives, ETag and Last-Modified validation, immutable assets with content-hashed filenames, stale-while-revalidate patterns, and cache partitioning in modern browsers for optimal repeat-visit performance.