스킬 찾기

Review the EF Core migrations a release (or a PR) carries against how Voxt is deployed: a rolling update whose new pods wait for the migration Job, while old pods keep serving. Use before cutting a release branch, before merging a PR that adds a migration, or when the user says "check the migrations", "are the migrations safe to ship", "expand/contract check", "/migration-release-check". Reports risks; never blocks, edits or runs anything on prod.

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

Use when more than one agent may need the same single-instance resource at the same time — most of all the local server loop, which holds the one URL (https://local.voxt.ai, port 7080) the app can run on. Also when you are about to dispatch several agents that will test the UI, when you find another agent already using the loop, or when the user says "coordinate", "shared resource", "queue for the server".

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

Use when the user says "review bugs", "/review-bugs", "pull new bugs", "what was reported in Bugs", "update the bug list", or asks for an auto-review of reported bugs. Pulls the new messages from the Voxt Bugs and Bugs (Mobile) chats, turns them into entries in docs/bugs.md, reconciles the list with GitHub issues, pull requests and dev commits, moves finished bugs to docs/bugs-closed.md, and lists what needs a human decision.

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

What this project has already learned the hard way, and where any new such fact belongs. Two jobs. (1) Routing: this project keeps NO per-project Claude memories — read this before writing anything down, and pick a durable home from the list here. (2) An index, by area, of non-obvious facts worth knowing before you guess: debugging rigs and measurements that lie, iOS/WebKit and the tethered iPhone, the Windows app, production and deployment, and general codebase traps. Use before setting up a browser- or server-driven debugging session, when a bug reproduces only on iPhone, in Safari or in the Windows app, before changing deployment configuration or reading store/crash data, when something behaves unexpectedly and you are about to guess why, and whenever you are tempted to record a fact for later.

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

Cut a new Voxt release. Use when the user says "prepare a release", "cut a release", "release Voxt", "do a release", "/prepare-release", or wants to run nbgv prepare-release, bump the version, generate end-user release notes, and announce them in the Releases chat.

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

Use when work on a task is about to start or has just started — after a design or plan is approved, when a feature branch is created or resumed in a new session, when the first commit lands on a branch that was only claimed — or when the user says "link this to an issue", "find the issue for this", "put it on the board", "claim the issue", or "/track-issue".

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

Instruments and workflow for debugging the VirtualList — the chat transcript (`InfiniteList`) and the sidebar (`FiniteList`). Covers the built-in consistency checker, the on-screen overlay, the five `?vl*` URL flags, the touch-gesture rig, the frame recorder, attaching to a real Android device over CDP, and how to read a trace without being fooled by a measurement artifact. Use when the list jumps while scrolling, blanks, sticks on skeletons, or the overscroll/bounce misbehaves. The component's specification is `docs/ui/virtual-list.md`; this skill is only how to *measure* it. Pairs with /debug-ui (browser side) and /server-loop (server side).

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

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

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

Drive the Voxt UI from Codex — chrome-devtools MCP setup, debugUI helpers, fast multi-user sign-in

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

Build, deploy and start the iOS app on a connected iPhone or in the simulator. Use proactively when user asks to test, run, or deploy iOS changes.

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

Stop the ActualChat server

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

Use when the user reports a problem or names a piece of work and wants to start on it in a fresh worktree — "start a task", "new task", "file this and make a branch", "/start-task". Finds or files the GitHub issue, creates the feat/… or bugfix/… branch linked to it, and prints the paste-ready `ai fwt|bwt` (Docker) and `ai os fwt|bwt` (host) commands that open the worktree. Linear flow with hard stops; asks nothing.

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

Publish a tested Voxt release to the stores: Google Play production, App Store review (iOS + Mac Catalyst), Microsoft Store certification. Use when the user says "promote the release", "publish the apps", "release to the stores", "/promote-release", or after /prepare-release once the staged builds have been tested.

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

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.

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

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).

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

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.

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

Find orphan processes holding the server port

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

Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.

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

Use when a feature branch is complete and its history must be cleaned up before merging back to dev — as the final step before creating or merging a PR, or when the user says "prepare for merge", "squash the branch", "clean up branch history", or "/prepare-merge".

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

Inspect and manually purge the Soniox artifacts — transcriptions and uploaded audio files — that offline transcription leaves behind, on dev or prod. Use when offline transcription silently stops working, when Soniox answers 429 `limit_exceeded`, when `SonioxTranscriberTest.OfflineTranscribeWorks` and `CleanerDeletesEnqueuedArtifacts` fail together, or when the user says "sweep Soniox", "soniox/sonoix sweep", "sonoix swipe", "purge Soniox", "check Soniox files", or "is Soniox at the cap".

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

Answer questions about Voxt — its features, what shipped and when, and how to use it — grounded in three sources: the public "Voxt Announcements" chat, the Landing pages, and the user guide. Use when asked things like "what features shipped this year", "list new features", "how do I use <feature>", "what is Voxt", or any product/usage question about Voxt. Answers are cited to the source.

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

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

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

Stream and search iOS device logs. Use proactively when debugging iOS issues or when user asks to check device logs.

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