2.5만건 · 관련도순
Collect Amazon product data from ASINs, unique product identifiers, and compare prices, specifications, reviews, and product images. Produce comparison tables and reports that highlight competitive strengths, weaknesses, and potential market opportunities.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run empirical and causal analyses in Python with StatsPAI, from stating assumptions to estimating effects and checking how results change under alternative choices. Produce diagnostic figures, regression tables, and replication bundles for economics, public health, or machine learning studies.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when asked to compare two annual reports, put two companies from the same sector side by side, or check whether two companies' adjusted numbers mean the same thing. Takes two uploaded annual reports from one sector and compares them on five ratios computed with identical definitions from audited figures, flagging every place the companies define a metric differently. Produces a page-referenced comparison table, a definitions-differ section (adjusted vs statutory, inside vs outside the audited statements), and three questions to ask before believing either company's highlights. Educational, not financial advice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to analyze competitors for SEO, content, backlinks, or positioning. Also use when the user mentions "competitor analysis," "competitor research," "competitor keywords," "competitor backlinks," "link gap," "content gap," "competitor content," "competitive analysis," or "competitor comparison." For content roadmap, use content-strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a competitive SEO analysis comparing the user's site to chosen competitors across SERP overlap, content depth, backlink profiles, technical posture, and brand presence. Use this skill whenever the user wants to analyze competitors, find content gaps, identify backlink opportunities, understand why competitors outrank them, or benchmark against the rest of their category. Triggers on competitor analysis, competitive analysis, SERP analysis, content gap, backlink gap, why is X ranking, who is winning the SERP, beat my competitor, benchmark, market positioning. Also triggers when planning a content strategy and the question 'what are competitors doing' is implicit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Competitive landscape analysis for A-share companies and Chinese industries. Maps competitors, compares positioning, and assesses relative strengths. Adapted from the original competitive-analysis skill for Chinese market context. Triggers on "A股竞争格局", "行业竞争分析", "competitive landscape China", "competitive analysis A-share", or "[company] competitors China".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write "X vs Y" comparison blog posts that help readers choose between two competing products. Triggers on: "write a comparison post", "X vs Y blog post", "compare [product A] and [product B]", "which is better [A] or [B]", "head to head comparison", "[product] vs [product] article", "comparison review", "write a versus article", "side by side comparison blog", "which should I choose [A] or [B]", "compare these two products for my blog".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Owns repositories, data sources and mapping for Compose and Compose Multiplatform apps: DTO to domain to UiModel boundaries, Ktor clients and bearer auth, WebSocket and SSE, Room, DataStore, Paging 3, offline-first and data-layer tests. Use when writing or reviewing a repository, data source, DTO, mapper, HttpClient, bearer token, WebSocket, SSE, Room DAO, migration, DataStore, PagingSource, RemoteMediator, offline cache or MockEngine test. Do NOT use for ViewModel or UI wiring (compose-feature), composables (compose-ui), the MVI contract or error tiers (compose-architecture), Gradle modules (compose-project), or commonMain vs platform splits (compose-platform).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Symfony UX LiveComponent for reactive server-rendered UI -- components that re-render via AJAX on user interaction, zero JavaScript required. Use when building live search, real-time filtering, dynamic forms, inline validation, dependent selects, auto-save, polling, deferred/lazy rendering, or any UI that updates itself based on user input. Code triggers: AsLiveComponent, LiveProp, LiveAction, data-model, data-loading, data-live-action-url, ComponentWithFormTrait, LiveListener, emit, defer, lazy, polling. Also trigger when the user asks "how to build a search that filters as I type", "how to validate a form in real-time", "how to make a reactive component in PHP", "how to build dependent selects", "how to defer component rendering", "how to communicate between components via emit", "how to bind a form to a LiveComponent". Do NOT trigger for static reusable UI without reactivity (use twig-component), pure client-side JS behavior (use stimulus), or page-level navigation (use turbo).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research companies, competitors, funding, news, leadership, and market context with Exa Agent and advanced search. Use when researching companies, competitor analysis, market research, or building company lists. Writes findings the caller can fold into brand/competitors.md or brand/landscape.md. Prefer this over ad-hoc web search for company deep dives. Distinct from competitive-intel (full brand competitive file methodology) - this skill is the Exa research engine those foundation skills should call.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis". For marketing positioning work that writes to knowledge/markets/competitors.md, see competitor-analyst.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tracks competitors weekly across 6 signals: pricing page diffs, homepage positioning changes, blog/RSS posts, job postings (hiring as strategy signal), GitHub star velocity and releases, and daily critical-change alerts for pricing or funding keywords. Delivers a structured digest to Slack, Telegram, WhatsApp, or Discord every Monday. Fires same-day alerts for critical changes. Use when asked to "add competitor", "track competitor", "competitor digest", "what changed at [company]", "competitor report", "monitor [company]", "who is [company] hiring", "did [company] change pricing".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vue.js 3와 Nuxt 화면 구현을 컴포넌트 설계부터 상태 관리, 화면 이동, 테스트까지 지원합니다. 구체적인 예제로 코드 구성과 데이터 갱신 방식을 검토합니다.
긴 Claude Code 작업에서 대화와 읽어 들인 정보를 압축할 시점을 제안합니다. 문맥 크기와 도구 호출 횟수를 참고해 단계 전환 시 중요한 계획을 보존하도록 돕습니다.
Storybook에서 프로젝트의 기존 UI 구성 요소와 설정 항목, 사용 예시를 확인합니다. 사용법 질문에 답하고 중복 구현 전에 재사용 가능 여부를 판단합니다.
Create alternative-product and comparison pages for developer tools, using search research and factual comparisons. Plan page structure, feature and pricing tables, migration information, and ongoing updates to help readers evaluate products and consider switching.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare for one company's upcoming earnings announcement with a compact HTML report. It combines the latest earnings call, competitor comparisons, valuation measures, and recent news, with links to supporting sources and calculation details.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.