'diff' 검색 결과

Adopt a virtual Dire Wolf dog at animalhouse.ai. Prehistoric. Pack instinct. Behaves differently in colonies vs solo. Feeding every 12 hours. Extreme tier dog.

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

Use when (1) building an AI agent that needs to communicate with other agents over the Agent2Agent (A2A) protocol, (2) publishing an AgentCard for discovery, (3) acting as an A2A client or server, or (4) integrating A2A capabilities into an existing agent framework. Solves agent isolation — enabling discovery, capability negotiation, task delegation, and structured data exchange across different frameworks and vendors.

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

Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.

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

Review PRs: diffs, inline comments via gh or REST.

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

Risk-tiered code review (Blocker / High / Medium / Low). Use when the user runs /review or wants the current branch or diff reviewed.

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

Generate multiple radically different interface designs before implementation. Use when designing an API, module boundary, command surface, data contract, or when the user says "design it twice".

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

Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.

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

You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels.

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

Perform repository-aware code reviews focused on bugs, regressions, architectural violations, missing tests, and operational risks. Use when the user asks for review of diffs, pull requests, patches, or implementation quality.

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

Implement MYOT changes safely with minimal diffs, behavior preservation, and post-change validation.

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

Tests APIs for injection vulnerabilities including SQL injection, NoSQL injection, OS command injection, LDAP injection, and Server-Side Request Forgery (SSRF) through API parameters, headers, and request bodies. The tester crafts malicious payloads targeting different backend technologies and injection contexts to extract data, execute commands, or access internal services. Maps to OWASP API8:2023 Security Misconfiguration and API7:2023 SSRF. Activates for requests involving API injection testing, SQLi in APIs, NoSQL injection, SSRF testing, or API input validation assessment.

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

Executes comprehensive red team exercises that simulate real-world adversary operations against an organization's people, processes, and technology. The red team operates with stealth as a primary objective, employing the full attack lifecycle from initial reconnaissance through objective completion while testing the organization's detection and response capabilities. This differs from penetration testing by focusing on adversary emulation rather than vulnerability identification. Activates for requests involving red team exercise, adversary simulation, adversary emulation, or full-scope offensive security assessment.

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

Full review of a PR, a file, or pasted text against the OpenMetadata Writing Style Guide checklist, plus checking every checkable claim for internal consistency against the diff/PR itself. One combined report, not separate passes. Does not fetch or verify against any external source repository. Link-checking is out of scope; a separate broken-links job covers that. Only runs on explicit /content-review invocation, never self-triggered.

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

One-shot brand-faithful presales redesign of a website page. The user provides only the URL; everything else — extraction, tension identification, three differentiated variants (one fully cinematic), validation — is derived from the captured brand surface. Use when the user asks to "uplift", "refresh", or "redesign a site for presales" without wanting to coordinate the extract / direct / prototype chain themselves.

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

Render a proposed redesign of a page on the current website as a self-contained static HTML file, then iterate via the impeccable craft loop. Per-page, idempotent, stale-aware. Use when the user asks for a redesign prototype, a before/after comparison, a design preview, a page mockup, a visual diff of the redesign, or invokes /stardust:prototype.

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

Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences or visitor groups — for example, "how do mobile visitors compare to desktop on conversion," "compare new vs. returning visitors," "show me the difference between these two segments," "compare these audiences on our KPIs," or "which segment performs better." Also trigger for "segment comparison" or "audience comparison."

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

Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences, cohorts, or groups — for example, "how do mobile users compare to desktop users on conversion," "compare new vs. returning visitors," "show me the difference between these two segments," "compare these audiences on our KPIs," or "which segment performs better." Also trigger for "segment comparison," "audience comparison," or "cohort comparison."

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

Optional focused post-implementation review routing. Use only when the user requests review or the changed surface has a clear specialist evidence need that direct diff inspection and the smallest relevant check cannot cover. Never creates an automatic review swarm.

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

PR test analysis routing. Use for pull request or diff test impact, changed-test review, CI failure interpretation, and focused test matrix recommendations; do not use for general code review or editing tests.

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

Compares old vs new prompts across test cases with diff summaries, stability metrics, breakage analysis, and fix suggestions. Use for "prompt testing", "A/B testing prompts", "prompt versioning", or "quality regression".

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

Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.

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

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

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

Use when a Spark branch or pull request needs final diff hygiene, validation selection, commit scope, remote topology, and readiness checked before publication.

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

Discover a single-page-app's hidden backend API from its public JS bundle, then test that API for broken access control / missing authentication. One of the highest-yield web plays in modern recon — SPAs ship their entire backend route map to the browser, and the API behind them is frequently missing the auth middleware the login page implies. Built from an authorized engagement where this play found an unauthenticated financial API that an ASM scan reporting hundreds of 'Criticals' completely missed. Use whenever a target serves a JS-heavy SPA (React/Vue/Angular/Next), an 'app'/'console'/'dashboard'/'portal' subdomain, or any `*api*` host shows up in recon. Leaked build artifacts (source maps / .env / .git / asset-manifest) are owned by hunt-source-leak; API version-inventory and behavioral diffing by hunt-shadow-api; this skill owns mapping a live SPA's backend routes from its JS bundle and testing them for broken access control / missing auth.

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