clarifying instructions around updating rules and the local trigger skill

Author: ericallam

.claude/rules/sdk-packages.md

@@ -8,5 +8,5 @@ paths:
 - Changes to `packages/` are **customer-facing**. Always add a changeset: `pnpm run changeset:add`
 - Default to **patch**. Get maintainer approval for minor. Never select major without explicit approval.
 - `@trigger.dev/core`: **Never import the root**. Always use subpath imports (e.g., `@trigger.dev/core/v3`).
-- When SDK features change, update both `rules/` directory (customer SDK docs) and `.claude/skills/trigger-dev-tasks/` skill files.
+- Do NOT update `rules/` or `.claude/skills/trigger-dev-tasks/` unless explicitly asked. These are maintained in separate dedicated passes.
 - Test changes using `references/hello-world` reference project.

CLAUDE.md

@@ -122,7 +122,7 @@ export const myTask = task({
 
 ### SDK Documentation Rules
 
-The `rules/` directory contains versioned SDK documentation distributed via the SDK installer. Current version: `rules/manifest.json`. When adding new SDK features, create a new version directory with only changed files. Keep `.claude/skills/trigger-dev-tasks/` in sync.
+The `rules/` directory contains versioned SDK documentation distributed via the SDK installer. Current version: `rules/manifest.json`. Do NOT update `rules/` or `.claude/skills/trigger-dev-tasks/` unless explicitly asked - these are maintained in separate dedicated passes.
 
 ## Testing with hello-world Reference Project
 

packages/trigger-sdk/CLAUDE.md

@@ -21,7 +21,7 @@ Always import from `@trigger.dev/sdk`. Never use `@trigger.dev/sdk/v3` (deprecat
 ## When Adding Features
 
 1. Implement the feature in the SDK
-2. Don't update the `rules/` directory at repo root
-3. Don't update the `.claude/skills/trigger-dev-tasks/` skill files
-4. Add/update docs in `docs/` (Mintlify MDX format). These will almost always be updated in a separate PR.
-5. Test with `references/hello-world` reference project
+2. Test with `references/hello-world` reference project
+3. Docs updates (`docs/`) are usually done in a separate PR
+
+Do NOT update `rules/` or `.claude/skills/trigger-dev-tasks/` unless explicitly asked. These are maintained in separate dedicated passes.