3,391 件 ・ 関連度順
概要と使いどころ
Evaluates high-yield issuance with call schedules, change of control puts, and restricted payment baskets. Use when analyzing HY bonds, comparing HY vs leveraged loan terms, or assessing issuer flexibility.
日本語の概要は準備中です。原文の説明を表示しています。
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive 7-phase SEO optimization workflow covering technical SEO auditing, keyword research strategy, on-page optimization, content SEO and E-E-A-T, structured data implementation, link building, and AI search optimization. Use when auditing search engine visibility, diagnosing ranking issues, implementing schema markup, conducting keyword research, optimizing content for E-E-A-T signals, or adapting for AI-driven search (AI Overviews, SGE).
日本語の概要は準備中です。原文の説明を表示しています。
Jira project management and issue tracking integration
日本語の概要は準備中です。原文の説明を表示しています。
Detect missing docs, undocumented files, project health issues, and coverage gaps on session start or on-demand. Scans for README gaps, TODO/FIXME counts, and test coverage holes.
日本語の概要は準備中です。原文の説明を表示しています。
Two-agent cleanup pattern. Implementer works freely, then a dedicated cleanup agent removes unused imports, console.logs, commented-out code, dead code, and formatting issues. Produces a diff of what was cleaned.
日本語の概要は準備中です。原文の説明を表示しています。
Concurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Force adversarial code review stance that eliminates confirmation bias — reviewer must find issues or re-analyze
日本語の概要は準備中です。原文の説明を表示しています。
Technical product expert specializing in platform engineering, DevOps, and AI dev tools. Critically reviews the SDD plugin for DX issues, inconsistencies, and gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Report a problem with the open-pr plugin itself, or ask for a change, on its public issue tracker. Use when a run of one of its commands left something to say. Takes no URL.
日本語の概要は準備中です。原文の説明を表示しています。
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management, making interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify cluttered UI by removing unnecessary elements, choices, features, and structural complexity. Use when the problem is too many controls, options, features, or competing elements—not when the structure is sound and the real issue is only visual intensity or lack of personality.
日本語の概要は準備中です。原文の説明を表示しています。
Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".
日本語の概要は準備中です。原文の説明を表示しています。
Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".
日本語の概要は準備中です。原文の説明を表示しています。
Implement features, fix bugs, and keep the codebase healthy and maintainable. Works from a defined PBI, issue, or task description.
日本語の概要は準備中です。原文の説明を表示しています。
Produce written specs and atomic PBIs that an implementation agent can execute independently. Authors specs and Linear issues.
日本語の概要は準備中です。原文の説明を表示しています。
Onboarding workflow for cross-library KB query in a consulting practice. Discovers existing user-scope library registrations, prompts for additions, validates each library, helps activate the relevant ones for the current project, runs a smoke test, and reports a clear "ready" or "issues to fix" verdict. Use --verify-only to skip prompting and just validate existing setup (sub-task 23 of
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "respect prefers-reduced-motion", "honor reduced motion", "make my animations accessible", "fix vestibular / motion-sickness issues", "add a useReducedMotion hook", "gate GSAP / Framer Motion / Lenis for reduced motion", or "meet WCAG 2.3.3 / C39". Provides tiered (not all-or-nothing) reduced-motion patterns in CSS and JS.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multi-agent Claude Code teams with Minoan-Semitic naming — auto-discover project context (CLAUDE.md, roadmaps, plans, issues) and generate named team configurations with structured task lists and file ownership. Triggers on parallel workstreams, agent teams, multi-agent, spawn agents, swarm, minoan-swarm.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy and manage Netlify projects using Next.js with serverless functions, environment variables, and continuous deployment. Use this skill when working with Netlify deployments, configuring netlify.toml, managing Netlify Functions, debugging webhooks, setting environment variables, or troubleshooting deployment issues for Next.js applications on Netlify. Essential for Twilio-Aldea and similar serverless SMS/telephony projects. v2.0 includes official Netlify documentation, production patterns from Twilio-Aldea (webhook timeout solutions, background functions), and TypeScript code examples.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, responsive design, theming, and anti-patterns. Generate a scored report with P0-P3 severity ratings. Report-only — documents issues for other skills to fix. Triggers on audit the design, check accessibility, technical review, performance audit, a11y check.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and fixes Claude behavioral issues in system prompts and Projects using tested countermeasure templates. Use when "Claude is too verbose," "keeps hedging," "agrees with everything," "claims it did something it didn't," "won't use a tool," "fix Claude's output," "tune Claude's behavior," "Claude ignores my preferences," "adds unsolicited disclaimers," "uses too many lists." Covers ten tendencies: agreeableness (output-content + persistent-preference), hedging, verbosity, list overuse, fabricated precision, over-exploration, tool miscalibration (over- and under-triggering), LaTeX defaulting, editorial drift, self-referential fabrication. Also use when auditing a system prompt for behavioral calibration or recalibrating a pre-4.7 prompt, and when users describe recurring output problems without naming a tendency. Do NOT use for scoring a prompt's overall quality — use rootnode-prompt-validation if available.
日本語の概要は準備中です。原文の説明を表示しています。