agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/connect-query/SKILL.md

connect-query

Skill4 starsChanged 11 days agoMITView on GitHub

Build typed ConnectRPC data flows with Connect Query and Protobuf v2. Use for API calls, mutations, query hooks, transports, invalidation, or generated clients.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run /read-the-damn-docs before current ConnectRPC/Connect Query/Protobuf API guidance.

    line 10
  2. Very specific:

    Prefer ConnectRPC transport over axios/fetch.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run /read-the-damn-docs before current ConnectRPC/Connect Query/Protobuf API guidance.

Enforce

  • In ConnectRPC files, ban raw TanStack useQuery/useMutation; use Connect Query, except useTransport/callUnaryMethod.
  • invalidateQueries() needs a query key.
  • Prefer ConnectRPC transport over axios/fetch.
  • Protobuf v2: create(Schema), not new Message(); MessageShape/MessageInitShape, not PlainMessage/PartialMessage; no manual $typeName.

Escape: // allow: direct-query [reason].

Query discipline

  • Define 2-3 semantic cache constants centrally; Infinity only when own invalidation is exclusive. QueryClient owns retry: retry network/5xx, never 4xx.
  • Hook transform/select returns display-ready data and enforces page size; components do not parse.
  • Invalidate rather than refetch and always await it. Keys are service/method broad but cardinality-aware.
  • Loader and hook use identical query keys; test parity to prevent double fetches.
  • One hook per RPC; split multi-RPC pages. Mutation names end Mutation, or WithToast when owning toasts.
  • Client protovalidate checks sent data, not server-validated responses.
  • Proto optionals use undefined, never null; unbounded lists use infinite query/load-more; polling uses refetchInterval.

Editable query data: read writable derived state for local overrides and save/refetch handoff; keep server truth in the query cache.

Timestamp, Duration, Any, caches: REFERENCE.md. Install: SETUP.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free