5,044 件 ・ 関連度順
概要と使いどころ
Use when behavior-preserving frontend refactoring focuses on variable meaning, field naming, derived state, or reference/value identity, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on behavior/data ownership, statement placement, loops, or dead-code knowledge, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on record, collection, value, responsibility, delegation, or algorithm boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on function structure, naming, parameters, shared context, or phase boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on conditional complexity, repeated branches, guards, special cases, or internal invariants, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when proving that a frontend refactoring preserved existing behavior, selecting an appropriate safety net, validating each structural step, or assigning a PASS, PARTIAL, or NOT PROVEN preservation verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing new observable frontend behavior or fixing a behavior-changing bug where a failing test can describe the missing or incorrect behavior first. Apply to components, hooks/composables, utilities, API clients, route guards, or user workflows; pure behavior-preserving refactoring uses an already-green contract instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use when safely removing dead frontend code, unused exports, stale components, obsolete routes, unused dependencies, or cleanup targets found by tools such as knip, depcheck, ts-prune, TypeScript, ESLint, or manual review. Do not use for feature rewrites that change behavior; Chinese triggers include dead code, clean up unused, refactor clean, dependency cleanup, delete useless code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on legacy OO hierarchies, subtype responsibilities, superclass extraction/collapse, or delegation, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when selecting or composing behavior-preserving refactoring techniques after structural evidence is known, especially when multiple candidate transformations, preconditions, or ordering choices must be compared.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on function API shape, flags, dependencies, mutability, construction, or command/function trade-offs, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when restructuring existing frontend code while preserving observable behavior, including responsibility extraction, module movement, conditional simplification, API cleanup, or data organization. Do not use for new feature behavior, behavior-changing bug fixes, dependency or framework migrations, or proven dead-code cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include accessibility, accessibility, a11y, WCAG, screen reader.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing or improving frontend performance, Core Web Vitals, bundle size, runtime rendering cost, network waterfalls, memory leaks, long tasks, Lighthouse findings, or performance budgets; Chinese triggers include performance optimization, page freeze, slow first screen, bundle volume, Web Vitals.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Database Architect — choosing a normalization level matched to the actual workload, resolving a CAP theorem tradeoff (consistency vs. availability) for a distributed data store, selecting a sharding/partition key aligned with the dominant query pattern, validating an indexing strategy against real query plans, or deriving RPO/RTO backup and replication requirements from actual business impact.
日本語の概要は準備中です。原文の説明を表示しています。
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an assisted living or elder care platform for resident safety and operational quality. Triggers: building or reviewing senior living software, nursing home management systems, or home health platforms.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/. For writing the individual posts, see linkedin-post, newsletter-writer or content-writer. For the campaign this sits inside, see campaign-brief. For the end-of-month review, see retro.
日本語の概要は準備中です。原文の説明を表示しています。
Write landing page copy for product pages, campaign pages, lead-gen pages, pricing pages, and feature pages. Use when the user asks for landing page copy, product page, lead magnet page, "write the page for X", pricing page copy, feature page, hero section, or web copy that converts. Uses the StoryBrand SB7 framework (Donald Miller) to structure every page. Reads brand voice, positioning, and ICP from knowledge/. For improving an existing page's copy, see copy-review. For diagnosing why a page does not convert, see page-cro. For the ads driving traffic to it, see ad-campaign-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Build interactive "living workflow" flowcharts in the visual style of https://statuesque-starship-49757d.netlify.app/revenue-engine - vanilla HTML/CSS/JS files with a horizontal step bar, a vertical trunk that grows per step, tool-to-tool columns with animated payload pills between brand-marked tool nodes, alternating left/right step descriptions, and per-step outputs. Use whenever the user says "build a flowchart", "interactive flowchart", "living workflow", "revenue engine flowchart", "demand gen flowchart", "GTM workflow diagram", "process diagram with animations", "Nebor-style flowchart", or asks to recreate the workflow visual from the Nebor site. Always asks which flowchart to build (Revenue Engine / Demand Gen / CRM & RevOps / Custom) and waits for explicit approval of the step + tool + edge table before generating any files.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and draft or explicitly apply paid-ad optimizations using evidence, financial constraints, experiments, and capability-gated adapters. Use for campaign optimization, budget reallocation, bid changes, pausing or archiving ads, requests to delete campaigns, search-term or negative-keyword actions, creative rotation, or improving CPA and ROAS.
日本語の概要は準備中です。原文の説明を表示しています。
Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model evaluations.
日本語の概要は準備中です。原文の説明を表示しています。
Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.
日本語の概要は準備中です。原文の説明を表示しています。
Dispatch to the right problem-solving technique based on how you're stuck
日本語の概要は準備中です。原文の説明を表示しています。