「dead code」の検索結果

Produce a truthful Japanese App Store metadata pack and app-name shortlist in twelve minutes without a multi-agent research round. Use for a live launch sprint, fallback ASO copy, app naming under a hard deadline, or when local product evidence is available but market research is intentionally deferred.

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

Timebox and coordinate a live three-lane iOS launch sprint from audience idea to tested SwiftUI app, landing page, ASO copy, screenshots, promo video, and privacy report. Use for a 50-minute talk, demo rehearsal, fallback drill, or any request to finish a tiny local iOS product under a hard deadline.

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

Use when choosing a linker, fixing link order or undefined symbol errors, enabling LTO or ThinLTO, or cutting dead code with --gc-sections. Not for inspecting the linked binary: use elf-inspection.

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

Use when the user says "simplify this diff" or asks for a compression pass over a change-set. Not for dead-code sweeps: use deslop.

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

Works through the surviving mutants that cargo-mutants reports for packages/engine — classify each one as a real test gap, a mutant not worth killing, or dead code, then fix it and verify with `just mutants-diff`. Use when picking up the weekly "Mutatietesten" issue, when asked to improve engine test coverage, or when a pull request fails the Mutation Testing (diff) gate.

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

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 a task needs the judgment of an Electrician — sizing a service panel upgrade with an NEC load calculation, troubleshooting a tripping breaker or dead circuit systematically, checking wire gauge/ampacity and voltage drop for a circuit run, resolving a code-vs-inspector interpretation dispute, or deciding when a job (aluminum wiring, knob-and-tube, undersized service) exceeds the immediate scope.

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

Use when auditing DecisionsAI, Codex, Claude, Cursor, Gemini, Pi, Cline, RTK, workflow pre_chain skills, hooks, projected commands, skill routing, or harness setup for drift, duplication, dead references, slow hooks, bloated context, or stale config.

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

Build visuals that sell a specific offer and value proposition. Translates an offer (price, bundle, guarantee, bonus, deadline) into hero visuals that make the value legible at a glance. Use when the user says "visualize the offer", "promo creative", "make the deal look good", "value prop hero", or has a concrete offer to merchandise. Part of the Creative Production set.

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

Rework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".

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

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

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

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

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

Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.

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

Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.

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

Load for behavior-preserving rename, move, decomposition, dead-code removal, dependency cleanup, record/class conversion, or immutable contract migration that needs caller, flow, test, and impact analysis; not for feature work or one-line cleanup.

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

Re-mint a ChatGPT bearer token when a nightly sync exits with a token-expired code: the session cookie lives for months and deterministically produces a fresh bearer, with no LLM and no browser. Triggers: "/chatgpt-token-heal", "chatgpt token dead", or the sync failing on that error.

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

Use when working on any Java or JVM project: plain Java, libraries, CLI tools, Maven/Gradle builds, Spring Boot, Jakarta EE, MyBatis/MyBatis-Plus, JPA/Hibernate, Lombok, Java tests, Java code review, API design, exception handling, security review, refactoring, dependencies, Java version upgrades, javax/jakarta migrations, or JVM runtime troubleshooting such as GC, OOM, thread dumps, deadlocks, high CPU, and performance issues.

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

Focused Signals scout for PostHog projects using feature flags. Watches the flag roster and the `$feature_flag_called` evaluation stream for contradictions between a flag's configured state and its real traffic: evaluation cliffs on healthy flags, ghost flags (code calling keys that no longer exist), response-distribution shifts with no corresponding flag edit, and flag debt (stale, fully-rolled-out, or dead flags still burning evaluations). Emits findings only when they clear the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.

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

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.

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

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

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

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

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

Detect i18n/locale keys that are removed from source but remain in locale files, or keys added to locale files without source usage.

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

Analyze a completed phase diff for high-confidence behavior-preserving simplifications and apply only explicitly approved proposals. Use after execution and before review to reduce duplication, dead code, needless complexity, or avoidable inefficiency.

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

Audit site navigation — find dead-end features, missing backlinks, and poor discoverability. Produces an improvement list, no code changes.

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