2,346 件 ・ 関連度順
概要と使いどころ
Drafts a combined Audit and Compensation Committee charter for U.S. boards, tailored for public or private companies with listing-standard compliance, independence criteria, and SOX readiness. Triggers when the user needs a board committee charter, audit committee charter, compensation committee charter, or governance mandate for SEC/NYSE/NASDAQ compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts an Appellee's Response Brief defending the trial court's judgment and arguing for affirmance. Covers standard of review analysis, record-based rebuttal, authority distinction, and procedural compliance. Trigger when drafting appellee briefs, response briefs, answering briefs, or defending trial court judgments on appeal.
日本語の概要は準備中です。原文の説明を表示しています。
Generates structured analytical summaries of appellate documents covering procedural posture, issues on appeal, standards of review, and strategic assessment. Use when onboarding to an appeal, preparing for oral argument, evaluating appellate risk, or summarizing the appellate record.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts the appellant's opening brief challenging a lower court decision in federal or state appellate courts. Covers issue selection, standard of review framing, record citation, argument structure, and procedural compliance under FRAP 28/32 or state equivalents. Use when preparing an appellant's opening brief, selecting appellate issues, structuring appellate arguments, or demonstrating reversible error on appeal.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts appellee response briefs for federal and state appellate courts, exploiting standards of review and record evidence to defend trial court decisions. Trigger when the user needs to respond to an appellant's opening brief or defend a favorable lower court ruling on appeal.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts an Adverse Event Reporting Policy compliant with 21 CFR 312.32 (IND safety reporting), 21 CFR 314.80 (postmarketing), and ICH E2A, with multi-jurisdictional overlays (EMA, PMDA, Health Canada). Covers seriousness/causality frameworks, expedited reporting timelines, roles, documentation standards, training mandates, and QA mechanisms. Use when drafting or updating an adverse event reporting policy, pharmacovigilance policy, AE/SAE reporting SOP, or safety reporting framework for a pharmaceutical company, CRO, biotech, or clinical research institution.
日本語の概要は準備中です。原文の説明を表示しています。
欧盟 AI 法案知识引擎——以 70 份官方欧盟来源文件为基础的权威监管问答（包括 2026 年委员会关于 Art. 6 高风险分类的指南草稿——一般原则、附件 I、附件 III）。基于完整条例文本、委员会指南、EDPB/EDPS 意见、《实践守则》、协调标准、FRIA 指南、事件模板和行业特定指引，以条款级引用回答关于 AI 法案的任何问题。当用户询问"EU AI Act"、"AI Act regulation"、"Regulation 2024/1689"、"KI-Verordnung"、要求"explain an AI Act article"、"what does Article X say"、"AI Act requirements"、"AI Act penalties"、"AI Act timeline"、"GPAI obligations"、"high-risk AI"、"prohibited AI practices"、"AI Act and GDPR"、"fundamental rights impact assessment"、"AI Act standards"、"AI Act national implementation"、"AI literacy"、"serious incident reporting"、"Digital Omnibus"、"AI regulatory sandbox"，或任何关于欧盟人工智能监管的问题时，应使用本技能。德语术语同样触发："KI-Gesetz"、"KI-Verordnung"、"Hochrisiko-KI"、"KI-Kompetenz"、"Grundrechte-Folgenabschaetzung"、"GPAI-Verhaltenskodex"。对于产出分类决定而非知识答案的评估工作流，提议在会话内运行结构化风险等级分类。
日本語の概要は準備中です。原文の説明を表示しています。
Deep multi-source technical research with citations — tech evaluation, ecosystem/standards comparison. NOT for API docs (mk:docs-finder), codebase discovery (mk:scout), or project Q&A (mk:ask-me).
日本語の概要は準備中です。原文の説明を表示しています。
Systematically QA-tests a web app and fixes bugs: test, then iteratively fix, re-verify, commit each fix. Tiers: Quick, Standard, Exhaustive. Produces before/after health scores and fix evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Implementing features or writing code. TDD is opt-in via --tdd / MEOWKIT_TDD=1. Provides code patterns, skill loading, and coding standards.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a decision needs deep multi-source technical research with cited evidence — technology evaluation, ecosystem comparison, standards/spec fact-finding, "how do others solve X". Triggers on "research X", "deep dive on X", "evaluate X vs Y", "find best practices for X". NOT for library/API doc lookup (see mk:docs-finder); NOT for one-shot URL fetch (see mk:web-to-markdown); NOT for internal codebase discovery (see mk:scout); NOT for project-only Q&A (see mk:ask-me); NOT for comparing solution designs (see mk:brainstorming); NOT for root-cause debugging (see mk:investigate); NOT for wiki ingestion of sources (see mk:wiki-research).
日本語の概要は準備中です。原文の説明を表示しています。
Enforces KISS/DRY/YAGNI during authoring and ad-hoc quality reviews. Pragmatic standards: concise, direct, no unnecessary comments. NOT for post-hoc diff/PR review (see mk:review); NOT for behavior-preserving simplification passes (see mk:simplify).
日本語の概要は準備中です。原文の説明を表示しています。
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
日本語の概要は準備中です。原文の説明を表示しています。
Type-safe TypeScript patterns from industry standards
日本語の概要は準備中です。原文の説明を表示しています。
Go backend patterns from Uber style and standard layout
日本語の概要は準備中です。原文の説明を表示しています。
Create, standardize, or update step-by-step algorithm visualizations for a given problem ID. Use when the user mentions 'visual', 'visualization', 'animate', or 'step-by-step' alongside a problem ID in /problem/:id format.
日本語の概要は準備中です。原文の説明を表示しています。
Core statistical methodology and pedagogical approach for all Inquiro analyses. Always loaded to maintain teaching quality and reproducibility standards.
日本語の概要は準備中です。原文の説明を表示しています。
Save important context to persistent memory for future sessions. PROACTIVELY USE THIS when you detect: - Decisions: "let's go with", "decided to", "chose", "went with" - Learnings: "I learned", "turns out", "TIL", "realized", "discovered" - Errors resolved: "fixed", "the problem was", "solution was" - Client info: names, emails, phone numbers, addresses, invoice amounts - Preferences: "I prefer", "I like", "don't like", "always use" - References: API keys locations, file paths, URLs, credentials - Patterns: "pattern", "convention", "always do", "standard approach" - Important commands run worth remembering Do NOT ask permission - just capture silently when these patterns appear.
日本語の概要は準備中です。原文の説明を表示しています。
Implementing the `Idempotency-Key` HTTP header pattern (Stripe-pioneered, IETF-standardizing) so retries don't double-charge or duplicate side effects — full Postgres schema with recovery-point state machine, fingerprint check, in-progress lock with 409 response, and 24h retention. Grounded in Stripe blog/docs, the IETF httpapi WG draft, and Brandur Leach's canonical implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Expert interior designer with deep knowledge of space planning, color theory (Munsell, NCS), lighting design (IES standards), furniture proportions, and AI-assisted visualization. Use for room layout optimization, lighting calculations, color palette selection for interiors, furniture placement, style consultation. Activate on "interior design", "room layout", "lighting design", "furniture placement", "space planning", "Munsell color". NOT for exterior/landscape design, architectural structure, web/UI design (use web-design-expert), brand color theory (use color-theory-palette-harmony-expert), or building codes/permits.
日本語の概要は準備中です。原文の説明を表示しています。
Framework for coordinating meaning across autonomous agents that use different conceptual models, vocabularies, and knowledge representations. Treats ontologies as first-class negotiable resources rather than hardcoded implementation details.
日本語の概要は準備中です。原文の説明を表示しています。
State-of-the-art data visualization for React/Next.js/TypeScript with Tailwind CSS. Creates compelling, tested, and accessible visualizations following Tufte principles and NYT Graphics standards. Activate on "data viz", "chart", "graph", "visualization", "dashboard", "plot", "Recharts", "Nivo", "D3". NOT for static images, print graphics, or basic HTML tables.
日本語の概要は準備中です。原文の説明を表示しています。
Validates agent outputs against expected schemas and quality criteria. Ensures outputs meet structural requirements and content standards. Activate on 'validate output', 'output validation', 'schema validation', 'check output', 'output quality'. NOT for confidence scoring (use dag-confidence-scorer) or hallucination detection (use dag-hallucination-detector).
日本語の概要は準備中です。原文の説明を表示しています。