'ept' 검색 결과

Write and refine Javadoc comments for Java types and members. Apply consistent summaries and tags for parameters, return values, exceptions, inherited behavior, code examples, version information, and deprecated members with suggested alternatives.

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

• Adding documentation to public Java APIs
• Standardizing parameter and exception descriptions
• Documenting generics and inherited behavior

Generate a customizable AI prompt for finding representative examples in an existing codebase. Configure analysis depth, categories, and snippets so GitHub Copilot can produce exemplars.md with real file references and explanations of coding conventions.

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

• Collecting existing code examples for team guidance
• Documenting patterns to follow when adding features
• Configuring the depth and format of a code example guide

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

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

• Add beginner-friendly explanations to existing code
• Document the reasoning behind syntax and design choices
• Adjust comment depth for readers with different experience

Apply consistent names to SGLang speculative decoding code, which verifies draft tokens to generate text. Distinguish tokens with or without the bonus token, counts, counters, and arrays when adding identifiers, renaming code, or reviewing changes.

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

• Naming variables in speculative decoding code
• Renaming identifiers to match their meaning
• Reviewing metric and counter names

Investigate suspicious mobile apps by examining permissions, network traffic, and runtime behavior. Use observed evidence to identify signs of data theft, SMS interception, credential stealing, or communication with attacker control servers, then classify the suspected malware.

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

• Triaging suspicious APK or IPA samples
• Investigating possible data leaks from mobile apps
• Checking for SMS interception and credential theft

Assess Bluetooth Low Energy devices by capturing wireless traffic, inspecting available data services, and checking pairing security. Identify signs of interception, reused commands, and data access that lacks authentication.

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

• Assess BLE security on IoT devices
• Check whether devices accept replayed commands
• Investigate suspicious pairing and device impersonation

Deploy decoy accounts, service entries, and policy objects in Active Directory to detect suspicious activity. Configure monitoring rules for Windows security events and validate alerts for credential misuse, reconnaissance, and movement between systems.

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

• Detecting Kerberoasting with decoy service entries
• Monitoring attempts to use decoy credentials
• Placing credential traps in decoy Group Policy objects

Turn a feature idea or user problem into a structured specification or product requirements document. Define goals, scope, priorities, success measures, and acceptance criteria, with phased delivery when the request is too large.

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

• Turn a vague idea into a feature specification
• Define feature scope and priorities
• Set success measures and acceptance criteria

Turn descriptions and existing notes into a standard operating procedure, a document explaining how work gets done. Capture process flow, responsibilities, detailed steps, exceptions, and metrics so teams can use it for handoffs or audits.

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

• Documenting a process known only to one person
• Clarifying who performs and owns each step
• Preparing procedures for handoffs or audits

Audit Python SDK logs, exceptions, and telemetry for sensitive data exposure. Trace values to their sources, fix confirmed leaks, and test that redaction hides sensitive information while preserving the caller's expected behavior.

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

• Audit logs and exceptions for sensitive data exposure
• Fix leaks involving model or tool data
• Test redaction and caller behavior

Plan features before coding by defining requirements, acceptance criteria, and scope. Validate the specification, generate starter tests from expected behaviors, and guide implementation and review so each delivered feature can be checked against its agreed requirements.

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

• Define requirements before implementing a feature
• Turn acceptance criteria into starter tests
• Check specifications for missing requirements

Build websites with layered depth, scroll-driven transitions, and animated text using static images, CSS, and JavaScript. The skill covers asset inspection, visual planning, implementation, and checks for performance and motion accessibility.

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

• Build a product landing page with scroll-driven effects
• Add layered depth and animated text to an existing site
• Inspect image transparency and plan asset placement

Review a deal before signing by scoring its margin and risks, flagging problematic contract terms, and recommending named human approvers. It prepares a consistent review packet for discount requests and policy exceptions without automatically approving them.

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

• Reviewing discounts above a sales representative's authority
• Flagging risky contract changes before legal review
• Preparing a margin breakdown for CFO review

Review proposal responses for missing requirements, compare competing products, and plan proof-of-concept trials that test customer needs. Supports technical sales work from requirement discovery and demo preparation through evaluation scorecards and technical proposals.

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

• Checking proposal responses for missing requirements
• Comparing product features against competitors
• Preparing a demo around customer priorities

Break a feature into job stories that describe the user's situation, motivation, and desired outcome. Add six to eight observable acceptance criteria per story, defining how success will be checked, and include links to designs or prototypes.

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

• Breaking a new feature into job stories
• Writing backlog items around user situations
• Defining acceptance criteria for desired outcomes

Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.

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

• Writing test cases from user stories
• Preparing acceptance test scenarios
• Checking invalid inputs and boundary cases

Review a completed development task against its acceptance criteria, check differences from design and architecture documents, and prompt code review. After approval, update the task's status and identify the next story to work on.

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

• Checking acceptance criteria before closing a development task
• Recording differences between implementation and design
• Remembering code review before marking work complete

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

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

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

Turn accepted architecture decisions, project preferences, and engine references into a practical rules document. Organize required patterns, forbidden approaches, and performance limits by architectural layer, with a source attached to each rule.

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

• Consolidating implementation rules from accepted decisions
• Updating rules after architecture decisions change
• Reviewing naming conventions and performance limits

Turn existing game code or prototypes into missing design, architecture, or concept documents. Extract implemented rules, formulas, and technical choices, ask about their intended purpose, and clearly separate observed behavior from unconfirmed interpretations.

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

• Documenting a feature built without a design document
• Understanding an inherited codebase with missing documentation
• Turning a gameplay prototype into a concept document

Turn system structures, processes, and concepts into dark-themed diagrams. Create architecture diagrams, flowcharts, timelines, and other visual explanations as scalable SVG files, with PNG versions for use as images.

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

• Explain system components and their connections
• Map process steps and decision branches
• Show interactions in chronological order

Audit saved project learnings against the current codebase to find outdated explanations, overlapping documents, and contradictions. Maintain the documentation with evidence-based updates, consolidation, replacement, or deletion, and deliver a per-document report with committed changes when applicable.

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

• Checking saved learnings against current code
• Consolidating overlapping knowledge documents
• Correcting outdated paths and links

Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.

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

• Implement an accepted issue within its agreed scope
• Repair a classified pull request finding
• Validate failure, recovery, and cleanup behavior

Use this design reference when planning centrally managed rules for outbound network traffic from a sandbox, an isolated execution environment. It covers design and acceptance gates, but does not itself enforce network restrictions.

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

• Planning centrally managed sandbox outbound network rules
• Reviewing acceptance gates before implementation
• Consulting the gateway reference before adding network controls