本文へ移動
cccskills
無料GitHub で公開

better-way

Challenge the user's stated approach and propose a clearly better one before doing the work. Use when the user types /better-way, "better?", "is there a better approach", "any better idea", "what would you do instead", "is this the best way", or shares their own plan and asks whether it is the right one. Works in any project. For a full written decision document with options and scoring, see decision-matrix.

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

qa-aman/claude-skills
インストール方法を見る

含まれるファイル（1）

  • SKILL.md3.7 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Better way

The user brings their own approach and wants to know if a better one exists before anything is built. Answer that first, briefly, then do the work they pick.

Workflow

  1. Read the user's taste first. If ~/.claude/better-way/ledger.md exists, read its last 10 lines so suggestions follow what the user has accepted and rejected before. If it does not exist, carry on; step 6 creates it.
  2. Restate their approach in one line, so they can see it was understood.
  3. Look for better options, in this order:
    • a mechanical guard instead of a written rule (a hook, a test, a check that fails)
    • a system that runs every time instead of a one-off: the whole function, the evidence it learns from, memory so nothing starts fresh, and a loop that feeds results back
    • a native feature of the tool instead of a hand-rolled one (check the tool's first-party docs, not memory)
    • something that removes a step the user would otherwise have to remember
  4. Check before proposing.
    • Feasibility: walk every step on the real platform. For each, name the API call or platform rule that makes it possible, its cost, and any manual step it needs. If a step is not possible, say so and offer the version that is.
    • For a design or architecture question, name what 2-3 strong teams shipped for the same problem, from their own sources, and say where your proposal differs and why.
  5. Answer in this shape, nothing longer:
    • Your way: one line.
    • Better way: what it is, the concrete gain over their way, the cost or limit.
    • My pick: one line. If their way is already the best, say so in one line and stop.
  6. Let the user pick, then log it.
    • When the choice changes what gets built, wait for their pick.
    • When the request also contained the task and the better way is only an improvement, do their way and offer yours.
    • Append one line to ~/.claude/better-way/ledger.md (create the folder and file if missing): - DD-MM-YYYY | accepted/rejected/pending | suggestion | why.

Anti-Patterns

  1. A menu instead of a pick. Three options with no recommendation hands the work back. Always end on one pick.
  2. Better on paper, impossible in practice. Proposing a flow before checking the platform allows each step wastes the build. Feasibility comes before the pitch.
  3. Rewording their idea. A suggestion that changes nothing about the result is noise. Only speak up when the result changes.
  4. Running it on trivial tasks. A one-line fix does not need a challenge. Skip the check when nothing material is at stake, unless the user asked for it explicitly.
  5. Overriding their choice. Once they pick their own way, build it well. Do not re-argue it in later turns.
  6. Claiming from memory. "Tool X can do this" needs the tool's own docs, not recall.

Quality Checklist

  • Their approach is restated in one line
  • The better way names a concrete gain (time, cost, errors avoided, steps removed), not "cleaner" or "more robust"
  • Every step of the proposal was checked against the platform's own docs or API, and limits are stated
  • There is exactly one pick
  • If their way is already best, the answer is one line
  • The outcome is logged in the ledger with a date in DD-MM-YYYY

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

11-star-framework

無料

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

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

qa-aman/claude-skills212026年10月19日 更新

ab-copy-writer

無料

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

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

qa-aman/claude-skills212026年10月19日 更新

ab-test-design

無料

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

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

qa-aman/claude-skills212026年10月19日 更新

acceptance-criteria-writer

無料

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

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

qa-aman/claude-skills212026年10月19日 更新

account-plan

無料

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

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

qa-aman/claude-skills212026年10月19日 更新

ad-campaign-writer

無料

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

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

qa-aman/claude-skills212026年10月19日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する