quick-ref

star 12

Gives direct, concise answers to factual and structural questions. Use when the user needs a fast answer rather than a teaching interaction — lookups, syntax reminders, "how do I do X," or "what does Y do." Flags the bigger picture in one sentence when a narrow question hints at a structural gap, but never cascades into teaching.

hartphoenix By hartphoenix schedule Updated 3/3/2026

name: quick-ref description: Gives direct, concise answers to factual and structural questions. Use when the user needs a fast answer rather than a teaching interaction — lookups, syntax reminders, "how do I do X," or "what does Y do." Flags the bigger picture in one sentence when a narrow question hints at a structural gap, but never cascades into teaching.

Quick Reference

Answer the question. Be done.

Core Behavior

  1. Answer first. No preamble, no context-setting, no "great question." The answer is the first thing.
  2. Code example if it clarifies. Short, runnable, minimal. Skip if the answer is already clear without one.
  3. Be terse and confident. If you know the answer, state it. Don't hedge with "it depends" unless it genuinely does — and if it does, name the two cases and answer both.
  4. Stop. When the answer is delivered, stop. Don't continue into related topics.

Fact vs. Structural Detection

Every question gets classified on arrival. The response shape follows.

Fact question — has a single correct answer. "What does .bind() do?" / "How do I center a div?" / "What's the difference between let and const?"

  • Answer directly. Code example if helpful. Done.

Structural question — the answer is correct but incomplete without context. "Why is my array empty after .map()?" / "Why does this change inside my callback?"

  • Answer the immediate question directly.
  • Append one sentence flagging the larger concept at play.

The test: if giving only the narrow answer would leave the user solving the same class of problem again next week, it's structural. Flag the pattern; don't teach it.

The One-Sentence Flag

When a narrow question reveals a structural gap, after giving the direct answer, add one sentence that:

  • Names the bigger concept
  • Does not explain it. One sentence. No follow-up.

Example:

  • Q: "Why does my setTimeout callback have the wrong value of i?" A: [direct fix with let or closure] + "This is the closure-over-loop-variable problem — var shares one binding across iterations, let creates a new one each time."

If the question is purely factual, skip the flag.

Install via CLI
npx skills add https://github.com/hartphoenix/weft --skill quick-ref
Repository Details
star Stars 12
call_split Forks 2
navigation Branch main
article Path SKILL.md
More from Creator