Data Structure Protocol (DSP)

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/data-structure-protocol

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Data Structure Protocol (DSP) LLM coding agents lose context between tasks. On large codebases they spend most of their tokens on "orientation" — figuring out where things live, what depends on what, and what is safe to change. DSP solves this by externalizing the project's structural map into a persistent, queryable graph stored in a .dsp/ directory next to the code. DSP is NOT documentation for humans and NOT an AST dump. It captures three things: meaning (why an entity exists), boundaries (what it imports and exposes), and reasons (why each connection exists). This is enough for an agent to navigate, refactor, and generate code without loading the entire source tree into the context window.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Concepts, How It Works, Integration, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• The project has a .dsp/ directory (DSP is already set up)
• The user asks to set up DSP, bootstrap, or map a project's structure
• Creating, modifying, or deleting code files in a DSP-tracked project (to keep the graph updated)
• Navigating project structure, understanding dependencies, or finding specific modules
• The user mentions DSP, dsp-cli, .dsp, or structure mapping
• Performing impact analysis before a refactor or dependency replacement

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Core Concepts

Code = graph

DSP models the codebase as a directed graph. Nodes are entities, edges are imports and shared/exports.

Two entity kinds exist:

• Object: any "thing" that isn't a function (module/file/class/config/resource/external dependency)
• Function: an exported function/method/handler/pipeline

Identity by UID, not by file path

Every entity gets a stable UID:

obj-<8hex>

func-<8hex>

For entities inside a file, the UID is anchored with a comment marker in source code:

// @dsp func-7f3a9c12
export function calculateTotal(items) { ... }

# @dsp obj-e5f6g7h8
class UserService:

Every connection has a "why"

When an import is recorded, DSP stores a short reason explaining why that dependency exists. This lives in the

exports/

Storage format

Each entity gets a small directory under

.dsp/

.dsp/
├── TOC                        # ordered list of all entity UIDs from root
├── obj-a1b2c3d4/
│   ├── description            # source path, kind, purpose (1-3 sentences)
│   ├── imports                # UIDs this entity depends on (one per line)
│   ├── shared                 # UIDs of public API / exported entities
│   └── exports/               # reverse index: who imports this and why
│       ├── <importer_uid>     # file content = "why" text
│       └── <shared_uid>/
│           ├── description    # what is exported
│           └── <importer_uid> # why this specific export is imported
└── func-7f3a9c12/
    ├── description
    ├── imports
    └── exports/

Everything is plain text. Diffable. Reviewable. No database needed.

Full import coverage

Every file or artifact that is imported anywhere must be represented in

.dsp

kind: external

Examples

Example 1: Ask for the upstream workflow directly

Use @data-structure-protocol-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @data-structure-protocol-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @data-structure-protocol-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @data-structure-protocol-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: Setting up DSP and documenting a module

python dsp-cli.py --root . init

python dsp-cli.py --root . create-object "src/app.ts" "Main application entrypoint"
# Output: obj-a1b2c3d4

python dsp-cli.py --root . create-function "src/app.ts#start" "Starts the HTTP server" --owner obj-a1b2c3d4
# Output: func-7f3a9c12

python dsp-cli.py --root . create-shared obj-a1b2c3d4 func-7f3a9c12

python dsp-cli.py --root . add-import obj-a1b2c3d4 obj-deadbeef "HTTP routing"

Example 2: Navigating the graph before making changes

python dsp-cli.py --root . search "authentication"
python dsp-cli.py --root . get-entity obj-a1b2c3d4
python dsp-cli.py --root . get-children obj-a1b2c3d4 --depth 2
python dsp-cli.py --root . get-recipients obj-a1b2c3d4
python dsp-cli.py --root . get-path obj-a1b2c3d4 func-7f3a9c12

Example 3: Impact analysis before replacing a library

python dsp-cli.py --root . find-by-source "lodash"
# Output: obj-11223344

python dsp-cli.py --root . get-recipients obj-11223344
# Shows every module that imports lodash and WHY — lets you systematically replace it

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ✅ Do: Update DSP immediately when creating new files, adding imports, or changing public APIs
• ✅ Do: Always add a meaningful why reason when recording an import — this is where most of DSP's value lives
• ✅ Do: Use kind: external for third-party libraries without analyzing their internals
• ✅ Do: Keep descriptions minimal (1-3 sentences about purpose, not implementation)
• ✅ Do: Treat .dsp/ diffs like code diffs — review them, keep them accurate
• ❌ Don't: Touch .dsp/ for internal-only changes that don't affect purpose or dependencies
• ❌ Don't: Change an entity's UID on rename/move (use move-entity instead)

Imported Operating Notes

Imported: Best Practices

• ✅ Do: Update DSP immediately when creating new files, adding imports, or changing public APIs
• ✅ Do: Always add a meaningful

  why

  reason when recording an import — this is where most of DSP's value lives
• ✅ Do: Use

  kind: external

  for third-party libraries without analyzing their internals
• ✅ Do: Keep descriptions minimal (1-3 sentences about purpose, not implementation)
• ✅ Do: Treat

  .dsp/

  diffs like code diffs — review them, keep them accurate
• ❌ Don't: Touch

  .dsp/

  for internal-only changes that don't affect purpose or dependencies
• ❌ Don't: Change an entity's UID on rename/move (use

  move-entity

  instead)
• ❌ Don't: Create UIDs for every local variable or helper — only file-level Objects and public/shared entities

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/data-structure-protocol

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @customer-support-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @customs-trade-compliance-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @daily-gift-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @daily-news-report-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: References

• Full architecture specification: ARCHITECTURE.md
• CLI source + reference docs: skills/data-structure-protocol
• Introduction article: article.md

Imported: How It Works

Initial Setup

The skill relies on a standalone Python CLI script

dsp-cli.py

curl -O https://raw.githubusercontent.com/k-kolomeitsev/data-structure-protocol/main/skills/data-structure-protocol/scripts/dsp-cli.py

Requires Python 3.10+. All commands use

python dsp-cli.py --root <project-root> <command>

Bootstrap (initial mapping)

If

.dsp/

1. Identify root entrypoints (

   package.json

   main, framework entry,

   main.py

   , etc.)
2. Document the root file:

   create-object

   ,

   create-function

   for each export,

   create-shared

   ,

   add-import

   for all dependencies
3. Take the first non-external import, document it fully, descend into its imports
4. Backtrack when no unvisited local imports remain; continue until all reachable files are documented
5. External dependencies:

   create-object --kind external

   , add to TOC, but never descend into

   node_modules

   /

   site-packages

   /etc.

Workflow Rules

• Before changing code: Find affected entities via

  search

  ,

  find-by-source

  , or

  read-toc

  . Read their

  description

  and

  imports

  to understand context.
• When creating a file/module: Call

  create-object

  . For each exported function —

  create-function

  (with

  --owner

  ). Register exports via

  create-shared

  .
• When adding an import: Call

  add-import

  with a brief

  why

  . For external deps — first

  create-object --kind external

  if the entity doesn't exist.
• When removing import/export/file: Call

  remove-import

  ,

  remove-shared

  ,

  remove-entity

  . Cascade cleanup is automatic.
• When renaming/moving a file: Call

  move-entity

  . UID does not change.
• Don't touch DSP if only internal implementation changed without affecting purpose or dependencies.

Key Commands

init

create-object

create-function

create-shared

add-import

update-description

update-import-why

move-entity

remove-import

remove-shared

remove-entity

get-entity

get-children --depth N

get-parents --depth N

get-path

get-recipients

read-toc

search <query>

find-by-source <path>

detect-cycles

get-orphans

get-stats

When to Update DSP

create-object

create-function

create-shared

add-import

add-import

create-object --kind external

remove-import

create-shared

create-function

remove-shared

move-entity

remove-entity

update-description

Imported: Integration

This skill connects naturally to:

• context-compression — DSP reduces the need for compression by providing targeted retrieval instead of loading everything
• context-optimization — DSP is a structural optimization: agents pull minimal "context bundles" instead of raw source
• architecture — DSP captures architectural boundaries (imports/exports) that feed system design decisions

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.