「refactoring」の検索結果

Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).

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

Use when writing, reviewing, refactoring, or planning Flutter/Dart code — screens, features, project structure, state management, folders, widgets, cubits/blocs, repositories, services, or tests.

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

Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.

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

Use when writing Dart code, reviewing for style, refactoring naming, adding doc comments, structuring imports, or enforcing type annotations.

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

Enhanced Mikado Method for complex architectural refactoring - systematic dependency discovery, tree-based planning, and bottom-up execution

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

[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking

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

Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows

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

Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the full journey, a validate-only pass ("is my idea worth building", "reality-check this idea"), and a plan-only path for someone arriving with validation done ("I already validated my idea", "I have the research, just plan my MVP", "skip the research"). ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.

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

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

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

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.

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

Analyze a codebase for high-leverage architectural improvements and explain evidence, tradeoffs, and next steps. Use explicitly for architecture audits or deep-module refactoring opportunities.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work test-first or do TDD, or otherwise raise code quality, readability, and maintainability. Also use when writing or reviewing Operately APIs or Ecto queries. Apply these rules by default when producing or changing code for a quality-conscious user.

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

Build modern React Native components using function components and composition. Use when building or refactoring React Native function components and composable UI.

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

Write maintainable Python with small functions, explicit boundaries, guard clauses, and readable state flow. Use when refactoring Python services, helpers, modules, or async logic for clarity—not generic test writing, tooling setup, or database transaction implementation.

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

Write PHP following PSR coding standards, SOLID principles, and code-quality guidelines. Use for PHP style, design, refactoring, naming, and guard clauses—not Composer/PSR-4 project configuration.

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

Apply core Effective Java patterns for robust, maintainable code. Use when applying SOLID principles, choosing between inheritance and composition, refactoring Java code smells, or reviewing class design.

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

Idiomatic JavaScript patterns and conventions for maintainable existing code. Use when reviewing or refactoring JavaScript language patterns; defer project scaffolding, dependency setup, and tool configuration.

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

Standardizes the creation and evaluation of high-density Agent Skills (Claude, Cursor, Windsurf). Ensures skills achieve high Activation (specificity/completeness) and Implementation (conciseness/actionability) scores. Use when: writing or auditing SKILL.md, improving trigger accuracy, or refactoring skills to reduce redundancy and maximize token ROI.

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

Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.

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

Analyze Elixir/Phoenix technical debt — duplicates, refactoring; Use when asked about code quality, cleanup, or what…

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

Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.

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

Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.

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