noxfen-essentials

Systematic debugging methodology. Use when the user reports a bug, unexpected behavior, test failure, compilation error, or runtime error. Activates on "debug this", "why is X happening", "this is broken", "fix this error", error messages pasted into chat, or stack traces. Avoids random-change debugging in favor of hypothesis-driven investigation.

JavaScript and TypeScript best practices. Activates when working with .js, .ts, .jsx, .tsx files, or when the user asks to "write javascript", "write typescript", "node.js", "react component", "refactor JS", mentions eslint/prettier/bun/vite, or discusses JS/TS patterns. Enforces typed, idiomatic, production-quality TypeScript.

Multi-agent task orchestration skill. Use when the user asks to "orchestrate", "spawn agents", "parallelize this", "plan with subagents", "break this into agents", or when a task is clearly complex enough to benefit from parallel subagents (large refactors, multi-module features, cross-cutting analysis). Also triggers on "/orchestrate" or "/swarm". Analyzes complexity, token budget, and routes work to the right models to minimize cost.

Structured planning before execution for non-trivial tasks. Use when the task involves multiple files, architectural decisions, or unclear scope. Activates on "/plan", "think before doing", "plan this out", "what's the approach", "how should we tackle", or when the user asks for a plan before implementation. Prevents costly wrong-direction work.

PowerShell scripting best practices for robust, maintainable scripts and modules. Activates when writing or reviewing .ps1/.psm1/.psd1 files, or when the user asks to "write a powershell script", "PS1 script", "powershell function", "pwsh", mentions PSScriptAnalyzer, or discusses PowerShell patterns. Covers both Windows PowerShell 5.1 and PowerShell 7+ (cross-platform).