clickhouse-js-node-coding
Write idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-20 00:12
41,970 results
Write idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js…
Generate TypeScript/JavaScript code that reads/decodes AND writes/encodes ClickHouse RowBinary streams for the ClickHouse HTTP server. Use this skill whenever…
Use when a user wants to build an application with ClickHouse, set up a local ClickHouse development environment, install ClickHouse, create a local server,…
Sets up and manages ClickHouse using the clickhousectl CLI — installs and runs a local ClickHouse server for development, and creates managed ClickHouse Cloud…
Use when the user needs to search or navigate code with Sourcegraph MCP tools. Provides disciplined search workflows for finding implementations, understanding…
Migrates Next.js projects to vinext (Vite-based Next.js reimplementation). Load when asked to migrate, convert, or switch from Next.js to vinext. Handles…
Run CodeRabbit CLI reviews, retrieve saved local or GitHub PR fix prompts, and interpret CodeRabbit authentication and review output. Use for CodeRabbit review…
The spec-coding methodology for AI-assisted development. Use when planning features, creating/refining/implementing/verifying specs, or organising a project.…
Maintain `.codestable/architecture/` this system map that records only the current state, with three modes: update / check / backfill. Trigger: the user says "refresh architecture", "do an architecture check", "backfill the architecture doc for this module", "do the design and code match", or feature…
Do targeted code exploration on a repository and distill "question → read code → reach conclusions" into searchable evidence, with three types: question / module-overview / spike. Trigger: the user says "explore this first", "how is X implemented in this repo", "quickly get familiar with this module", "archive the exploration results".
Implement new features or feature changes. Not for pure bug fixes (cs-issue), behavior-equivalent refactoring (cs-refactor), or breaking down large requirements (cs-epic).
Deprecated compatibility entry: used by old cs-feat-accept calls; forwards to cs-feat --stage accept. Do not proactively choose it for new requests.
Deprecated compatibility entry: for legacy cs-feat-design calls; forwards to cs-feat --stage design. Do not actively choose it for new requests.
Deprecated compatibility entry: for old cs-feat-impl calls; delegates to cs-feat --stage impl. Do not actively select for new requests.
Diagnose or fix a bug, error, performance regression, or abnormal existing behavior. Not for new features (cs-feat) or behavior-equivalent refactoring (cs-refactor).
Deprecated compatibility entry: for legacy cs-issue-analyze calls; forwards to cs-issue --stage analyze. New requests should not actively select it.
Deprecated compatibility entry: used by old cs-issue-fix calls; hands off to cs-issue --stage fix. Do not actively select for new requests.
Deprecated compatibility entry: used by old cs-issue-report calls; hands off to cs-issue --stage report. Do not actively choose it for new requests.
Generate reference documentation for each entry on the library's public surface (components / functions / commands), with manifest tracking, supporting both single entries and batches. The information source is the source code itself (unlike the guidedoc task-oriented approach). Trigger: the user says "write API docs", "component docs", "libdoc", or a new public interface is discovered after acceptance.
attention short-rule append. Trigger: one- or two-line project rules that are long-lived and must be known in every session; detailed experience goes to cs-keep, structural decisions go to cs-domain.
Behavior-equivalent refactoring, splitting, and performance optimization. Requirements that change externally observable behavior go to cs-feat or cs-issue.
Deprecated compatibility entry point: used by old cs-refactor-ff calls; delegates to cs-refactor --mode fastforward. Do not select it proactively for new requests.
Organize reusable programming patterns / library usages / technical techniques into a prescriptive reference library, with three types: pattern / library / technique. Trigger: when the user says "record a technique", "this usage is worth recording", "tricks", "record library usage", or when the design / analyze phase discovers a technique worth capturing. Push it.
API versioning strategies for ASP.NET Core. Covers Asp.Versioning library, URL segment, header, and query string strategies, version deprecation, and OpenAPI…