rhyssullivan/executor · Archived

wrdn-package-boundaries

Preserve workspace package boundaries. Use when lint flags relative imports that cross package roots.

First seen Jun 21, 2026

Installation

$ npx skills add rhyssullivan/executor --skill wrdn-package-boundaries

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rhyssullivan/executor.

npx skills add rhyssullivan/executor

Browse all from rhyssullivan/executor

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.1K
License LICENSE
Default branch main
Open issues 54
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead Grep Glob Bash

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 766 B
  • docs SUMMARY.md 132 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Workspace packages should import each other through package exports, not relative paths.

Fix Shape

  • Replace cross-package relative imports with the target package name.
  • If the needed module is not exported, add the smallest package export that matches the package's public surface.
  • Keep relative imports only within the same package root.
  • Do not reach into another package's private source tree from an app or package.

Good

import { createExecutor } from "@executor-js/sdk";

Bad

import { createExecutor } from "../../../core/sdk/src";