Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions. Use at the end of a coding session or when the codebase feels bloated. Reports findings and fixes them with user confirmation. Cleanups limited to the current working changes belong in a native simplify flow instead.
日本語の概要は準備中です。原文の説明を表示しています。
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Scan the codebase for technical debt and eliminate it. Run at end of session or when the codebase feels bloated.
/techdebt — full scan + report, confirm before fixing/techdebt fix — scan and fix without confirmationPROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
Look for:
Use Grep and Glob to identify candidates. Confirm each item is truly dead/duplicated before reporting.
## Tech Debt Found
### Duplicated Code
- `src/utils/formatDate.ts:12` and `src/helpers/dates.ts:45` — identical logic
Fix: consolidate into formatDate.ts, delete dates.ts
### Dead Code
- `src/api/legacyAuth.ts` — no imports found anywhere
Fix: delete file
### Stale TODOs
- `src/components/Modal.tsx:89` — TODO from 6 months ago, feature shipped
Fix: remove comment
For each item, ask the user to confirm unless they said "fix". After fixes:
# Run tests to verify nothing broke
npm test 2>&1 | tail -20
GATE: Tests still pass after cleanup.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
日本語の概要は準備中です。原文の説明を表示しています。