'backend' 검색 결과

How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game Critic)? Who does which subtask? What does a development chain (concept → backend → frontend → polish → test) look like? How do you write a Game Design Document / KONZEPT.md? How do several (AI) agents divide up a game? Also trigger on "plan a new game", "create Game Design Document", "which roles do I need for my game", "development workflow for a game", "who tests the game", "structure a game idea", "Roblox genre/monetization".

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

Implements and reviews mobile data privacy across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for consent withdrawal, SDK collection controls, account and data deletion, retention, privacy manifests or store data disclosures. Covers the app and backend handoff; security exploits belong to mobile-security.

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

Use when building custom agent backends, implementing the AG-UI protocol, debugging streaming issues, or understanding how agents communicate with frontends. Covers event types, SSE transport, AbstractAgent/HttpAgent patterns, state synchronization, tool calls, and human-in-the-loop flows.

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

Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.

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

Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits

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

Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.

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

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

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

Rules for when an agent should recall from long-term memory before acting and when it should save decisions, corrections and failures afterwards. Works with any memory backend.

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

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

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

Supabase Flutter integration for PostgreSQL, Auth, Realtime subscriptions, Storage, Edge Functions, and Row Level Security. Use when building backend features with supabase_flutter or configuring database policies.

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

Firebase integration for Flutter including Auth, Firestore, FCM, Cloud Storage, Analytics, and Crashlytics. Use when implementing serverless backend features, real-time sync, or push notifications.

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

Designs and reviews production observability for mobile apps on every stack — Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers crash and error reporting with usable context, breadcrumbs, structured logs, traces and custom metrics, release and cohort segmentation, correlation with backend requests, alerting thresholds, sampling and cost, and what must never be collected. Use when production problems cannot be explained from the available data, when setting up crash reporting or telemetry, or when defining release health alerts.

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

Use when validating logical secret-ID maps, config, and reference syntax for a KeePassXC integration; output is redacted and the fake backend is test-only.

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

Express/Fastifyを使用した本番環境対応のNode.jsバックエンドサービスを構築し、ミドルウェアパターン、エラーハンドリング、認証、データベース統合、APIデザインのベストプラクティスを実装します。Node.jsサーバー、REST API、GraphQLバックエンド、マイクロサービスアーキテクチャの作成時に使用してください。

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

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

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

Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.

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

Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.

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

Use for Nauthilus Lua plugins, Lua callback tests, policy compiler and registry work, Lua environment and subject sources, Lua actions, hooks, backend scripts, policy facts, obligation targets, `server/lualib`, `server/lua-plugins.d`, `server/policy`, and JSON fixtures under `testdata/lua`.

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

Use when validating a packaged build of this Hydrolix Grafana datasource plugin against Grafana's official plugin-validator — the pre-release gate that catches missing metadata, unsigned/mis-signed archives, non-executable backend binaries, and packaging errors. Builds the plugin, zips `dist/` under the plugin ID, and runs `@grafana/plugin-validator` (npx, or docker as fallback). Apply for "validate the plugin", "is this zip release-ready", or before publishing / submitting a release artifact.

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

Use when building this Hydrolix Grafana datasource plugin — frontend webpack bundle (`dist/module.js*`) or Go backend binary (`dist/gpx_plugin_*`). Covers the split between host-built frontend and container-built Go, when each needs an explicit rebuild, watch vs one-shot, and the verification chain (typecheck / lint / unit tests). Apply for any task that edits `src/**`, `pkg/**`, `Magefile.go`, `webpack.config.ts`, or that needs to confirm `dist/` matches the working tree before running e2e or the dev stack.

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

Orchestrate backend spec production from completed IA shards through classify and write passes with mandatory ambiguity gates

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Use when working with Convex — convex backend platform management covering project inventory, table schemas, function deployments, scheduled job status, index configuration, environment variable auditing, and usage metrics. Use for comprehensive Convex project health and resource optimization.

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

Use when working with Aws Amplify — aWS Amplify application management and deployment analysis. Covers Amplify apps, branches, backend environments, build status, domain associations, and webhook configurations. Use when inspecting Amplify deployments, debugging build failures, reviewing hosting configurations, or auditing Amplify app settings.

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