Skip to content

docs: refresh README branding #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ian-pascoe merged 2 commits into from
May 16, 2026
Merged

docs: refresh README branding #44

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c893cbe
docs: refresh README branding
ian-pascoe May 16, 2026
11d15f5
docs: address branding review feedback
ian-pascoe May 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/bright-caplets-brand.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"caplets": patch
---

Refresh the README header, add the Caplets icon artwork, and update plugin metadata with the new icon and brand color.
6 changes: 3 additions & 3 deletions .codex-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,11 @@
"developerName": "Spirit-Led Software LLC",
"category": "Developer Tools",
"capabilities": ["MCP", "Tools"],
"composerIcon": "./assets/icon.png",
"websiteURL": "https://github.com/spiritledsoftware/caplets",
"defaultPrompt": [
"Use Caplets to discover configured capability domains before calling downstream tools.",
"Use Caplets progressive discovery before calling downstream tools."
"Use Caplets to discover configured capability domains via progressive discovery before calling downstream tools."
],
Comment thread
coderabbitai[bot] marked this conversation as resolved.
"brandColor": "#4F46E5"
"brandColor": "#E0582F"
}
}
24 changes: 23 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,26 @@
# Caplets
<div align="center">
<img src="assets/icon.png" alt="Caplets logo" width="140" height="140" />

@coderabbitai coderabbitai Bot May 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial | 💤 Low value

Consider using consistent icon path format.

The README uses assets/icon.png while plugin.json uses ./assets/icon.png. Both work as relative paths, but using the same format in both files would improve consistency.

♻️ Suggested alignment 
-  <img src="assets/icon.png" alt="Caplets logo" width="140" height="140" />
+  <img src="./assets/icon.png" alt="Caplets logo" width="140" height="140" />
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<img src="assets/icon.png" alt="Caplets logo" width="140" height="140" />
<img src="./assets/icon.png" alt="Caplets logo" width="140" height="140" />
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 2, Update the icon path for consistency: change the img
src value in README.md (the <img ... src="assets/icon.png" ... /> tag) to match
the format used in plugin.json by prepending "./" (i.e., "./assets/icon.png"),
or alternatively update the plugin.json icon entry to remove the "./" so both
files use the same relative-path style; ensure both README.md's image tag and
plugin.json's icon field use the identical path format.


<h1>Caplets</h1>

<p>
<strong>Capability cards for coding agents.</strong><br />
Wrap sprawling tool stacks behind focused, progressive-disclosure interfaces.
</p>

<p>
<a href="https://www.npmjs.com/package/caplets"><img alt="npm" src="https://img.shields.io/npm/v/caplets?style=flat-square&color=E0582F" /></a>
<a href="https://github.com/spiritledsoftware/caplets/actions/workflows/ci.yml"><img alt="CI" src="https://img.shields.io/github/actions/workflow/status/spiritledsoftware/caplets/ci.yml?branch=main&style=flat-square&label=ci&color=E0582F" /></a>
<a href="LICENSE"><img alt="MIT License" src="https://img.shields.io/badge/license-MIT-F6E8C8?style=flat-square&labelColor=1F2018" /></a>
<img alt="Node 22+" src="https://img.shields.io/badge/node-%3E%3D22-F6E8C8?style=flat-square&labelColor=1F2018" />
</p>

<p>
<code>MCP</code> · <code>OpenAPI</code> · <code>GraphQL</code> · <code>HTTP</code> · <code>CLI</code>
</p>
</div>

---

Caplets turns sprawling tool setups into focused capability cards for coding agents.
Connect MCP servers, OpenAPI specs, GraphQL endpoints, HTTP actions, and curated CLI
Expand Down
Binary file added assets/icon.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading