toss
- 36 skills
- 0 followers
- 5 days ago last updated
- ▌ Inject · toss bundlePatch an existing Apps in Toss mini-app's build setup. Three facets: `/ait:inject-devtools` adds the `@apps-in-toss/devtools` unplugin for browser dev, registered for whichever bundler the project uses ("기존 Vite 프로젝트에 devtools 붙여줘", "Rspack 쓰는 기존 프로젝트에 devtools 붙여줘"); `/ait:inject-debugger-client` installs `@apps-in-toss/debugger-client` (on-device attach) as a devDependency behind an opt-in build flag so release builds do not contain it; `/ait:inject-tossface` wires the Tossface emoji web font (CDN link or subset bundling) into the project's global stylesheet. Idempotent, minimal edits. This skill only INSTALLS packages/assets into a build setup — it never diagnoses a running app. "폰에서 이상하게 동작하는데 디버깅하고 싶어" / "라이브 상태를 보고 싶어" is `debug`, not this.
- ▌ Launch · toss bundlePre-launch check, review request and rejection handling for an Apps in Toss mini-app (검수 = the Apps in Toss app review, not code review). Use it right away for "검수 넣기 전에 한번 봐줘", "출시해도 되는지 점검해줘", "검수 요청 넣어 줘", or a pasted rejection ("검수에서 반려됐어. 사유가 …"); it reads the project itself, so don't ask which files first. Checks code against the official checklist and console review state, and drafts an inquiry when the cause isn't in the code. Use it before any `bundle_submit_review` call: it shows the full request and submits only after the user approves it; never releases or rolls back. It refuses to propose a submission for a deployment recorded as a debug build or whose uploaded output contains debug-tool markers. Phone testing is `/ait:test-on-device`; screen fixes, even for review criteria, are `/ait:design`. Triggered by `/ait:launch [rejection reason]`.
- ▌ Server · tossWrite or review the server side of an Apps in Toss mini-app: any backend that stores per-user data or calls the Apps in Toss partner API (Toss login token exchange, anonymous-key exchange, other partner calls), on Cloudflare Workers, Node, a BaaS (Supabase, Firebase) or any other hosting. Use it right away, before writing server code, for "서버에 저장해서 다른 기기에서도 보이게 해줘", "서버 붙여줘", "Supabase·Firebase에 내 기록 저장해줘", "Workers로 서버 만들어줘", "토스 로그인 붙여줘" (even client side only — login needs console setup and a server exchange), "서버에서 사용자 구분은 어떻게 해?", or "getAnonymousKey 값을 서버에서 그대로 써도 돼?" — even when the user only names the feature. It decides how the server identifies users (anonymous-key exchange vs Toss login), wires mTLS for partner API calls, parses the resultType envelope and sets exact CORS origins, then writes or fixes the code. Keeps the user's chosen hosting. Deploys only when asked; no console calls. Client screens are `/ait:design`; phone testing is `/ait:test-on-device`. Triggered by `/ait:server [request]`.
- ▌ Feature · toss bundleImplement an Apps in Toss SDK feature in the user's existing project: banner / interstitial / rewarded ads, in-app purchase (IAP), share, game-center leaderboard, haptics, local storage and other SDK domains. Use it right away for "배너 광고 붙여줘", "보상형 광고 넣어줘", "광고 보면 코인 주는 버튼 만들어줘", "인앱결제 붙여줘", "상품 결제 버튼 만들어줘", "공유 버튼 달아줘", "리더보드 연결해줘", "햅틱 넣어줘", "즐겨찾기를 저장소에 저장해줘" — even when the user only names the feature. Stack-neutral: it reads the project first (web framework of any kind, Unity C#, engine HTML5 build, React Native), confirms the exact API on the docs MCP page, then writes the call in that stack's idiom with cleanup. Applies the ad policy and IAP grant rules, and tells the user what must be set up in the console first; never calls console write tools. Not this skill: a visual-only change is `/ait:design`, server code is `/ait:server`, requirement mapping before building is `/ait:plan`, checking on a phone is `/ait:test-on-device`. Triggered by `/ait:feature [request]`.
- ▌ Welcome · tossPrint the harness entry-point map right after plugin install, and check the local environment/integration state (git, Node/npm/npx, cwd shape, MCP wiring) to suggest or hand off the next concrete step — since `/plugin install` itself prints no next step. Station-0→1 hand-off. Triggered by `/ait:welcome`, no args.
- ▌ UX Writing · tossRewrite mini-app screen copy against measurable UX writing principles. Use when the user asks "문구 다듬어줘", "카피 점검해줘", or "UX 라이팅 기준으로 봐줘" — invoke it right away even with no screen or file named yet, it surveys the current project's screen copy first, so do not ask a clarifying question or answer with generic advice instead of running it. This is a structured rewrite pass, not a one-off inline answer: collect every string, check it against the standard, propose before/after pairs, apply only what the user confirms. Covers loading states, empty results, network failures, permission denials, submit CTAs, terms agreements, amount/period notices. Turns design skill's G6 copy grading ("조정 필요") into concrete before/after proposals — user-as-subject phrasing, no loss-framing, no assumed emotions, no crammed conditions, no repeated claims, error copy with cause + next action, clear CTA labels, consistent tone. Never mass-replaces strings without confirmation. Hands off to `/ait:design` for G6 re-grading. Triggered by `
- ▌ New Miniapp · toss bundleScaffold a new Apps in Toss mini-app by driving the official `create-ait-app` CLI non-interactively (`--inline`, always `@latest`), then verifying the `@apps-in-toss/devtools` wiring (mock SDK + panel) the CLI performs so `npm run dev` runs in a plain browser immediately — falling back to manual wiring only when the CLI did not do it. Stack-neutral: defaults to `react-ts`, and when the user names a stack ("Vue로", "Svelte + TS") picks the matching preset from `create-ait-app --list-templates`. Supports `--tds` and `--sample iap,iaa` passthrough. `--local` is a React-only offline fallback (bundled react-vite template, being phased out); `--no-devtools` un-wires devtools afterwards. The freshly scaffolded project also gets a design guide seeded into it (tokens, hard rules, icon set, Tossface emoji font wiring) so later sessions build screens against the same standard — `--no-design-guide` and `--no-tossface` opt out of that seeding. Greenfield only (see `inject-devtools` for existing projects). Triggered by `/ai
- ▌ Setup Debugger · toss bundleWire the `ait-debugger` debug MCP server (`@apps-in-toss/debugger`) into the current project's MCP config (project scope, opt-in) — `.mcp.json` on Claude Code, `.cursor/mcp.json` on Cursor — so `/ait:debug` can run on-device CDP relay attach (environment 3). Idempotent JSON merge — preserves other server entries, never renames the `ait-debugger` key. An old `ait-devtools` entry or an old `@apps-in-toss/debug-console` dependency (0.3.0 and earlier names) is an upgrade to migrate, not "not installed". Run THIS skill instead of hand-writing `.mcp.json` or inventing a server entry — even when the request sounds like a plain JSON edit ("MCP 서버를 .mcp.json에 등록해줘", "디버거 서버 추가해줘"): the correct package, args, and key live here. Installing the `debugger-client` package into the app itself is `inject`, not this. Triggered by `/ait:setup-debugger`, no args.
- ▌ Test On Device · toss bundlePut the current mini-app on a real phone through the standard path — build the `.ait` bundle (release variant by default; debug variant only when the user is debugging on-device), upload it with console MCP (`bundle_upload` → `bundle_upload_complete`), confirm the compile with `miniapp_get_status`, and hand over the entry link the tools returned so it opens in the Toss app. Debug-build deployments are recorded locally and must not be submitted for review. Review submission, release, rollback, and promotion are out of scope. Triggered by `/ait:test-on-device`, no args.
- ▌ Plan · toss bundleTake a mini-app from a vague idea to a plan — ideate when the user has no concrete idea yet, shape a lightweight PRD, look up official docs for reference, then map it to the needed SDK domains, the runtime permissions they prompt for, and console terms (약관) that gate registration. Use when the user asks "미니앱 만들고 싶은데 뭘 만들지 모르겠어" or "미니앱 만들 건데 필요한 SDK 도메인/권한/약관 먼저 정리해줘", or asks for a PRD ("출시 일정이랑 범위 정리한 PRD 써줘") — requirements work, not a docs lookup. Writes at most one file (`PRD.md`); no CLI, no console calls. Hands off to `/ait:new`. Triggered by `/ait:plan [requirements]`.
- ▌ Debug · toss bundleDebug an Apps in Toss mini-app across two environments — local browser (devtools panel, `window.__ait`, browser DevTools) and on-device intoss-private candidate (real Toss WebView via `ait-debugger` MCP relay-staging QR attach). Branches by what it observes, then runs an autonomous observe → hypothesize → minimal-fix → re-verify loop and hands off when it stalls (§6). Triggered by `/ait:debug` (no args). Distinct from `status`/`logs` (console-side, not live device state).
- ▌ Design · toss bundleBuild and fix mini-app screens. Run it for "화면 만들어줘", "출석 체크 화면 그려줘", "화면이 구린데 예쁘게 해줘", "디자인 좀 봐줘" — it writes and edits the project's actual screen files, not a chat answer about design. Works from nothing: with no screen, no CSS file and no design assets in the project, it still produces the screens. On projects built with TDS, MUI, Tailwind, shadcn or their own tokens it keeps that system, so "어색한데 기존 스타일 유지하면서 다듬어줘" is this skill too. Fixes hard-rule breaks itself (text under 11px, touch targets, bottom safe area, text-glyph chevrons, ads covering content, dark patterns) and checks Apps in Toss container constraints against the docs MCP. Also produces registration image assets at the console MCP `miniapp_create` specs (logo, thumbnail, screenshots). Figma MCP is optional input. Not a refactor pass (no component API, props or state changes). Never registers or uploads. Skip it only when the user wants feature code and no visual change at all ("스타일은 기존이랑 똑같이", "디자인은 손대지 말고", "Figma 시안 그대로"). Triggered by `/
- ▌ Docs Search · toss bundleSearch and retrieve Toss / Apps-in-Toss documentation using the ax CLI via run-ax.sh. Supports docs, TDS React Native, and TDS Web sources. Use bash to execute run-ax.sh in this skill's directory.
- ▌ Cohesion · tossUse when 한 기능 수정 시 여러 디렉토리를 건드리거나, 같은 숫자/상수가 여러 파일에 흩어져 있거나, import 경로가 `../../..`처럼 길어질 때
- ▌ Coupling · tossUse when props가 3개 이상 컴포넌트 계층을 통과하거나, 하나의 Hook이 5개 이상 값을 반환하거나, A 수정 시 관련 없는 B가 깨질 때
- ▌ Readability · tossUse when 삼항 연산자가 중첩되거나, 복잡한 조건식 `a && !b || c`가 이름 없이 사용되거나, 동시에 실행되지 않는 코드가 한 컴포넌트에 섞여 있을 때
- ▌ Predictability · tossUse when `getX()`나 `fetchX()`에 숨은 부수 효과가 있거나, 같은 종류의 함수들이 서로 다른 반환 타입을 가지거나, 함수 이름과 실제 동작이 다를 때
- ▌ Branch · toss bundleCreate branches following repo conventions. Use when creating branches, starting new features.
- ▌ Commit · toss bundleCreate commits following repo conventions. Use when committing changes, creating commit messages.
- ▌ Scaffolder · tossScaffold new hooks/components/utilities. Generate standard structure and boilerplate. Use when creating new hooks, components, utilities.
- ▌ Jsdoc Guide · toss bundleJSDoc writing rules for AI-powered documentation generation. Use when writing JSDoc, documenting functions, or adding code comments.
- ▌ Test Writer · toss bundleWrite test code. 100% coverage, SSR tests, edge cases. Use when writing tests, adding test coverage.
- ▌ Code Reviewer · tossPR/code review. 100% coverage, SSR safety, JSDoc validation. Use when reviewing code, checking PRs.
- ▌ React Simplikit · toss bundleSelects and applies react-simplikit hooks, components and utils (useDebounce, useThrottle, useToggle, useBooleanState, useCounter, useList, useMap, useSet, useInterval, useTimeout, usePrevious, usePreservedCallback, useOutsideClickEffect, useIntersectionObserver, useStorageState, useLongPress, SwitchCase, Separated, mergeRefs, buildContext, ...) instead of hand-written equivalents, including the mobile-web keyboard, safe-area, visual viewport and body-scroll-lock hooks. Use when writing React state or effect logic, debouncing or throttling, boolean/counter/list/map/set state, intervals and timeouts, click-outside, long-press or double-click handling, viewport visibility or impression tracking, persisted state in localStorage/sessionStorage, conditional rendering, merging refs, React Context boilerplate, or SSR-safe browser access, and whenever the project depends on react-simplikit.
- ▌ Library API Design · toss bundleReact library public API design principles. Use when designing hooks, components, or utility APIs.
- ▌ Development Workflow · toss bundleComplete workflow from new Hook/Component/Util development to deployment. Use when starting new feature development.
- ▌ React Simplikit Codemod · tossMigrates a codebase off the deprecated @react-simplikit/mobile package onto the react-simplikit root entry. Use when a project still imports @react-simplikit/mobile, when an install warns that the package is deprecated, or when someone asks how to migrate off it.
- ▌ Recommend · tossAnalyze code or requirements and recommend the best es-toolkit functions. Use when the user asks which es-toolkit function to use, needs help finding a utility, or wants alternatives to manual implementations.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Guide · tosses-toolkit usage guide covering installation, import patterns, and setup for Node.js, Bun, Deno, and browsers. Use when the user asks how to install, import, or set up es-toolkit in their project.
- ▌ Migrate · tossGuide migrating lodash code to es-toolkit. Use when the user wants to migrate from lodash, replace lodash imports, reduce bundle size by switching to es-toolkit, or understand the difference between es-toolkit and es-toolkit/compat.