'tui' 검색 결과

Inspect a declared React Native or Expo feature slice and produce a read-only SwiftUI behavioral parity contract before any implementation.

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

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.

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

Design guidance for changing the @rhinestone/sdk public surface so it is safe, intuitive, and pleasant to integrate. Use when adding, renaming, or changing public exports, types, account/action APIs, config objects, error classes, or defaults in sdk/src.

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

Separates signal from noise in metrics you cannot observe directly, updating a belief from evidence instead of reacting to the latest reading - Bayesian updates over competing explanations, and a filter that says whether this week's move is real. Use when a metric moves and someone wants to act, when diagnosing why traffic or revenue changed, when a dashboard number contradicts intuition, or when deciding whether a trend is real yet.

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

Drive QA of a SwiftUI app on a real iPhone over USB - screenshot, read the accessibility tree, inspect @Observable state, tap, swipe, and type through an HTTP bridge embedded in the app under test. Use when asked to test an iOS app on a physical device, find bugs on the device, or expose a connected iPhone to a remote agent over Tailscale. Requires the ios-agent-qa runtime; not for simulator or XCTest work.

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

How to run tests using remote executor.

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

Model visible context

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

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

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

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

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

Update the title and body of one or more pull requests.

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

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

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

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.

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

Change size guidance (800 lines)

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

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

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

Test authoring guidance

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

Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.

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

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

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

Breaking changes

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

Run a final code review on a pull request

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

Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.

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

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

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

Design and review intuitive, scalable, maintainable HTTP APIs. Use this skill whenever the user wants to design a new REST API, review an existing API or spec, write OpenAPI 3.x definitions, or work with HTTP semantics (GET/POST/PUT/PATCH/DELETE), status codes, idempotency (Idempotency-Key), error envelopes (RFC 7807 problem+json), pagination, filtering, versioning, or API auth (API keys, OAuth2 client credentials, rate limits). Also trigger for "API design", "RESTful", "endpoints", "OpenAPI", "Swagger", "ReDoc", "contract testing", or GraphQL and gRPC design questions.

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

Build a rich, self-contained HTML explanation of a code change — diff, branch, commit range, MR/PR — with background, intuition, a code walkthrough, diagrams, and a glossary, then quiz the reader interactively in chat. Use when the user asks to explain a change, understand a PR/MR, walk through a diff, onboard onto a branch, or says "explain this PR", "what does this branch do", "teach me this change", or "/explain-diff".

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

Use when adding, running, or debugging proctmux end-to-end integration tests, especially PTY/TUI behavior, terminal snapshots, unified/client modes, timing flakes, VT100 emulator limits, or files under tests/e2e and internal/testharness/e2e.

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