'test' 검색 결과

Fetch up-to-date, version-specific documentation for any major library (Next.js 16, Sanity, LangGraph, React, Tailwind CSS, Vitest, Framer Motion) via the Context7 MCP server. Use when writing code against unfamiliar or recently-changed framework APIs, when training data may be stale, when resolving deprecations or version-specific syntax, or when the repo warns about framework drift (e.g. the nextjs-agent-rules block in portfolio-v1/AGENTS.md). Invokes the resolve-library-id and get-library-docs MCP tools.

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

Implement feature flags for gradual rollouts and A/B testing.

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

Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.

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

E2E artifact handling routing. Use when traces, videos, screenshots, reports, or failure bundles need controlled repository-local placement; do not use for simple unit tests or production-mutating E2E flows.

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

Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.

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

Refines raw ideas through structured divergent and convergent thinking for ordinary non-command brainstorming, idea shaping, options comparison, and explicit IDEATE deepening routed by `aili-delivery-flow`; do not use as the top-level `/ideate` command owner or for existing-plan stress-test, review, or completion-claim checks.

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

Clarify a concrete requirements decision, create one bounded static interview packet, or run an explicitly user-invoked frontier batch over a plan, decision, or idea; trigger on explicit grill/interview/refinement intent or a named material ambiguity, not on ordinary planning, implementation, research, test-plan, report-style review, or BUILD work.

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

Build React Native/Expo mobile apps with navigation, native UI, state, networking, tests, and release workflows.

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

Code-review quality gate and test-enhancement rubric. Use when ROSE needs sharper review output contracts, severity and risk prioritization, evidence anchors, negative review cases, fixture or golden-output drift guidance, or a Chinese review report profile; do not use as a duplicate code-review agent or final PASS authority.

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

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

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

Configure or modify concrete CI/CD pipelines, jobs, quality gates, test runners, or deployment automation; do not trigger merely because an existing CI gate failed or ordinary source code needs repair.

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

Perform direct, bounded browser inspection through the `browser.qa` capability when the user requests runtime UI evidence or one browser-specific claim needs DOM/accessibility/console/network/visual verification; do not trigger for every UI change, backend work, delegated QA, or durable E2E artifact routing.

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

Build a backend service or an end-to-end frontend/backend integration when service/API/data boundaries are the primary deliverable; do not trigger for pure UI, contract design only, security review, test workflow, or every feature touching both folders.

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

Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.

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

Implements security headers and Content Security Policy with safe rollout strategy (report-only → enforce), testing, and compatibility checks. Use for "security headers", "CSP", "HTTP headers", or "XSS protection".

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

Generates .http files for the VS Code REST Client extension from Express, Next.js, Fastify, or other API routes. Creates organized request files with variables, environments, and authentication. Use when users request "generate http files", "rest client requests", "create .http file", or "vscode api testing".

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

How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.

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

Sets up Storybook for component documentation with controls, actions, accessibility testing, and visual regression. Use when users request "Storybook setup", "component documentation", "UI library", "component stories", or "design system docs".

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

Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.

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

Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed. Covers sticky hover states, tap highlight flashes, the 100vh bug, inputs that zoom the page, laggy taps, pull-to-refresh hijacking scroll, content under the notch, long-press selecting button text, carousels that scroll the wrong way, mismatched status bars, and the rule that you test on real hardware. Use when a web app is being built for or reviewed on mobile, when something "works in Chrome but feels wrong on my phone", when building a PWA, a bottom sheet, a carousel, a full-screen layout, or any touch interaction. For motion itself use animate; for React Native use animate-expo.

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

Optimizes CI pipelines for monorepos by detecting affected packages/apps and running only necessary builds and tests. Includes Turborepo/Nx strategies, caching, and parallel execution. Use for "monorepo CI", "affected detection", "incremental builds", or "workspace optimization".

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

Creates stable mocks for APIs, services, and UI components using MSW (Mock Service Worker), fixture conventions, and example patterns. Use for "API mocking", "MSW", "test mocks", or "service mocking".

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

Diagnoses LLM output failures including hallucinations, constraint violations, format errors, and reasoning issues. Provides root cause classification, prompt fixes, tool improvements, and new test cases. Use for "debugging AI", "fixing prompts", "quality issues", or "output errors".

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

Implements role-based access control with permission matrix, route guards, policy functions, and UI permission hints. Provides middleware/guards, helper utilities, test suggestions, and permission checking patterns. Use when building "RBAC", "permissions", "access control", or "authorization".

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