'comp' 검색 결과

Docker 컨테이너, 이미지, 저장 볼륨과 네트워크를 관리합니다. 여러 서비스 실행, 로그를 통한 장애 조사, 디스크 정리와 Dockerfile 개선에도 사용합니다.

• 컨테이너를 시작하고 중지합니다
• Docker Compose로 여러 서비스를 실행합니다
• 로그로 컨테이너 종료 원인을 조사합니다

유사 기업의 매출, 이익률, 가치평가 배수를 비교하는 Excel을 만듭니다. 수식, 중앙값, 사분위수와 데이터 출처를 정리해 투자나 인수 검토 자료를 준비합니다.

• 동종 기업과 기업가치 비교
• 인수 검토용 비교 자료 작성
• 업계 성장성과 수익성 비교

Helps Claude work in desktop apps by viewing screenshots, clicking, typing, and scrolling. It covers access approval, choosing appropriate tools, and handling app restrictions for tasks in Notes, Finder, settings, and other native apps.

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

• Organizing notes in Notes
• Working with files in Finder
• Checking settings shown on screen

Research a listed company's business quality and valuation using official filings, comparisons with similar companies, and historical performance. Produce an evidence-backed report and scorecard, with separate modes for accounting concerns and companies preparing for an IPO.

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

• Compare a company's financial strength with sector peers
• Investigate gaps between reported profit and cash flow
• Assess assumptions built into a stock's current price

Review proposal responses for missing requirements, compare competing products, and plan proof-of-concept trials that test customer needs. Supports technical sales work from requirement discovery and demo preparation through evaluation scorecards and technical proposals.

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

• Checking proposal responses for missing requirements
• Comparing product features against competitors
• Preparing a demo around customer priorities

Build and maintain interfaces with shadcn/ui by finding, adding, and combining components. The skill uses project settings, component documentation, and change previews to guide styling, debugging, preset changes, and updates that preserve local edits.

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

• Building settings pages and dashboards from existing components
• Fixing form and dialog composition issues
• Updating components while preserving local edits

Use a computer connected to Kortix to read and write files, run shell commands, and operate desktop apps. The skill covers machine selection, access checks, screen inspection, and handling connection or permission errors.

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

• Reading and editing files on a connected computer
• Running commands on a selected laptop or server
• Clicking and typing in desktop applications

Organize competitive analysis across six areas, from market structure to competitors’ future plans. Choose the steps relevant to a business decision and turn findings into comparison matrices, sales reference sheets, positioning responses, and threat assessments.

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

• Planning competitive research for an annual strategy review
• Combining scattered competitor research into usable materials
• Preparing sales responses against a specific rival

Research key competitors and produce cited profiles, a comparison table, and implications for a product decision. Separate facts from inferences and assumptions, highlight evidence quality, and create a consistent baseline for later comparisons.

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

• Reviewing a product's positioning against competitors
• Informing roadmap priorities with competitive evidence
• Investigating a rival's strengths after lost deals

Find and install reusable HyperFrames blocks and effect components, then integrate them into an existing composition. Configure block timing and layer order, merge component HTML, CSS, and JavaScript, and adjust installation paths.

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

• Find reusable blocks and components in the registry
• Add an installed block to an existing composition
• Merge effect snippets into HTML, CSS, and JavaScript

Build and maintain interfaces with shadcn/ui by finding, adding, and combining components. The skill uses project settings, component documentation, and change previews to guide styling, debugging, preset changes, and updates that preserve local edits.

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

• Building settings pages and dashboards from existing components
• Fixing form and dialog composition issues
• Updating components while preserving local edits

Create or edit CodeCompanion.nvim documentation with clear English, consistent page structure and complete configuration examples. Follow detailed rules for headings, tables, terminology and links, then regenerate Neovim help documentation after changes.

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

• Writing a new CodeCompanion.nvim usage page
• Revising configuration examples for direct copying
• Standardizing headings, tables and terminology

Extract YouTube transcripts and analyze messaging, structure, intended viewers, emotional appeal, credibility, and calls to action—requests for viewers to act. Analyze one video or compare several keyword-selected videos to identify recurring strategies and content gaps.

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

• Compare competitors' video content strategies
• Research intended viewers and their problems
• Identify topics competitors have not covered

Build Vue 3 components with TypeScript and Composition API, a way to organize component logic. Define inputs, events, and two-way bindings, manage reactive data, and use built-in components for transitions and state preservation.

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

• Build Vue components with TypeScript
• Define component inputs, events, and two-way bindings
• Update displays and react to data changes

Get reminders to compact conversation context, meaning summarize it for continued work, during long Claude Code sessions. A tool-call counter prompts consideration of manual compaction, with guidance on choosing useful breaks between task phases.

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

• Compact context between research and implementation
• Organize context after a milestone
• Clear debugging context before continuing

Company discovery and deep research skill. Researches a company's product and ICP, discovers target companies to sell to using Browserbase Search API, deeply researches each using a Plan→Research→Synthesize pattern, and scores ICP fit — compiled into a scored research report and CSV. Supports depth modes (quick/deep/deeper) for balancing scale vs intelligence. Use when the user wants to: (1) find companies to sell to, (2) research potential customers, (3) discover companies matching an ICP, (4) build a target company list, (5) do market research on prospects. Triggers: "find companies to sell to", "company research", "find prospects", "ICP research", "target companies", "who should we sell to", "market research", "lead research", "prospect list".

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

Clones and audits competitor repositories into evidence-based intelligence with file:line citations. Use to track competitors, add a competitor repo, review competitor code, compare capabilities, build a competitor landscape, or check for code updates: 竞品分析 / 竞品 / competitor scan / analyze competitor / compare with X / latest competitor code. Not for market research without code (use deep-research).

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

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X."

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

Owns project and build-level work for Compose and Compose Multiplatform apps: bootstrapping a new project, adopting the kit in an existing project, adding or extracting a module, convention plugins in build-logic, the version catalog, and CI plus agent hooks. Use when starting a Compose Multiplatform app, adding a module, or editing settings.gradle.kts, build.gradle.kts, build-logic, libs.versions.toml, or packaging. Do NOT use for routing and architecture choices (compose-architecture), feature code (compose-feature), repositories and persistence (compose-data), composables or resources (compose-ui), or commonMain vs platform code (compose-platform).

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

Use when writing, changing or reviewing code that touches the house contract for Jetpack Compose and Compose Multiplatform apps: module graph, MVI/BaseViewModel, error tiers, state ownership, naming, Koin DI, Navigation 3 and coroutines. The compose skill is the entry point. Do NOT use for Gradle-only work (compose-project), new screens (compose-feature), composable-only work (compose-ui), repositories or persistence (compose-data), or expect/actual splits (compose-platform).

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

Writes and reviews composables for Compose and CMP: the Route/Screen/leaf split, state-read placement and stability, loading/empty/error UX states, LazyColumn lists and grids, animation choice, accessibility and semantics, design-system tokens, CMP Res resources, Coil images, and keyboard/focus. Use when touching @Composable code, recomposition, stability, LazyColumn, animation, shimmer or skeleton, accessibility, theme, colors, Res.string, Coil, focus, or keyboard. Do NOT use for MVI, error tiers, or module graph (compose-architecture), ViewModel or data work (compose-feature, compose-data), Gradle or module work (compose-project), or expect/actual splits (compose-platform).

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

Expert in competitive intelligence - systematic gathering, analysis, and application of information about competitors. Covers competitive research, win/loss analysis, competitive positioning, and building competitive advantage. Knows when to compete and when to differentiate. Use when "competitive intelligence, competitor analysis, win loss, battlecard, competitive positioning, market landscape, competitor, " mentioned.

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

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. Inside: 4-step research framework (website → social → traffic → ad spend) · 3-version Wayback evolution analysis · X/Twitter propagation-chain mapping · growth-flywheel 6-stage scoring · KOL identification · content-effectiveness ranking · ICP + freemium pricing teardown · self-check checklist. New in 1.2: time-machine competitor archaeology — Google date-range search back to pre-fame years, star-history launch-day reconstruction (AppFlowy ~40-channel zero-budget launch teardown), competitor funding news as a launch-timing signal, and the "open source alternative" positioning play. Sourced from first-hand founder interviews (AFFiNE co-founder, 2026-04, self-reported figures marked). 🇨🇳 你的竞品刚刚爆了。你完全不知道他们怎么做到的。该拆官网？盯社媒？画增长飞轮？这份 SOP 给你从 Wayback Machine 快照到 X/Twitter 传播链路还原到飞轮六阶段评分的完整方法论。基于 150+ AI 创业公司竞品分析实战，含 Lovable 完整案例。 🇯🇵 競合が突然バズった。どうやって成長したか全く分からない。このSOPは、Waybackスナップショットからツイッター伝播チェーン分析、フライホイール6段階スコアリングまでの完全な競合調査フレームワークを提供します。150以上のAIスタートアップ分析から構築。 🇰🇷 경쟁사가 갑자기 폭발적으로 성장했습니다. 어떻게 그렇게 빨리 성장했는지 모릅니다. 이 SOP는 Wayback 스냅샷부터 X/Twitter 전파 체인 분석, 플라이휠 6단계 스코어링까지 완전한 경쟁사 조사 프레임워크를 제공합니다. 150개 이상의 AI 스타트업 분석에서 구축. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "竞品调研" | "竞品分析" | "增长飞轮" | "传播链路" | "競合分析" | "경쟁사 분석" | "social media teardown" | "Twitter propagation" | "content strategy analysis"

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

Computational thinking as a problem-solving discipline independent of programming languages. Covers the four pillars (decomposition, pattern recognition, abstraction, algorithm design), computational problem-solving methodology (understand, decompose, generalize, formalize, verify), abstraction levels (from hardware through user interface), modeling and simulation, automata and formal languages (DFA, NFA, regular expressions, context-free grammars, Turing machines), computational complexity classes (P, NP, NP-complete, undecidable), and constructionist pedagogy (learning by building, Logo, Scratch, physical computing). Use when approaching unfamiliar problems, teaching problem-solving strategies, analyzing problem complexity, or bridging between domain knowledge and computational solutions.

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