Agent skill

Eng Data Boundaries

by compozy in compozy/compozy

Data-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs.

MITAuto-check passedDevelopment

Install Eng Data Boundaries

skills CLI
$ npx skills add compozy/compozy --skill eng-data-boundaries -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compozy/compozy eng-data-boundaries --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/eng/eng-data-boundaries .claude/skills/eng-data-boundaries && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
eng-data-boundaries
GitHub stars
2.8k
Token cost
~720 tokens
SKILL.md length
325 words
Files
5 (incl. references)
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Data-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs.

  • Debugging those paths
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Presentational-only UI
  • Backend work with no public read-model impact

What it does

Eng Data Boundaries is an agent skill from compozy/compozy. Data-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs. Use when adding, changing, or debugging those paths. Don't use for presentational-only UI or backend work with no public read-model impact.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/boundary-map.md`, `references/catalog-contract.md` and `references/live-cache-contract.md`).

It sits in Development. It works with TanStack. The repository describes itself as: An operating system for AI agents. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each… The licence is MIT.

When your agent uses it

  • Debugging those paths
  • Presentational-only UI
  • Backend work with no public read-model impact

Example prompts

  • “/eng-data-boundaries”

What it can do on your machine

Read from SKILL.md and the folder at commit c46be43. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eng Data Boundaries loads about 720 tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 325 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~720
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from compozy/compozy at commit c46be43, republished under its MIT licence (© compozy). 325 words, ~720 tokens.

Download SKILL.mdSave it as .claude/skills/eng-data-boundaries/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
eng-data-boundaries
description
Data-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs. Use when adding, changing, or debugging those paths. Don't use for presentational-only UI or backend work with no public read-model impact.

Compozy Data Boundaries

Preserve the owner's scope, order, completeness, identity, and continuity across the changed read path.

  • Identify the authoritative store/service/projection and whether the datum is global, workspace, session, or agent scoped. Distinguish complete populations from pages, samples, tails, and projections. Use references/boundary-map.md for a new or ambiguous contract; reuse an existing map for unchanged fields.
  • Trace affected Web reads through loaders, query options/keys, adapters, contract, transport, and owner; trace live writes through cursor/frame, listener, cache merge, and view model. Repair the first boundary that loses truth and remove compensation made obsolete by that repair.
  • For catalog/filter/sort/count/cursor changes, read the matching sections of references/catalog-contract.md. For pagination with SSE, polling, optimistic writes, or reconnect, use references/live-cache-contract.md. Read the complete contract when a change spans those coupled invariants.
  • Preserve the API envelope in Query caches; flatten only at the view-model read boundary. Reuse canonical option/key factories across loaders, hooks, mutations, and stream writers. Do not reconstruct server scope, order, totals, cursors, or continuity from weaker client data.

Use relevant rows of references/test-matrix.md to identify the invariant, owning layer, and existing suite before changing coverage. Adversarial identities, scale, and reconnect cases should falsify the changed assumption; reuse existing cases for unchanged invariants. eng-consolidate-test-suites helps when ownership is unclear.

Public contract changes co-ship affected transports, generated types, consumers, docs, and skills/compozy/. Record that once in the owning docs/_memory/change-impact.md audit and update affected QA scenarios. Use the enclosing workstream's scoped verification and delivery gates without repeating them for each boundary.

Unresolved boundaries

  • Trace an unknown owner/population before designing its query; do not ask the user to resolve discoverable code facts.
  • Exact totals need an aggregate/projection, not an unbounded rich read or a relabeled loaded count.
  • A stream without stable identity or a reset fence remains a wake signal for a canonical reread; do not heuristically merge it.
  • If a static rule cannot distinguish a valid view-model transformation from server-contract compensation, prove the invariant behaviorally instead of expanding a syntax ban.

© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in .agents/skills/eng/eng-data-boundaries of compozy/compozy.

  • SKILL.md
  • references/boundary-map.md
  • references/catalog-contract.md
  • references/live-cache-contract.md
  • references/test-matrix.md

Open the folder on GitHubat commit c46be43

Compare with similar skills

Eng Data Boundaries next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eng Data Boundaries compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eng Data Boundaries this skillcompozy/compozy2.8k—~720Automated safety check: PassMIT
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Wagmi Feature Developmentwevm/wagmi6.8k—~3.8kAutomated safety check: PassMIT
Sync Templatetsu-moe/tsu-stack126—~2kAutomated safety check: PassMIT
Cleanup Specialistahaodev/shadmin174—~1.3kAutomated safety check: PassMIT
Changelogquests-org/quests464—~596Automated safety check: PassApache-2.0

Similar skills

  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.

    6.8k GitHub stars~3.8k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Sync Template

    tsu-moe/tsu-stack

    Compare or update a project derived from tsu-moe/tsu-stack while preserving application features, identity, configuration, and deployment behavior.

    126 GitHub stars~2k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Cleanup Specialist

    ahaodev/shadmin

    Safe cleanup of Shadmin's Go backend, React frontend, Go CLI, and docs — remove dead code, consolidate duplication, and improve maintainability without changing behavior or adding features.

    174 GitHub stars~1.3k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Changelog

    quests-org/quests

    Generate changelog from git commits

    464 GitHub stars~596 tokensUpdated 6 mo ago
    DevelopmentAuto-check passed
  • Tanstack Router Best Practices

    DeckardGer/tanstack-agent-skills

    TanStack Router best practices for type-safe routing, data loading, search params, and navigation.

    222 GitHub stars~1.1k tokensUpdated 28 days ago
    DevelopmentAuto-check passed

More from compozy/compozy

All 47 skills in this repo
  • Eng Real Scenario QA

    compozy/compozy

    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.

    2.8k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Eng Test Conventions

    compozy/compozy

    Go test-shape discipline for Compozy. An agent skill from compozy/compozy.

    2.8k GitHub stars~467 tokensUpdated today
    Auto-check passed
  • Assistant UI

    compozy/compozy

    Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.

    2.8k GitHub stars~958 tokensUpdated today
    Auto-check passed
  • Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.

    2.8k GitHub stars~999 tokensUpdated today
    Auto-check passed
  • Assistant UI Runtime

    compozy/compozy

    Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.

    2.8k GitHub stars~856 tokensUpdated today
    Auto-check passed
  • Assistant UI Streaming

    compozy/compozy

    Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.

    2.8k GitHub stars~813 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Eng Data Boundaries

What does Eng Data Boundaries do?

Data-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs. Eng Data Boundaries is an agent skill from compozy/compozy. Data-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs.

When should I use Eng Data Boundaries?

Eng Data Boundaries fits situations like: debugging those paths; presentational-only UI; backend work with no public read-model impact.

How do I install Eng Data Boundaries in Claude Code?

Run `npx skills add compozy/compozy --skill eng-data-boundaries -a claude-code`. Or copy the skill folder (.agents/skills/eng/eng-data-boundaries in compozy/compozy) into .claude/skills/eng-data-boundaries in your project. Claude Code loads it when a task matches its description.

How do I install Eng Data Boundaries in Codex?

Run `npx skills add compozy/compozy --skill eng-data-boundaries -a codex`. Or copy the skill folder (.agents/skills/eng/eng-data-boundaries in compozy/compozy) into .agents/skills/eng-data-boundaries in your project. Codex loads it when a task matches its description.

Can I use Eng Data Boundaries in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compozy/compozy --skill eng-data-boundaries -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eng-data-boundaries, .gemini/skills/eng-data-boundaries, .github/skills/eng-data-boundaries and .opencode/skills/eng-data-boundaries in your project.

What does Eng Data Boundaries need to run?

SKILL.md names no scripts, command-line tools or credentials: Eng Data Boundaries is instructions for the agent only.

Does Eng Data Boundaries access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Eng Data Boundaries safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Eng Data Boundaries use?

Eng Data Boundaries is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eng Data Boundaries use?

About 720 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Eng Data Boundaries?

Skills that share tags, products or a category with Eng Data Boundaries: Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Wagmi Feature Development (wevm/wagmi, 6.8k stars), Sync Template (tsu-moe/tsu-stack, 126 stars) and Cleanup Specialist (ahaodev/shadmin, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eng Data Boundaries?

compozy (a GitHub organization) maintains it in compozy/compozy, which has 2,791 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 7, 2026.

Source: compozy/compozy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.