7,879 件 ・ 関連度順
概要と使いどころ
Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.
日本語の概要は準備中です。原文の説明を表示しています。
Redistricting analysis in R using the redistverse ecosystem. Use whenever the user is working with redist, redistmetrics, ggredist, geomander, adj, alarmdata, PL94171, censable, easycensus, tinytiger, baf, rict, or redistio. Covers the complete pipeline: Census and spatial data loading, adjacency graph construction, SMC/MCMC simulation, constraints (population balance, county splits, VRA compliance), convergence diagnostics, plan metrics (compactness, partisan fairness, splits), visualization, summary tables, and interactive plan drawing. Invoke whenever the user mentions redistricting, gerrymandering, district plans, simulation ensembles, or any redistverse package by name.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.".
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging with root cause investigation. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Technology Acceptance Model (Davis, 1989) and Unified Theory of Acceptance and Use of Technology (Venkatesh et al., 2003) to predict technology adoption. Use this skill when the user needs to evaluate user acceptance of a new system, diagnose adoption barriers, design interventions to improve technology uptake, or when they ask 'why aren't users adopting this', 'what drives technology acceptance', or 'how do we increase adoption rates'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Grounded Theory (Glaser and Strauss) to build theory inductively from qualitative data through open, axial, and selective coding. Use this skill when the user needs to develop new theory from data rather than test existing hypotheses, conduct theoretical sampling and constant comparison, determine when theoretical saturation is reached, or when they ask 'what theory explains this phenomenon', 'how do I code qualitative data systematically', or 'when do I stop collecting data'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply mechanism design (reverse game theory) to engineer incentive-compatible rules for allocation problems. Use this skill when the user needs to design auctions, voting systems, or matching markets, or when evaluating whether a proposed mechanism satisfies incentive compatibility and individual rationality constraints.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply flow theory to diagnose optimal experience conditions and design environments that balance challenge and skill for sustained engagement. Use this skill when the user needs to explain why users disengage from tasks, optimize task difficulty for peak performance, design learning progressions or gamification systems, or when they ask 'why do people lose focus', 'how to design for engagement', or 'what conditions produce peak performance'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Habitual Domain (HD) theory by Taiwanese scholar P.L. Yu (游伯龍, 1977) — integrates four domains (potential/actual/reachable/activated), eight general hypotheses, seven-layer decision structure, and nine HD-expansion tools to analyze decision blind spots, break cognitive inertia, and support cross-domain integration. Use for diagnosing why alternatives are invisible, decision paralysis, breaking cognitive frames, or explaining perception gaps between people. Triggers: 『思維框架』『打破盲點』『創新思考』『決策盲區』『跨域整合』『游伯龍』『習慣領域』『HD 理論』『七層決策』『四領域』『八大通性』『P.L. Yu』. Especially for NYCU EMBA HD course, 政大科管所, 中山企管系 decision-analysis/innovation/leadership courses. Taiwan-origin theory cited in J. Optimization Theory, Theory & Decision, Human Systems Management.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Capital Asset Pricing Model (CAPM) to estimate expected returns and assess risk-return tradeoffs. Use this skill when the user needs to calculate expected return on an asset, interpret beta as systematic risk exposure, evaluate whether an investment compensates for risk, or when they ask 'what return should I expect', 'what is the risk premium', or 'how does beta affect pricing'.".
日本語の概要は準備中です。原文の説明を表示しています。
Build accessible UI—semantic HTML, keyboard support, ARIA when needed, WCAG-oriented checks. Use when implementing or reviewing web UI, forms, modals, and design systems.
日本語の概要は準備中です。原文の説明を表示しています。
Triage and address GitHub PR review comments systematically—classify, respond, fix or defer with rationale. Use when a PR has review feedback, requested changes, or unresolved threads.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply behavioral finance theory to identify systematic investor biases and their impact on asset prices. Use this skill when the user needs to analyze irrational market behavior, explain pricing anomalies through cognitive biases, diagnose investor decision errors, or when they ask 'why do investors hold losers too long', 'how does loss aversion affect pricing', or 'what biases drive this market pattern'.".
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. Use when building landing pages, portfolios, redesigns, or frontend interfaces that need strong visual taste.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Theory of Constraints (TOC) to identify and manage system bottlenecks. Use this skill when the user needs to find what limits throughput, optimize a constrained process, apply the Five Focusing Steps, or implement Drum-Buffer-Rope scheduling — even if they say 'our output is stuck', 'what's the bottleneck', or 'why can't we produce more'.".
日本語の概要は準備中です。原文の説明を表示しています。
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
日本語の概要は準備中です。原文の説明を表示しています。
"Measure social media influence using engagement-weighted metrics beyond follower count. Use this skill when the user needs to evaluate influencer effectiveness, compare influence across accounts, or build an influence scoring system — even if they say 'who is more influential', 'influencer ranking', or 'measure social impact'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Customer relationship management strategy — integrated framework with six pillars: customer segmentation (RFM/CLV), journey orchestration (cross-channel), CDP technology stack, loyalty-program design, B2B key-account management (KAM), and CRM organization/governance. Use for VIP program design, membership-system decision, retail/ecommerce/B2B customer strategy, CDP buy-vs-build, marketing-automation adoption, or key-customer churn. Triggers: 『CRM 系統』『會員經營』『客戶分級』『大客戶策略』『CDP』『行銷自動化』『客戶生命週期』『VIP 方案』『顧客忠誠』『RFM』『CLV』『KAM』『Journey Orchestration』. For 師大 EMBA CRM, 政大 ecommerce, 中山 marketing cases. Complements Asgard `biz-cac-ltv` (tactics) and `biz-customer-journey` (single method) with the strategic integration layer.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement a web crawler pipeline covering URL discovery, fetching, parsing, and storage. Use this skill when the user needs to build a site crawler, audit website structure, or collect web data systematically — even if they say 'scrape a website', 'crawl all pages', or 'site audit spider'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Enterprise risk management (ERM) framework layer — integrates COSO ERM 2017 (five components, 20 principles), ISO 31000, three-lines model, risk appetite, risk heatmap, and key risk indicators (KRI) into a complete governance playbook covering structure through culture. Use for ERM implementation, risk-system build, risk mapping, risk-appetite statement drafting, three-lines setup, CRO role design, or Taiwan FSC corporate-governance evaluation response. Triggers: 『ERM 導入』『風險管理框架』『COSO』『風險地圖』『風險胃納』『KRI』『CRO 職責』『三道防線』『風險委員會』『ISO 31000』『風險熱圖』『風險治理』. For 師大／政大／陽交 EMBA risk-management/governance/audit cases. Complements Asgard `algo-risk-*` (Altman Z, Benford, credit, VaR) with the framework/governance layer. 獨董挑選/董事會組成/IPO 治理: use `biz-corporate-governance`.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement PageRank algorithm to compute web page importance scores using the random surfer model. Use this skill when the user needs to rank pages by link authority, build a simplified search ranking system, or understand how link structure determines page importance — even if they say 'which pages are most important', 'link analysis', or 'page authority score'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Design hybrid recommendation systems combining multiple strategies for improved accuracy. Use this skill when the user needs to overcome single-method limitations, combine collaborative and content-based filtering, or build a production recommendation pipeline — even if they say 'combine recommendation approaches', 'best recommendation architecture', or 'cold start plus personalization'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Design and analyze factorial experiments to identify significant process factors and optimize settings. Use this skill when the user needs to systematically test factor effects, optimize a manufacturing process, or determine which variables matter most — even if they say 'which factors affect quality', 'optimize process settings', or 'design an experiment'.".
日本語の概要は準備中です。原文の説明を表示しています。