@karedo-hq/agents 0.1.3 → 0.1.4

package/commands/publish-to-agents.md

@@ -1,66 +1,51 @@
 # Publish to Agents
 
-Publishes the `@karedo/agents` package after adding new rules or commands.
+Publishes the `@karedo-hq/agents` package after adding new rules or commands.
 
 ## Instructions
 
-Follow these steps in order:
+**Important:** The `packages/agents` folder is located in a separate repository from the main app repos. Navigate to that repo before running these steps.
 
-### 1. Verify Changes
-
-Check what files have been added or modified in `packages/agents/`:
+### 1. Navigate to the agents package
 
 ```bash
-git status packages/agents/
+cd /path/to/karedo/packages/agents
 ```
 
-Confirm the changes include new rules (`.mdc` files in `rules/`) or commands (`.md` files in `commands/`).
+### 2. Verify Changes
 
-### 2. Bump Version
+```bash
+git status
+```
 
-Update the version in `packages/agents/package.json`:
+Confirm the changes include new rules (`.mdc` files in `rules/`) or commands (`.md` files in `commands/`).
 
-```json
-"version": "X.X.X"
-```
+### 3. Bump Version
 
-Use semantic versioning:
+Update the version in `package.json`. Use semantic versioning:
 
-- **Patch (X.X.1)**: Minor rule updates, typo fixes
-- **Minor (X.1.0)**: New rules or commands
+- **Patch (0.1.4)**: Minor rule updates, typo fixes
+- **Minor (0.2.0)**: New rules or commands
 - **Major (1.0.0)**: Breaking changes to rule structure
 
-### 3. Commit and Push
+### 4. Commit and Push
 
 ```bash
-git add packages/agents/ && git commit -m "chore(agents): bump to vX.X.X
-
-- Brief description of changes" && git push
+git add . && git commit -m "chore: bump to vX.X.X - brief description" && git push
 ```
 
-### 4. Publish to npm
-
-From the `packages/agents` directory:
+### 5. Publish to npm
 
 ```bash
 pnpm publish --access public
 ```
 
-**Note**: You must be logged in to npm with publish access to `@karedo` scope.
+**Note**: You must be logged in to npm with publish access to `@karedo-hq` scope.
 
-### 5. Verify Publication
+### 6. Verify Publication
 
 ```bash
-npm view @karedo/agents version
+npm view @karedo-hq/agents version
 ```
 
 Confirm the version matches what you just published.
-
-## Example Output
-
-```
-✅ Changes verified in packages/agents/
-✅ Version bumped to X.X.X
-✅ Committed and pushed to remote
-✅ Published @karedo/agents@X.X.X to npm
-```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@karedo-hq/agents",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Centralized agent skills, rules, and commands for our engineering team",
   "type": "module",
   "bin": {

package/rules/web/data-fetching-and-server-actions.mdc

@@ -28,9 +28,24 @@ alwaysApply: false
 
 ### Error Handling
 
-- API errors (`!res.ok`): use `resJSON.message` directly
-- Catch block: use `getErrorMessage(error)` from `@/lib/utils/get-error-message`
-- Never use `getErrorMessage()` on strings (causes double-quoting)
+Use `parseApiResponse` from `@/lib/utils/parse-api-response` to safely parse API responses. This handles HTML error pages from proxies/load balancers gracefully (prevents cryptic "Unexpected token '<'" errors in production).
+
+```typescript
+const { data, errorMessage } = await parseApiResponse<ResponseType>(
+  response,
+  'Fallback error message',
+);
+
+if (errorMessage) {
+  return {
+    isSuccess: false,
+    isError: true,
+    errorMessage,
+  };
+}
+```
+
+**Catch block:** Use `getErrorMessage(error)` from `@/lib/utils/get-error-message`. Never use `getErrorMessage()` on strings (causes double-quoting).
 
 ### Fetch Headers