1,761 件 ・ 関連度順
概要と使いどころ
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating cross-platform readiness
日本語の概要は準備中です。原文の説明を表示しています。
Publishes mobile applications to iOS App Store and Google Play with code signing, versioning, and CI/CD automation. Use when preparing app releases, configuring signing certificates, or setting up automated deployment pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory, license/security review, explicit allowlist, clean staging package, approval dry run, and fresh public clone/install smoke. Triggers on "open source this", "publish these skills", "make this repo public", "export and sanitize", "подготовь публичный релиз", "выложи скиллы", "опенсорсни", "санитизируй и опубликуй". NOT for ordinary upstream bugfix PRs, vulnerability disclosure, or creating a corp-* department.
日本語の概要は準備中です。原文の説明を表示しています。
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be disclosed publicly, keeping claims traceable to shipped changes, and writing a headline that carries information instead of hype. Use when drafting or revising anything aimed at people who do not use the product yet, and when deciding whether a link, key, price, or unreleased detail can appear in public copy.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked to run smoke tests, validate an end-to-end user journey, dogfood a product, test a release candidate, or execute a non-deterministic workflow that may include authentication or human checkpoints. Do not use as a substitute for deterministic unit, integration, or scenario tests.
日本語の概要は準備中です。原文の説明を表示しています。
Design reproducible evaluations for AI agents with representative task sets, explicit rubrics, appropriate graders, baselines, regression gates, and failure analysis. Use when defining agent quality, comparing prompts or models, validating a release, measuring tool-use reliability, investigating regressions, or deciding whether an agent is ready for production.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert MEMS Engineer. Use when a task calls for MEMS Engineer judgment. Reasons from scale-dependent mechanics, squeeze-film damping, and electrostatic pull-in through DRIE Bosch/surface micromachining, CoventorMP/COMSOL, foundry PDKs, LDV/WLI metrology, and AEC-Q103 qual while treating release stiction, DRIE scallop bias, package-stress offset drift, and functional-WLT-vs-reliability gaps as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Mechanical Design Engineer. Use when a task calls for Mechanical Design Engineer judgment. Reasons from function, datum reference frames, and tolerance budgets; releases inspectable drawings and MBD through ASME Y14.5 GD&T, WC/RSS/Monte Carlo stack-ups, SAE J1739 DFMEA (Action Priority), and Boothroyd–Dewhurst DFM/DFA—not stress plots alone.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Immunotherapy Scientist. Use when a task calls for Immunotherapy Scientist judgment. Reasons from antigen recognition and checkpoint circuits through CAR-T/bispecific design, ASTCT CRS/ICANS grading, flow cytometry release CQAs, iRECIST response assessment, COMPASS/TIDE biomarker modeling, and JACIE/FACT IEC accreditation while treating antigen escape, pseudoprogression, tonic signaling, and step-up CRS as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Flavor & Fragrance Chemist. Use when a task calls for Flavor & Fragrance Chemist judgment. Reasons from odor activity values, threshold perception, matrix release, and degradation kinetics through GC-MS with retention indices, GC-O/AEDA, chiral GC authentication, ISO 8586 trained sensory panels, and IFRA/FEMA regulatory limits while treating aldehyde oxidation, citral cyclization, top-note fade, and allergen exceedance as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Connectomics Scientist. Use when a task calls for Connectomics Scientist judgment. Reasons from vEM acquisition and petascale alignment through FFN/RoboEM segmentation, FlyWire/neuPrint/MICrONS/H01 graphs, and synapse-level QC while treating split/merge errors, alignment tears, false synapses, and release-version drift as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Vaccine catalyst analysis across the two-gate path: CBER BLA review and the ACIP recommendation gate that turns FDA approval into commercial availability. Lot release, procurement milestones, pediatric bridging, and healthy-population efficacy context — dated, verified, and sized per event.
日本語の概要は準備中です。原文の説明を表示しています。
wacrawl: WhatsApp Desktop archive import/search, slices, backups, repo/release work.
日本語の概要は準備中です。原文の説明を表示しています。
Provider-independent ecommerce product imagery production for marketplace listings, product pages, hero shots, lifestyle scenes, comparison charts, infographics, variant/packaging images, virtual try-on or placement mockups, ads, and AI-assisted product visuals. Use when an agent must plan, generate, edit, review, localize, package, or QA truthful commercial product images while managing SKU continuity, marketplace requirements, claims, rights, releases, accessibility, and approval.
日本語の概要は準備中です。原文の説明を表示しています。
Query the Ensembl REST API for gene/transcript/protein lookup, sequence retrieval, comparative genomics (Compara), variant effect prediction (VEP), regulatory features, and cross-species ortholog/paralog calls. Use when pulling Ensembl-native data (Ensembl Gene IDs, version-pinned releases, archive endpoints for reproducibility), gene/transcript/exon structure with stable IDs, or VEP for variant annotation. Encodes the 15 req/sec rate limit, archive (e110.rest.ensembl.org) for reproducibility, Ensembl divisions (vertebrates / plants / fungi / metazoa / bacteria), and the symbol-vs-ID stability problem.
日本語の概要は準備中です。原文の説明を表示しています。
Generate AI-friendly repository documentation with the SourceSage CLI. Use when Codex needs to run `sage` or `sourcesage` to create `.SourceSageAssets/Repository_summary.md`, analyze the current repository or another local repository, switch the output language between English and Japanese, use `--lite` to keep the summary small, change the output directory, or optionally create a deprecated tag-diff release report with `--diff`.
日本語の概要は準備中です。原文の説明を表示しています。
MiniMax presents itself as a premium AI infrastructure brand through a striking duality — bold black-pill CTAs and stark white canvas for marketing, paired with vibrant gradient product cards (orange-red, magenta-pink, purple, blue) that turn each model release into a distinctive visual identity. The system uses DM Sans across all surfaces, employs an oversized 80px hero display, anchors major actions in deep near-black pills, and layers content density via a 3-column documentation grid with sidebar nav, prose body, and TOC. Coverage spans the marketing homepage, model showcase pages, developer documentation, and platform pricing surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Test application performance with k6 load/stress/soak/spike scripts and k6 scenarios, Lighthouse CI for Web Vitals, and performance budgets as CI gates. Covers load profiles, custom metrics, bottleneck identification, and Core Web Vitals (LCP, INP, CLS). Use when: "performance test," "load test," "stress test," "soak test," "spike test," "k6," "k6 scenarios," "Lighthouse," "Web Vitals," "Core Web Vitals," "performance budget." Not for: scheduled production probes — use synthetic-monitoring; pixel-diff regressions — use visual-testing; designing tests from prod telemetry — use observability-driven-testing. Related: ci-cd-integration, qa-metrics, release-readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.
日本語の概要は準備中です。原文の説明を表示しています。
Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, realistic targets by company stage, and the action to take when each metric goes red. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate." Not for: building the dashboard UI (Allure/Grafana) — use qa-dashboard; measuring coverage gaps and mutation score — use coverage-analysis. Related: qa-dashboard, coverage-analysis, ci-cd-integration, release-readiness, quality-postmortem.
日本語の概要は準備中です。原文の説明を表示しています。
Build and visualize QA dashboards and reports with Allure Report, Grafana, and ReportPortal. Covers test execution visualization, stakeholder-facing quality reports, trend/flakiness panels, release-readiness gates, alerting, and CI integration for automated report generation. Use when: "test dashboard," "Allure," "test report," "quality dashboard," "Grafana," "ReportPortal," "test results visualization." Not for: defining which KPIs to measure or how to interpret them — use qa-metrics (this skill builds the panels; qa-metrics decides what they should show). Related: qa-metrics, ci-cd-integration, ai-bug-triage.
日本語の概要は準備中です。原文の説明を表示しています。
Create a changelog-style promotion PR between two branches. Use for release promotions or branch-to-branch merges with a structured changelog.
日本語の概要は準備中です。原文の説明を表示しています。