Results for “node”

Write and improve documentation for ComfyUI nodes in per-node JSON files. Use when asked to document nodes, write node descriptions, add tips to nodes, improve node docs, enrich node content, fill in empty node descriptions, or batch-write documentation for new/updated nodes. Also triggers on "write docs for nodes", "document the new nodes", "improve node tips", "fill in node descriptions", "enrich nodes", "node content pass", "update nodes", "sync comfyui nodes", "new comfyui version", or "node enrichment".

The English summary is being prepared. Showing the original description.

Pencil CLI（`pencil`コマンド）だけを使って、.penファイル（Pencilで作成されたデザインファイル）の中のNodeのデザインデータ（属性・構造）とスクリーンショット画像を読み取り専用で取得するスキル。Node IDが分かっているケースだけでなく、名前の正規表現（例: 「ヘッダー」「.*Button」）、Nodeタイプ（frame / text / image など）、再利用可能コンポーネント、特定フレーム配下、ドキュメント全体のトップレベルなど、**ID以外の指定方法**にも対応する。ユーザーが「.penのこのNodeの中身を見せて」「特定コンポーネントのデザインデータを取り出して」「Nodeのスクリーンショットだけ欲しい」「ヘッダーの構造を確認したい」「ボタンのスタイルをコピーしたい」「再利用可能コンポーネント一覧を見せて」「ドキュメント全体の構造を覗きたい」「全てのテキストNodeを取得して」のように.pen内の要素の調査・参照・確認・抜き出しを依頼した場合に必ずこのスキルを使う。インタラクティブモード（`pencil interactive`）で `batch_get` の `nodeIds` / `patterns` / `parentId` を使い分けてNode属性をJSONで取得し、`get_screenshot` / `export_nodes` で画像を`.pen`と同階層の`snapshots/`にPNG出力する。編集はしない（`save()`を呼ばない）ため、対象ファイルは絶対に書き換わらない。Pencil MCPには依存せず`pencil`コマンドのみで完結。

The English summary is being prepared. Showing the original description.

Diagnose unresponsive GKE GPU or TPU nodes and pods stuck terminating through read-only checks of node status, logs, serial output, and repair history. Receive documented recovery guidance to apply yourself.

• Investigate nodes stuck in NodeStatusUnknown
• Find kernel panic or hardware failure evidence
• Check node auto-repair settings and failures

Manage NodeGroup resources in a KubeSphere environment, including creation, updates, and deletion. Bind or unbind nodes, namespaces, and workspaces, verify changes, and investigate synchronization problems or deployment settings using the bundled API script.

• Inspecting and updating NodeGroup resources
• Binding nodes, namespaces, and workspaces
• Investigating synchronization failures

pen.dev CLI（`pencil` / `pen`コマンド）だけを使って、.penファイル（pen.devで作成されたデザインファイル）の中のNodeのデザインデータ（属性・構造）とスクリーンショット画像を読み取り専用で取得するスキル。Node ID指定に加え、名前の正規表現（例: 「ヘッダー」「.*Button」）、Nodeタイプ（frame / text / image など）、再利用可能コンポーネント、特定Node配下、ドキュメント全体のトップレベルなど、**ID以外の指定方法**にも対応する。ユーザーが「.penのこのNodeの中身を見せて」「特定コンポーネントのデザインデータを取り出して」「Nodeのスクリーンショットだけ欲しい」「ヘッダーの構造を確認したい」「ボタンのスタイルをコピーしたい」「再利用可能コンポーネント一覧を見せて」「ドキュメント全体の構造を覗きたい」「全てのテキストNodeを取得して」のように.pen内の要素の調査・参照・確認・抜き出しを依頼した場合に必ずこのスキルを使う。インタラクティブモード（`pencil interactive`）で `execute` の `Get` / `Print`（読み取り専用関数のみ）を使ってNode属性を取得し、同じ `execute` の `Export` / `TakeScreenshot` で画像を`.pen`と同階層の`snapshots/`にPNG出力する。編集はしない（`save()` も変更系関数も呼ばない）ため、対象ファイルは絶対に書き換わらない。pen.dev MCPには依存せず`pencil`コマンドのみで完結。

The English summary is being prepared. Showing the original description.

Write JavaScript for n8n Code nodes to aggregate, filter, and transform workflow data. Guidance covers data access, output formats, execution modes, common errors, and performance choices when processing large numbers of records.

• Aggregating and deduplicating multiple records
• Transforming complex API responses
• Fixing data access and return format errors

Write JavaScript for n8n Code nodes to aggregate, filter, and transform workflow data. Guidance covers data access, output formats, execution modes, common errors, and performance choices when processing large numbers of records.

• Aggregating and deduplicating multiple records
• Transforming complex API responses
• Fixing data access and return format errors

Use Bun to run JavaScript and TypeScript, manage project dependencies, build applications, and run tests. Includes guidance for choosing between Bun and Node, migrating existing projects, and configuring deployments on Vercel.

• Setting up a new JavaScript or TypeScript project
• Migrating scripts and dependencies from Node to Bun
• Writing and debugging tests with bun test

Debug Node.js from the terminal by pausing execution, inspecting variables, and tracing function calls. Use interactive commands or scripts to investigate failing tests, collect runtime state, and capture CPU profiles or memory snapshots.

• Inspecting intermediate state in failing Node.js tests
• Tracing function calls and unexpected variable values
• Investigating stalled asynchronous processing

Configure n8n nodes by checking which fields each operation needs and which settings reveal additional options. Start with a minimal configuration, validate it, look up unclear properties, and make targeted edits to existing code or text fields.

• Checking required fields when changing a node operation
• Finding why a configuration field is hidden
• Editing part of a long code or text field

Guides Node.js scripts and shared modules in the Handsontable monorepo using .mjs files, native APIs, and asynchronous file operations. It covers task registration, error handling, and compatibility across Linux, macOS, and Windows.

• Create build scripts and shared Node.js modules
• Replace shell commands with cross-platform Node.js code
• Register tasks and dependencies in tasks.json

Diagnose GKE nodes marked NotReady or Unknown using node conditions, events, logs, and resource metrics. The skill gathers evidence, distinguishes temporary transitions from faults, and proposes fixes for a person to apply.

• Investigate persistent NotReady or Unknown node status
• Check why kubelet stopped reporting node status
• Investigate evictions or Pending Pods linked to node health

Configure n8n nodes by checking which fields each operation needs and which settings reveal additional options. Start with a minimal configuration, validate it, look up unclear properties, and make targeted edits to existing code or text fields.

• Checking required fields when changing a node operation
• Finding why a configuration field is hidden
• Editing part of a long code or text field

Recover from stale RFDB nodes that survive `commit_batch` cleanup despite having their `file` field listed in `changed_files`. Use when: (1) re-running an enricher/orchestrator step but old data with the same file field stays in the graph, (2) `commit_batch(changed_files=[X], ...)` reports success but a query later still returns nodes with `file = X`, (3) you re-pointed structural nodes (e.g., DIRECTORY/FILE) from a synthetic file path to real file paths and the old synthetic-path nodes won't go away, (4) graph-stream / find_by_type returns a mix of "stale" and "new" nodes for the same logical entity. Root cause: `handle_commit_batch` calls `engine.find_by_attr({file: X})` to enumerate nodes-to-delete, but that query path returns only a PARTIAL set after compaction (L1 segments and the file→nodes index can desync). Workaround: enumerate stale nodes via the TS rfdb client `queryNodes({file: X})` (different code path that finds all of them) and call `deleteNode(id)` per node, then re-commit the intended state. Related: rfdb-manifest-l1-carryforward (same L1 family).

The English summary is being prepared. Showing the original description.

Investigate Node.js bugs by pausing execution, examining variables, and stepping through code. Diagnose stalled asynchronous work and unreliable tests, or collect memory snapshots and CPU profiles to investigate growing memory use and slow execution.

• Investigate stalled asynchronous work
• Debug tests that fail inconsistently
• Examine startup timing and child processes

Assess Node.js applications for unsafe input handling and configuration weaknesses. The skill covers prototype pollution, where shared object properties are altered, plus template and command injection, proxy trust issues, and file exposure, with checks for observable impact.

• Investigate prototype pollution in Node.js APIs
• Check Express proxy trust and IP restrictions
• Review template rendering and command execution inputs

Discover OPC UA servers, connect MATLAB clients, and browse/navigate server nodes using opcuaserverinfo, the Local Discovery Service (LDS), opcua, connect, setSecurityModel, certificate-trust functions, findNodeById, opcuanode, and Namespace/Children traversal. Use when finding OPC UA servers on the network, querying endpoints and security policies, connecting to a server, authenticating with username/password or certificates, configuring security modes, handling certificate-trust or hostname-mismatch errors, troubleshooting failed connections or empty discovery, inspecting an OPC UA certificate (.der/.pem), browsing an address space, finding nodes by name or NodeId, navigating node hierarchies, invoking method nodes, or batch-processing large namespaces. Trigger on: opcuaserverinfo, LDS, opcua, opc.ua.Client, setSecurityModel, opc.ua.trustServerCertificate, OPC UA certificate, findNodeById, opcuanode, browse OPC UA, find node, OPC UA namespace, OPC UA method node, Industrial Communication Toolbox.

The English summary is being prepared. Showing the original description.

Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + `temps agent`, wired with the real multi-host overlay (VXLAN, compute_cidr allocation) via `tools/dev-cluster/` in whichever checkout/worktree you run it from. Invoke when the user says "start the temps cluster", "spin up a multi-node dev cluster", "test this with multiple workers", "bring up worker nodes locally", "docker in dind cluster", or wants to verify cross-node behavior (node targeting, cluster DNS, overlay networking, node join/mTLS) that a single-node `start-temps` server cannot exercise. Distinct from `start-temps` (single-node, native binary, port-slot based) and `start-temps-ee` (single-node EE binary) — this is the only path that actually has more than one node.

The English summary is being prepared. Showing the original description.

Helps build JavaScript and TypeScript projects with Bun, covering setup, package management, testing, and bundling code for distribution. It also guides migration from Node.js and use of Bun’s built-in APIs.

• Start a JavaScript or TypeScript project with Bun
• Migrate an existing Node.js project to Bun
• Set up tests and production builds

Build, debug, and refactor JavaScript applications for browsers and Node.js. Covers asynchronous tasks with async/await, module organization, performance checks, and test creation, with explicit error handling and modern ES2023+ syntax.

• Build a vanilla JavaScript application
• Fix errors in asynchronous API requests
• Organize code into ESM modules

Fix nodes silently disappearing from RFDB when an enricher or post-resolution pass writes new nodes via BatchHandle. Use when: (1) writing a TypeScript enricher that should ADD nodes/edges to existing files, (2) after calling `client.createBatch()` + `batch.addNode({file: 'X', ...})` + `batch.commit()` the original nodes in file X have vanished, (3) tests that load a graph fixture, run an enricher, then query original nodes get empty results, (4) a verification step shows expected nodes pre-enrichment but 0 post-enrichment. Root cause: `BatchHandle.commit()` invokes RFDB's `commit_batch` which AUTO-POPULATES `changed_files` from each added node's `file` field, then the server DELETES all existing nodes whose `file` matches before inserting new ones — file-level upsert semantics. This is correct for the JS/Haskell analyzers (which fully re-emit a file's contents) but catastrophic for enrichers that only ADD to existing files.

The English summary is being prepared. Showing the original description.

Build or review server-side APIs in Node.js, Express, and Next.js. Apply patterns for organizing business logic and data access, reducing unnecessary database queries, caching results, validating requests, and handling authentication and errors.

• Designing APIs and separating business logic from data access
• Reducing repeated database queries
• Adding caching and background processing

Diagnose GKE TPU node pool creation or expansion failures despite reserved capacity. Trace which virtual machines and unhealthy node pools occupy reservation slots, check automatic repair settings, and provide remediation steps for the user to apply.

• Investigate TPU capacity errors despite a reservation
• Identify node pools occupying reserved TPU capacity
• Check automatic repair settings on unhealthy TPU nodes

Diagnose GKE TPU virtual machines that remain in repair by checking instance status, host events, and automatic repair history. Understand the impact on grouped TPU nodes and identify recovery steps for the user to apply.

• Investigating TPU VMs that remain in REPAIRING
• Assessing how a failed node affects a TPU slice
• Checking automatic repair history and failure reasons