'frontend' 검색 결과

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

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

Iterate on tasks using debug instrumentation and browser tools. Use when you need to debug web applications, verify frontend behavior, or fix issues without asking the user to manually test.

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

Test and debug browser UIs using Chrome DevTools MCP — DOM inspection, console errors, network requests, performance traces, and visual verification. Load when building or debugging anything that renders in a browser, verifying a UI fix, profiling Core Web Vitals in a real page, or the user asks for browser testing with DevTools. Requires chrome-devtools MCP configured. Not for backend-only or CLI work. Pairs with frontend-design and performance-optimization.

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

Verify a code change end-to-end in the current worktree: identify what changed, run the relevant tests, get the app running, drive a browser over the affected areas, and report a verdict with screenshots. Generic across project types (Laravel/Herd, Node/bun, frontend, CLI, library). Use when the user wants to verify/QA/smoke-test a change, check that a PR or branch works, validate uncommitted work, or says "/flow", "verify this change", "does this PR work", "test and click through this". Optional target: PR number/URL, branch/ref, or worktree path; default is the current working changes.

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

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

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

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

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

Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.

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

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

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

Build low-fidelity wireframes, screen mockups, and user-flow diagrams in Frame0 (the hand-drawn Balsamiq-style wireframing tool) through its connected MCP server. Use when asked to wireframe a screen, sketch a UI, make a low-fi mockup, lay out an app's screens, or diagram a user flow with clickable links. Triggers: "wireframe", "frame0", "low-fi mockup", "sketch a screen", "user flow", "lo-fi", "rough out the UI". NOT for high-fidelity visual design, brand systems, or color/typography polish (use web-design-expert / Figma); NOT for production UI code (use frontend skills).

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

Aesthetic assessment and design scoring across 6 dimensions. Use for UI critique, design review, visual quality assessment, remix suggestions. Activate on "design critique", "aesthetic review", "UI assessment", "visual quality", "design score", "remix this design". NOT for implementation (use frontend-developer), accessibility-only audits (use color-contrast-auditor), or brand identity creation.

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

Audit and maintain design system consistency, UX/UI patterns, color palettes, and design best practices across frontend applications

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

Use when building content-heavy sites with Astro, deciding between SSG/SSR/hybrid, choosing client directives (idle/visible/load/media), structuring content collections with type-safe schemas, integrating React/Vue/Solid/Svelte components in the same project, or migrating from Next.js for marketing/docs. Triggers: client:idle vs client:load tradeoffs, content collections schema with zod, image optimization via @astrojs/image, view transitions, server islands, MDX layouts. NOT for SPA-style apps that need full interactivity (use Next/Remix), Astro internals/plugin authoring, or non-content sites where islands provide no benefit.

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

Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).

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

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.

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

Brokered short-lived provider credentials client in matrx-frontend (`lib/api/broker/`). Use when browser code needs a provider realtime session, a direct provider call, an ephemeral token, or a provider API key in the browser or `NEXT_PUBLIC_*`. NOT for adding a new audience server-side (use aidream's token-broker).

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

The re-measure and standing report of the canonical data model's live DB conformance. Use when asked 'where are we at' on DB drift or conformance, to update the drift numbers, when a drift-audit brief is re-issued, or on /drift-audit. NOT the per-table fix recipe (use matrx-frontend's db-canonicalize-table).

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

Working playbook preloaded into the browser-tester helper; the coach updates its Lessons after each round. Use only when acting as browser-tester or coaching it. NOT for general UI work (use matrx-frontend's browser-testing doc).

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

The staged pipeline that turns any API, provider payload, scrape, or computed result into registered, rendered platform kinds. Use on 'create kinds for X', 'distill X into kinds', 'point yourself at API X', or as a stage (A/B/V/D/C) of a running data-to-kinds run. NOT for consuming existing kinds (use aidream's workflow-io-kinds / matrx-frontend's shape-system).

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

The frontend Error Inspector capture system (captureError, lib/diagnostics/**). Use when wiring a new CapturedErrorSource or adapter, calling captureError from a new site, picking a red/orange/yellow tier or errorTierRules downgrade, or turning a console.error or swallowed catch into a captured error.

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

React、Next.js、状態管理、パフォーマンス最適化、UIベストプラクティスのためのフロントエンド開発パターン。

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

ゼロからまたはPowerPointファイルの変換により、美しくアニメーション豊かなHTMLプレゼンテーションを作成。プレゼンテーションの構築、PPT/PPTXのWeb変換、トーク/ピッチ用スライド作成に使用。デザイン初心者が抽象的な選択ではなくビジュアル探索を通じて自分の美学を発見するのを支援。

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

Orchestrate the authentication & access team — security-engineer, backend-engineer, frontend-engineer, qa-tester — auth, RBAC, multi-tenancy, sessions, and invites.

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

Orchestrate the billing team — pricing-economist, backend-engineer, frontend-engineer, qa-tester — plans, Stripe Checkout, webhooks, and customer portal.

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

Orchestrate the content & communication team — ux-content-strategist, copywriter, api-documentation-engineer, frontend-engineer — UX writing, API docs, transactional emails, and onboarding.

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