「fix」の検索結果

Create, build, deploy, and localize declarative agents for M365 Copilot and Teams. USE THIS SKILL for ANY task involving a declarative agent — including localization, scaffolding, editing manifests, adding capabilities, and deploying. Localization requires tokenized manifests and language files that only this skill knows how to produce. Triggers: "create agent", "create a declarative agent", "new declarative agent", "scaffold an agent", "new agent project", "add a capability", "add a plugin", "configure my agent", "deploy my agent", "fix my agent manifest", "edit my agent", "localize my agent", "add localization", "translate my agent", "multi-language agent", "add an API plugin", "add an MCP plugin", "add OAuth to my plugin", "review instructions", "improve instructions", "fix my instructions"

日本語の概要は準備中です。原文の説明を表示しています。

Guide for running, interpreting, and fixing code style and analysis violations in grails-core using GrailsCodeStylePlugin, GrailsCodeAnalysisPlugin, and GrailsViolationAggregationPlugin - covering CodeNarc, Checkstyle, PMD, SpotBugs, and JaCoCo

日本語の概要は準備中です。原文の説明を表示しています。

Guide for running, reviewing, and fixing test failures across grails-core modules using Gradle test reports

日本語の概要は準備中です。原文の説明を表示しています。

Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose and fix Anthropic Claude API errors by HTTP status code. Use when encountering API errors, debugging failed requests, or troubleshooting authentication, rate limiting, or input validation issues. Trigger with phrases like "anthropic error", "claude api error", "fix anthropic 429", "claude not working", "debug claude api".

日本語の概要は準備中です。原文の説明を表示しています。

Organization-grade cloud and supply-chain attack-surface discovery: S3/GCS/Azure Blob bucket discovery via observed-name mining (CNAME/cert-SAN/Wayback) and bounded two-class permutation (6 prefixes x 15 suffixes on trusted tokens, bounded target-bound expansion on subdomain stems), existence (HEAD/GET) vs public-listing confirmation, object-key triage into 9 value tiers (database dumps, credentials, IaC state, kubeconfig, VCS dirs, config, archives, PII, logs), dangling-CNAME bucket-takeover detection, and the ownership-gated severity model that stops an unattributable public bucket from becoming a false CRITICAL; the fully offline AWS-account-ID recovery from a leaked AKIA/ASIA/AROA access key (base32 decode, runnable stdlib Python, canonical test vector, AWS-documentation-example-ID screening); dependency-confusion confirmation for npm/PyPI (internal-signal classifier -- private-registry binding vs org-namespace match -- paired with a read-only public-registry 404 check and the npm scope-claimability nuance the public search API misses); and passive cloud-native/container/Kubernetes/CI control-plane fingerprinting (Lambda URLs, API Gateway, Cloud Run, App Service, kubelet/etcd/K8s API/dashboard, Jenkins/GitLab/Argo CD) as an org-attribution and exposure surface. Passive/discovery only -- no exploitation, no credential submission, no active control-plane confirmation (a stage-6 validate_cloud active tier is described but out of scope). Use when enumerating a target's cloud storage footprint, recovering an AWS account ID from a leaked key, confirming a supply-chain dependency-confusion vector, or fingerprinting cloud-native/K8s/CI infrastructure for an authorized external recon engagement.

日本語の概要は準備中です。原文の説明を表示しています。

Review a skillshare change before it becomes a pull request, or review an open pull request. Use this skill whenever the user asks to: review a diff, branch, commit range or PR, check a change before opening a PR, run a pre-Codex review, or find what a change missed. It checks correctness, the repository's documented rules, the originating issue or spec, every consumer of a changed concept, and cleanup (reuse, simplification, efficiency, depth of fix), then verifies each finding against the code before reporting it. Read-only unless the user asks for fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/). Use this skill whenever you: build or modify a dashboard page or component in ui/src/, style or layout website pages or custom CSS in website/, create new React components for the dashboard, add pages to the dashboard, fix visual bugs in either frontend, or need to know which design tokens, ss-* classes, components, or patterns to use. Covers the two dashboard styles (Clean / Playful) in light and dark, design tokens, the ss-* class system, component API, page structure, accessibility, keyboard shortcuts, and anti-patterns. Even if the user just says "fix the styling" or "add a card", use this skill to ensure consistency.

日本語の概要は準備中です。原文の説明を表示しています。

Guides work on the Figma I/O package (@grida/io-figma, packages/grida-canvas-io-figma/). Covers the fig-kiwi binary parser, Kiwi→REST→Grida conversion pipeline, fig2grida CLI, REST API JSON conversion, and testing with clipboard/fig/REST fixtures. Use when adding node type support, fixing conversion bugs, extending fig2grida, working on the fig-kiwi parser, writing tests for Figma import, or debugging clipboard paste failures after a Figma update.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.

日本語の概要は準備中です。原文の説明を表示しています。

Guided journey from a live website that underperforms to a prioritized, evidence-backed backlog of conversion, usability, message, and speed fixes - each shipped as a testable experiment. Orchestrates eight skills phase by phase - cro-methodology, ux-heuristics, refactoring-ui, web-typography, storybrand-messaging, high-perf-browser, made-to-stick, design-everyday-things - asking the user questions at every decision point and recording results in the project docs/ folder (WEBSITE.md, DESIGN.md, IMPROVE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a landing page that isn't converting, diagnose why visitors leave, audit for clarity and usability, or says 'the homepage feels off but a redesign didn't help'. No site yet, create-website; converts but needs traffic, grow-website; if the friction is in a product app, not the marketing site, improve-app; if one specific flow leaks, conversion-optimization. For one framework in isolation, invoke that skill directly.

日本語の概要は準備中です。原文の説明を表示しています。

Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says 'users sign up then disappear'. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.

日本語の概要は準備中です。原文の説明を表示しています。

When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.

日本語の概要は準備中です。原文の説明を表示しています。

Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.

日本語の概要は準備中です。原文の説明を表示しています。

Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.

日本語の概要は準備中です。原文の説明を表示しています。

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

日本語の概要は準備中です。原文の説明を表示しています。

Find failing PR checks, inspect logs or external check links, and apply focused fixes

日本語の概要は準備中です。原文の説明を表示しています。

Generates complete reference-grounded single-drug adverse-effect network-pharmacology research designs from a user-provided drug, adverse event, and desired evidence depth. Always use this skill when a user wants to design, plan, or upgrade a conventional network-pharmacology study centered on one fixed drug and one fixed adverse-effect endpoint, using drug-target prediction, adverse-event target collection, overlap analysis, PPI hub prioritization, enrichment interpretation, molecular docking, and optional orthogonal transcriptomic or literature validation. Covers five study patterns (canonical hub-first, cardiotoxicity or electrophysiology-oriented, immune-inflammatory adverse effect, organ-toxicity pathway context, translational validation) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with a recommended primary plan, dependency/evidence map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path, verified-reference pack, and self-critical risk review.

日本語の概要は準備中です。原文の説明を表示しています。

Generates complete reference-grounded single-drug adverse-effect network-pharmacology research designs from a user-provided drug, adverse event, and desired evidence depth. Always use this skill when a user wants to design, plan, or upgrade a conventional network-pharmacology study centered on one fixed drug and one fixed adverse-effect endpoint, using drug-target prediction, adverse-event target collection, overlap analysis, PPI hub prioritization, enrichment interpretation, molecular docking, and optional orthogonal transcriptomic or literature validation. Covers five study patterns (canonical hub-first, cardiotoxicity or electrophysiology-oriented, immune-inflammatory adverse effect, organ-toxicity pathway context, translational validation) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with a recommended primary plan, dependency/evidence map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path, verified-reference pack, and self-critical risk review.

日本語の概要は準備中です。原文の説明を表示しています。

Debug and fix failing GitHub PR checks for xquic. Use when a PR, branch, or commit has failed CI, GitHub Actions, build checks, test checks, or requested validation failures that should be diagnosed from logs before editing.

日本語の概要は準備中です。原文の説明を表示しています。

Permutation and sequencing integer-programming formulations with ordered local-window variables, prefix/suffix continuity, and overlap penalties. Use when assigning exams, jobs, tasks, visits, blocks, or resources to ordered positions and costs depend on adjacent pairs, sliding triples, n-grams, short-horizon pressure, or overlapping local patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Build and query suffix arrays and related structures

日本語の概要は準備中です。原文の説明を表示しています。

Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes

日本語の概要は準備中です。原文の説明を表示しています。

Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.

日本語の概要は準備中です。原文の説明を表示しています。