「component」の検索結果

Vue 3 Composition API — reactivity primitives, composables, lifecycle, the 3.4+ and 3.5+ macros. Load when writing Vue 3 components or composables.

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

Type-safe i18n for Vue 3 Composition API — useI18n, pipe-syntax plurals, i18n-t/d/n components, lazy-loaded locales. Load when a project imports vue-i18n.

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

React Native mobile development patterns - New Architecture (Fabric, TurboModules, JSI), component architecture, React Navigation 7+, FlashList v2 optimization, gestures with Reanimated 4, platform-specific code, React 19 features

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

NativeWind v4+ - Tailwind CSS utility classes for React Native, className prop, CSS variables, dark mode, platform prefixes, animations, theming, third-party component integration

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

Clerk managed authentication - ClerkProvider, middleware, pre-built components, hooks, server-side auth, organizations, webhooks

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

Upgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade instructions for the extension SPI (middleware lifecycle, codec / migration-tools / framework-components churn, seed-migration on-disk shape), verifies the pins are correctly exact via `prisma-next-check-pins`, runs the extension's own typecheck and tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next" in an extension package, or to update an extension's `@prisma-next/*` deps to a new minor.

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

Use when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, docs source type, controls, and export naming conventions.

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

Use when writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.

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

Dry-run Trust Magnitude for proposed named skills or suites before curation. Use when deciding whether a proposed suite deserves A/S treatment, when checking Fusion Score structural inputs, when comparing repo stars vs suite component counts, or when asked to appraise a candidate before adding it to the registry.

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

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.

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

Fuse all of a contributor's named skills into a single fusion node (suite capstone) in the registry. Use when the user says "fuse <contributor>'s skills", "create a suite for <contributor>", "build a capstone for <user>", "fuse all of <user>'s named skills", "create a suite fusion", "consolidate <contributor> into one skill", or explicitly types /gaia-fuse-full-suite. Also triggers when a contributor has accumulated 3+ named skills and the user asks what to do next with them, or when someone asks "can we make a suite from these?". This skill: collects component IDs from registry/named/<contributor>/, verifies nodes exist, researches evidence and appraises Trust Magnitude, runs `gaia dev fuse` to write the fusion node and suite manifest, validates, and opens a PR on a review/meta/ branch.

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

Plan a feature before writing any code. Use this skill at the START of non-trivial feature work — when the user says they want to "add", "build", "implement", "create", "develop", or "ship" a feature, endpoint, component, page, service, or capability. Especially trigger when the user's prompt is short or under-specified ("add a dashboard", "build an auth flow", "let's do user activity reports") — those need planning, not direct execution. The skill walks through requirements clarification, codebase exploration, sketches a Mermaid architecture/flow diagram of the proposed design, and produces a plan.md document the user can hand off to a fresh AI session for execution. Skip only when the change is genuinely trivial (typo fixes, single-line tweaks, renames). When in doubt, plan.

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

This skill provides expert-level guidance for Test-Driven Development (TDD) in VS Code extension development following t-wada methodology. Use when writing tests before implementation, creating comprehensive test suites, implementing Red-Green-Refactor cycles, or improving test coverage for extension components like WebViews, terminal managers, and activation logic.

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

Add or update the code syntax in demo app from all components

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

Reverses Android malware: unpacking APKs, decompiling DEX bytecode to readable Java, auditing the manifest for abused permissions and components, and locating dynamically loaded or native payloads. Activates for requests to analyze an APK, decompile DEX, or investigate a suspicious Android app.

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

VST3 format adapter for Pulp — SingleComponentEffect wiring, bus arrangement negotiation, parameter / MIDI event routing, state round-trip, and the pitfalls discovered while wiring the adapter against Steinberg's SDK.

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

Developer-Figma collaboration: dev mode, design tokens, component inspection, handoff, and design-system alignment. Use when implementing designs from Figma or aligning code with a design system.

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

Test frontend code: unit, component, E2E, visual regression, and accessibility tests with a sane pyramid. Use for reliable UI quality.

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

Master Figma workflows with auto layout, components, variables, prototyping, and team collaboration.

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

Build and govern scalable design systems with tokens, components, documentation, and adoption strategy.

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

Battery science fundamentals — cell components, electrochemistry metrics, testing protocols, and degradation analysis.

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

Idiomatic Angular: standalone components, signals, RxJS patterns, DI, and enterprise structure. Use when writing, reviewing, or structuring Angular applications.

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

Reviews VST3 plugin implementations for spec compliance, host compatibility, and correctness. Use when the user asks to review a VST3 plugin, check bus arrangements, audit parameter handling, or verify their process() callback is safe. Trigger on phrases like "review my VST3 plugin", "check VST3 bus arrangement", "is my VST3 process safe", "audit my IAudioProcessor", or when you see IComponent, IAudioProcessor, IEditController, ProcessData, or Vst:: namespaced types in the code.

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

Traces and documents signal paths, bus/aux architecture, and sidechain connections in audio systems. Surfaces hidden coupling between audio components. Use when the user asks to trace a signal chain, explain audio routing, understand an audio graph, locate sidechain sources, or describe how audio flows through a plugin or engine. Trigger on phrases like "trace this signal chain", "explain this audio routing", "what calls what in this audio graph", "where does the sidechain come from", "how does audio flow through this plugin".

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