一键导入
kysely-converter
Capable of converting raw SQL queries into type-safe Kysely TypeScript code. Knows how to handle various SQL dialects and complex query structures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Capable of converting raw SQL queries into type-safe Kysely TypeScript code. Knows how to handle various SQL dialects and complex query structures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for implementation, review, refactoring, migration, or diagnosis in a React 18 or React 19 project built with Vite 7 when the task requires React design judgment, version compatibility, or a Vite client build decision. The primary scope is browser-rendered CSR SPA/MPA and Vite client builds embedded in an existing backend. Do not use by default for non-Vite React, React 17 or earlier, React 20 or later, Vite 6 or earlier, Vite 8 or later, framework-owned SSR/RSC/server functions, or isolated copy and styling work.
Generate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description, with the plan body written in caveman **full** mode as a register-only transform that preserves every fact, bullet, execution stage, field, and section depth from the normal-mode equivalent. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections keyed to Conventional Commits types so coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Briefset mode emits a parent execution-management document plus N child briefs when the input describes multiple execution contexts. Chat / questions / status reporting stay in normal prose — caveman applies to the saved file only. Use only when the user explicitly asks for the caveman register or invokes this skill by name; for normal-prose briefs use task-brief-creator instead.
Generate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections are keyed to Conventional Commits types so coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Briefset mode emits a parent execution-management document plus N child briefs when the input describes multiple execution contexts. Manual trigger only — use when the user explicitly invokes this skill or asks for a work plan, implementation plan, work brief, task brief, handoff brief, implementation ticket, or task spec for a coding agent. Not for prose summaries, status reports, design docs, or meeting notes. For the plain-language caveman variant, use task-brief-creator-caveman instead.
Use only when the user explicitly invokes this skill.
Analyze repository structure and generate or update standardized AGENTS.md files that serve as contributor guides for AI agents. Supports both single-repo and monorepo structures. Measures LOC to determine character limits and produces structured documents covering overview, optional ownership maps, patterns, conventions, and working agreements. Update mode refreshes only the standard sections while preserving user-defined custom sections, and only modifies AGENTS.md files previously generated by this skill — externally-authored files are reported, never rewritten. Use when the user wants an AGENTS.md generated or refreshed — setting one up for a new repository, onboarding AI agents to an existing codebase, updating an existing AGENTS.md after meaningful project changes, or when the user mentions AGENTS.md. Not for CLAUDE.md, README, or other documentation files.
Orchestrate a large task as a manager-run sequence of isolated sub-agent phases when the user explicitly invokes this skill or asks for this. The main agent decomposes the task into phases of different kinds, picks the topology that fits (linear pipeline, parallel fan-out, dependency DAG, or iterative loop), assigns each phase a capability-by-deliberation tier, and runs each as a fresh isolated sub-agent exchanging file paths only -- never doing phase work itself. It proves any expensive step cheaply before committing, and halts for the user at up to two points: go/no-go before that commitment, and accept/reject on review findings. Runs are resumable by run id; a changed condition re-versions the prior run. For large heterogeneous work: research sweeps, multi-variant runs, migrations, audits. Explicit-invocation only. Not for single-artifact build-review-improve loops (use delegated-review-loop) or single-answer blind verification (use iterative-self-review).
| name | kysely-converter |
| description | Capable of converting raw SQL queries into type-safe Kysely TypeScript code. Knows how to handle various SQL dialects and complex query structures. |
This agent is capable of transforming SQL queries into idiomatic Kysely TypeScript code. It understands SQL syntax and maps it to the corresponding Kysely query builder methods.
SELECT -> .select(), WHERE -> .where()).*), and handling table prefixes.as syntax.DISTINCT and PostgreSQL-specific DISTINCT ON.INNER JOIN, LEFT JOIN, RIGHT JOIN, and other join types with complex ON conditions.=, >, <, etc.).AND, OR) using expression builders.NULL checks (IS NULL, IS NOT NULL).IN clauses and pattern matching (LIKE).GROUP BY and HAVING clauses with aggregate functions (COUNT, SUM, AVG, MAX, MIN).ORDER BY (asc/desc), LIMIT, and OFFSET.RETURNING clauses for PostgreSQL to return inserted data.SET assignments for simple values and expressions (e.g., incrementing a counter).WHERE conditions.DELETE FROM statements with conditions.RETURNING clauses for deleted rows (PostgreSQL).ROW_NUMBER, RANK, DENSE_RANK, NTILE, PERCENT_RANK, CUME_DIST.LAG, LEAD, FIRST_VALUE, LAST_VALUE, NTH_VALUE.AVG, COUNT, MAX, MIN, SUM.OVER clauses with PARTITION BY, ORDER BY, and frame specifications using the Kysely expression builder (eb.fn.agg).CASE WHEN ... THEN ... ELSE logic into Kysely's eb.case() chain.sql template tags are needed for unsupported or complex raw fragments.The agent applies specific patterns found in the references/ directory:
select.md: Query structure and clause mapping.insert.md: Insertion patterns and return value handling.update.md: Update logic and assignment expressions.delete.md: Deletion mapping.window_function.md: Complex window function construction using the expression builder.