'eslint' 검색 결과

Biome v2 unified linter, formatter, and import organizer — single Rust-powered tool replacing ESLint + Prettier with 97% Prettier compatibility and 20x faster performance

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guideline for designing, implementing, and verifying secure TypeScript and JavaScript applications following OWASP Top 10 best practices. Use when the user wants to: (1) review TypeScript or JavaScript code for security vulnerabilities, (2) design a secure Node.js, Deno, or browser application architecture, (3) implement security features (authentication, authorization, cryptography, input validation), (4) audit npm/yarn/pnpm dependencies for known vulnerabilities, (5) create security checklists or verification plans, (6) fix security bugs or harden existing TypeScript or JavaScript code, (7) set up security testing and static analysis (ESLint security plugins, Semgrep, Snyk), or (8) handle any TypeScript/JavaScript security concern including injection prevention, prototype pollution, XSS protection, SSRF prevention, secrets management, and secure deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

用于安全移除前端死代码、未使用导出、陈旧组件、废弃路由、未使用依赖，或由 knip、depcheck、ts-prune、TypeScript、ESLint、人工审查发现的清理目标。不要用于会改变行为的功能重写；中文触发词包括 死代码、清理未使用、refactor clean、依赖清理、删除无用代码。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when safely removing dead frontend code, unused exports, stale components, obsolete routes, unused dependencies, or cleanup targets found by tools such as knip, depcheck, ts-prune, TypeScript, ESLint, or manual review. Do not use for feature rewrites that change behavior; Chinese triggers include dead code, clean up unused, refactor clean, dependency cleanup, delete useless code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing", "kmp testing", or "screenshot testing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures ESLint, Prettier, Ruff, mypy, and .NET analyzers

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing TypeScript code, fixing type errors, or configuring strict type safety. Auto-activates on .ts/.tsx files. Covers null handling, utility types, and ESLint.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing, reviewing, refactoring, or enforcing Angular application architecture with isolated lazy features, eager core/layout, reusable ui/pattern architecture building blocks, one-way dependency graphs, eslint-plugin-boundaries rules, or folder placement decisions. This skill takes precedence over angular-developer when architecture rules conflict with general Angular advice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Re-run the analysis pipeline on all runs matching an RQ, reaggregate metrics, and propose findings updates against the fresh data. Trigger when the user says "reanalyze RQ-N", "reanalyse RQ-N", "Runs neu analysieren", or wants to refresh metrics/findings after a pipeline change (analyze-run.sh fix, adapter added, ESLint config).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Idiomatic programming style, patterns, and conventions for TypeScript and JavaScript development. Trigger when: - Writing, refactoring, reviewing, or debugging TypeScript or JavaScript code. - Files matching the patterns **/*.ts, **/*.tsx, **/*.js, **/*.jsx, package.json are in the workspace or referenced. - Tasks involve: tsc, npm, yarn, pnpm, bun, eslint, prettier, vite, next.js. - Prompt contains keywords: typescript, ts, js, javascript, interface, type, async, await, promise, es6, node, deno.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide TypeScript code quality work. Use when touching TypeScript, TSX, tsconfig, typed ESLint or Biome config, Node TypeScript scripts, or TypeScript-heavy framework code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement Adobe-specific lint rules, CI policy checks, and runtime guardrails covering credential scanning (p8_ patterns), Firefly content policy pre-screening, PDF Services quota enforcement, and OAuth scope validation. Trigger with phrases like "adobe policy", "adobe lint", "adobe guardrails", "adobe eslint", "adobe content policy".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React Three Fiber (R3F, three.js 用 React レンダラー @react-three/fiber v9) のリファレンス。 R3F Canvas props, createRoot, useFrame, useThree, useLoader, extend, attach, primitive, args, piercing, pointer イベント / pointer capture, frameloop demand / invalidate, ThreeElements 型, @react-three/test-renderer, @react-three/eslint-plugin, React Native (Expo), v9 移行。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React (UI ライブラリ本体, react / react-dom 19.3) の公式リファレンス。 Hooks (useState, useEffect, useActionState, useOptimistic, useEffectEvent), use, cache, Suspense, Activity, ViewTransition, createRoot, hydrateRoot, createPortal, flushSync, react-dom/server, Server Components / Server Functions, React Compiler, eslint-plugin-react-hooks, DevTools, Rules of React。React Router・Next.js・TanStack 系・RHF とは別。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TanStack Router (型安全 React ルーター、@tanstack/react-router) の API リファレンス。 React Router (react-router) とは別ライブラリ。 createRouter, createFileRoute, createRootRoute, createLazyFileRoute, createLazyRoute, Link, Outlet, useNavigate, useParams, useSearch, useLoaderData, useBlocker, loader, beforeLoad, validateSearch, redirect, notFound, Await, file-based routing, routeTree.gen.ts, router-plugin, tsr CLI, code splitting, SSR, TanStack Query 統合, eslint-plugin-router。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TanStack Query (React Query) v5 (@tanstack/react-query) の API リファレンス。 useQuery, useQueries, useInfiniteQuery, useMutation, useSuspenseQuery, QueryClient, QueryClientProvider, queryOptions, HydrationBoundary, invalidateQueries, prefetchQuery, skipToken, keepPreviousData, placeholderData, staleTime, gcTime, optimistic updates, SSR / hydration, persistQueryClient, eslint-plugin-query。 kubb（フック生成側）とは別。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Biome (Rust 製フォーマッター・リンター) リファレンス。 JavaScript / TypeScript / JSX / CSS / JSON / GraphQL / HTML (Vue, Svelte, Astro) 対応。 biome.json, biome check / lint / format / ci / migrate / upgrade, linter ルール・preset・domains, GritQL プラグイン, assist (organizeImports), suppressions (biome-ignore), LSP / VS Code / Zed, ESLint / Prettier 移行, monorepo, CI。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work on the dashboard's frontend — the vanilla JS/CSS page with no framework or bundler. Use this whenever a task touches `static/nowplaying.js`, `static/style.css`, the Jinja templates (`templates/nowplaying.html`, `_icons.html`), the accent-color tinting, the karaoke lyrics sync, the now-playing poll, or the empty-state mosaic / recent-plays pile. Covers how the page is wired, how it reads i18n and data from the server, the ESLint gate, and the Android bridge, so changes match the existing patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Quality gates determinísticos para aplicações e serviços Node.js, JavaScript e TypeScript. Use quando o usuário pedir "quality gate Node.js", ESLint ou tsc em Node.js, testes, cobertura, complexidade, SAST, SCA, build ou baseline para Node.js.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Quality gates determinísticos para Vue.js, JavaScript e TypeScript. Use quando o usuário pedir "quality gate Vue.js", ESLint, vue-tsc ou Vitest em projeto Vue.js, cobertura, complexidade, bundle, acessibilidade ou baseline para Vue.js.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.