From 3be7c49e17eb2659f31a62d14fa61e1e7014d6b1 Mon Sep 17 00:00:00 2001
From: Gercek Kriptocu <110336938+Gercekkriptocu@users.noreply.github.com>
Date: Thu, 14 May 2026 01:48:21 +0300
Subject: [PATCH 1/2] fix(readme): update stale base-skills repository
 references

## Summary

Updates stale `base/base-skills` references in the README to the current `base/skills` repository.

## Changes

- Updated GitHub badge URLs
- Updated GitHub badge links
- Updated the installation command from `base/base-skills` to `base/skills`

## Why

The repository is currently hosted at `base/skills`, but the README still references `base/base-skills`.

Fixes #ISSUE_NUMBER
---
 README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index d9dcbde..f799663 100644
--- a/README.md
+++ b/README.md
@@ -6,9 +6,9 @@
 
 <!-- Badge row 1 - status -->
 
-[![GitHub contributors](https://img.shields.io/github/contributors/base/base-skills)](https://github.com/base/base-skills/graphs/contributors)
-[![GitHub commit activity](https://img.shields.io/github/commit-activity/w/base/base-skills)](https://github.com/base/base-skills/graphs/contributors)
-![GitHub repo size](https://img.shields.io/github/repo-size/base/base-skills)
+[![GitHub contributors](https://img.shields.io/github/contributors/base/skills)](https://github.com/base/skills/graphs/contributors)
+[![GitHub commit activity](https://img.shields.io/github/commit-activity/w/base/skills)](https://github.com/base/skills/graphs/contributors)
+![GitHub repo size](https://img.shields.io/github/repo-size/base/skills)
 
 <!-- Badge row 2 - links and profiles -->
 
@@ -20,8 +20,8 @@
 
 <!-- Badge row 3 - detailed status -->
 
-[![GitHub pull requests by-label](https://img.shields.io/github/issues-pr-raw/base/base-skills)](https://github.com/base/base-skills/pulls)
-[![GitHub Issues](https://img.shields.io/github/issues-raw/base/base-skills.svg)](https://github.com/base/base-skills/issues)
+[![GitHub pull requests by-label](https://img.shields.io/github/issues-pr-raw/base/skills)](https://github.com/base/skills/pulls)
+[![GitHub Issues](https://img.shields.io/github/issues-raw/base/skills.svg)](https://github.com/base/skills/issues)
 
 ## Available Skills
 
@@ -42,7 +42,7 @@
 Install with [Vercel's Skills CLI](https://skills.sh):
 
 ```bash
-npx skills add base/base-skills
+npx skills add base/skills
 ```
 
 ## Usage

From 76fce9c7777011affd0763a907098ab3d321aa5e Mon Sep 17 00:00:00 2001
From: Gercek Kriptocu <110336938+Gercekkriptocu@users.noreply.github.com>
Date: Fri, 15 May 2026 22:47:14 +0300
Subject: [PATCH 2/2] Create NOTIFICATIONS.md

Add missing MiniKit notification migration reference
---
 .../NOTIFICATIONS.md                          | 54 +++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 skills/converting-minikit-to-farcaster/NOTIFICATIONS.md

diff --git a/skills/converting-minikit-to-farcaster/NOTIFICATIONS.md b/skills/converting-minikit-to-farcaster/NOTIFICATIONS.md
new file mode 100644
index 0000000..ea50505
--- /dev/null
+++ b/skills/converting-minikit-to-farcaster/NOTIFICATIONS.md
@@ -0,0 +1,54 @@
+# Notifications Migration
+
+MiniKit's `useNotification` hook does not have a direct one-to-one client-side replacement in the Farcaster Mini App SDK.
+
+When migrating notification functionality, move notification sending logic to your backend instead of sending notifications directly from the client.
+
+## Migration Summary
+
+### Before
+
+MiniKit apps may use `useNotification()` from `@coinbase/onchainkit/minikit` inside client components.
+
+### After
+
+Farcaster Mini Apps should trigger a backend endpoint from the client. The backend is responsible for handling notification delivery.
+
+## Recommended Pattern
+
+Create a server endpoint, such as:
+
+`POST /api/send-notification`
+
+Then call that endpoint from your client when a notification should be sent.
+
+Example client-side trigger:
+
+```typescript
+async function sendNotification() {
+  await fetch('/api/send-notification', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/json',
+    },
+    body: JSON.stringify({
+      title: 'Hello!',
+      body: 'You have a new message',
+    }),
+  });
+}
+```
+
+## Important Notes
+
+- Do not keep notification credentials or secrets in client-side code.
+- Validate the user and request on the backend before sending notifications.
+- Avoid blindly forwarding arbitrary client-provided notification content.
+- Treat notification sending as a server-side capability.
+
+## Migration Checklist
+
+- Remove `useNotification` imports from `@coinbase/onchainkit/minikit`.
+- Replace direct client notification calls with a backend API call.
+- Add backend validation before sending notifications.
+- Keep any notification tokens, secrets, or credentials server-side.