diff --git a/context/skills/omnibus/instrument-error-tracking/description.md b/context/skills/omnibus/instrument-error-tracking/description.md index 6c0f4f35..8e923750 100644 --- a/context/skills/omnibus/instrument-error-tracking/description.md +++ b/context/skills/omnibus/instrument-error-tracking/description.md @@ -46,7 +46,7 @@ STEP 7: Set up environment variables. STEP 8: Verify and clean up. - Check the project for errors. Look for type checking or build scripts in package.json. - Ensure any components created were actually used. - - Run any linter or prettier-like scripts found in the package.json. + - Run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase. ## Reference files diff --git a/context/skills/omnibus/instrument-integration/description.md b/context/skills/omnibus/instrument-integration/description.md index 1e00ff9c..745d3eec 100644 --- a/context/skills/omnibus/instrument-integration/description.md +++ b/context/skills/omnibus/instrument-integration/description.md @@ -40,7 +40,7 @@ STEP 6: Set up environment variables. STEP 7: Verify and clean up. - Check the project for errors. Look for type checking or build scripts in package.json. - Ensure any components created were actually used. - - Run any linter or prettier-like scripts found in the package.json. + - Run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase. ## Reference files diff --git a/context/skills/omnibus/instrument-product-analytics/description.md b/context/skills/omnibus/instrument-product-analytics/description.md index c9a507fe..d2c6f6ab 100644 --- a/context/skills/omnibus/instrument-product-analytics/description.md +++ b/context/skills/omnibus/instrument-product-analytics/description.md @@ -55,7 +55,7 @@ STEP 9: Set up environment variables. STEP 10: Verify and clean up. - Check the project for errors. Look for type checking or build scripts in package.json. - Ensure any components created were actually used. - - Run any linter or prettier-like scripts found in the package.json. + - Run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase. ## Reference files