1,498 件 ・ 関連度順
概要と使いどころ
Minimalist UX/Interaction Audit Expert that deconstructs complex interactions through cognitive load and operational efficiency lenses. Use this skill when you need to perform a UX walkthrough audit on a Figma prototype or web interface, evaluating usability based on principles like fewer clicks, less UI elements, no hidden logic, and self-explanatory design.
日本語の概要は準備中です。原文の説明を表示しています。
Review generated or changed WooCommerce code — extensions, payment and shipping integrations, checkout customizations, and order/product logic — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WooCommerce APIs: wc_get_order, wc_get_orders, wc_get_product, WC() cart or session, woocommerce_* hooks, Store API endpoints, payment gateways, order or product meta, HPOS, subscriptions, or bookings. Use on 'review this Woo plugin', 'is this HPOS compatible', or after tasks like 'write a WooCommerce extension', 'add a checkout field', 'hook into the order flow', or 'update stock'. Enforces HPOS-safe order access, CRUD over direct meta, feature-compatibility declarations, server-side checkout validation, money-handling discipline, and hooks over template overrides. DO NOT USE for WordPress code without WooCommerce APIs (use wp-guard), generic code review (use clean-code-guard), test review (use test-guard), or store configuration and admin-screen questions.
日本語の概要は準備中です。原文の説明を表示しています。
Review generated or changed WordPress code — plugins, themes, and blocks — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WordPress APIs: add_action/add_filter, shortcodes, meta boxes, AJAX handlers, REST routes, WP_Query or $wpdb, widgets, or WP-CLI commands. Use on 'review this plugin', 'is this safe to ship', 'make this translatable', 'speed up this query', or after tasks like 'write a plugin' or 'add an endpoint/shortcode/meta box'. Enforces escaping and sanitization, nonces plus capability checks, prepared database queries, core-API-first development, translation-ready strings, and query/caching discipline. DO NOT USE for WooCommerce-specific order, product, or checkout logic (use woo-guard), non-WordPress PHP, generic code quality review (use clean-code-guard), test code review (use test-guard), server or hosting configuration, or conceptual WordPress questions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding whether an anthropology project fits American Anthropologist (AA) and which section to target. AA is the four-field AAA flagship, so the test is significance across anthropology (sociocultural, archaeology, biological, linguistic), not single-subfield novelty. Helps frame the question and pick a section; it does not collect data or conduct fieldwork.
日本語の概要は準備中です。原文の説明を表示しています。
Use when targeting Global Change Biology or deciding whether a biology/ecology manuscript fits this venue. Encodes the journal's fit, the global-change-driver framing and biological-evidence bar, scale and mechanism expectations, house style, official-submission re-check, and desk-reject heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when targeting the Journal of Cleaner Production or deciding whether a cleaner-production/sustainability manuscript fits this venue. Encodes the journal's fit, the cleaner-production contribution and methodological-transparency bar, LCA/system-boundary expectations, house style, official-submission re-check, and desk-reject heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when targeting Forest Ecology and Management or deciding whether a forest-science manuscript fits this venue. Encodes the journal's fit, the ecological-evidence-with-management-relevance bar, silviculture and disturbance expectations, Elsevier house style, official-submission re-check, and desk-reject heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning an American Anthropologist (AA) manuscript against the literature so it reads as a four-field contribution. AA readers span sociocultural, archaeology, biological, and linguistic anthropology, so the paper must engage the conversations they expect and decenter a US/Anglophone-only canon. Stakes the contribution and citational politics; it does not write the lit review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting or navigating any American Anthropologist (AA) manuscript as the entry point. Routes to the right AA sub-skill based on lifecycle stage, subfield (sociocultural, archaeology, biological, linguistic), and section type (Research Article, Vital Topics Forum, World/Public/Multimodal Anthropologies, Review Essay). It dispatches; it does not draft content.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defending the research design of an American Anthropologist (AA) manuscript — fieldwork and participant observation, interview and archival design for ethnographic/qualitative work, material/contextual analysis for archaeology, and appropriate lab/quantitative design for biological anthropology. AA judges each mode on its own terms with reflexivity. Strengthens the design; it does not write code or run fieldwork.
日本語の概要は準備中です。原文の説明を表示しています。
Use when targeting Agricultural and Forest Meteorology or deciding whether a land–atmosphere manuscript fits this venue. Encodes the journal's fit, the land–atmosphere-process and flux-measurement bar, micrometeorological evidence expectations, Elsevier house style, official-submission re-check, and desk-reject heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building the theoretical engine for an Administrative Science Quarterly (ASQ) manuscript — mechanisms, process vs. variance logic, constructs, and boundary conditions. Builds the argument; it does not select methods or run analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing the study for an Accounting, Organizations and Society (AOS) manuscript — qualitative field studies (access, case logic, interviews, observation), behavioral experiments, surveys, historical/archival inquiry, or theory-laden archival designs, each with the ethics and site-anonymity groundwork done early. Designs the inquiry; it does not run the coding or estimation (aos-data-analysis).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building the theoretical engine of an Accounting, Organizations and Society (AOS) manuscript — choosing a social/organizational theory tradition (institutional theory, governmentality, Bourdieu, actor-network theory, practice theory, psychological process theory) and making it generate the analysis rather than decorate it. Builds the lens; it does not collect data (aos-methods) or frame the contribution (aos-contribution-framing).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building the actual theory for an Academy of Management Review (AMR) manuscript — turning a positioned puzzle into defined constructs, explicit relationships, propositions, and boundary conditions. Constructs the theory; it does NOT stress-test the argument's logic (that is amr-data-analysis) or design any data collection (AMR has none).
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to understand the Academy of Management Review (AMR) developmental, multi-round review and interpret a decision letter focused on theoretical novelty and logical soundness. Explains the process and decision types; it does NOT draft the response document (that is amr-rebuttal).
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing and applying a theory-construction method for an Academy of Management Review (AMR) manuscript — building constructs, defining their domain, specifying relationships, articulating the underlying logic/mechanisms, and setting boundary conditions. This is the THEORY-CONSTRUCTION craft, NOT empirical method; AMR publishes no datasets, no measures, and no statistical tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when polishing the prose and structure of an Academy of Management Review (AMR) manuscript to AOM house style and an argument-driven voice. Late-stage polish; it does NOT build theory or check logic — do those first with amr-theory-development and amr-data-analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when articulating and differentiating the theoretical contribution of an Academy of Management Review (AMR) manuscript — showing precisely what is NEW versus prior theory and why it matters. Frames the contribution; it does NOT build the theory (amr-theory-development) or check its internal logic (amr-data-analysis).
日本語の概要は準備中です。原文の説明を表示しています。
Render a static iOS QWERTY keyboard as inline HTML+CSS sized for the 750-wide 9:16 stage. Includes the 3-suggestion bar, alpha keys, shift/backspace, 123/emoji/space/return row, and the bottom globe+mic strip. No animation logic — slide up/down is the molecule's job (CSS transform on the .keyboard root).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks to summarize, or asks why Simulink Coverage objectives are missing, unsatisfied, or uncovered on a coverage result they already have — why specific decision, condition, MCDC, relational-boundary, or saturation/overflow outcomes weren't exercised, whether uncovered logic is dead code, or how to close the gap (a test, a coverage filter, or a design change). It reads an existing cvdata, .cvt file, sim-with-coverage output, or Simulink Test result; it never runs cvsim to collect coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Reads, queries, and writes bigWig indexed binary signal tracks (coverage, fold-change, conservation, methylation-rate) with pyBigWig (Python) and the UCSC Kent tools (bedGraphToBigWig, bigWigToBedGraph, bigWigInfo, bigWigSummary, bigWigAverageOverBed) and deepTools (multiBigwigSummary, computeMatrix, bigwigCompare). Covers the central trap that a wide query returns a precomputed zoom-level summary (by default the mean, which annihilates narrow peaks) not per-base data, when exact=True/values() is mandatory, the NaN-not-zero gap-handling fork, choosing mean vs max vs sum vs coverage by biological question, and the sorted-bedGraph plus chrom.sizes build requirement. Use when extracting signal at regions, computing mean signal per gene/peak, building a browser track from bedGraph, comparing tracks, or building TSS/gene-body metaprofiles.
日本語の概要は準備中です。原文の説明を表示しています。
Assigns isolate identity at the right resolution for the question -- ANI/Mash species triage, 7-locus MLST historical comparability, cgMLST/wgMLST outbreak resolution (chewBBACA, BIGSdb, Ridom SeqSphere, EnteroBase HierCC), in-silico serotyping (SISTR/SeqSero2 Salmonella, SerotypeFinder E. coli, Kaptive Klebsiella, SeroBA pneumococcus, spa+SCCmec S. aureus), and lineage callers (TB-Profiler/Mykrobe barcode for MTBC, Pangolin + Nextclade for SARS-CoV-2, PopPUNK GPSC for S. pneumoniae). Use when typing bacterial isolates for surveillance or outbreak investigation, choosing between cgMLST allele distance and core-SNP distance for cluster definition, harmonising calls across schemas/database versions, assigning MTBC lineage with the Napier 90-SNP barcode, calling Salmonella serovar via SISTR with monophasic Typhimurium awareness, running Pangolin UShER mode with pangolin-data version pinning, or selecting a typing resolution to match the surveillance question.
日本語の概要は準備中です。原文の説明を表示しています。
Detects acquired antimicrobial-resistance determinants and chromosomal point-mutation resistance in bacterial assemblies using AMRFinderPlus, ResFinder 4.0 (acquired + PointFinder), CARD-RGI, abritAMR, staramr, and species-specific callers (TB-Profiler, Mykrobe). Harmonises cross-tool output via hAMRonization, contextualises determinants with mobile-genetic-element annotation (MOB-suite, PlasmidFinder, MobileElementFinder, ICEberg), predicts phenotype against EUCAST or CLSI breakpoints, and translates calls into WHO GLASS reporting categories. Use when screening clinical or surveillance isolates for AMR, distinguishing acquired vs intrinsic vs point-mutation resistance, calling rpoB / katG / pncA / gyrA / mgrB mutations, reconciling AMRFinderPlus vs RGI vs ResFinder disagreement, contextualising carbapenemases or mcr alleles on plasmids, predicting susceptibility from genotype against the WHO Mtb 2nd-edition catalogue, or building a hAMRonized multi-lab AMR surveillance pipeline.
日本語の概要は準備中です。原文の説明を表示しています。