jkit

Jkit Build — Feature Implementation. Build features with specialist agent coordination. Triggers: build, implement, 구현, 만들기, create feature, develop

Jkit Next — What To Do Next. VibeCTO recommends the most impactful next task. Triggers: next, 다음, what next, 뭐 할까, recommend, priority

Jkit Plan — Project Planning. Turn discovered ideas into actionable implementation plans. Triggers: plan, planning, 계획, requirements, TCREI, architecture design

Jkit Review — Code Review & Architecture Verification. Check architecture compliance and code quality. Triggers: review, 리뷰, architecture check, code quality, 코드 리뷰, verify

Jkit Start — Project Discovery. VibeCTO discovers and shapes project ideas through conversation. Triggers: start project, new idea, 프로젝트 시작, 아이디어, begin, create

Architecture Mentor — designs and verifies Clean Architecture structures. Sets up folder hierarchies, dependency injection, and ensures the dependency rule is never violated. Triggers: architecture, clean architecture, dependency, folder structure, DI, separation of concerns, layer, refactor structure, 아키텍처, 폴더 구조, 의존성, 계층, 리팩토링 Do NOT use for: UI implementation, test writing, or backend API work.

Frontend Buddy — UI/UX implementation specialist. Builds pages, components, layouts with Next.js App Router, Tailwind CSS, shadcn/ui. Creates responsive, accessible, modern interfaces. Triggers: UI, component, page, layout, design, responsive, tailwind, shadcn, frontend, CSS, styling, form, button, modal, sidebar, dashboard, 화면, 컴포넌트, 페이지, 레이아웃, 디자인, 반응형 Do NOT use for: business logic, database operations, or test writing.

SaaS Guide — backend integration specialist for Supabase, payments, APIs, deployment. Handles database schema, authentication, RLS policies, payment integration, and production deployment. Triggers: supabase, database, API, auth, payment, subscription, billing, RLS, migration, deploy, vercel, backend, server action, 데이터베이스, 인증, 결제, 구독, 배포, API, 마이그레이션 Do NOT use for: UI components, test writing, or architecture design.

TDD Coach — ensures all code is written test-first using Red-Green-Refactor. Writes failing tests before implementation, guides minimum code to pass, then refactors for quality. Triggers: test, tdd, red green refactor, spec, coverage, vitest, jest, 테스트, TDD, 레드 그린, 커버리지 Do NOT use for: UI work, architecture decisions, or deployment tasks.

VibeCTO — the lead agent who orchestrates the entire project. Discovers user's idea through conversation, decides technical direction, delegates to specialist teammates, and explains every decision at beginner level. Triggers: project, start, plan, idea, build, what should I make, help me build, 프로젝트, 시작, 계획, 아이디어, 만들기, 뭘 만들까, 도와줘, team, coordinate, architecture decision, tech stack Do NOT use for: simple single-file edits or questions unrelated to project work.

1 hook across 1 event