Migrate docs automation to skills repo

[nrichers]

What and why?

Migrate the Cursor documentation rule to a shareable skill format hosted in the new https://github.com/validmind/skills repo.

Changes:

• Update README to point to validmind/skills for the documentation skill
• Add installation instructions for Cursor Settings remote rule import
• Remove local rule and skill (now lives in validmind/skills)
• Add local rules and skills to the .gitignore to ensure we make improvements in the skills repo

Why: Skills can be shared across multiple repos via Cursor Settings, making the documentation automation available to other ValidMind repositories.

How to test

1. Clone git@github.com:validmind/skills.git.
2. In the documentation repo, install the skill via Cursor Settings → Rules, Skills, Subagents → New Skill → "Import the skill from https://github.com/validmind/skills".
3. Let Cursor do its thing.
4. Verify the skill appears in Cursor Settings under Skills but that it doesn't show up under changed files for git.
5. Test with a prompt like "Create documentation for feature X".

Dependencies, breaking changes, and deployment notes

• Depends on: validmind/skills PR (skills repo changes)
• No breaking changes — the skill functionality is identical to the previous rule

Release notes

Internal tooling change — migrates documentation automation from a local Cursor rule to a shared skill repository.

[sc-14457]

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[validbeck]

The directions in this repo's README and the skills repo README aren't accurate, even though your testing instructions in the PR more or less are ... seems kind of important!

Refer to the comments/suggestions I left — I updated the instructions based on testing / what ended up being the most seamless (less of Cursor going in circles, struggling with access to the private Skills repo even with GitHub MCP set up, writing to unnecessary files etc.) for me personally.

Can you please update the other README to have the accurate info? 🙏🏻

[github-actions]

PR Summary

This PR removes the existing Cursor rule and skill files used for generating or updating user documentation and updates the README to refer to the new documentation skill. Specifically, the files ".cursor/rules/create-user-documentation.mdc" and ".cursor/skills/create-user-documentation/SKILL.md" were removed, consolidating the functionality under the new approach. The README.md has been updated to instruct users to invoke the new skill (using the /create-user-documentation command) instead of the old rule-based workflow.

The changes focus on streamlining the documentation process by deprecating the older rule configuration and nudging users towards the new skill-based method, which offers enhanced clarity and a more direct way to generate user documentation in accordance with ValidMind style guidelines.

Test Suggestions

• Verify that invoking the new /create-user-documentation skill in a Cursor chat produces the expected prompts and behavior.
• Confirm that the README correctly explains the usage of the new skill and that all references to the old rule are removed.
• Ensure that the removal of the old rule and skill files does not impact any other functionality in the repository.
• Test the integration to check that the new skill correctly fetches the required context from Shortcut, GitHub, and attached screenshots.

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

[github-actions]

Lighthouse check results

⚠️ WARN: Average accessibility score is 0.87 (required: >0.9) — Check the workflow run

Show Lighthouse scores

Folder depth level checked: 0

Commit SHA: 9ace085

Modify the workflow to check a different depth:

• 0: Top-level navigation only — /index.html, /guide/guides.html, ...
• 1: All first-level subdirectories — /guide/.html, /developer/.html, ...
• 2: All second-level subdirectories — /guide/attestation/*.html, ...

Page	Accessibility	Performance	Best Practices	SEO
/developer/validmind-library.html	0.85	0.65	1.00	0.82
/get-started/get-started.html	0.85	0.69	1.00	0.73
/guide/guides.html	0.85	0.69	1.00	0.82
/index.html	0.93	0.66	1.00	0.82
/releases/all-releases.html	0.86	0.68	1.00	0.73
/support/support.html	0.91	0.65	1.00	0.82
/training/training.html	0.85	0.67	0.96	0.73

[nrichers]

@validbeck I removed the installation instructions from this repo, they now live only in the skills repo. Can you please approve this PR so that we don't see the rule/skill pop up in our changed files on the regular?

[validbeck]

When I follow your Cursor prompt I get the following results where Cursor has trouble accessing the repo for the subdirectories even though the repo is available locally:

Cursor transcript

I have already cloned the skills repo and have the GitHub MCP set up, so I would recommend adjusting the instructions to locate the skills subdirectories locally which I'd usually do so myself but I have no write access to skills:

skills repo cloned	GitHub MCP setup	no write access

I'm not even able to access the Settings tab in the skills repo to change any permissions as well:

[validbeck]

As I am now able to create branches/PRs for the skills repo, issues I mentioned resolved in https://github.com/validmind/skills/pull/2 (please review & approve).