'interface' 검색 결과

웹 화면 코드를 최신 Web Interface Guidelines와 대조해 개선할 부분을 확인합니다. 지적 사항은 파일명과 줄 번호를 함께 표시합니다.

• 웹 화면 코드를 검토합니다
• 기준에 따라 접근성을 확인합니다
• 디자인과 사용성을 검토합니다

Golang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfaces, struct field tags, and pointer vs value receivers. Use this skill when designing Go types, defining or implementing interfaces, embedding structs or interfaces, writing type assertions or type switches, adding struct field tags for JSON/YAML/DB serialization, or choosing between pointer and value receivers. Also use when the user asks about "accept interfaces, return structs", compile-time interface checks, or composing small interfaces into larger ones.

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

Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.

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

• Simplify a module interface
• Review module structure during refactoring
• Decide where behavior should be swappable

Builds a DRAFT interface register between disciplines or parties from meeting notes, action lists and drawings or document lists: one row per interface with the requesting and providing party, the information needed, the related document number, the need-by date with its source, the status as minuted and a quoted source, plus UNKNOWN and questions where the notes are silent. Never sets a date, rates priority, assigns ownership beyond what the notes state or closes an interface. Use when the user asks to "build an interface register from these minutes", "list the interfaces between piping and civil", "who owes what to whom on this package", "update the interface register from this week's meeting" or "turn these action items into an interface list". Do not use for recording a design or document change raised in a meeting, use management-of-change-intake instead. Drafts for human review; never approves, authorises or signs off.

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

웹 화면 코드를 Vercel 지침에 따라 검토합니다. 배치, 글자, 색상, 움직임, 접근성을 점검하고 문제를 파일명과 줄 번호로 표시하며, 동봉된 고정판으로 검토 기준을 맞춥니다.

• 제품의 화면 코드 검토
• 지침에 따른 사용 편의성 확인
• 배치·글자·색상·움직임 점검

Review web interface code against the latest Web Interface Guidelines to identify issues in design, usability, and accessibility. Specify files or a file pattern, and receive concise findings with file names and line numbers.

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

• Review the code behind a web interface
• Check accessibility against the guidelines
• Request a design or usability review

Review web interface code against the latest Web Interface Guidelines to identify issues in design, usability, and accessibility. Specify files or a file pattern, and receive concise findings with file names and line numbers.

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

• Review the code behind a web interface
• Check accessibility against the guidelines
• Request a design or usability review

Review interface code against the latest Web Interface Guidelines to check accessibility, design, and usability. Provide files or a file pattern, and receive concise findings with file names and line numbers for locating issues.

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

• Reviewing interface code for accessibility
• Auditing the design and usability of a site
• Checking selected files against the latest guidelines

Review web interface code against the latest Web Interface Guidelines to identify issues in design, usability, and accessibility. Specify files or a file pattern, and receive concise findings with file names and line numbers.

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

• Review the code behind a web interface
• Check accessibility against the guidelines
• Request a design or usability review

Review web interface code against the latest Web Interface Guidelines to identify issues in design, usability, and accessibility. Specify files or a file pattern, and receive concise findings with file names and line numbers.

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

• Review the code behind a web interface
• Check accessibility against the guidelines
• Request a design or usability review

Design APIs and interfaces between parts of an application with clear input and output types, consistent errors, and predictable names. The guidance helps you extend existing interfaces while preserving compatibility for the code that uses them.

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

• Designing new REST or GraphQL endpoints
• Defining contracts between frontend and backend
• Reviewing changes to a public interface

Design dashboards, admin panels, and app interfaces around users’ tasks and data. Establish screen layouts, colors, typography, and interaction states, then document reusable patterns to keep future interface work consistent.

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

• Designing dashboard information layouts
• Unifying admin panel colors and typography
• Defining settings page interaction states

Review a branch, pull request, or uncommitted changes for interface problems involving accessibility, layout, text, typography, and color. The report distinguishes newly introduced issues, regressions, and existing problems, including effects on screens that use changed components.

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

• Review interface changes in a pull request
• Check whether shared component changes affect other screens
• Find accessibility regressions before merging

Review web interface code for accessibility, visual design, and interaction issues. This skill checks specified files against interface guidelines and returns concise findings grouped by file, with line numbers to help locate each issue.

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

• Reviewing interface code before release
• Checking keyboard access and focus behavior
• Inspecting form labels and validation

Organize complex feature work into exploratory prototypes, written behavior contracts, shared tests, and focused pull requests. Use this workflow to settle interfaces before review, split large changes around clear responsibilities, and handle review findings without expanding scope.

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

• Planning a feature that changes multiple public interfaces
• Resolving interface changes that recur during review
• Splitting a large branch into focused pull requests

Use the skill to control and verify the code interface configuration of your model — how Simulink® model elements are represented in the generated C or C++ code. This includes — (1) specifying names, types (storage classes), and placement of variables that represent model elements (for example, making a model parameter tunable as a global extern variable); (2) specifying names, types, and placement of functions that represent model algorithms; (3) selecting the deployment type (Component, Subcomponent, or Automatic); (4) selecting the interface configuration type (data or service interface); (5) linking a shared Embedded Coder dictionary to a model; (6) creating Embedded Coder dictionary entries and setting their properties; (7) for service interface configuration — specifying service interface definitions, including sender, receiver, client, and server services. Items 1 and 2 can be set per element or as a category-wide default. Item 1 applies to GRT and ERT models; the rest to ERT models only.

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

Generates PSR-17 HTTP Factories implementation for PHP 8.5. Creates RequestFactoryInterface, ResponseFactoryInterface, StreamFactoryInterface, UriFactoryInterface, ServerRequestFactoryInterface, UploadedFileFactoryInterface. Includes unit tests.

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

라우터, 스위치, Linux의 통신 오류와 연결 끊김을 조사합니다. 링크 양쪽 설정과 오류 증가량을 비교해 케이블 불량이나 혼잡 등의 원인을 좁힙니다.

• 통신 끊김과 패킷 손실을 조사합니다
• 스위치의 CRC 오류 증가를 조사합니다
• 링크 양쪽의 설정을 비교합니다

API와 모듈 사이의 입출력을 정의하고 이름, 오류 형식, 입력 검증을 통일합니다. 기존 호출 측과의 호환성과 재시도로 인한 중복 처리도 고려합니다.

• 새 REST API를 설계합니다
• 화면과 서버 사이의 데이터 규격을 정합니다
• 호환성을 유지하며 API를 확장합니다

Apple 제품의 화면과 조작을 설계할 때 관련 지침을 찾는 안내입니다. iOS와 macOS 등에서 설계 기초, 구성 요소, 조작 방식을 다루는 14개 스킬을 소개합니다.

• iOS 앱 설계 지침을 확인합니다
• macOS 화면 구성 요소를 찾아봅니다
• visionOS 조작 설계를 살펴봅니다

Embed Zoom meetings in native Android apps with guidance on authentication, joining and starting meetings, and SDK integration. Begin with the default interface, then move to a custom interface once authentication, permissions, and meeting state changes are stable.

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

• Embedding Zoom meetings in an Android app
• Validating meeting join and start flows with the default interface
• Moving from the default interface to a custom interface

Review an interface across accessibility, layout, writing, typography, color, and visual polish. It coordinates specialist skills, combines evidence from code and rendered screens, and produces one report with findings ranked by their impact on users.

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

• Reviewing a screen or complete user flow
• Checking loading, error, and narrow-screen states
• Prioritizing interface fixes by user impact

Refine interface details such as typography, shadows, rounded corners, icons, and animations within the project's existing styling system. Supports implementation and quick or full reviews with prioritized findings, concrete changes, and verification results.

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

• Refine button and card appearance
• Adjust hover feedback and animations
• Improve text wrapping and changing number displays

Generates complete modules and components from interface contracts and specifications. Use when Claude needs to build larger software components, implement interfaces, create service layers, or generate complete modules with multiple related classes. Supports Python (with type hints and protocols) and Java (with interfaces and abstract classes). Trigger when users request "implement this interface", "generate a module for", "create a service layer", "build a component that implements", or provide interface definitions that need implementation.

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