'packaging' 검색 결과

Review a JavaScript SDK release plan or final candidate against the previous release. Check compatibility, packaging, regressions, and Changesets version records, then recommend shipping or blocking with supporting evidence and a separate assessment of documentation coverage.

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

• Review the next SDK release plan
• Assess whether a final release candidate can ship
• Check generated versions and changelogs for consistency

Build or extend a Tutti app with a web interface, server, and shared data contracts. The skill guides local agent execution, dynamic agent selection, app tools, localization checks, packaging, and release workflows.

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

• Building a Tutti app with local agent execution
• Restructuring an existing web and server app for Tutti
• Adding agent selection and app-specific tools

Create or update Codex skills that package specialized knowledge, repeatable workflows, and tool instructions. The guide covers concrete use cases, folder structure, reusable resources, starter generation, and basic validation of names and required metadata.

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

• Turning recurring work into a reusable skill
• Packaging company knowledge and API instructions
• Reorganizing an existing skill and its reference files

Check whether work is ready to call complete by running relevant tests, builds, or other checks. Review fresh output and compare results with requirements, then report completion or remaining problems with supporting evidence.

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

• Checking test and build results before reporting completion
• Confirming that a fix resolves the original bug
• Verifying changes reported as complete by another agent

Investigate bugs, failing tests, and build errors through reproduction, logs, and comparisons with working code. Follow a staged process to test possible causes, implement a focused fix, and check that the problem is resolved.

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

• Investigating failing tests or build errors
• Tracing production bugs through logs and data flow
• Reassessing bugs after repeated failed fixes

Guide feature changes and bug fixes through test-driven development: write a failing test, add the minimum code to pass, then improve the structure. Check coverage and include tests for boundary conditions, errors, and relevant integration points.

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

• Adding features with tests written first
• Writing a regression test before fixing a bug
• Keeping tests passing while improving code structure

Turn raw test results into readable reports with pass and fail totals, unstable tests, and coverage, meaning how much code tests exercise. Package results for releases, quality assurance, or reviews, with follow-up actions.

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

• Preparing test reports for a release
• Turning pytest or JUnit output into a readable summary
• Sharing coverage and quality-gate status

Build an adapter that exposes API, database, or object storage data as files in Mirage. Covers Python or TypeScript implementation, mount configuration, and tests for reading, access restrictions, and supported changes.

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

• Connect an API or database to Mirage
• Implement file operations for a custom data source
• Package a reusable Mirage adapter

Develop reusable external Holoscan Modules with the Holoscan CLI, from scaffolding and testing to Python bindings and package creation. Verify that applications can use installed packages in a clean environment, with checks for each requested format.

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

• Creating a reusable Holoscan operator module
• Adding and testing Python bindings
• Using an installed module from another application

Coordinate the end-to-end CAD/source-asset to SimReady workflow. Use for broad requests such as CAD to SimReady, source asset to simulation-ready USD, or prop packaging that require conversion, material/physics assignment, SimReady conformance, validation, and optional package creation; deploy or verify Content Agents services first when property assignment is enabled; route single-stage work through nested references.

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

Official NVIDIA-authored guidance for navigating PhysicsNeMo — pick the model, datapipe, or example for a SciML/AI4Science task (surrogates, forecasting, downscaling, physics-informed, inverse, generative). Points at existing files via live repo search; never writes code. Do NOT use for installation or environment setup, training-loop or other code authoring/scaffolding, contributor/CI/packaging questions, repo-specific questions in physicsnemo-sym/-cfd/-curator, or general (non-physics) ML/PyTorch.

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

Build, migrate, review, and maintain third-party NVIDIA NeMo Fabric adapters against the public adapter contract. Use when creating adapter or target descriptors, mapping AgentConfig into an agent harness or custom-agent runtime, implementing start/invoke/stop, declaring schemas and capabilities, packaging discovery metadata, or assessing adapter conformance. Do not use for consumer applications that only call the NVIDIA NeMo Fabric SDK.

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

Package reusable NeMo Relay behavior as an embedded component or an independently distributed plugin. Design shared configuration, validate it before activation, and register behavior with rollback handling so failed setup does not leave partial changes active.

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

• Share runtime behavior across Relay applications
• Validate plugin configuration before activation
• Package a native Rust plugin or a local gRPC worker

Use when choosing or evaluating a startup revenue model, pricing/value metric, packaging/tier design, or calculating unit economics (LTV, CAC, payback, gross margin, NRR), including usage-based/credit/AI pricing and variable compute/COGS constraints.

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

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

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

Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use eas-app-stores.

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

Creates and deploys Node.js HTTP web applications on AWS Lambda Web Functions. Guides users through building web apps and APIs with Express, Fastify, or Hono, packaging, deploying via the aws lambda-web CLI, and iterating. Triggers when user wants to deploy a website or web app to AWS as serverless, deploy a Node.js HTTP server to AWS, build a serverless website or API with Node.js, deploy Express/Hono/Fastify apps, set up multi-region HTTP endpoints, connect a Node.js web app to private VPC resources, or explicitly mentions Lambda Web Functions. Does NOT trigger for non-Node.js runtimes, event-driven patterns (SQS, Kinesis, S3 events), or container deployments.

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

Authors and edits AWS Step Functions state machines: writes Amazon States Language (ASL) in JSONata, and chooses and structures state types (Task, Choice, Map, Parallel, Pass, Wait, Succeed, Fail). Covers ASL syntax, JSONata data transformation and variables, Retry/Catch error handling, service integrations (.sync, waitForTaskToken callbacks), Distributed Map for large-scale S3/CSV processing, saga/compensation patterns, Standard vs Express workflow choice, TestState API unit testing, and migrating state machines from JSONPath to JSONata. Use when the user is building, authoring, debugging, or migrating a Step Functions state machine or ASL definition, or orchestrating multi-step workflows with branching, retries, or human-approval callbacks, even if they don't say 'Step Functions.' Do NOT use for general Lambda function code, API Gateway, EventBridge wiring, or SAM/CDK application packaging.

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

Pythonic code with modern type hints, dataclasses, async patterns, packaging, and testing

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

Create irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity. Use when the user mentions "grand slam offer", "make my offer more compelling", "what bonuses should I add", "guarantee strategy", "offer naming", or "people say its too expensive". Also trigger when packaging a product for higher perceived value, justifying premium pricing instead of discounting, designing a money-back guarantee, or structuring tiers to maximize conversions. Covers the MAGIC naming formula and starving-crowd targeting. For product positioning, see obviously-awesome. For outbound sales, see predictable-revenue.

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

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

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

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).

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

Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.

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

Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.

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