418건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build the native MSIX isolated-session Gateway from npm latest, a published packaging release with -GatewayChannel Packaged, or explicit openclaw sources. Register it beside the Store Gateway and run Companion with OPENCLAW_NATIVE_GATEWAY_DEV_PATCH. Use for native Gateway development, release-channel compatibility, unreleased source changes, or removing a development Gateway.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first. Use for "audit my channel", "why isn't my channel growing", "review my videos", or a pasted channel URL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and lint the title and thumbnail for a YouTube video as one pairing, checking truncation, duplication and vagueness before publish. Use for "title ideas", "what should I call this", "thumbnail text", "my CTR is bad", packaging, or any request to rename or repackage an existing video.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds robust Python MCP (Model Context Protocol) servers with FastMCP — tool design, error contracts, event-loop-safe blocking work, subprocess/CLI wrapping, single-file vs packaged distribution, global-state-free testing, and prompt-injection awareness. Use when writing an MCP server, exposing a tool or CLI to an LLM client, debugging tool registration/packaging, or testing MCP tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update skills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews React Native TV apps for focus/D-pad navigation, 10-foot UI layout, TV playback/DRM integration, low-memory TV performance, and TV accessibility. Use when building, debugging, or reviewing react-native-tvos, Expo TV, Amazon Vega/Kepler, or React Native web TV targets where the issue depends on remote input, TV focus, TV packaging, TV hardware, or TV playback constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assemble a submission-ready replication package to the AEA Data and Code Availability Standard (DCAS) / openICPSR / Social Science Reproduction Platform expectations — standard replication README, dataset manifest, computational-requirements capture, a Table/Figure → script:line map, and a confidential-data deposit plan. Use when user says "build the replication package", "prepare the openICPSR deposit", "make the AEA data and code package", "DCAS compliance", "assemble the deposit for the journal", or after a paper is accepted and the journal's data editor needs the package. NOT a numeric verifier — it calls /audit-reproducibility to confirm claims reproduce before packaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Desktop JVM and build traps: JNA natives, bundling, memory, packaging, code signing, R8, deep links, Gradle and CI releases. Use when a desktop build fails packaged, signed, on another OS or arch, or in CI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely package codebases with repomix by automatically detecting and removing hardcoded credentials before packing. Use when packaging code for distribution, creating reference packages, or when the user mentions security concerns about sharing code with repomix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing migration plan: the new value metric, fences, agent-tier design, cannibalisation math, and a phased migration for existing customers. For general pricing and packaging strategy use pricing-strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help users validate willingness-to-pay, select the right value metrics, and continuously optimize pricing and packaging to drive growth.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when packaging AISTATS code, data, proofs, simulation scripts, notebooks, random seeds, and logs as anonymous supplementary evidence or public post-acceptance artifacts, even when there is no separate artifact badge. Covers what statistically minded AISTATS reviewers inspect first and how to make Monte Carlo studies turnkey.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when packaging code, models, datasets, or media as ACM MM (ACM Multimedia) artifacts — building the anonymous review package versus the public release, and choosing between the Open Source Software Competition, the Dataset track, the Reproducibility track, and main-track supplementary evidence, each with its own blinding and expectations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when organizing the ACM MM (ACM Multimedia) supplementary material due after the paper deadline — deciding what belongs in the 6-8 page body versus the supplement, packaging video/audio/interactive demos that render on a reviewer's machine, keeping all assets anonymous for double-blind tracks, and pointing to code and data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when packaging ACM CCS artifacts for the artifact-evaluation committee and the ACM badges — Artifacts Available, Artifacts Evaluated Functional, Artifacts Evaluated Reusable, and Results Reproduced — covering what security evaluators inspect, how to make attacks and defenses turnkey, and how to justify withheld artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.