Skip to content

Add cloudinary-next skill#20

Open
eportis-cloudinary wants to merge 3 commits into
mainfrom
next-skill
Open

Add cloudinary-next skill#20
eportis-cloudinary wants to merge 3 commits into
mainfrom
next-skill

Conversation

@eportis-cloudinary

Copy link
Copy Markdown

No description provided.

@njb90 njb90 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

A couple of small comments, otherwise all good based on my testing.

### Signed vs unsigned — when to use which

**Unsigned** (simpler, no backend):
- For: prototypes, low-risk apps, when anyone with the preset name may upload.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I wouldn't say unsigned uploads are completely not for production. There's certainly use-cases where it is valid providing account and preset are correctly configured.


Use this first when the user is unsure which Cloudinary component, helper, or SDK API to use.

> Source: converted from the uploaded `.cursorrules.template` and reorganized for progressive Skill loading.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Probably don't need/want these source comments

@jackieros jackieros left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@eportis-cloudinary - We also need to update the main skill repo readme to add an entry (row in the table) for cloudinary-next. Added below.

Comment thread README.md
| `cloudinary-transformations` | Turns natural language image and video transformation requirements into valid URL transformation strings that follow Cloudinary best practices. Use when building delivery URLs, applying transformations, optimizing media, or debugging transformation syntax errors. |
| `cloudinary-react` | Provides opinionated React SDK patterns for configuration, common integration scenarios, and troubleshooting for frequent errors and TypeScript pitfalls. Use when developing with the Cloudinary React SDK. |
| `cloudinary-react` | Provides opinionated React SDK patterns for configuration, common integration scenarios, and troubleshooting for frequent errors and TypeScript pitfalls. Use when developing React apps with Cloudinary. |
| `cloudinary-next` | Provides opinionated Next.js SDK patterns for Server and Client Component boundaries, server-side uploads and deletes, and troubleshooting for frequent errors and TypeScript pitfalls. Use when developing Next.js apps with Cloudinary. |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@eportis-cloudinary - Added to the repo readme. Pls check.

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.

3 participants