Create a new page skill and no docs director rule

.cursor/skills/navigation-button-add/SKILL.md

@@ -16,8 +16,7 @@ description: Implements a new Sales navigation button with the existing highligh
    - Set `buttonColor` to `#ffffff` (inactive) unless the new button replaces the active page; then set its own definition (`on the relevant page`) to `appsmith.theme.colors.backgroundColor`.
    - Ensure `dynamicBindingPathList` stays empty when `buttonColor` is static white; populate it only if the button needs dynamic logic.
    - Point `onClick` to `navigateTo` the new page slug and keep `placement`/`responsiveBehavior` matching other nav buttons.
-4. **Update documentation**: After modifying navigation, update `docs/README.md` with a short note about the new button and its color behavior.
-5. **Run git status/diff** to verify only the intended files changed before reporting back.
+4. **Run git status/diff** to verify only the intended files changed before reporting back.
 
 ## Examples
 
@@ -26,5 +25,4 @@ description: Implements a new Sales navigation button with the existing highligh
  2. Set `text` to “Units Ordered”, `onClick` to `navigateTo('Sales - Units Ordered', {}, 'SAME_WINDOW');`.
  3. Assign `buttonColor` to `#ffffff` for inactive cases and to `appsmith.theme.colors.backgroundColor` inside the `Sales - Units Ordered` page definition for highlight.
  4. Adjust `bottomRow` incrementally so buttons stack vertically.
- 5. Mention the update in `docs/README.md`.