742건 · 관련도순
Generate unit test files with structure, fixtures, and mocking patterns for Python (pytest) or JS/TS (Jest), auto-detecting the framework. Use when starting tests for a source file. Trigger on "scaffold tests", "generate test file", "write test boilerplate", "set up tests for".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
说明如何读取 IELTS Buddy 模考与已提交练习的事实数据；不定义模考解读、诊断或训练优先级。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cypress E2E testing patterns - test structure, data-cy selectors, cy.intercept() mocking, custom commands, fixtures, component testing, accessibility testing with cypress-axe, and CI/CD integration
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Playwright E2E testing patterns - test structure, Page Object Model, locator strategies, assertions, network mocking, visual regression, parallel execution, fixtures, and configuration
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detox E2E gray-box testing for React Native - matchers, actions, expectations, waitFor, device API, synchronization, mocking, artifacts, CI integration
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
E2E testing with Playwright, main process unit testing, IPC testing, dialog/menu mocking, CI headless setup
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GPT-image-2 的 prompt 工程方法论，**公众号配图的唯一入口**。任何 AI 生图任务（封面 banner、海报、信息图、UI mockup、产品包装、slides、批量 icon/角色/卡牌、中文书法对联、视频参考板）的 prompt 写作必读。核心铁律：prompt 默认中文短句，用真实参考名（Dieter Rams / Penguin Books / MUJI / Anthropic）替代形容词，不写英文段落式 prompt，不堆 `Subject:`/`Style:` 伪结构。与 huashu-xhs-image 的分工：那个是端到端小红书业务流程，本 skill 是被它底层调用的 prompt 方法论层。SKIP：图片压缩、HTML 截图、复用已有图。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when independently reviewing a research-paper draft before submission, running a mock top-conference panel, assessing readiness or accept/reject risk, or predicting reviewer concerns for venues such as CVPR, ICCV, ECCV, ICLR, NeurIPS, and AAAI. Does not draft or audit author responses after official reviews arrive.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when testing Django applications with pytest - TDD workflow, pytest-django setup, factory_boy and model-bakery fixtures, DRF API testing, mocking and patching, integration tests, mutation testing with mutmut, or coverage
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test helpers/mocks/fixtures
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate interactive, animated, responsive HTML-based terminal simulators to showcase CLI commands, scripts, pipelines, or interactive workflows. Use this whenever you need to visually showcase a command line sequence, mock interactive CLI tools, or simulate code executions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Visual design verification loop for matching a goal PNG to a live render. Use when the user shares a design mock / goal image and asks to match the UI to it, asks to "iterate on this design" or "match this 1:1", or calls out visual drift in a previous UI iteration. Provides histogram color sampling, shape inspection (radius/border/shadow/bg-mode/fill-vs-context), computed-style checking on the live render, snap, and side-by-side diff. After every UI change the assistant MUST snap the live render and Read the snap with the Read tool before reporting the change done — skipping that is the
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity Test Framework patterns for EditMode and PlayMode tests including async testing, mocking, and test organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
用于编写或审查靠近 UI 代码的前端单元、组件或轻量集成测试，包括 React Testing Library、Vue Test Utils、hooks/composables、props/emits、回调、可访问查询、user-event 交互、mock、loading/error/empty 状态和回归覆盖。若是测试分层规划、真实浏览器旅程或现有验证失败，优先选择对应测试或验证工作流；中文触发词包括 组件测试、组件单测、单元测试、轻量集成测试。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when generating or editing diagrams, charts, visual assets, posters, UI mockups, product images, infographics, academic figures, comics, avatars, storyboards, brand boards, or image-edit workflows, especially when exported PNGs need visual QA and bounded self-repair. Prefer deterministic Mermaid/SVG/HTML/canvas sources for text-heavy diagrams; use HTML technical diagrams for browser-ready system blueprints, architecture, deployment topology, agent runtime, memory flow, before-after architecture, workflow, sequence, data-flow, lifecycle, runbook, PII/data-lineage, and state-machine diagrams. Do not use for ordinary UI polish without generated imagery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when authoring or reviewing frontend unit, component, or light integration tests close to UI code, including React Testing Library, Vue Test Utils, hooks/composables, props/emits, callbacks, accessible queries, user-event interactions, mocks, loading/error/empty states, and regression coverage. For layer planning, real-browser journeys, or existing validation failures, choose the matching testing or validation workflow first; Chinese triggers include component testing, Component unit testing, unit testing, lightweight integration testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing UI from Figma, Sketch, MasterGo, Pixso, Modao, MockingBot, screenshots, design selections, design tokens, or design-to-code tasks for production frontend components/pages; Chinese triggers include design draft, implementation by design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Critique a design for usability, hierarchy, and accessibility. Use when the user says "critique this design", "review this screen", "what's wrong with this UI", "design feedback", "UX review", "how can I improve this", "review my mockup", "is this good UX", or shares a design and wants structured feedback - even if they don't explicitly say "design critique".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify Spring Boot 4.x projects for correct dependencies, configuration, and migration readiness. Use when analyzing pom.xml, build.gradle, application.yml, discussing Spring Boot project setup, dependency versions, configuration validation, version compatibility, migration to Spring Boot 4, deprecated dependencies, or when user mentions "verify project", "check dependencies", "upgrade Spring Boot", "migration readiness", "Jackson 3", "@MockBean deprecated", or "Spring Security 7".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate App Store & Google Play screenshot generation for Flutter apps. Scans routing and screens, scores high-value marketing screens, generates self-contained mock harness, runs native simulator captures (iPhone 6.9", iPad 13", Android Phone/Tablet), strips alpha channels, and validates exact store resolutions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apex test patterns for @InvocableMethod agent actions: per-reason-code branch coverage, bulk safety, callout mocking, deterministic assertions. NOT for testing whether the agent routes to the right topic or answers well — use agentforce/agent-testing-and-evaluation. NOT for designing the error envelope the tests assert on — use agentforce/agent-action-error-handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Router for the 159 SfSkills `apex` skill packages. Apex and SOQL: triggers, Apex governor limits, async processing, OUTBOUND HTTP callouts, security enforcement, and test patterns. Owns calling an external API FROM Salesforce; salesforce-integration owns inbound. Generic nightly scheduling without naming code belongs to salesforce-flow. Codebase security review belongs to salesforce-security. NOT for SOSL — use salesforce-data. Use when the request mentions Apex, trigger, SOQL, Apex governor limit, batch, queueable, @future, schedulable, test class, CPU time, heap, with sharing, StripInaccessible, callout, HTTP callout, HttpRequest, call an external API, consume a REST API from Apex, Named Credential in Apex, HttpCalloutMock, Apex REST service. Finds and opens the exact skill package to read; it does not contain the guidance itself.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.