「pip」の検索結果

Data architecture patterns (warehouse, lake, lakehouse, mesh), ETL/ELT pipelines, streaming architectures, scaling strategies, and schema design patterns

日本語の概要は準備中です。原文の説明を表示しています。

Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.

日本語の概要は準備中です。原文の説明を表示しています。

Dung khi mot CA NHAN muon len hinh bang AI thay vi tu quay — pipeline avatar AI: 3 tier cong cu, 4 workflow gom avatar don, dich da ngon ngu, san xuat hang loat va hybrid nguoi that cong AI; nhan anh reference de tao prompt avatar; thay mat, style, logo; ghep voice clone; tranh bi nen tang danh dau; cong bo AI theo Nghi dinh 147/2024 va QA 100 diem. Cong cu HeyGen, Synthesia, ElevenLabs, Captions, Vbee. Kich hoat khi user nhac 'tao avatar AI', 'video HeyGen', 'talking head AI', 'lam video ma ngai lo mat', 'batch video AI', 'dich video sang tieng Anh', 'prompt avatar'. Khong dung cho — clone giong cho podcast va audio thi dung skill 25-voice-clone-podcast; viet loi thoai video thi dung skill 04-script-video; anh tinh thi dung skill 30-thiet-ke-master.

日本語の概要は準備中です。原文の説明を表示しています。

Dung khi doanh nghiep Viet Nam muon ban ra NUOC NGOAI theo duong B2B — ho so nang luc tieng Anh, chon thi truong muc tieu, pitch deck cho buyer, email chao hang quoc te, chuan bi hoi cho thuong mai va kenh Alibaba, Amazon Business. Kich hoat khi user nhac 'xuat khau', 'ban hang nuoc ngoai', 'tim buyer quoc te', 'company profile tieng Anh', 'email chao hang export', 'di hoi cho thuong mai', 'khach nuoc ngoai hoi gia', 'lam sao co don hang xuat khau'. Khong dung cho — tim va nuoi lead B2B trong nuoc thi dung skill 33-b2b-lead-gen; bo tai lieu ban hang va pipeline thi dung skill 71-sales-enablement; chuoi email nuoi duong thi dung skill 14-email-marketing.

日本語の概要は準備中です。原文の説明を表示しています。

Dung khi can tim va tiep can khach hang doanh nghiep — xac dinh ICP, dung danh sach prospect co nguon va ngay verify, cham diem Hot/Warm/Cold, va viet outreach qua Zalo, dien thoai, email. Kich hoat khi user nhac 'tim khach hang B2B', 'danh sach prospect', 'lead gen B2B', 'tiep can doanh nghiep', 'cold outreach', 'ban cho cong ty'. Khong dung cho — khach hang o NUOC NGOAI thi dung skill 29-xuat-khau-b2b; tai lieu ban hang va quan ly pipeline thi dung skill 71-sales-enablement; khach hang le B2C thi dung skill 09-insight-khach-hang.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a structured AskUserQuestion multi-option picker for user agency, and dispatches the chosen mode. Mode D (Atlas Fleet) is selectable only when detect_capabilities returns tier=premium (licensed atlas-launcher detected); otherwise it is a locked Atlas Pro teaser. Plan Mode is NOT used (spec section 13.5): AskUserQuestion is the sole user-agency mechanism. Declares HANDOFF complete so EXECUTE can follow.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholders_found, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis, and expands every task into verifiable subtasks. Autonomous-safe. Declares GENERATE complete so HANDOFF can follow.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

日本語の概要は準備中です。原文の説明を表示しています。

한국+EU 병기 처리방침·이용약관 자동 생성. 한국 본사가 EU 사용자까지 대상으로 서비스할 때 사용. 한국어(PIPA)·영문(GDPR) 두 세트 문서를 동시 생성하고, Footer에 언어·관할 전환 링크 자동 삽입.

日本語の概要は準備中です。原文の説明を表示しています。

한국+일본 병기 처리방침·이용약관 자동 생성. 한국 본사가 일본 사용자까지 대상으로 서비스할 때 사용. 한국어(PIPA)·일본어(APPI) 두 세트 문서를 동시 생성하고, Footer에 언어·관할 전환 링크 자동 삽입.

日本語の概要は準備中です。原文の説明を表示しています。

처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). 호출 시 privacy-kr·privacy-eu·privacy-us·privacy-global 4개 하위 스킬을 번호 메뉴로 제시하고 번호 입력 즉시 해당 스킬 인터뷰로 직행. 한국 PIPA + EU GDPR + US CCPA/CPRA 대응.

日本語の概要は準備中です。原文の説明を表示しています。

Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.

日本語の概要は準備中です。原文の説明を表示しています。

Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.

日本語の概要は準備中です。原文の説明を表示しています。

Implements safe error boundaries, cancellation and user recovery contracts; not telemetry pipelines or durable retry machinery.

日本語の概要は準備中です。原文の説明を表示しています。

Design NestJS module boundaries and provider ownership. Use only when structuring feature/core/shared modules, controller-service boundaries, or provider lifetime; defer JWT/security, caching, and unrelated request-pipeline recipes.

日本語の概要は準備中です。原文の説明を表示しています。

Implement modern concurrency with Virtual Threads and Structured Concurrency in Java. Use when implementing Java Virtual Threads (Java 21), Structured Concurrency with StructuredTaskScope, CompletableFuture pipelines, or debugging race conditions.

日本語の概要は準備中です。原文の説明を表示しています。

Set up CI/CD pipelines for Flutter apps. Use when configuring automated testing, build, or deployment workflows with GitHub Actions or Fastlane.

日本語の概要は準備中です。原文の説明を表示しています。

OWASP LLM Top 10 (2025) audit checklist for AI applications, agent tools, RAG pipelines, and prompt construction. Use when performing any security review touching LLM client code, prompt templates, agent tools, or vector stores.

日本語の概要は準備中です。原文の説明を表示しています。

Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".

日本語の概要は準備中です。原文の説明を表示しています。

Unified team skill for performance optimization. Coordinator orchestrates pipeline, workers are team-worker agents. Supports single/fan-out/independent parallel modes. Triggers on "team perf-opt".

日本語の概要は準備中です。原文の説明を表示しています。

Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review.

日本語の概要は準備中です。原文の説明を表示しています。

Unified team skill for architecture optimization. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team arch-opt".

日本語の概要は準備中です。原文の説明を表示しています。

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

日本語の概要は準備中です。原文の説明を表示しています。