LumabyteCo/clarifyprompt-mcp

v1.6.4 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 7d MCP Developer Tools

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

ReleasePort's take

Light signal

editorial:auto 7d

The release consolidates pack distribution into a single repository and updates related documentation, including fixing a placeholder URL in the release notes.

Why it matters: Affects pack management, authoring guides, project docs, architecture diagrams, and release note accuracy; no measurable gate or trigger is provided.

Summary

AI summary

Updates https://github.com/LumabyteCo/clarifyprompt-packs, https://github.com/LumabyteCo/clarifyprompt-mcp/blob/main/packs/README.md, and https://github.com/LumabyteCo/clarifyprompt-mcp/blob/main/CHANGELOG.md across a mixed release.

Changes in this release

Type	Severity	Summary	CVE
Deprecation	Medium	Archived the LumabyteCo/clarifyprompt-packs repository on GitHub. Archived the LumabyteCo/clarifyprompt-packs repository on GitHub. Source: granite4.1:30b@2026-05-27-audit Confidence: low	—
Bugfix	Low	Fixed placeholder URL in release notes to correct engine‑repo reference. Fixed placeholder URL in release notes to correct engine‑repo reference. Source: llm_adapter@2026-05-27 Confidence: high	—
Refactor
Refactor	Low	Consolidated pack distribution into a single repository. Consolidated pack distribution into a single repository. Source: llm_adapter@2026-05-27 Confidence: high	—
Refactor	Low	Added packs/README.md guide for pack authoring. Added packs/README.md guide for pack authoring. Source: llm_adapter@2026-05-27 Confidence: high	—
Refactor	Low	Added "Knowledge packs" section to main README explaining usage and contribution. Added "Knowledge packs" section to main README explaining usage and contribution. Source: llm_adapter@2026-05-27 Confidence: high	—
Refactor	Low	Updated architecture tree to reflect packs/ as canonical home from 1.6.4+. Updated architecture tree to reflect packs/ as canonical home from 1.6.4+. Source: llm_adapter@2026-05-27 Confidence: high	—

Full changelog

What's new in 1.6.4

Pure docs + process patch. No engine code changes, no MCP tool changes, no platform changes, no env-var changes.

This release resolves a long-standing architectural inconsistency between two homes for knowledge packs.

Changed

Pack distribution consolidated into a single repo. LumabyteCo/clarifyprompt-packs has been archived on GitHub with a tombstone README redirecting users here. All four bundled knowledge packs (`anthropic-brand-voice`, `higgsfield-creative-handbook`, `nextjs-14-best-practices`, `sox-compliance`) plus all platform configs (`packs/platforms/*.yaml`) now have a single source of truth: this repo.
New `packs/README.md` — pack-authoring guide lifted from the archived registry. Covers YAML frontmatter schema, H2 chunk-boundary rules, the quality bar that gets PRs merged.
New `## Knowledge packs` section in the main README — explains the four bundled starter packs, how to load via `load_knowledge_pack({source: "", scope: ...})`, the `user` / `project` / `session` scope semantics, and how to contribute.
Architecture tree updated to reflect packs/ as the canonical home from 1.6.4+.
Fixed placeholder URL in the 1.6.2 release notes — was the elided `https://raw.githubusercontent.com/.../packs/...`, now the canonical engine-repo URL.

Why this direction

Quick math: ~10 users, 4 packs (all maintainer-authored), 0 external pack PRs, registry repo at 1 commit in a month. The cost of keeping two repos in sync was paying for a community-contribution surface that hadn't materialized. The drift caught up: `higgsfield-creative-handbook` shipped in 1.6.2 directly to the engine repo and never made it to the registry — exhibit A.

The split-repo approach makes structural sense once there's a forcing function (real PR queue, pack count >20, divergent licensing/governance). Until then the single-repo model keeps the source of truth singular and unambiguous.

Migration

None. Any code that was loading packs via either:

`https://raw.githubusercontent.com/LumabyteCo/clarifyprompt-packs/main/packs/.md` — still resolves (archived repo content is preserved)
`https://raw.githubusercontent.com/LumabyteCo/clarifyprompt-mcp/main/packs/.md` — canonical going forward
bundled `packs/.md` path — unchanged

The npm tarball ships identical `packs/` contents to 1.6.2 / 1.6.3.

Install

```bash
npm install -g [email protected]
```

Full rationale: CHANGELOG.md → 1.6.4.

Breaking Changes

The repository LumabyteCo/clarifyprompt-packs has been archived; all packs and platform configs now reside solely in LumabyteCo/clarifyprompt-mcp.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track LumabyteCo/clarifyprompt-mcp

Get notified when new releases ship.

About LumabyteCo/clarifyprompt-mcp

MCP server for AI prompt optimization — transforms vague prompts into platform-optimized prompts for 58+ AI platforms across 7 categories (image, video, voice, music, code, chat, document).

All releases →