Menu
Configure package.json and project.json for hyperfrontend libraries. Use when setting up library configuration, adding entry points, configuring build targets, or fixing ESLint errors about missing fields.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | library-package-config |
| version | 1.0.0 |
| description | Configure package.json and project.json for hyperfrontend libraries. Use when setting up library configuration, adding entry points, configuring build targets, or fixing ESLint errors about missing fields. |
| allowed-tools | ["Read","Write","Edit","Grep","Glob"] |
Generators create compliant configs. Manual edits must pass these ESLint rules.
| Rule | Enforces |
|---|---|
lib-project-metadata | name starts with lib-, has description + tags |
lib-project-version-targets | Publishable has version + version-check targets |
lib-project-bundle-config | IIFE/UMD have both entry + globalName |
lib-pkg-fields | name, description, license, sideEffects, engines, keywords |
lib-pkg-no-main | No main field — use exports |
lib-pkg-exports-js-only | Export paths use .js not .ts |
lib-pkg-exports-exist | Export paths point to existing files |
lib-pkg-package-json-export | Exports include "./package.json" |
lib-tsconfig-paths | Every export has tsconfig.base.json path mapping |
no-unwanted-barrel-files | index.ts only at declared entry points |
lib-readme-structure | README has required sections/badges |
root-readme-packages | Root README lists library in packages table |
docs-site-library-docs | docs-site has page routes for library markdown |
// package.json exports
{
".": "./src/index.js",
"./browser": "./src/browser/index.js",
"./package.json": "./package.json"
}
// tsconfig.base.json paths (grouped by package)
{
"@hyperfrontend/<name>": ["libs/<name>/src/index.ts"],
"@hyperfrontend/<name>/browser": ["libs/<name>/src/browser/index.ts"]
}
Each entry point index.ts requires @module JSDoc header — see lib-require-module-header.
| Tag | private: true | Has build/publish targets |
|---|---|---|
scope:public | ✗ | ✓ |
scope:internal | ✓ | ✗ |
Write conventional commits for the hyperfrontend monorepo — types, scopes (Nx project names), one-line subjects, atomic commits, versioning-harness boundaries. Use when committing, splitting work into commits, choosing a commit scope/type, or asked about commit format.
Register friction found while building hyperfrontend demos into the showcase findings registry. Use when a demo consuming @hyperfrontend/features surfaces an unclear API, confusing error, missing feature, docs gap, packaging snag, or DX papercut — file the finding before writing the workaround.
Write README.md files for hyperfrontend libraries and sub-modules. Use when creating library documentation, writing sub-module READMEs, documenting API tables, adding quick start guides, or reviewing README structure compliance.
Write ARCHITECTURE.md files for hyperfrontend libraries. Use when creating architecture documentation, documenting design decisions, adding system overview diagrams, or explaining module composition and data flow.
Coding conventions for the hyperfrontend Nx monorepo. Use when refactoring, adding features, fixing bugs, or writing any new code across libs/, apps/, tools/, or plugins/.
Achieve 100% code coverage for custom ESLint rules. Use when reviewing ESLint rules for coverage gaps, adding missing tests, or applying istanbul ignore comments.