菜单
Bun runtime, package management, HTTP server, and testing conventions. Use when working with bun, bun test, bun build, Bun.serve, or building JavaScript/TypeScript projects with the Bun runtime.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | bun |
| description | Bun runtime, package management, HTTP server, and testing conventions. Use when working with bun, bun test, bun build, Bun.serve, or building JavaScript/TypeScript projects with the Bun runtime. |
bun init - create projectbun install - faster than npm/yarnbun run dev - run dev serverbun test - Jest/Vitest compatiblebun build - production bundlingBun.serve() for HTTP serverBun.file() for file operations.ts and .js natively - no transpilerawait req.json(), Response.json(data)import { Database } from "bun:sqlite"Bun.password.hash()bun.lockGodot 4.x engine with GDScript, MVC architecture, headless testing, JSON configs, and performance patterns (MultiMesh, flow-field, decoupled simulation). Use when working on .gd files, Godot projects, game development with Godot 4, or any task involving the Godot engine CLI, project structure, GDScript coding conventions, Godot 4.x version-specific syntax, or game architecture patterns.
Concatenate many files in a directory into a single markdown document when the user asks to read, analyze, scan, load, dump, audit, concatenate, or merge many files in a project or folder at once. Triggers on phrases like "read all files", "analyze the project", "load every file", "concatenate files in folder X", "give me everything in src/", "audit the code", or wants to understand an entire codebase as a whole. Specifically when 5 or more files would otherwise need to be read individually.
Git + GitHub CLI workflow for solo projects. Conventional Commits, branch naming, destructive-command safety rails, and the merge/PR/keep/discard decision. Use when committing, branching, merging, rebasing, pushing, opening a PR, running git status/log/diff, or using the gh CLI for issues/PRs/CI runs.
Pine Script v6 for TradingView .pine files: indicators and strategies. Use when adding inputs (input.int, input.source, input.float, input.color, input.session), plots, signals, alerts, requests (request.security), tables, labels, lines, or any feature to a .pine file, or when discussing TradingView indicators, strategies, performance, common Pine Script v6 issues, or the AFTC coding standards (color.new with RGB, camelCase with boolean prefixes, 80-char section separators, START/END markers). Content targets Pine Script v6 specifically - Pine Script v5 has different syntax for some features.
Web frontend development: HTML5, CSS3, SCSS, Tailwind, accessibility, and performance. Use when working on full web frontend projects, choosing between CSS approaches, or auditing accessibility/performance.
Angular framework with standalone components, signals, the new control flow syntax, and the ng CLI. Use when working with Angular, ng generate, signals, inject(), or standalone components in .ts files.