4,026 件 ・ 関連度順
概要と使いどころ
Guides conversion of gap analysis findings into phased implementation plans with milestones and risk-based prioritisation. Activate when building compliance programmes or allocating privacy budgets. Keywords: remediation roadmap, implementation plan, phased approach, prioritisation.
日本語の概要は準備中です。原文の説明を表示しています。
Implements data lineage tracking for privacy compliance including origin tracking, transformation logging, access auditing, deletion verification, and cross-system lineage graphs. Covers source-to-sink mapping, GDPR Art. 30 RoPA integration, automated lineage discovery, and breach impact scoping. Keywords: data lineage, data provenance, data flow mapping, transformation logging, deletion verification.
日本語の概要は準備中です。原文の説明を表示しています。
Builds comprehensive data inventory per GDPR Art. 30 Records of Processing Activities. Covers system-by-system discovery, data flow diagramming, third-party identification, and legal basis per category. Keywords: data inventory, data mapping, Art 30, RoPA, data flow, processing activities.
日本語の概要は準備中です。原文の説明を表示しています。
Master prioritization frameworks, roadmap planning, timeline estimation, and resource allocation. Create executable roadmaps that drive focus and alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning with fixed deadline or target outcome, working backward from future goal to present, defining milestones and dependencies, mapping critical path, identifying what must happen when, planning product launches with hard dates, multi-year strategic roadmaps, event planning, transformation initiatives, or when user mentions "backcast", "work backward from", "reverse planning", "we need to launch by", "target date is", or "what needs to happen to reach".
日本語の概要は準備中です。原文の説明を表示しています。
Badger Maps integration. Manage data, records, and automate workflows. Use when the user wants to interact with Badger Maps data.
日本語の概要は準備中です。原文の説明を表示しています。
Fix LRU-bounded Flutter/bloc state classes that silently lose insertion-order updates. Use when: (1) a state class uses `Equatable` with a `LinkedHashMap<K, V>` field to preserve insertion order (LRU, MRU, recent-items caches), (2) `Cubit.emit` appears to drop emissions when an existing key is re-inserted or moved to most-recent, (3) LRU eviction evicts the "wrong" entry after a refresh, (4) a test that reports the same key twice and then overflows the cap sees the refreshed entry evicted instead of the oldest. Root cause: Equatable's default map comparison is structural (unordered), so reordering without changing keys/values produces an "equal" state that `Cubit.emit` suppresses.
日本語の概要は準備中です。原文の説明を表示しています。
Code intelligence over repositories Guaardvark has indexed: semantic code search, exact-text search, file listing, PageRank repository map, import dependency graph, reading one class or function, analysis and generated rewrites, plus the System Mapper and self-improvement status. Use when the user asks where something is implemented, how modules depend on each other, or wants an architecture map of an indexed repo.
日本語の概要は準備中です。原文の説明を表示しています。
Establish explicit traceability between formal specifications (preconditions, postconditions, invariants) and verified code components with their correctness proofs. Produce structured Markdown mapping reports showing verification coverage and proof evidence. Use when auditing formal verification, documenting verified systems, establishing traceability for certification, or when the user asks to map specifications to code, generate verification reports, or analyze verification coverage in Coq, Dafny, Isabelle, or other proof assistants.
日本語の概要は準備中です。原文の説明を表示しています。
Map the big picture around a topic or software repository by identifying its boundaries, layers, actors, components, relationships, flows, history, fault lines, and open questions, then explain how the pieces fit together and where to look next. Use when a user asks to understand a whole field, domain, technology, ecosystem, industry, codebase, architecture, unfamiliar repo, or phrases such as "give me the big picture", "map the landscape", "how does this all fit together?", "help me get oriented", or "what am I missing?"
日本語の概要は準備中です。原文の説明を表示しています。
A high-level conceptual mapping from Active Directory attack techniques to the compliance controls they touch. Kerberoasting relates to authentication and logging, so it brushes ENS op.acc.5 / op.exp.8, NIS2 Art.21(2)(h), DORA RTS Art.9 / Art.21. Use this when a reader wants to understand which regulatory control an AD finding relates to, or to add an orientation note to a technical finding. This is a conceptual, orientative mapping only; it is NOT an auditor-defensible, curated, ID-by-ID control matrix. Covers ENS (op.acc.*, op.exp.*), NIS2 (Directive 2022/2555 Art.21), and DORA (RTS 2024/1774).
日本語の概要は準備中です。原文の説明を表示しています。
Visualize and map user flows with Mermaid diagrams, decision points, error states, and conversion metrics to optimize user journeys. Use when the user requests user flow mapping or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Apply umap-learn in reproducible local data workflows with version-aware APIs, explicit assumptions, and validation. Use when the user chooses umap-learn or its strengths fit the task.
日本語の概要は準備中です。原文の説明を表示しています。
Predict enhancer-gene regulatory connections from ATAC-seq using ABC, ENCODE-rE2G, HiChIP, or Cicero. Use when linking distal enhancers to target genes, choosing between contact-aware (ABC, ENCODE-rE2G), accessibility-only (Cicero), and orthogonal (HiChIP H3K27ac, EpiMap) approaches, validating predictions against CRISPRi-FlowFISH gold-standard, or building cell-type-specific regulatory maps for fine-mapping or therapeutic target discovery.
日本語の概要は準備中です。原文の説明を表示しています。
Select colormaps and qualitative palettes for scientific figures using perceptual-uniformity, color-vision-deficiency safety, and luminance-monotonicity criteria. Covers Crameri scientific colormaps, viridis/cividis/magma, Okabe-Ito categorical, ColorBrewer, and the rainbow/jet critique. Use when choosing palettes for heatmaps, scatter, networks, or any encoding where color carries quantitative or categorical meaning.
日本語の概要は準備中です。原文の説明を表示しています。
Align preprocessed CLIP-seq reads (eCLIP, iCLIP, iCLIP2, PAR-CLIP) to genome with STAR or bowtie2 using crosslink-preserving parameters, choosing between unique-mapper-only and multi-mapper-aware alignment for repeat-binding RBPs, deciding STAR vs HISAT2 memory trade-offs, and applying ENCODE-compatible filters. Use when turning preprocessed CLIP FASTQ into a deduplicated, MAPQ-filtered BAM ready for peak calling or crosslink-site detection.
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct ancestral states at internal phylogenetic nodes for sequences (PAML codeml, IQ-TREE --ancestral, GRASP, FastML), discrete traits (corHMM hidden-rate Markov, ape::ace, phytools::make.simmap stochastic mapping, BayesTraits), and continuous traits (phytools::fastAnc, geiger Brownian/OU, RPANDA). Use when designing constructs for ancestral protein resurrection, tracing trait evolution along a tree, performing stochastic character mapping, testing models of trait evolution (BM vs OU vs EB), inferring ancestral genome content via Dollo or DTL reconciliation, or quantifying ancestral-state uncertainty for downstream comparative analyses.
日本語の概要は準備中です。原文の説明を表示しています。
Detect allele-specific chromatin accessibility from ATAC-seq using WASP, GATK ASEReadCounter, or RASQUAL. Use when mapping cis-regulatory genetic variants from heterozygous SNPs, separating cis from trans regulation, building chromatin QTL (caQTL) maps, validating GWAS variant function with allelic imbalance, or detecting reference allele mapping bias before downstream analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Annotate CLIP-seq peaks or crosslink sites to RNA features (5'UTR, CDS, 3'UTR, intron, splice junction, snoRNA, tRNA, ncRNA, repeat elements) with ChIPseeker, RCAS, RBP-Maps (Yeo splicing regulatory maps), and bedtools, applying feature-priority hierarchies, transcript-context resolution, and metagene aggregation. Use when characterizing where in transcripts an RBP binds, comparing peak distribution across regions, generating splicing-regulatory maps relative to alternative-splicing events, or distinguishing exonic vs intronic vs UTR binding.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Includes stakeholder interview frameworks and continuous reassessment. Run this BEFORE test-strategy or test-planning. Use when: "risk assessment," "risk matrix," "risk heatmap," "what could break," "critical paths," "failure modes," "where to focus testing." Not for: multi-quarter QA direction — use test-strategy. Not for: a single sprint/release test plan — use test-planning. Not for: hands-on session-based bug hunting — use exploratory-testing. Related: test-strategy, test-planning, release-readiness, qa-metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and manages project roadmaps with milestones and PRD queues. Use after architecture is defined for project planning. Triggers on: create roadmap, plan milestones, organize prds.
日本語の概要は準備中です。原文の説明を表示しています。
Map customer journeys from awareness to advocacy. Visualize touchpoints, identify drop-off points, analyze channel interactions, and optimize the end-to-end experience. Use when the user asks about customer journey, funnel mapping, touchpoint analysis, or experience optimization.
日本語の概要は準備中です。原文の説明を表示しています。
awareness-stage-mapper workflow skill. Use this skill when the user needs One sentence - what this skill does and when to invoke it and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
招聘与猎头 (招聘与猎头 (Recruiting & Executive Search) — 面向甲方招聘负责人/HR 与市场化猎头顾问「双侧视角」的『把一个模糊的用人需求，变成一个来得了、干得好、留得住的人』的判断体系；不是候选人一侧的求职与简历面经（那是 job-hunting-coach 的范围），也不是薪酬绩效/员工关系/组织发展的泛 HR 全模块，更不是劳动法条文解读。覆盖：(a) 第一性张力 —— 这行的核心世界观分歧：**需求诊断优先 ⇄ 快速供给优先**（用人经理提来的岗位需求几乎总是一张愿望清单，资深招聘先开 intake 会把『必须有』与『最好有』拆开、把画像逼成可证伪的成功标准；但按成单计酬的猎头把诊断时间压不进单价里，于是行业里同时存在『先诊断再搜寻』和『先扔简历再说』两种作业习惯）；**结构化面试 ⇄ 看人的直觉**（工业与组织心理学近一个世纪的效度元分析一致指向：结构化面试、工作样本、认知能力测验的预测效度明显高于非结构化面谈与经验年限，但一线用人经理绝大多数仍相信自己聊两句就能看准人——这是本行最大的知行落差，也是所有循证招聘流派的出发点；顺带一提，业内长期奉为圭臬的 Schmidt-Hunter 效度排序近年被重新校正，工作样本的效度被下调，这场修正本身就是本行必须如实呈现的争议）；**能力素质 ⇄ 文化匹配**（culture fit 既是最常被写在拒信里的理由，也是被批评得最凶的偏见外壳，Google 一派主张改口叫 culture add，看的是这个人补上了团队缺的东西，而不是像不像我们）；**主动寻访 sourcing ⇄ 被动投递漏斗**（高端与稀缺技能岗只有 outbound 人才地图一条路；量大岗位靠渠道效率、转化率与自动化，两条路的技能树几乎不重叠）；**人才地图是资产 ⇄ 人才地图是浪费**（保留制猎头把 mapping 当交付物的一部分，成功付费猎头认为地图做完单子已经黄了）；**保留制 retained ⇄ 成功付费 contingency**（按阶段预付、独家、深度地图 vs 多家赛马、入职才收钱、速度压倒深度；两种商业模式塑造出两种截然不同的作业节奏、候选人对待方式与职业道德边界，比如 off-limits 不挖回自己安置过的人）；**内部招聘团队 ⇄ 外部猎头与 RPO**（成本、速度、知识沉淀、雇主品牌归属谁的长期争论；embedded recruiter 是近年的折中）；**候选人体验 ⇄ 筛选效率**（漏斗越严体验越差，被拒者也是客户与口碑）；**AI 筛选的效率 ⇄ 合规与偏见**（简历解析、AI 面试评分、自动排序已在大规模使用，同时被监管盯上：纽约市 Local Law 144 要求自动化决策工具做偏见审计并公示、欧盟 AI 法案把招聘划为高风险场景、伊利诺伊州对 AI 视频面试单独立法；业内既离不开它，也在诉讼与审计里学做记录）；**offer 谈判的锚定 ⇄ 薪酬透明**（多地薪酬区间披露立法把谈判起点从『你现在多少』改成『这个岗位值多少』，问薪酬历史在不少法域已被禁止）；**counter-offer 该不该接**（猎头几乎一致反对，认为留下来的人多数一年内还是会走，但这条业内定论的证据基础本身也在被质疑）；**入职后早期流失算谁的**（保证期与退款条款把这场争论直接写进了合同）。(b) 工具栈 —— 申请人追踪系统 ATS（Greenhouse、Lever、Ashby、Workday Recruiting、SmartRecruiters、iCIMS、Taleo，中国侧 Moka、北森、大易、e成）、猎头 CRM 与交付系统（Bullhorn、Vincere、Loxo、Clockwork、Recruit CRM）、寻访与触达（LinkedIn Recruiter、SeekOut、hireEZ、Amazing Hiring、GitHub 与学术检索，中国侧 BOSS 直聘、猎聘、脉脉、拉勾、牛客）、评估与测评（HackerRank、CodeSignal、CoderPad、结构化面试题库与 scorecard 评分卡、Hogan、SHL、Predictive Index、Criteria、案例作业与工作样本）、面试调度与视频（GoodTime、Calendly、HireVue、Spark Hire）、背景调查与合规（HireRight、Checkr、Sterling，中国侧 i背调、八方锦程，以及个人信息保护法与 GDPR 下的授权链、FCRA 的不利行动通知）、数据与漏斗分析（time to fill 与 time to hire 的口径差异、offer 接受率、通过率与转化漏斗、quality of hire 的度量困境、招聘成本 cost per hire 的口径战争）、以及最被低估的纸笔工具（intake 提纲、成功标准清单、scorecard、人才地图表格、Boolean 检索式、一页纸的岗位价值主张）—— 选型的真正分岔从来不是功能清单，而是『你的岗位是靠触达赢还是靠转化赢』。(c) 心智模型层 —— 招聘是一次双向销售而不是一场考试；岗位画像要写成结果（这个人半年内要做成什么）而不是资历清单；信号与噪音（公司名与学历是弱信号，工作样本与具体行为证据是强信号）；结构化与评分卡的意义在于让判断可比而不是显得严谨；漏斗每一层都在丢人，所以要从入职倒推触达量；稀缺人才不看招聘广告，只在熟人与私域里流动；offer 是谈判也是承诺，谈崩与反悔的代价高度不对称；招聘的质量要到入职之后才结算。(d) 工作流 —— intake 需求诊断会、岗位画像与成功标准、渠道策略与人才地图 mapping、Boolean 与主动触达、简历筛选与电话初筛、结构化面试与 debrief 定校准、工作样本与技术评估、reference check 与背调、offer 设计与谈判、counter-offer 应对、入职前 no-show 防范与 pre-boarding、试用期与早期留存复盘、招聘漏斗与数据复盘、以及岗位关闭或撤销时的收尾。(e) 表达 DNA、质量基准（什么算一次好的招聘）、反模式（外行与新手最容易犯的错：照抄 JD、面试问脑筋急转弯、用薪酬历史锚定、把候选人当库存、背调走过场、offer 口头承诺）、智识谱系（工业与组织心理学的效度学派、循证与结构化招聘派、保留制高管寻访派、增长型 sourcing 与招聘运营派、雇主品牌与候选人体验派、中国互联网大厂的人才盘点与赛马派）。) Master OS — automated mastery of 招聘与猎头 (Recruiting & Executive Search) — 面向甲方招聘负责人/HR 与市场化猎头顾问「双侧视角」的『把一个模糊的用人需求，变成一个来得了、干得好、留得住的人』的判断体系；不是候选人一侧的求职与简历面经（那是 job-hunting-coach 的范围），也不是薪酬绩效/员工关系/组织发展的泛 HR 全模块，更不是劳动法条文解读。覆盖：(a) 第一性张力 —— 这行的核心世界观分歧：**需求诊断优先 ⇄ 快速供给优先**（用人经理提来的岗位需求几乎总是一张愿望清单，资深招聘先开 intake 会把『必须有』与『最好有』拆开、把画像逼成可证伪的成功标准；但按成单计酬的猎头把诊断时间压不进单价里，于是行业里同时存在『先诊断再搜寻』和『先扔简历再说』两种作业习惯）；**结构化面试 ⇄ 看人的直觉**（工业与组织心理学近一个世纪的效度元分析一致指向：结构化面试、工作样本、认知能力测验的预测效度明显高于非结构化面谈与经验年限，但一线用人经理绝大多数仍相信自己聊两句就能看准人——这是本行最大的知行落差，也是所有循证招聘流派的出发点；顺带一提，业内长期奉为圭臬的 Schmidt-Hunter 效度排序近年被重新校正，工作样本的效度被下调，这场修正本身就是本行必须如实呈现的争议）；**能力素质 ⇄ 文化匹配**（culture fit 既是最常被写在拒信里的理由，也是被批评得最凶的偏见外壳，Google 一派主张改口叫 culture add，看的是这个人补上了团队缺的东西，而不是像不像我们）；**主动寻访 sourcing ⇄ 被动投递漏斗**（高端与稀缺技能岗只有 outbound 人才地图一条路；量大岗位靠渠道效率、转化率与自动化，两条路的技能树几乎不重叠）；**人才地图是资产 ⇄ 人才地图是浪费**（保留制猎头把 mapping 当交付物的一部分，成功付费猎头认为地图做完单子已经黄了）；**保留制 retained ⇄ 成功付费 contingency**（按阶段预付、独家、深度地图 vs 多家赛马、入职才收钱、速度压倒深度；两种商业模式塑造出两种截然不同的作业节奏、候选人对待方式与职业道德边界，比如 off-limits 不挖回自己安置过的人）；**内部招聘团队 ⇄ 外部猎头与 RPO**（成本、速度、知识沉淀、雇主品牌归属谁的长期争论；embedded recruiter 是近年的折中）；**候选人体验 ⇄ 筛选效率**（漏斗越严体验越差，被拒者也是客户与口碑）；**AI 筛选的效率 ⇄ 合规与偏见**（简历解析、AI 面试评分、自动排序已在大规模使用，同时被监管盯上：纽约市 Local Law 144 要求自动化决策工具做偏见审计并公示、欧盟 AI 法案把招聘划为高风险场景、伊利诺伊州对 AI 视频面试单独立法；业内既离不开它，也在诉讼与审计里学做记录）；**offer 谈判的锚定 ⇄ 薪酬透明**（多地
日本語の概要は準備中です。原文の説明を表示しています。