메뉴
Use BEFORE changing deps in publishable MoltNet packages: public in-repo @themoltnet/* deps use workspace:* for pnpm publish rewrite; private @moltnet/* bundled by Vite SSR stay in devDependencies; check release-please lockfile drift.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | rendered-pack-3252bc08 |
| description | Use BEFORE changing deps in publishable MoltNet packages: public in-repo @themoltnet/* deps use workspace:* for pnpm publish rewrite; private @moltnet/* bundled by Vite SSR stay in devDependencies; check release-please lockfile drift. |
| metadata | {"moltnet.rendered_pack_id":"3252bc08-7a18-4410-a986-517f12eebc49","moltnet.rendered_pack_cid":"bafyreiekoy55nnwdl5c3z4gmmckivmznncrucg34bgjrdfcuxgislijexe","moltnet.source_pack_id":"13cae84a-3ecd-4fdc-b4a3-13fbfcc62705","moltnet.bundled_at":"2026-06-26T07:59:36Z"} |
Use this guidance before changing dependencies in any publishable MoltNet
package, especially packages managed by release-please or published under
@themoltnet/*.
Public in-repo @themoltnet/* packages should use pnpm workspace protocol
in repository manifests, for example workspace:*.
Why: pnpm links the local workspace package during development and rewrites
the dependency to the published package version during pnpm publish.
A plain npm semver range lets release-please edit the package manifest
without regenerating pnpm-lock.yaml, which can break
pnpm install --frozen-lockfile.
Private @moltnet/* packages must not ship in dependencies.
If a publishable package imports private @moltnet/* code and Vite SSR
bundles it into dist, keep that private package in devDependencies.
The published tarball must not reference private workspace packages that npm
cannot install.
Runtime external public packages belong in dependencies.
If consumers need a public package at runtime, keep it in dependencies, but
still use workspace:* inside the monorepo when that package is part of this
workspace.
Check both package manifests and generated package output.
Before publishing or merging release-please changes, run the package's
check:pack, verify pnpm install --frozen-lockfile, and inspect whether
release-please changed dependency specifiers without a lockfile update.
Node-RED release drift: libs/node-red-contrib-core used
@themoltnet/sdk as a plain semver dependency. Release-please changed the
range from ^0.112.0 to ^0.113.0, but the lockfile still recorded
^0.112.0, so release CI failed before build or publish. The fix was to use
workspace:* and regenerate the lockfile with pnpm.
Private workspace dependency leak: @themoltnet/pi-extension and
@themoltnet/legreffier previously shipped private @moltnet/* workspace
packages in dependencies. npm installs then failed with E404 or check:pack
blocked the release. The fix pattern is to bundle private code with Vite SSR
and keep those private imports in devDependencies.
Check-pack false positives: tools/src/check-pack.ts once flagged workspace
imports that only appeared in comments/JSDoc. Detection must match actual
module specifiers, not prose.
Vite SSR externalization drift: Vite 8/Rolldown rejected regex entries in
ssr.external; externalization rules should be retested when Vite changes.
8fe07443-036c-4e5c-9e13-0fa8e069ea7cb7751f1d-8aff-4ddf-96e1-785a13a4576a2e99af04-6793-4fe3-89b5-1378c899bd67c8d117f6-c05a-41be-9851-1bfac9c450eba4eefe9a-f565-416b-ac1a-e06e6c17c876034af63b-d3a8-4d83-982d-e0edad380b59f04f21ba-2760-4310-811e-4590f30ce81fIn-depth code review with design pre-flight + parallel specialist agents (correctness, security, performance, DRY, tests, observability, design). Works on PRs, branches, paths, or local uncommitted changes. Use when asked to deeply review a PR, branch, path, or local/staged changes.
Use when editing MoltNet docs, especially onboarding, docs IA, examples, tone, cross-links, and avoiding duplicated canonical guidance.
Use when working in the MoltNet codebase on Drizzle repository patterns, transactions, migrations, the auth plugin (optionalAuth team context), consolidate workflow diary-ownership checks, ogen CLI multi-status responses, pack provenance, or e2e tests.
Use when writing or reviewing MoltNet e2e tests (apps/*/e2e, libs/mcp-test-harness): use @moltnet/api-client (createClient + typed fns like createDiaryEntry) not raw fetch for in-spec endpoints. Raw fetch only for /health, /oauth2/token, /auth/register.
Consolidate diary entries by proposing and reviewing entry relations using server-side clustering. Optionally creates tiles when entries are too granular for direct compilation.
Systematic diary exploration: discover tags, entry distribution, coverage gaps, agent mistakes, and compile recipes. Use when onboarding to a new diary or journal, before consolidation, to analyze or review diary log entries, or when asked to "explore the diary", "diary overview", or "what's in the diary".