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

reference-hunt

Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

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

Reference hunt

Some requirements are too intricate or too tacit to write down, but working code somewhere already embodies them. The best reference is not a screenshot or a description — it's source. Read it like a spec, then reimplement the semantics, not the syntax.

Steps

  1. Get the reference: a repo path, a vendored folder, a library name, or a site whose underlying code can be read. Ask what specifically to extract from it — behavior, structure, visual system, API shape — so you don't imitate the wrong dimension.
  2. Read the reference and produce a semantics summary before writing any code:
    • the behaviors and guarantees it implements (timing, ordering, error handling, edge cases),
    • the decisions that look deliberate versus incidental,
    • anything that won't translate to the target language or stack, with a proposed equivalent.
  3. Have the user confirm the semantics summary. This is the moment misreadings get caught cheaply.
  4. Reimplement in the target stack: same semantics, native idioms. Do not transliterate line by line, and do not copy code verbatim from references whose license doesn't allow it — note the license if it's unclear.
  5. Close the loop: list each behavior from the summary and where the new implementation honors it, plus any place you consciously diverged and why.

Guardrails

  • The reference defines what; the target codebase's conventions define how.
  • If the reference itself turns out to be buggy or inconsistent, surface that instead of faithfully reproducing the bug.
  • Respect licenses: extracting semantics is fine; copying incompatible code is not.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

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

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

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

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

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

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

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

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

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

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

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

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Neeeophytee のスキルをすべて見る

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