「review」の検索結果

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

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

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

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

/council — Deliberative multi-provider review. Use when the user runs /council.

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

Run the full Forge pipeline unattended: each phase is reviewed by a fresh evaluator subagent, the findings feed back, and the run advances itself. Use when the user runs /forgemaster-auto or wants a feature built end to end without approval gates.

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

Triage GitHub issues through gh and a label-based state machine. Use when the user intentionally wants GitHub issue triage, incoming bug or feature review, issue workflow labels, needs-info follow-up, or ready-for-agent briefs.

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

Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.

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

Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines. Use PROACTIVELY for content review.

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

Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns. Use PROACTIVELY for mobile security implementations or mobile security code reviews.

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

Expert in secure frontend coding practices specializing in XSS prevention, output sanitization, and client-side security patterns. Use PROACTIVELY for frontend security implementations or client-side security code reviews.

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

Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.

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

Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.

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

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

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

Upgrades .NET to a newer TFM. LTS-to-LTS, staged through STS, preview, upgrade paths.

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

Detects C# code smells during review. Anti-patterns, async misuse, DI mistakes, fixes.

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

Use as the single visible starter and controller for workspace work that may change files, runtime assets, planning state, docs, settings, or governance. Normalize the request into the Super Agent lifecycle: intake, spec registration for non-trivial work, planning registration, specialist routing, execution, testing, review, closeout, and planning-state updates before implementation begins.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is reached.

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

Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.

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

Create PR, run review, and prepare for merge after verification passes

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

Retroactive 6-pillar visual audit of implemented frontend code

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

Create a clean PR branch by filtering out .planning/ commits — ready for code review

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

Generate a comprehensive project summary from milestone artifacts for team onboarding and review

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

Create or update product-update / release-notes content for a given OpenMetadata/Collate patch version across getcollate, openmetadata-site, and docs-om. Sources getcollate's changelog from openmetadata-collate + OpenMetadata + ai-platform; openmetadata-site's from OpenMetadata only; docs-om reuses openmetadata-site's already-written content, reformatted into its Mintlify snippet structure. Filters to customer-facing changes only, runs each target's own doc-review checklist, verifies every link live, and requires explicit approval before any commit.

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

AEM Cloud Service expert skill for OSGi Event Admin handlers (non-resource events). Covers migration of javax.jcr.observation.EventListener (residual non-resource cases) and OSGi EventHandler with inline business logic to the lightweight EventHandler + JobConsumer split. Includes routing rules (resource events go to resource-change-listener, external notification goes to AEM Eventing), TopologyEventListener for leader-only execution, replication and workflow event patterns, service-user setup, review checklist, troubleshooting, and common pitfalls.

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