frontend-fundamentals
claudeFrontend development best practices: code quality principles (readability, predictability, cohesion, coupling) and accessibility guidelines by Toss
4 skills · 1 command · 1 agent
Build Apps in Toss mini-apps from inside AI coding agents — scaffolding via create-ait-app, docs MCP + console MCP by default, opt-in devtools/debugger.
Plugin ait from marketplace apps-in-toss in toss/apps-in-toss-harness. Commands read from the repo's manifest — today.
debugDebug 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 → hypothe
designBuild 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 scree
featureImplement 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 "배너 광고 붙여줘", "보상형 광고 넣어줘", "광고 보면 코인 주는 버튼 만들어줘", "인앱결제 붙여줘", "상품 결제
injectPatch 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` i
launchPre-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
new-miniappScaffold 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 wir
planTake 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
serverWrite 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 rig
setup-debuggerWire 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 s
test-on-devicePut 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`,
ux-writingRewrite 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
welcomePrint 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:welc
ait-docsconnects to: https://developers-apps-in-toss.toss.im/~gitbook/mcp
ait-consoleconnects to: https://mcp.toss.im/adapters/apps-in-toss-console/mcp
Frontend development best practices: code quality principles (readability, predictability, cohesion, coupling) and accessibility guidelines by Toss
4 skills · 1 command · 1 agent
DDD-driven development skills, sub-agents and workflow commands for Rust, React, miniapp, Flutter, Chrome Extension, and Shopify App projects
33 skills · 40 agents
앱인토스(Apps in Toss) 미니앱 개발 전문가. WebView/React Native SDK, TDS(Toss Design System), Unity WebGL, Cocos Creator, 토스 로그인/결제, 푸시 알림, 광고 통합을 다룹니다.
1 skill
Telegram skills for AI agents on Bot API 10.3: rich and classic messages, block JSON, uploaded media, streaming AI replies, polls, HTML widgets, sticker packs, digests, reply rewriting, operator cards, Mini App launch, initData auth and UI, Stars payments, bot operations, and a capability map
15 skills
Visual output an agent's reader grasps at a glance. Ships the Digital Stoic design system v0.6 "Tablette" (design-system): tokens, type, class vocabulary, inline-SVG chart parameters, and an assembler that injects the base CSS and base64 fonts so they never pass through context. Six demo screens (document, landing, dashboard, charts, decision, mini-app) kept in sync by a checker. Also ships verdict (ex review-html): self-contained review pages assembled from the design system, with cards typed by the action the reader takes and a JSON of deviations pasted back, plus its 108-entry visual grammar catalog and generator.
2 skills
Private Chat Engines: the three architectural families that every messenger falls into — centralised end-to-end-encrypted, centralised server-encrypted cloud, and federated or decentralised — the threat-model taxonomy that decides every other choice, a comparison matrix, how the field reached its 2026 state, and the forces reshaping it. Signal's protocol stack from X3DH and the double ratchet through sealed sender, private contact discovery, key transparency and post-quantum ratcheting, plus the Foundation's cost structure, its legal fights, and why there is no Signal server to operate. Telegram's MTProto and cloud-chat compromise, why Secret Chats are one-to-one mobile-only and off by default, the Durov prosecution and the compliance turn, scale and economics, and the bot and Mini-App developer ecosystem. Matrix and Element's federation and room model, Olm and Megolm, Matrix 2.0, the ecosystem's organisations and funding, and a homeserver operator handbook including the European sovereignty deployments. The wider field assessed honestly — MLS and RFC 9420 with Wire, WhatsApp's interoperability opening, iMessage PQ3, Threema, Olvid, SimpleX, Session, Nostr, XMPP with OMEMO, Briar, Delta Chat, the dormant and the niche — with a policy annex. And builder and operator playbooks: choosing the protocol shape before touching cryptography, the crypto stack as checklists, the metadata budget every service must fill in, abuse and trust-and-safety under end-to-end encryption, maintained libraries, operations and incident checklists, and budget intuition from public numbers.
6 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.