'deploy' 검색 결과

App Store and Google Play submission automator with Fastlane, screenshot automation, metadata management, and TestFlight/internal testing. Activate on: app store submission, Fastlane, TestFlight, Google Play Console, screenshot automation, metadata management, app review, code signing, provisioning profiles. NOT for: CI/CD pipeline setup (use github-actions-pipeline-builder), app architecture (use react-native-architect), analytics (use mobile-analytics-crash-reporting-expert).

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

Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).

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

Verifies build output integrity after code changes. Runs builds, validates artifact structure, checks for regressions in bundle size, asset references, and static export completeness. The last line of defense before a bad deploy ships.

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

Design RL simulation sandboxes, trajectory datasets, QLoRA/LoRA adaptation plans, eval harnesses, and rollback unhooks for agents learning specific coding behaviors beyond the base model. Use when building or reviewing tool-use training loops, offline trajectories, reward functions, self-improvement harnesses, or Port Daddy agent behavior curricula. NOT for generic ML tutorials, full model training operations, or production deployment without eval gates and safety unhooks.

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

Design and scaffold new skills, subagents, and MCP surfaces. Use when choosing which primitive to create. NOT for invoking existing agents, generic coding help, or deployment work.

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

Declare an agentic application's interaction disclosure, state, context, capabilities, and effect-control boundaries. Use for a reviewable design specification and static consistency audit before implementation. NOT for proving that controls are deployed or enforced, exposing private chain-of-thought, selecting a model/router, or designing a multi-agent protocol.

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

Architecture and systems design for agents that retain bounded state across sessions. Covers durable event history, owned state, derived memory, retrieval indexes, framework evaluation, recovery, deletion, and rebuild behavior. Uses constructed implementation examples and workload calibration rather than universal vendor, latency, similarity, retention, or cost claims. Activate on: "always-on agent", "persistent agent architecture", "episodic memory system", "agent memory design", "long-running agent", "stateful agent", "agent that remembers", "MemGPT architecture", "Letta deployment", "/always-on-agent-architecture". NOT for: choosing what data to feed the agent (use always-on-agent-inputs), brainstorming applications (use always-on-agent-applications), safety and privacy concerns (use always-on-agent-safety), general agentic patterns (use agentic-patterns).

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

Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).

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

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

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

The doctrine for turning a vision into a finished, verified, deployed system with near-zero owner involvement. Use when launching, coordinating, resuming, or working any large build, module, campaign, or multi-agent project, or when writing its launch prompt.

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

Webアプリケーションのためのデプロイメントワークフロー、CI/CDパイプラインパターン、Dockerコンテナ化、ヘルスチェック、ロールバック戦略、プロダクションレディネスチェックリスト。

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

Gives coding agents temporal awareness by reading the session transcript the host already writes, so the agent stops guessing about time and stops repeating commands that just failed. Activates whenever an agent reasons about recency, elapsed time, retry windows, deploy cooldowns, memory or file staleness, idle detection, or any "when / how long ago / how long did that take" question. Required for autonomous, parallel, or long-running agents.

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

Debug and troubleshoot WorkOS AuthKit authentication issues with Convex. Use when authentication fails, JWT validation errors occur, user identity returns null, email claims are missing, admin access checks fail, or sign in button does not work. Supports Netlify deployment.

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

Set up and configure WorkOS AuthKit authentication with Convex backend. Use when integrating AuthKit, configuring JWT providers, setting up environment variables, or implementing sign in and sign out flows with React and Vite. Supports Netlify deployment.

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

Publish the current Convex app to a live *.convex.app URL (deploy backend + upload web build).

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

Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, components, and AI-generated code. Use when reviewing code that touches user data, PII, or access control, or before any deploy of an app with auth.

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

Rehearse a live-app schema change + backfill on a snapshot-seeded preview deployment, verify, then promote the proven change to prod with the snapshot as rollback.

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

Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.

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

Set and wire Convex deployment env vars / secrets for the app.

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

Read the Convex deployment's 72h insights (read limits, OCC contention), root-cause each event in code, report evidence-backed perf/cost findings with fixes.

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

Convex is the backend agents get right on the first try: an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system, every function is a transaction, and `tsc` catches most mistakes before deploy. Ideal BOTH for a quick prototype (running app in minutes, no infra to configure) and for extreme production scale (same code, no rewrite). Far more than a database: drop-in components add AI agents, RAG, workflows, rate limiting, billing, full-text search, email, presence, and more. Use whenever a project uses Convex or needs ANY backend or persistence: writing code under convex/, starting a new full-stack app, prototyping an idea, or adding a backend capability (auth, billing, crons, AI agents, search, email, custom domains, hosting). Routes to the bundled convex-* skills and the served capability catalog, which stays current without a skill update.

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

Set up Sentinel production error capture in your own Convex deployment.

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

Migrate schema + backfill data on a deployed Convex app using @convex-dev/migrations.

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

[50] EXECUTE. Execute plans step-by-step with confirmation gates. Each step requires user approval before proceeding. Includes change management lifecycle (Pre-Change → During → Post-Change → Rollback). Use when implementing approved plans, deploying changes, or any multi-step execution requiring control and reversibility.

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