Menu
Use @hyperfrontend/package generators to create, promote, rename, or move libraries. Use when scaffolding a new library, promoting internal to publishable, renaming a project, or relocating a library directory.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
| name | library-generators |
| version | 1.1.0 |
| description | Use @hyperfrontend/package generators to create, promote, rename, or move libraries. Use when scaffolding a new library, promoting internal to publishable, renaming a project, or relocating a library directory. |
| allowed-tools | ["Read","Write","Edit","Terminal"] |
All support --dry-run.
# Create internal library
nx generate @hyperfrontend/package:library --name=my-utils --type=util --description="..."
# Create nested (libs/utils/my)
nx generate @hyperfrontend/package:library --name=my-utils --directory=libs/utils --type=util --description="..."
# Create publishable
nx generate @hyperfrontend/package:library --name=my-utils --type=util --description="..." --publishable
# Promote to publishable
nx generate @hyperfrontend/package:make-publishable --project=lib-my-utils
# Rename
nx generate @hyperfrontend/package:rename --project=lib-my-utils --newName=my-helpers
# Move
nx generate @hyperfrontend/package:move --project=lib-my-utils --destination=libs/utils
Generator creates E2E project + CI status workflow. 6 manual entries required:
| Step | File | Entry |
|---|---|---|
| 1 | .github/workflows/ci-libraries.yml | Path filter + matrix entry |
| 2 | .github/workflows/ci-main.yml | Coverage entry in LIBS array |
| 3 | README.md | Row in packages table |
| 4 | apps/docs-site/scripts/generate-docs.ts | LIBRARIES array entry |
| 5 | apps/docs-site/src/lib/content.ts | LIBRARIES array entry |
| 6 | apps/docs-site/src/app/docs/libraries/{slug}/page.tsx | Page route file |
See library-ci-workflows skill for steps 1–2.
import type { Metadata } from 'next'
import { LibraryDocPage } from '@/components/library-doc-page'
import { getLibraryMetadata } from '@/lib/metadata'
export function generateMetadata(): Metadata {
return getLibraryMetadata('my-lib')
}
export default function MyLibPage() {
return (
<LibraryDocPage
title="My Lib"
packageName="@hyperfrontend/my-lib"
slug="my-lib"
category="core"
fallbackDescription="One-line description."
fallbackFeatures={['Feature 1', 'Feature 2']}
/>
)
}
{
name: 'My Lib',
packageName: '@hyperfrontend/my-lib',
slug: 'my-lib',
readmePath: 'libs/my-lib/README.md',
entryPoints: ['libs/my-lib/src/index.ts'],
category: 'core',
},