코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.5만건)
Agent-to-Agent (A2A) server configuration patterns for HTTP, STDIO, SSE, and WebSocket transports. Use when building A2A servers, configuring MCP transports, setting up server endpoints, or when user mentions A2A configuration, server transport, MCP server setup, or agent communication protocols.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integration patterns for combining Agent-to-Agent (A2A) Protocol with Model Context Protocol (MCP) for hybrid agent communication. Use when building systems that need both agent-to-agent communication and agent-to-tool integration, implementing composite architectures, or when user mentions A2A+MCP integration, hybrid protocols, or multi-agent tool access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SDK installation and setup patterns for Agent-to-Agent Protocol across Python, TypeScript, Java, C#, and Go. Use when implementing A2A protocol, setting up SDKs, configuring authentication, or when user mentions SDK installation, language-specific setup, or A2A integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read analysis results. Use when user asks about maximum stress, extracting displacements, reaction forces, or exporting results. Post-processes ODB files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive Agent2Agent (A2A) JavaScript SDK skill for building A2A-compliant agents and clients. Use when implementing or integrating @a2a-js/sdk, creating A2A servers/clients, using JSON-RPC/REST/gRPC transports, streaming task updates, handling tasks/artifacts, authentication, or push notifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Final step in building instruction context for codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinator workflow for orchestrating dockeragents through fix-review-iterate-present loop. Use when delegating any task that produces code changes. Ensures agents achieve 10/10 quality before presenting to human.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Third step in building instruction context for codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep knowledge expert for the 33GOD agentic pipeline system, understands component relationships and suggests feature implementations based on actual codebase state
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fifth step in building instruction context for codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ALWAYS use this skill when user needs ANY API functionality (AI models, image generation, video, audio, text processing, etc.). Automatically search 302.AI's 1400+ APIs and generate integration code. Use proactively whenever APIs or AI capabilities are mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fourth step in building instruction context for codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to review, improve, or refactor Java code for generics quality — including avoiding raw types, applying the PECS (Producer Extends Consumer Super) principle for wildcards, using bounded type parameters, designing effective generic methods, leveraging the diamond operator, understanding type erasure implications, handling generic inheritance correctly, preventing heap pollution with @SafeVarargs, and integrating generics with modern Java features like Records, sealed types, and pattern matching. Part of the skills-for-java project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Second step in building instruction context for codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads and structured concurrency, scoped values, backpressure, cancellation discipline, and observability for concurrent systems. Part of the skills-for-java project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coding patterns and best practices for OneKey development. Use when writing React components, handling promises, error handling, or following code conventions. Triggers on react, component, hooks, promise, async, await, error, pattern, convention, typescript.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use MCP without installing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill for generating 1C:Enterprise (BSL) code with mandatory validation through MCP tools to prevent hallucinations. Use when generating, editing, or validating 1C BSL code, working with 1C metadata, or answering questions about 1C platform API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.