「fea」の検索結果

Transforms vague UI/feature requests into structured, optimized prompts with design system awareness. Use when generating prompts for UI implementation, feature specification, or design-to-code translation. Triggers on tasks requiring prompt refinement, UI specification, or design system integration.

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

Validate whether a proposed new artifact is feasible in the current stack before creator workflows run.

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

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.

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

Create a new feature with proposal, retrospective, and branch. Use when starting new development work.

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

Molecular ML with diverse featurizers and pre-built datasets. Use for property prediction (ADMET, toxicity) with traditional ML or GNNs when you want extensive featurization options and MoleculeNet benchmarks. Best for quick experiments with pre-trained models, diverse molecular representations. For ready-made ADMET numbers without training a model use admet-prediction; for benchmark datasets and task-aware splits use pytdc.

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

Generate a polished release video for a tbh-meter release in the Claude-Code motion style (recreated animated UI + real game sprites + synth soundtrack), to post with a launch. Primary input is a GitHub release LINK — the skill turns it into a video named after that release, covering ONLY the features that shipped in that release, version stamped on the intro. Use when asked to make/update a release video, showcase clip, feature trailer, or promo video for a meter release, or "make the video for <release link>".

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

Convert SVG files to high-quality PNG images with precise control over dimensions, background color, and CSS rendering (including mix-blend-mode, filters, gradients). Use this skill when the user wants to: (1) convert SVG to PNG, (2) generate app icons or splash screens from SVG source, (3) batch-generate multiple PNG sizes from a single SVG, (4) render SVG with advanced CSS features like mix-blend-mode or filters to PNG. Triggers: "SVG to PNG", "SVG変換", "PNG変換", "アイコン生成", "スプラッシュ生成", "app icon from SVG", "favicon generation", "splash screen generation".

機能要件から画面構成・ワイヤーフレームまでを段階的に落とし込むスキル。 design-discussion や feature-discussion の成果物を入力として、 2ステップ（アクションフロー → ワイヤーフレーム + 画面設計ノート）で画面設計を行う。 ワイヤーフレームを見ながらユーザーと一緒に必要な機能・画面要素を詰めていく。 成果物は PlantUML Salt による視覚的なワイヤーフレーム。 Use when: 機能から画面に落としたい、画面構成を考えたい、 ワイヤーフレームを作りたい、画面設計をしたい、画面フローを整理したい。 design-discussion の後に使うと効果的。 Triggers: "画面構成", "画面設計", "ワイヤーフレーム", "画面に落とす", "ui flow design", "UIフロー設計", "wireframe", "画面を考えたい", "UIフロー", "画面遷移", "screen design", "画面フロー", "screen flow"

Use when the user needs to scope, write, or audit a product spec — a PRD, feature spec, user stories, acceptance criteria, or a "spec this out"/"break this into stories"/"definition of done" request — or wants an existing spec reviewed for gaps and anti-patterns. Triggers whenever a feature idea needs to become structured requirements that align a team on what to build. For the analytics behind success metrics, use data-analysis; for the technical design, use software-architect.

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

Create, track, switch, sync, and clean up Git branches. Covers naming conventions, safe branch switching with stash, upstream synchronization, and pruning merged branches. Use when starting work on a new feature or bug fix, switching between tasks on different branches, keeping a feature branch up to date with main, or cleaning up branches after merging pull requests.

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

Plan a software release cycle with milestones, feature freezes, release candidates, and go/no-go criteria. Covers calendar-based and feature-based release strategies. Use when starting planning for a major or minor version release, transitioning from ad-hoc to structured release cadence, coordinating a release across multiple teams or components, defining quality gates for a regulated project, or planning the first public release (v1.0.0) of a project.

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

Classify gate call variants in a minified JavaScript bundle. Covers context-window extraction around a flag occurrence, identification of 4–6 reader variants (sync boolean, sync config-object, bootstrap-aware TTL, truthy-only, async bootstrap, async bridge), default-value extraction (boolean / null / numeric / config-object literal), conjunction detection across `&&` predicates, kill-switch inversion detection, and production of a gate-mechanics record that feeds probe- feature-flag-state. Use when a flag's behavior cannot be inferred from its name alone, when the binary uses multiple reader libraries, or when config-object gates carry structured schemas distinct from boolean gates.

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

Universal SDLC pipeline orchestrator with stack provider auto-discovery. Reads stack.md profiles from installed plugins, picks the highest-priority match, executes a 5-phase pipeline (BA → Dev → QA → Sec → Docs) plus stack-defined extra phases. Use when: - User invokes /sdlc:start "<feature>" - User asks to "run the SDLC pipeline" or "go through the full pipeline" - You need to coordinate specialist agents to deliver a complete feature Do NOT use for: - Trivial single-file edits (just edit directly) - Read-only questions about the codebase - Casual conversation

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

Next.js project structure, App Router conventions, file-based routing primitives, layouts, error boundaries, metadata, image and font optimization, configuration. Apply when implementing or modifying Next.js features. Use this skill to: - Pick the correct file convention (page/layout/loading/error/not-found/route/template/default). - Structure a feature within the App Router tree. - Set up metadata for SEO and OpenGraph. - Configure next.config.js for headers, redirects, image domains. - Use built-in fonts and images correctly. Do NOT use this skill for: - Server vs Client component boundaries (see server-component-patterns). - Data fetching patterns (see nextjs-data-fetching). - Complex routing (parallel/intercepting routes — see nextjs-routing). - Testing (see nextjs-testing).

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

NestJS module structure, dependency injection, lifecycle, configuration, exception handling, and logging conventions. Apply when implementing or modifying NestJS backend code. Use this skill to: - Structure feature modules (one feature = one module). - Wire DI correctly (constructor injection, scopes, custom tokens). - Set up ConfigModule, ValidationPipe, exception filters in main.ts. - Use lifecycle hooks for init and graceful shutdown. - Pick the right exception class for each error case. Do NOT use this skill for: - Decorator-specific patterns (see decorator-patterns). - ORM/data access (see nest-data-layer). - GraphQL/WebSockets/Microservices (see nest-advanced). - Testing (see nest-testing).

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

Reviews PRs that modify the Feature Table in CLAUDE.md. Use when a PR adds CC version rows or modifies docs/CLAUDE-feature-table.md.

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

Spec-driven development workflow. Interactive phase-by-phase confirmation from proposal to implementation. Trigger: 'spec-flow', 'spec mode', 'need a plan', 'structured development', 'write a spec', 'feature spec', 'technical spec', '需求文档', '技术方案', '任务拆解', '规格驱动', '写个方案', '做个规划', '结构化开发', 'plan this feature', 'break this down', 'design doc'. Creates .spec-flow/ directory with proposal, requirements, design, and tasks.

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

Record product demos and walkthroughs for marketing assets. Two modes: quick screenshot-stitch demos via ply + ffmpeg, or polished Remotion compositions. Use when the user mentions product demo, demo video, walkthrough video, feature showcase, screen recording, GIF demo, product tour, onboarding video, visual tutorial, feature walkthrough, landing page video, hero video, product video, app preview video, or wants to show their product in action. Even if they just say 'show what it does', 'make a video of the app', 'I need a demo for my landing page', or 'record the app' — this is the skill. If someone has a working product and needs marketing assets that show it off, start here. Owns screen-recorded product demos and walkthroughs. For an AI-generated marketing or brand video with no real product footage, see /higgsfield-generate; for Remotion code and `remotion render` issues, see /remotion-best-practices; for stitching existing slides into an MP4, see /video-content.

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

This skill should be used when the user asks "How do I...", "What is...", "How does X work in Prismatic?", "What's the best practice for...", wants to understand Prismatic concepts, features, or architecture, or needs guidance on marketplace deployment, customer connections, embedded UI, config pages, triggers, or other Prismatic product features. Search and retrieve documentation from prismatic.io/docs and reference examples from github.com/prismatic-io/examples.

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

Use when a feature or code change made by Claude is complete and the developer wants to confirm they actually understood it before shipping. Triggers on "handoff", "quiz me", "comprehension check", "did I understand this", "verify I read the code", "test my understanding", or after finishing a feature when the developer wants to take ownership of AI-written code. Also triggers on requests for an interactive or clickable quiz ("interactive mode", "let me answer with the mouse", "mode interactif", "je réponds à la souris"). Quizzes the developer on WHERE the logic lives (file/function) and WHY decisions were made (trade-offs, behavior, debugging), with the number of questions scaled to the size of the change. Multiple-choice questions are clickable by default (asked through `AskUserQuestion`) and fall back to typed answers. Points to file:line on wrong answers, allows one retry, then reveals the answer, and ends with a score plus the weak areas to re-read. Conducts the quiz in the developer's language.

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

Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.

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

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

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

Start a new Flywheel planning round for a Forge feature. Writes the initial markdown plan to .flywheel/plans/ and gives instructions for sending it to competing frontier models. Use at the very beginning of a new feature or subsystem.

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

Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.

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