171 件 ・ 関連度順
概要と使いどころ
Talent acquisition across recruiting strategy, sourcing, interviews, and hiring analytics. Use when writing job descriptions, designing interview scorecards, analyzing hiring funnels, or improving offer acceptance rates.
日本語の概要は準備中です。原文の説明を表示しています。
Orientação completa sobre conformidade com regulamentações do Banco Central do Brasil: Resolução CMN nº 4.893/2021 (Política de Segurança Cibernética), Resolução BCB nº 85/2021 (GRSIC), Open Finance Brasil (Resoluções BCB nº 32/2020 e atualizações), e demais normas prudenciais do BACEN. Cobre elaboração e revisão de Política de Segurança Cibernética, Plano de Ação e Resposta a Incidentes (PARI), Gestão de Riscos de Serviços de Informação e Comunicação (GRSIC), consentimento e compartilhamento de dados no Open Finance, requisitos de API, gestão de terceiros (outsourcing) e sanções do BACEN. Triggers: Bacen, Banco Central, CMN 4.893, Resolução 4.893, segurança cibernética bancária, PARI, GRSIC, Open Finance, Open Banking, compartilhamento de dados financeiros, consentimento Open Finance, API financeira, outsourcing bancário, risco cibernético, incidente cibernético banco, LGPD financeira, fintech compliance, instituição financeira, DICT, Pix segurança.
日本語の概要は準備中です。原文の説明を表示しています。
Build students' capacity to interrogate a historical source before reading — asking who authored it, when, why, and what this means for reliability. Use when students read documents without attending to authorship.
日本語の概要は準備中です。原文の説明を表示しています。
Wholesale product sourcing — supplier discovery, negotiation, MOQ optimization, margin analysis
日本語の概要は準備中です。原文の説明を表示しています。
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution
日本語の概要は準備中です。原文の説明を表示しています。
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
日本語の概要は準備中です。原文の説明を表示しています。
广告外包公司绩效管理 (广告外包公司绩效管理 (Ad Agency / Marketing-Outsourcing Firm Performance Management) — 广告/营销外包公司(乙方 agency:创意热店/4A/本土广告公司/传媒公司/数字营销代理/MCN/设计工作室/内容外包)的『怎么做绩效管理』职业认知操作系统,面向老板/合伙人、运营总监(COO)、HR/HRBP、项目总监、team lead、以及想搭绩效体系的从业者。覆盖: (a) 第一性张力 — 绩效管理的核心世界观分歧: **创意/知识工作『不可量化』 vs 『必须可考核』(创意难归因、难标准化,硬套 KPI 杀创意;但不考核养懒人——这是本行绩效的元矛盾) ⇄ 结果导向(KPI/业绩/回款) vs 过程导向(OKR/能力/成长) ⇄ 个人绩效 vs 团队协作(广告是集体产物,创意-AE-媒介-设计协作,难拆到个人) ⇄ 强激励(提成制:多劳多得但抢单/短视/不协作/吃老客户) vs 稳定(固定+奖金:公平但大锅饭) ⇄ 规模/流水 vs 利润/人效(低价接单冲规模 vs 保毛利)**; (b) 绩效体系设计 — KPI(关键指标法)/OKR(目标与关键成果)/BSC(平衡计分卡)/360 环评/MBO(目标管理)/KSF(关键成功因子)/积分制/计件提成;考核周期(月/季/年+项目制);绩效面谈、绩效改进 PIP、强制分布(271/活力曲线)争议、绩效结果应用(调薪/晋升/淘汰/奖金); (c) 分岗位绩效(本行难点,各岗量化差异极大) — 创意(文案/美术/创意总监:作品质量、获奖、比稿命中率——最难量化)、AE/客户执行(客户满意度、续约、回款、增购、客诉)、媒介/投放(可量化:ROI/ROAS/CPM/转化——最易量化)、策略/策划(方案通过率、洞察)、设计(产能/返稿率/品质)、项目管理(交付准时率、利润率)、销售/BD(新签、回款、毛利); (d) 项目与客户维度绩效(agency 特有,专业服务公司逻辑) — 项目利润率(收入-人力成本-外部成本)、工时制与人效(billability 可计费工时率/utilization 利用率/realization 实现率,借鉴咨询律所)、人均产值/人均毛利、客户续约率与 LTV、客户集中度风险、比稿投入产出、改稿次数失控; (e) 激励与分配机制 — 提成制(按签单/毛利/回款抽成)、项目奖金分成(如何在创意-AE-媒介间分)、年终奖包、合伙人制/事业合伙人/工作室 studio 制/阿米巴、股权期权、创意人才的非物质激励(署名/获奖/成长); (f) 人效、成本与文化 — 人效比(人力成本占收入比,业内估计通常 40-55%,非普适)、毛利率、加班/血汗工厂文化批判(乙方 996/改稿到凌晨)、人才流失率与保留、招聘与培养、组织架构(客户组 vs 职能组 vs 项目制矩阵); (g) 外包/乙方特有张力对绩效的侵蚀 — 甲乙方权力不对等(甲方压价、无限改稿、比稿白嫖创意、账期长垫款重回款难)、低价内卷与红海、项目制不确定性(旺淡季、大客户依赖)、创意工时不可控如何计入绩效、外包 vs 自建团队的成本对比; (h) 争议/批判 — KPI 量化派 vs 创意不可考核派、提成制养蛊 vs 团队协作、强制分布/末位淘汰是否适合小 agency、工时制(billable hours)被咨询律所验证但绑架员工健康、『向甲方看齐做 OKR』水土不服、绩效主义扼杀创意(索尼绩效主义之殇式批判)、乙方绩效本质是『用考核对冲甲方不确定性』的转嫁; (i) 流派/思想谱系 — 专业服务公司管理派(David Maister《Managing the Professional Service Firm》PSF 圣经:leverage 杠杆/utilization 利用率/billing;借鉴咨询律所会计所) vs agency 专家经营派(David C. Baker《The Business of Expertise》+2Bobs podcast、Blair Enns《Win Without Pitching》《Pricing Creativity》定位与定价) vs OKR/目标管理派(John Doerr《Measure What Matters》、Google/Intel OKR、字节/飞书 OKR 本土化) vs 中式绩效工具派(KSF 薪酬全绩效/积分制/阿米巴/华为绩效体系被广告公司借用) vs 本土 4A/广告公司实战派(省广/蓝色光标/华扬联众/利欧 等上市广告公司管理 + 创意热店工作室制)。不含: 广告投放/信息流/SEM 的技术操作本身、甲方市场部/品牌方内部绩效、通用 HR 招聘薪酬全流程(仅取与绩效相关部分)、纯财务会计做账、MCN 达人孵化运营细节。) Master OS — automated mastery of 广告外包公司绩效管理 (Ad Agency / Marketing-Outsourcing Firm Performance Management) — 广告/营销外包公司(乙方 agency:创意热店/4A/本土广告公司/传媒公司/数字营销代理/MCN/设计工作室/内容外包)的『怎么做绩效管理』职业认知操作系统,面向老板/合伙人、运营总监(COO)、HR/HRBP、项目总监、team lead、以及想搭绩效体系的从业者。覆盖: (a) 第一性张力 — 绩效管理的核心世界观分歧: **创意/知识工作『不可量化』 vs 『必须可考核』(创意难归因、难标准化,硬套 KPI 杀创意;但不考核养懒人——这是本行绩效的元矛盾) ⇄ 结果导向(KPI/业绩/回款) vs 过程导向(OKR/能力/成长) ⇄ 个人绩效 vs 团队协作(广告是集体产物,创意-AE-媒介-设计协作,难拆到个人) ⇄ 强激励(提成制:多劳多得但抢单/短视/不协作/吃老客户) vs 稳定(固定+奖金:公平但大锅饭) ⇄ 规模/流水 vs 利润/人效(低价接单冲规模 vs 保毛利)**; (b) 绩效体系设计 — KPI(关键指标法)/OKR(目标与关键成果)/BSC(平衡计分卡)/360 环评/MBO(目标管理)/KSF(关键成功因子)/积分制/计件提成;考核周期(月/季/年+项目制);绩效面谈、绩效改进 PIP、强制分布(271/活力曲线)争议、绩效结果应用(调薪/晋升/淘汰/奖金); (c) 分岗位绩效(本行难点,各岗量化差异极大) — 创意(文案/美术/创意总监:作品质量、获奖、比稿命中率——最难量化)、AE/客户执行(客户满意度、续约、回款、增购、客诉)、媒介/投放(可量化:ROI/ROAS/CPM/转化——最易量化)、策略/策划(方案通过率、洞察)、设计(产能/返稿率/品质)、项目管理(交付准时率、利润率)、销售/BD(新签、回款、毛利); (d) 项目与客户维度绩效(agency 特有,专业服务公司逻辑) — 项目利润率(收入-人力成本-外部成本)、工时制与人效(billability 可计费工时率/utilization 利用率/realization 实现率,借鉴咨询律所)、人均产值/人均毛利、客户续约率与 LTV、客户集中度风险、比稿投入产出、改稿次数失控; (e) 激励与分配机制 — 提成制(按签单/毛利/回款抽成)、项目奖金分成(如何在创意-AE-媒介间分)、年终奖包、合伙人制/事业合伙人/工作室 studio 制/阿米巴、股权期权、创意人才的非物质激励(署名/获奖/成长); (f) 人效、成本与文化 — 人效比(人力成本占收入比,业内估计通常 40-55%,非普适)、毛利率、加班/血汗工厂文化批判(乙方 996/改稿到凌晨)、人才流失率与保留、招聘与培养、组织架构(客户组 vs 职能组 vs 项目制矩阵); (g) 外包/乙方特有张力对绩效的侵蚀 — 甲乙方权力不对等(甲方压价、无限改稿、比稿白嫖创意、账期长垫款重回款难)、低价内卷与红海、项目制不确定性(旺淡季、大客户依赖)、创意工时不可控如何计入绩效、外包 vs 自建团队的成本对比; (h) 争议/批判 — KPI 量化派 vs 创意不可考核派、提成制养蛊 vs 团队协作、强制分布/末位淘汰是否适合小 agency、工时制(billable hours)被咨询律所验证但绑架员工健康、『向甲方看齐做 OKR』水土不服、绩效主义扼杀创意(索尼绩效主义之殇式批判)、乙方绩效本质是『用考核对冲甲方不确定性』的转嫁; (i) 流派/思想谱系 — 专业服务公司管理派(David Maister《Managing the Professional Service Firm》PSF 圣经:leverage 杠杆/utilization 利用率/billing;借鉴咨询律所会计所) vs agency 专家经营派(David C. Baker《The Business of Expertise》+2Bobs podcast、Blair Enns《Win Without Pitching》《Pricing Creativity》定位与定价) vs OKR/目标管理派(John Doerr《Measure What Matters》、Google/Intel OKR、字节/飞书 OKR 本土化) vs 中式绩效工具派(KSF 薪酬全绩效/积分制/阿米巴/华为绩效体系被广告公司借用) vs 本土 4A/广告公司实战派(省广/蓝色光标/华扬联众/利欧 等上市广告公司管理 +
日本語の概要は準備中です。原文の説明を表示しています。
Build students' capacity to interrogate a historical source before reading — asking who authored it, when, why, and what this means for reliability. Use when students read documents without attending to authorship.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a PCBA BOM and proposed components before circuit or placement freeze, including exact manufacturer part numbers, pin semantics, packages, footprints, CAD and 3D models, lifecycle, live stock, MOQ, assembly class, price, and approved substitutes. Use for sourcing locks, unavailable or expensive parts, JLCPCB/LCSC matching, BOM risk, or cost-aware substitution decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Manage an electronics bill of materials across distributors and fabricators: part selection, stock, pricing, alternates, ordering, KiCad properties, and BOM/CPL export. Use for distributor-neutral sourcing, cost comparison, order preparation, or requests such as "what parts do I need" and "export for JLCPCB". Do not take over schematic analysis or a complete new-design workflow unless the requested task is specifically its sourcing/manufacturing stage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building data pipelines, ETL jobs, event processors, message-broker producers/consumers, application caching layers, database migrations, BigQuery queries, or event-sourcing handlers in TypeScript. Triggers on edits to indexer/ETL/migration code, Prisma or Drizzle schemas, BigQuery integration code, RabbitMQ/Kafka/SQS/BullMQ producer or consumer code, Redis cache wrappers, or mentions of "data engineering", "ETL", "pipeline", "indexer", "event sourcing", "data warehouse", "data migration", "message queue", "RabbitMQ", "Kafka", "SQS", "BullMQ", "Redis cache", or "caching".
日本語の概要は準備中です。原文の説明を表示しています。
Message queues, pub/sub, event sourcing with Kafka, RabbitMQ, Redis Streams. Activate on: event-driven, message queue, pub/sub, Kafka, RabbitMQ, event bus, async messaging, dead letter queue. NOT for: CQRS projections (use cqrs-event-sourcing-architect), real-time WebSocket (use websocket-realtime-expert), observability (use observability-apm-expert).
日本語の概要は準備中です。原文の説明を表示しています。
Saga patterns, compensating actions, and two-phase commit for distributed transactions. Activate on: distributed transaction, saga, compensating action, two-phase commit, eventual consistency, cross-service transaction. NOT for: single-database transactions (use database-connection-pool-manager), event sourcing (use cqrs-event-sourcing-architect).
日本語の概要は準備中です。原文の説明を表示しています。
Product-research (选品) desk (Busabase App-in-Skill) for a cross-border e-commerce seller. The agent sweeps trend sources — Amazon BSR movers, TikTok viral product videos, Temu/AliExpress rising items, Google Trends terms, competitor new launches — and files product candidates with margin cards (landed cost, fees, breakeven ACOS) and competition reads; Kelly verdicts them develop / watch / drop, and develop items become sourcing and listing briefs handed to kelly-listing. Use when the user invokes $kelly-picks or /kelly-picks, or asks for 选品, product research, a product sourcing radar, BSR movers, TikTok viral products, a margin calculator, breakeven ACOS, competition reads, or product candidate triage.
日本語の概要は準備中です。原文の説明を表示しています。
Busabase-backed App-in-Skill control panel / kanban board for a BD or sourcing team triaging merchant and business financing leads for a lender or investment fund. Use when the user invokes $kelly-lead-funnel or /kelly-lead-funnel, wants to review the deal sourcing pipeline, funnel, lead board, or asks to move a lead's stage, reject a lead, add a note, score a lead, or see funnel conversion rates. Deterministic rule-based lead scoring only — never an LLM call — and never sends outreach, signs term sheets, or moves money.
日本語の概要は準備中です。原文の説明を表示しています。
Temu, SHEIN, AliExpress, and TikTok product selection big data analysis agent. Identify trending products, analyze competition, estimate demand, and find sourcing opportunities across fast-fashion and marketplace platforms. Triggers: temu product selection, shein product research, aliexpress trending, tiktok shop products, temu selector, fast fashion products, temu trending, shein trends, product sourcing, dropshipping products, temu winning products
日本語の概要は準備中です。原文の説明を表示しています。
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
日本語の概要は準備中です。原文の説明を表示しています。
Designs event-driven architectures with event sourcing, CQRS, pub/sub patterns, and domain events for decoupled systems. Use when users request "event sourcing", "CQRS", "domain events", "pub/sub", or "event-driven".
日本語の概要は準備中です。原文の説明を表示しています。
Message queues, pub/sub, event sourcing with Kafka, RabbitMQ, Redis Streams. Activate on: event-driven, message queue, pub/sub, Kafka, RabbitMQ, event bus, async messaging, dead letter queue. NOT for: CQRS projections (use cqrs-event-sourcing-architect), real-time WebSocket (use websocket-realtime-expert), observability (use observability-apm-expert).
日本語の概要は準備中です。原文の説明を表示しています。
Saga patterns, compensating actions, and two-phase commit for distributed transactions. Activate on: distributed transaction, saga, compensating action, two-phase commit, eventual consistency, cross-service transaction. NOT for: single-database transactions (use database-connection-pool-manager), event sourcing (use cqrs-event-sourcing-architect).
日本語の概要は準備中です。原文の説明を表示しています。
運送会社の選定、運賃交渉、入札、実績評価、貨物の割り当てを支援します。米国の輸送実務を基に、費用・配送品質・輸送力を踏まえた契約や更新の判断を整理します。
Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when audio already placed in a HyperFrames composition needs to be mixed: fade-in/fade-out, crossfade, track gain or volume, volume automation, ducking, a music bed that fights a voiceover (voiceover carve), effects on a track (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser, bitcrush), automation envelopes drawn on a track's volume or any effect parameter, or one submix bus carrying a chain, a fader and an automation clock for several tracks at once (`<hf-audio-group>`). Don't use for sourcing or generating audio — finding BGM, SFX, or making a voiceover is `/media-use`. Don't use for clip timing or track layout, which is `/hyperframes-core`.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
日本語の概要は準備中です。原文の説明を表示しています。