Skip to content

docs: promote email and SMS in the Codex listing prompts - #68

Merged
sherwinski merged 4 commits into
mainfrom
sherwin/omnichannel-listing-prompts
Oct 12, 2026
Merged

sherwinski merged 4 commits into
mainfrom
sherwin/omnichannel-listing-prompts

Conversation

@sherwinski

@sherwinski sherwinski commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

One Line Summary

Add email and SMS examples to the Codex listing copy in .codex-plugin/plugin.json, and fix the composer icon in dark mode.

Motivation

The listing prompts only showed push examples. OneSignal also sends email and SMS, and the listing copy now shows all 3 channels.

Scope

  • defaultPrompt: the second banner prompt is now an email example, "Send an email to promote our new product." The prompt is short enough to fit on 1 line in the banner card.
  • longDescription: the "Try prompts like" list has 2 email examples and 2 SMS examples, in the order email, SMS, then push. The 4 push prompts did not change.
  • composerIcon: now points to assets/composer-icon.svg, the media-kit logomark on a white disc. The Codex manifest has no dark variant of composerIcon (see codex-rs/plugin/src/manifest.rs), so Codex ignored composerIconDark and showed the navy logomark on dark cards. Codex shows the composer icon as an image with no container, so a currentColor SVG did not help either; the icon needs its own background, the same approach the CircleCI, Notion, and Linear plugins use. The unsupported field is removed from the manifest and from OPTIONAL_BRAND_ASSET_FIELDS in scripts/package_directory_bundle.py.
  • AGENT.md: the assets row and the bundle note now describe the 3 supported asset fields.
  • No changes to skills, references, or the Claude Code manifest.
  • No version bump. The tree is at 1.1.1 and the last tag is 1.1.0, so main already moved past the last release.

Testing

  • python3 -m json.tool .codex-plugin/plugin.json parsed with no errors.
  • python3 -m py_compile scripts/*.py passed.
  • python3 scripts/package_directory_bundle.py --check printed bundle check passed (version 1.1.1; nothing written).
  • python3 scripts/package_directory_bundle.py --self-test passed.
  • python3 scripts/package_directory_bundle.py --out built a bundle that contains the composer icon and the 3 asset fields.
  • Reinstalled the plugin from the local marketplace with codex plugin remove onesignal@onesignal and codex plugin add onesignal@onesignal. The card icons read correctly in the Codex app in dark mode.

Affected code

  • Skills
  • Scripts
  • References
  • Templates
  • Manifests

Checklist

  • Commit subjects use conventional prefixes
  • Bundle gate passes
  • No secrets in the diff

Change the second banner prompt to an email example. Add email and SMS
examples to the "Try prompts like" list, and order the list as email,
SMS, then push. Many users do not know that OneSignal supports email
and SMS, and the listing copy now shows all 3 channels.
@sherwinski
sherwinski force-pushed the sherwin/omnichannel-listing-prompts branch from c25c69d to a5a2989 Compare October 12, 2026 23:11
The Codex manifest has no dark variant of composerIcon, so Codex ignored
composerIconDark and showed the dark logomark on dark cards. The composer
icon now points to logomark-mono.svg, which fills with currentColor and
follows the text color of the theme. Drop the unsupported field from the
manifest and from the packager's optional asset list.
Codex shows composerIcon as an image with no container, so currentColor
falls back to black and the icon stays dim on a dark card. The icon is now
the logomark on a white disc, which matches the header logo and reads on
both themes.
@nan-li
nan-li self-requested a review October 12, 2026 23:50
@sherwinski
sherwinski merged commit 726d7c5 into main Oct 12, 2026
8 checks passed
@sherwinski
sherwinski deleted the sherwin/omnichannel-listing-prompts branch October 12, 2026 23:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants