'nle' 검색 결과

Manage an electronics bill of materials across distributors and fabricators: part selection, stock, pricing, alternates, ordering, KiCad properties, and BOM/CPL export. Use for distributor-neutral sourcing, cost comparison, order preparation, or requests such as "what parts do I need" and "export for JLCPCB". Do not take over schematic analysis or a complete new-design workflow unless the requested task is specifically its sourcing/manufacturing stage.

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

Generate KiCad schematics from a Circuit Weaver design.yaml or a project's own checked-in generator. Use for large, repetitive, or machine-synchronized designs. Prefer the Circuit Weaver CLI unless the project actually contains and documents its own generation scripts.

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

Generate an institutional-grade commercial real estate underwriting model — input schema (T-12 income, T-3 trailing, rent roll, debt terms, exit assumptions), calc engine (Cap Rate, NOI, Cash-on-Cash, IRR, DSCR, Debt Yield, ROI, Equity Multiple, levered & unlevered returns).

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

FALLBACK ONLY — do not invoke unless you have already ruled out (1) a native API (Gmail API, GitHub API, Slack API …), (2) a CLI (git, gh, aws, npm, curl …), (3) direct file editing, and (4) existing browser automation (Playwright, Puppeteer). Only when all four are unavailable or have already failed should you use this skill. It gives AI agents a cursor and a keyboard on a real desktop — the last mile when the only remaining surface is a GUI. Concretely: use it when an earlier attempt via API, CLI, or direct file edit has failed and the user says things like "open X", "click Send", "type this in Word", "read what is on my screen", "do this in Outlook", "drive the Figma UI", "control my desktop", "automate this workflow", "fill out this form", or "copy text between apps". Works on Windows, macOS, and Linux with any LLM that can call functions (Claude, GPT, Gemini, Llama, Kimi, Ollama) over MCP — stdio for editor hosts (Claude Code, Cursor, Windsurf, Zed) or HTTP for daemons and dashboards.

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

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

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

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

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

法国法领域的法律助理专家。法律研究、法律咨询、法律文书起草、反论证、合同与文件分析、法律动态跟踪、参考文献核验与统一。生成 Word 文档（computer use）或结构化的对话式答复。MCP：OpenLegi、Themia、LegalDataHunter。任何法律问题、任何法国法概念（合同、责任、判例、民法典、法院、损害赔偿）、任何关于欧盟法、欧洲法院（CJUE）或欧洲人权法院（CEDH）的问题，以及任何法国法律参考文献核验或统一的请求，均触发本技能。

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

Use this skill to maintain an agent log in .agents/log, a decision journal shared by the developer and agents. Trigger when the user explicitly asks to use agent-log or record/update an agent log entry; when planning, implementing, or finalizing a significant feature in a repo with an existing .agents/log; or before non-trivial changes or questions in areas covered by existing entries. Never initialize .agents/log unless the user explicitly asks for an agent log.

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

MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.

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

Optimizes natural-language image requests and rough prompts into ready-to-use GPT Image 2.5 prompts using the official prompting guide as a live reference. Use when users ask to improve image prompts, 优化生图提示词, 把想法变成提示词, or write prompts for GPT Image 2.5 Flare or Sunburst. Produces prompt text, not images, unless the user explicitly asks to generate.

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

Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.

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

Build and diagnose visionOS projects with Seiro MCP. Use inspect_xcode_schemes (if needed) -> validate_sandbox_policy -> build_visionos_app -> inspect_build_diagnostics (on failure) -> fetch_build_output (on success), and avoid direct xcodebuild or swiftc unless the user explicitly asks for shell-level execution or MCP cannot handle the task.

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

VitePress documentation workflow for Software Metrics Machine docs under docs/vitepress. Use when creating, updating, reviewing, or restyling SMM documentation pages, especially feature docs that must keep CLI terminal examples and dashboard views/screenshots in sync. Covers Markdown style, VitePress tabs, command examples, dashboard screenshots, sidebar links, and docs validation. USE FOR: docs/vitepress, VitePress docs, documentation style, CLI docs, dashboard docs, screenshots, feature pages. DO NOT USE FOR: application code changes unless needed to verify documented behavior.

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

Use ane for ALL file exploration, discovery, reading, and editing unless the user states otherwise. `ane exec <file> --chord "<chord>"` handles reads (Yank), searches (List), and edits (Change, Delete, Replace, Append, Prepend, Insert). Prefer ane over builtin file tools and shell utilities like grep, sed, and cat.

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

Design, implement, and evaluate risk-based software tests across unit, integration, contract, end-to-end, and regression layers. Use when adding tests, reproducing bugs, improving coverage, diagnosing flaky tests, or defining a test strategy; do not use to change production behavior unless the user also requests implementation.

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

Review application and infrastructure changes for exploitable security risks by tracing assets, trust boundaries, attacker-controlled input, authorization, sensitive data, and dangerous sinks. Use for security reviews, threat-focused PR reviews, authentication or authorization changes, input handling, secrets, dependencies, and infrastructure permissions; do not use to exploit live systems or modify code unless separately requested.

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

Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.

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

Practical UI refactoring and visual design review inspired by Refactoring UI by Steve Schoger and Adam Wathan. Use when an AI coding agent needs to improve an existing interface, audit visual polish, redesign a rough UI, review frontend code for hierarchy/spacing/typography/color/depth/image issues, or turn a plain implementation into a cleaner product-quality screen. Do not use for creating UI from scratch, scaffolding a new app, building a new landing page, or designing a new design system unless the user explicitly asks to review or refactor an existing interface.

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

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.

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

Use TaskBelay for substantial development that benefits from saved progress, verification reuse or interruption recovery, or when explicitly requested. Reuse existing user authority. Skip ordinary questions and small mechanical edits unless requested.

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

Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until it reaches the repository's configured Greptile merge threshold with zero unresolved actionable comments, or until the five-review maximum is reached. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review only for new head SHAs unless a 5/5 score is already published, and repeats. Use when the user wants to optimize a PR/MR/CL against Greptile's code review standards without creating runaway review loops.

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

Identifies likely duplicate profiles or companies using available record evidence. Use when the user provides a list and wants duplicate groups, match confidence, and merge recommendations. Describe records as likely duplicates unless there is an exact deterministic match.

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

Audit or update this Windows computer's fixed third-party Codex helper toolchain when the user requests local helper-tool maintenance. Always show the complete registered list and obtain confirmation for each update group; exclude Codex itself and general runtimes unless explicitly added.

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

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

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