example.content-generation
Content generation example using @lssm-tech/lib.content-gen.
@lssm-tech/example.content-generationbun add @lssm-tech/example.content-generationManifest declarations describe the current workspace; they do not verify registry publication or runtime execution.
Package guide
Website: https://contractspec.io
Content generation example using @lssm-tech/lib.content-gen.
What This Demonstrates
- Content generation pipeline with typed contracts.
- Integration with the content-gen library.
- Structured logging for generation steps.
- DocBlock documentation for the generation flow.
- Deterministic provider-free preview data for content, image, video, TTS, STT, and conversation workflow artifacts.
src/docs/contains docblocks and documentation-facing exports.
Preview / export workflow
Content Generation previews use deterministic local pipeline fixtures for brief/prompt editing, generation review, publishing/version snapshots, and audit status. The ./ui export must not call LLM providers, production endpoints, or live storage.
The first-class preview packet covers these local artifact kinds:
content— blog, email, landing, social, and SEO draft outputs from typed briefs.image— campaign hero image fixture references.video— launch teaser storyboard fixture references.tts— narration script fixture references.stt— transcript fixture references.conversation— human review assistant handoff fixture references.
Public key behavior is compatibility-sensitive because current catalog consumers may resolve both examples.content-generation and normalized keys. Document and test any alias migration before release. The Phase 0 compatibility gate lives in .omx/plans/content-generation-compatibility-matrix.md.
Compatibility / Migration Notes
- Keep
content-generationas the canonical feature key; any registry alias cleanup is major-version-only. - Prefer future contract-source imports from
@lssm-tech/lib.contracts-spec/content-generationonce the contracts lane lands them; existing@lssm-tech/lib.content-gengenerator imports remain valid for this example. - Provider credentials are non-goals for this package. Real provider adapters belong in integration packages and are injected by apps/modules, while this example stays deterministic.
- Keep this README synchronized with
packages/apps/web-landing/public/llms-packages/example.content-generation.txtuntil generated docs own the mirror.
Running Locally
From examples/content-generation:
bun run devbun run buildbun run testbun run typecheck
Usage
Use @lssm-tech/example.content-generation as a reference implementation, or import its exported surfaces into a workspace that composes ContractSpec examples and bundles.
Architecture
src/content-generation.feature.tsdefines a feature entrypoint.src/docs/contains docblocks and documentation-facing exports.src/example.tsis the runnable example entrypoint.src/generate.tsis part of the package's public or composition surface.src/index.tsis the root public barrel and package entrypoint.
Public Entry Points
- Export
.resolves through./src/index.ts. - Export
./content-generation.featureresolves through./src/content-generation.feature.ts. - Export
./docsresolves through./src/docs/index.ts. - Export
./docs/content-generation.docblockis an alias of./docsand resolves through./src/docs/index.ts. - Export
./exampleresolves through./src/example.ts. - Export
./generateresolves through./src/generate.ts. - Export
./uiresolves through./src/ui/index.ts. - Export
./ui/content-generation-preview.dataresolves through./src/ui/content-generation-preview.data.ts. - Export
./ui/ContentGenerationPreviewresolves through./src/ui/ContentGenerationPreview.tsx.
Local Commands
bun run dev— contractspec-bun-build devbun run build— contractspec-bun-build buildbun run test— bun test --pass-with-no-testsbun run lint— bun lint:fixbun run lint:check— biome check .bun run lint:fix— biome check --write --unsafe --only=nursery/useSortedClasses . && biome check --write .bun run typecheck— tsgo --noEmitbun run publish:pkg— bun publish --tolerate-republish --ignore-scripts --verbosebun run publish:pkg:canary— bun publish:pkg --tag canarybun run clean— rimraf dist .turbobun run build:bundle— contractspec-bun-build transpilebun run build:types— contractspec-bun-build typesbun run prebuild— contractspec-bun-build prebuild
Recent Updates
- Replace eslint+prettier by biomejs to optimize speed.
- Missing contract layers.
Notes
- Works alongside
@lssm-tech/lib.content-gen,@lssm-tech/lib.contracts-spec,@lssm-tech/lib.logger,@lssm-tech/tool.bun,@lssm-tech/tool.typescript.
Relationships
Arrows point from a package to its direct dependency. Counts are derived from captured workspace manifests.
6 declarations
@lssm-tech/lib.contracts-specworkspace:^
Read the package manual ↗@lssm-tech/lib.content-genworkspace:^
Read the package manual ↗@lssm-tech/lib.loggerworkspace:^
Read the package manual ↗@lssm-tech/lib.design-systemworkspace:^
Read the package manual ↗reactcatalog:
react-domcatalog:
Declared capabilities
This manifest does not declare a capability catalogue. Use the guide, import map and source to assess the package.
Scripts
publish:pkgbun publish --tolerate-republish --ignore-scripts --verbosepublish:pkg:canarybun publish:pkg --tag canarybuildcontractspec-bun-build buildbuild:bundlecontractspec-bun-build transpilebuild:typescontractspec-bun-build typesdevcontractspec-bun-build devcleanrimraf dist .turbolintbun lint:fixlint:fixnode ../../scripts/biome.cjs check --write --unsafe --only=nursery/useSortedClasses . && node ../../scripts/biome.cjs check --write .lint:checknode ../../scripts/biome.cjs check .testbun test --pass-with-no-testsprebuildcontractspec-bun-build prebuildtypechecktsgo --noEmit