2,210 件 ・ 関連度順
概要と使いどころ
Backend specification planning frameworks. Use when a spec touches API endpoints, database schema, middleware, or auth. Covers endpoint contracts with request/response shapes, error catalogs, auth per endpoint, schema design with constraints and indexes, migration strategy, and middleware pipeline ordering.
日本語の概要は準備中です。原文の説明を表示しています。
Broad, pre-curation evidence reconnaissance for a declared Gaia skill, intake batch, upstream repository, or proposed generic capability. Run before choosing a discovery strategy or mapping topology, to give the curator independent research leads and counterevidence. Context only: never scores, grades, ratifies, ingests, or mutates the registry. Later ev-discovery and ev-pipeline phases validate/promote any selected leads.
日本語の概要は準備中です。原文の説明を表示しています。
Profiling strategy for audio CPU issues — xruns, spikes, and buffer underruns. Use when the user reports CPU overload, audio glitches under load, or performance regressions. Trigger on phrases like "I'm getting xruns", "my plugin causes CPU spikes", "dropouts under high voice count", "audio thread is too slow", "how do I profile my DSP". References audio-numerics-review for denormal slowdown and audio-dsp-review for lock contention.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
日本語の概要は準備中です。原文の説明を表示しています。
Create a complete feature module with folder structure, Assembly Definition (.asmdef), test assembly, and namespace. Use when adding a new feature, system, or module to a Unity project. Triggers on requests like "create a new feature", "scaffold a module", "add a combat system", "I need a health system", "set up inventory", "create a new module for X", "add a new system", "new feature folder", or any task requiring new folders, assemblies, or namespaces for a gameplay feature — even when the user just names a system they want to build from scratch. Reads ProjectConfig.yaml for folder_strategy and MCP availability.
日本語の概要は準備中です。原文の説明を表示しています。
用于规划或审查前端测试策略，按风险选择正确测试层级，将覆盖映射到静态检查、单元测试、组件测试、集成测试、E2E、Storybook/视觉回归、a11y、安全、性能或 CI gates。不要用于编写单个组件/E2E 测试或只是运行现有验证命令；中文触发词包括 测试策略、测试分层、测试计划、覆盖矩阵。
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing, implementing, or reviewing browser storage such as localStorage, sessionStorage, IndexedDB, cookies, client persistence, offline data, secure storage, or cleanup strategy; Chinese triggers include browser storage, client persistence.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end SEO operations for B2B SaaS organic visibility. Use this skill when you need keyword research, technical SEO audits, content optimization, link building strategy, international expansion, AI/AEO optimization, schema markup, Core Web Vitals improvements, and organic traffic growth planning. Also triggers on: SEO, keyword research, can we rank for this keyword, which keywords are actually worth it, qualify these keywords, check the SERPs, keyword shortlist, too many keywords, technical SEO, link building, content optimization, international SEO, hreflang, x-default, multilingual site, translated pages not ranking, our German site gets no traffic, language switcher, auto-redirect by country, machine translation SEO, content parity, ccTLD vs subfolder, AI search, AEO, GEO, Core Web Vitals, schema markup, organic traffic, G2 listing, Capterra, TrustRadius, review-platform category page, best software roundup, listicle placement, directory submissions, do we need a Google Business Profile in [country], local SEO with no office, Google Business Profile eligibility, virtual office address SEO, coworking address business profile, business profile suspended, NAP consistency, local citations for SaaS, LocalBusiness schema, server log analysis, log file analysis, what is Googlebot crawling, is Googlebot hitting errors, verify Googlebot, fake Googlebot, crawl budget, do we have a crawl budget problem, Crawl Stats report, new pages not getting crawled.
日本語の概要は準備中です。原文の説明を表示しています。
Email marketing operations and automation for B2B SaaS. Use this skill for newsletter strategy, email automation sequences, lifecycle campaigns, nurture workflows, onboarding sequences, deliverability optimization, email copywriting, lead scoring, marketing automation platform setup, and cold-email sending infrastructure — secondary sending domains, SPF/DKIM/DMARC, and domain warmup — plus the contact budget: a cross-channel frequency cap across every sender (marketing, sales sequences, customer success, in-app). Also triggers on: email, newsletter, drip campaign, lifecycle, nurture, onboarding sequence, deliverability, email automation, lead scoring, marketing automation, our emails are going to spam, SPF, DKIM, DMARC, sender reputation, sending domain, cold email domains, domain warmup, mailbox setup, blacklist, bounce rate, BIMI, brand logo in inbox, VMC, Verified Mark Certificate, Common Mark Certificate, transactional email, password reset emails going to spam, frequency cap, email fatigue, customers get too many emails, too many messages, sales and marketing both emailing the same person, communication limits, send frequency safeguard, global frequency capping, quiet period, message precedence.
日本語の概要は準備中です。原文の説明を表示しています。
Field marketing, events, and webinars for B2B SaaS. Use this skill for conference and sponsorship selection, booth strategy, owned events and roadshows, executive dinners, the webinar program, and event-sourced pipeline measurement. Also triggers on: field marketing, events, conference, trade show, booth, sponsorship, roadshow, executive dinner, webinar, webinar follow-up, webinar lead handoff, event ROI, event pipeline, user conference, meetups.
日本語の概要は準備中です。原文の説明を表示しています。
Master orchestrator for B2B SaaS marketing campaigns using the CATALYST framework (Coordinated Agents for Targeted, Analytics-Led, Year-round SaaS Transformation). Coordinates 90 specialist agents across 17 marketing disciplines. Use this skill for ANY large-scale marketing initiative: full GTM launches, annual marketing plans, multi-channel campaigns, quarterly planning, or any task requiring coordination across content, SEO, paid media, social, email, design, sales enablement, product marketing, analytics, project management, and client operations. Also triggers on: marketing strategy, campaign plan, GTM launch, quarterly plan, marketing ops, full-funnel campaign, marketing audit, growth plan.
日本語の概要は準備中です。原文の説明を表示しています。
Public relations, corporate communications, and analyst relations for B2B SaaS. Use this skill for earned media and press strategy, announcements and press releases, executive and crisis communications, media relationships and briefings, and the Gartner/Forrester/IDC analyst program including Magic Quadrant and Wave evaluation submissions. Also triggers on: PR, public relations, press release, earned media, media relations, journalist, embargo, announcement, crisis comms, corporate communications, analyst relations, AR, Gartner, Forrester, IDC, Magic Quadrant, Forrester Wave, analyst briefing, inquiry, newsjacking, rapid response, should we comment on this news story, expert commentary, reactive comment, source request, Qwoted, is this newsworthy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Data Warehousing Specialist — defining the grain of a fact table before modeling it, choosing a slowly changing dimension (SCD) type for a dimension attribute, designing an incremental ETL/ELT load strategy against a full-refresh alternative, resolving a conformed-dimension conflict across source systems, or diagnosing why a BI report's numbers don't reconcile to the source system.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Database Architect — choosing a normalization level matched to the actual workload, resolving a CAP theorem tradeoff (consistency vs. availability) for a distributed data store, selecting a sharding/partition key aligned with the dominant query pattern, validating an indexing strategy against real query plans, or deriving RPO/RTO backup and replication requirements from actual business impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Computer and Information Systems Manager (IT Manager/Director/CIO-adjacent) — planning IT infrastructure and systems strategy, evaluating a technology vendor or platform decision, allocating an IT budget, or managing IT risk (security, uptime, technical debt) at an organizational level. Broader than the devops-sre or software-engineer roles — this one owns IT as a business function, not a specific engineering discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a board-certified cardiologist — triaging chest pain with a risk score, titrating heart-failure guideline-directed medical therapy, deciding revascularization strategy for stable or acute coronary disease, or working through anticoagulation decisions in atrial fibrillation. US practice default (ACC/AHA guideline framework). A reasoning aid, not medical advice.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a CEO/chief executive — setting company strategy, allocating scarce resources (capital, headcount, attention) across competing priorities, making a call that only the top of the org can make, or communicating direction to the board, investors, or the whole company.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs. civil penalty vs. certificate action), auditing a Safety Management System for a functioning safety-assurance loop rather than paperwork completeness, scoping a records-sampling strategy across a fleet under surveillance, or deciding whether to ground an aircraft pending an AD compliance finding.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Biochemist — determining enzyme kinetics (Km/Vmax, inhibition mechanism) from rate data, choosing a structural-biology method (X-ray crystallography, cryo-EM, or NMR) for a target, designing or interpreting a binding assay (ITC, SPR, fluorescence polarization), or selecting a protein-purification strategy and diagnosing why a prep failed.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Biofuels/Biodiesel Technology and Product Development Manager — deciding whether a lab/bench-scale process is ready to scale up, evaluating feedstock flexibility tradeoffs in process design, pricing a technology's value against regulatory credit pathways (RFS RIN, LCFS CI score), or managing IP strategy for a novel conversion process. Distinct from biofuels-production-manager, which runs an existing operating facility — this role owns R&D and commercialization of new or improved process technology.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a board-certified anesthesiologist — building a preoperative anesthesia plan and risk stratification, choosing general vs. regional technique and airway strategy, managing an intraoperative crisis (difficult airway, malignant hyperthermia, local anesthetic systemic toxicity), or writing a PACU handoff and postoperative pain-management order set.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Anthropologist/Archeologist working in cultural resource management (CRM) — scoping a Section 106 Phase I identification survey, designing a shovel-test-pit sampling strategy, evaluating National Register of Historic Places eligibility under Criteria A-D, interpreting excavation stratigraphy via a Harris matrix and radiocarbon results, or running the ethnographic field-methods branch (participant observation, informant interviewing) for a cultural-anthropology component of a project.
日本語の概要は準備中です。原文の説明を表示しています。
Playwright-first strategy for shared DB + shared test accounts. Use when E2E tests collide in QA/staging, need safe parallelism, or require deterministic cleanup without touching baseline data. Covers per-test ownership, namespacing, ID-based teardown, serial shared-state suites, and optional stale-data janitor jobs.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute integrative analysis combining multiple ENCODE experiments for cross-dataset or multi-omic workflows. Use when the user wants to combine experiments, perform cross-dataset comparison, multi-omic integration, peak overlap analysis, differential binding, signal correlation, chromatin state segmentation, enhancer-gene linkage, or any analysis that requires merging or comparing data from two or more ENCODE experiments. Covers same-assay cross-sample, multi-omic same-sample, cross-organism, and perturbation integration designs. Guides compatibility checks, batch effect detection, normalization, integration strategy selection, and provenance documentation.
日本語の概要は準備中です。原文の説明を表示しています。