bichikim

Applies project TypeScript conventions and library-grade module boundaries. Use when writing or editing .ts/.tsx files, designing exported APIs or cross-layer contracts, creating reusable modules, or refactoring dependencies between features, packages, services, and adapters.

Analyze project vulnerabilities with pnpm audit and resolve them automatically when a fix version is available; report unfixable deep dependency issues.

Plan and (only after user confirmation) delete remote and matching local git branches whose PR is already merged or closed (not merged) and that have no remaining commits or file changes. Use when the user asks to clean up, prune, or delete merged/closed branches (브랜치 정리, cleanup branches, delete merged branches).

Remove safe git worktrees that have no uncommitted changes and no commits missing from a pull request. Use when the user asks to clean up, prune, or remove worktrees (워크트리 정리, worktree cleanup).

Applies project conventions for Solid.js components, custom hooks, reactivity, and styling. Use when writing or editing Solid.js .tsx/.ts files.

Write and refine Korean text in developer contexts — code comments, AIDEV-NOTE anchors, commit messages, PR descriptions, review replies, design docs, memory notes — so it reads as natural, grammatical Korean a native engineer would write, not as awkward literal translation, broken word order, or forced metaphor. Use whenever producing Korean prose for engineering work, and especially self-review Korean output before finalizing.

Reduce an existing Codex skill to its minimum useful form, extract on-demand context into linked sibling files, or decide that the skill should be deleted. Use when the user asks to diet, slim, trim, simplify, minimize, reevaluate, or remove bloat from a skill while preserving its trigger behavior, tone, safety constraints, and practical usefulness.

Design, implement, refine, or review user interfaces using logic-driven hierarchy, interaction semantics, readability, and accessibility rules. Use for screens, pages, components, design systems, screenshots, mockups, prototypes, and frontend code when creating a UI, improving one that feels cluttered or confusing, or reviewing UI quality.

Reduce an existing Codex skill to its minimum useful form, extract on-demand context into linked sibling files, or decide that the skill should be deleted. Use when the user asks to diet, slim, trim, simplify, minimize, reevaluate, or remove bloat from a skill while preserving its trigger behavior, tone, safety constraints, and practical usefulness.

Create a GitHub pull request from the current branch—commit uncommitted changes, push, and open a PR against main with an auto-generated title and Summary/Testing body sections.

Use when adding or updating unit tests for create-vibe-start CLI modules, especially Vitest tests that must isolate prompts, shell commands, platform detection, and package imports from real external resources.

Review code for correctness risks, maintainability, security, and lifecycle issues with severity-tagged findings.

Update an existing GitHub pull request for the current branch—commit and push latest changes, then refresh the PR title and body from the full diff against main.

Interview the user with Socratic questions to turn an ambiguous request into actionable requirements. Use when the user asks for a deep-interview, requirement clarification, or help organizing their thoughts, or when the goal, scope, constraints, or definition of done are unclear. Do not use when the request is already concrete, or for low-value work like typo fixes, small config tweaks, or test top-ups.

Use when creating or updating project-specific Codex skills for create-vibe-start, especially skills stored under .agents/skills with concise SKILL.md instructions and progressively loaded reference files.

Create or update custom React hooks with clear API design, TypeScript-friendly patterns, and test-first workflow. Use when the user asks to make/build/create/modify a custom hook, refactor hook logic, or add/update hook tests.

Write and maintain unit tests with Vitest. Test titles MUST be English `it('should ...')` strings. Use when adding or updating unit tests, improving test coverage, or handling unavoidable coverage gaps with documented ignore comments.

Basic Vitest module mocking pattern with vi.mock.

Keep real exports and override only selected functions in Vitest.

Mocking patterns for Vitest unit tests. Read this only when mocking is required.