'defi' 검색 결과

Create and configure Claude Code agents using Markdown files with YAML configuration headers. Define when each agent should run, write its responsibilities and workflow, choose models and tools, and check configuration and triggering behavior.

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

• Create a Claude Code subagent
• Define triggering conditions with concrete examples
• Configure an agent's model, color, and tools

Turn ready project tasks into clear instructions for AI workers, with defined ownership, deliverables, acceptance criteria, and reporting rules. Handle assignment notifications and check submitted results before passing them to the project management workflow for acceptance.

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

• Writing instructions for ready project tasks
• Defining deliverables and acceptance criteria
• Checking submitted worker results

Create Vally evaluation specifications for skills, custom agents, and workflow packages. Design distinct test requests, prepare fixture files, define automated checks and outcome rubrics, and size comparisons to provide meaningful evidence without favoring the skill’s wording.

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

• Create an eval.yaml for a skill or custom agent
• Define outcome-based checks and judging rubrics
• Prepare fixture files that reproduce specific failures

Investigate code with the lsp tool, which uses a language server to understand names, imports, and types. Find definitions and usages, inspect signatures and file outlines, and check compiler or type errors after edits.

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

• Finding where a function or variable is defined
• Tracing symbol usages across imports and aliases
• Reading type signatures and documentation

Define and check GitHub Copilot instructions and specialized agents using Markdown files. It explains file locations, configuration fields, tool access, path-specific rules, and workflow integration, with examples for documentation, testing, reviews, and other development tasks.

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

• Defining repository-wide coding standards
• Applying instructions to specific directories
• Creating agents for README and test writing

Diagnose missing language features in Kode by checking LSP, the protocol connecting code tools to language servers. Update plugin configuration, confirm servers are recognized, and test an operation such as jumping to a definition.

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

• Diagnosing missing LSP results in Kode
• Adding a language server through a plugin
• Reviewing a plugin's language server configuration

Create and configure Claude Code agents using Markdown files with YAML configuration headers. Define when each agent should run, write its responsibilities and workflow, choose models and tools, and check configuration and triggering behavior.

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

• Create a Claude Code subagent
• Define triggering conditions with concrete examples
• Configure an agent's model, color, and tools

Plan and coordinate penetration tests with checklists covering objectives, scope, environment preparation, tester selection, monitoring, and follow-up. Helps teams define deliverables, prioritize vulnerabilities, arrange fixes and verification, and clean up test accounts and artifacts.

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

• Defining penetration test objectives and scope
• Preparing test environments and monitoring
• Selecting testers and agreeing on report requirements

Build, refactor, or review macOS menubar apps using Tuist and SwiftUI. Separate data models, networking, state management, and views, then align project definitions and launch scripts for consistent local builds and restarts.

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

• Creating a macOS menubar utility
• Separating networking and state management from views
• Organizing Tuist project definitions

Define and launch Marin SkyRL reinforcement learning experiments on Iris. It guides configuration checks, model and data dependencies, small trial runs, and progress verification while keeping artifact versions and runtime revisions explicit.

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

• Define a reinforcement learning experiment
• Check resource allocation and role configuration before launch
• Verify training with a small trial run

Coordinate parallel coding agents by specifying where shared types are defined and requiring reuse of existing definitions. Prompt templates add searches before creating types and TypeScript checks before completion to catch conflicting definitions and type errors.

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

• Sharing type rules across parallel coding agents
• Checking for existing types before adding new ones
• Specifying where shared types should be imported from

Use language servers, tools that understand code structure, to check errors, locate definitions, and find references in Codex. Check whether a symbol can be renamed and apply the rename across the workspace.

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

• Checking code errors after edits
• Locating function or variable definitions
• Finding where a symbol is used

Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit. Use when asked to write a specification, spec a material or system, prepare an NBS-style section, or when a specification produced wildly different tender prices. Produces the scope and interface definition, the performance requirements, the product or system definition, execution and tolerance requirements, and the submittals and testing schedule.

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

Manages Fabric Dataflow Gen2 items, including creation, M editing, connections, output destinations, getDefinition and updateDefinition inspection, executeQuery, refresh history, and Gen1-to-Gen2 save-as upgrades via saveAsNativeArtifact. Use for Dataflow items or Power Query M definitions. For pipeline JSON use pipeline-migration; for Spark or Warehouse transformations use their own skills.

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

Infers person-to-person transmission from pathogen genomes using outbreaker2, TransPhylo, phybreak, BadTrIP, SCOTTI, BEASTLIER, and SNP-distance / cluster-picker approaches (HIV-TRACE for HIV; transcluster). Defines outbreak clusters using pathogen-specific SNP thresholds (NOT a universal cutoff -- TB <=12 SNPs; MRSA <=15; C. difficile <=2; Klebsiella <=21), models within-host diversity and transmission bottlenecks, integrates contact-tracing data, distinguishes generation from serial interval, and attributes source via Bayesian source attribution (islandR). Use when investigating outbreaks for who-infected-whom, defining SNP-cluster outbreak definitions, accounting for unsampled intermediates, choosing between outbreaker2 (rich epi data) and TransPhylo (genomic-only after a dated phylogeny), running source attribution between host populations, calling HIV-TRACE thresholds appropriate to the local subtype, or distinguishing recent transmission from reactivation in TB or chronic HIV.

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

Expert SOX IT General Controls (ITGC) advisor for finance, internal audit and IT compliance teams. Covers the four ITGC domains external auditors test for SOX 404 — access to programs and data, program changes, computer operations, and program development — plus scoping in-scope systems from the financial statements, designing risk-and-control matrices (RCMs), writing control narratives and test scripts, evaluating deficiencies (control deficiency vs significant deficiency vs material weakness under AS 2201 and Reg S-X), drafting remediation plans, SOX 404(a)/404(b) applicability and filer status, IPO readiness timelines, and COSO 2013 alignment. Use this skill whenever a user mentions SOX, ITGC, IT general controls, 404(a)/404(b), ICFR, material weakness, user access reviews, segregation of duties in IT, change management controls for financial systems, SOX testing or walkthroughs, PCAOB audits, or quarterly compliance for financial reporting systems.

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

Authoring ComfyUI v2 frontend extensions with @comfyorg/extension-api, covering defineNode/defineExtension/defineWidget, shell UI (sidebar tabs, commands, hotkeys), typed events, and handles. Use when writing or editing ComfyUI web-UI extension code (custom node JS, sidebar panels, widgets).

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

One-pass crypto read - tracked-protocol positions and health plus macro context, with regime take, DeFi verdict, biggest movers, yields, fees, breadth, Fear & Greed, and prediction markets.

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

指导如何通过自定义注解（如@Unicom）标识Dubbo接口，利用BeanDefinitionRegistryPostProcessor在启动时扫描并动态注册ReferenceBean，实现RPC调用的封装。

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

Use when exposure, outcome, covariate or eligibility definitions and cutoffs need a citable basis before the protocol. Reads the data dictionary first, then maps each variable to a guideline or published definition and the database columns in a citation-backed table.

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

Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy.

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

Synthesize behavioral personas from prior stage evidence for journey mapping and marketing during PRD v0.4 User Journeys. Triggers on requests to define personas, create user profiles, identify target users, or when user asks "who are our users?", "define personas", "user profiles", "target users", "persona creation", "who uses this product?". Consumes CFD- (v0.1-v0.3), BR- (targeting from v0.3 Moat), FEA- (v0.3 Feature Value Planning). Outputs PER- entries with behavioral profiles and feature relationships. Feeds v0.4 User Journey Mapping.

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

Define implementation contracts (APIs and data models) that developers will build against during PRD v0.6 Architecture. Triggers on requests to define APIs, design database schema, create data models, or when user asks "define APIs", "data model", "database schema", "API contracts", "technical spec", "endpoint design", "schema design". Consumes ARC- (architecture), TECH- (Build items), UJ- (flows), SCR- (screens). Outputs API- entries for endpoints and DBT- entries for data models. Feeds v0.7 Build Execution.

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

Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases", "test coverage", "TEST-", "test-first". Consumes EPIC- (scope), API-, DBT-, BR-, UJ-. Outputs TEST- entries with Given-When-Then format. Feeds v0.7 Implementation Loop.

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