Skip to content

chore: move Cursor skills/rules to MeshFlow umbrella#392

Merged
pskillen merged 1 commit into
mainfrom
chore/pskillen/consolidate-cursor-skills
Jun 3, 2026
Merged

chore: move Cursor skills/rules to MeshFlow umbrella#392
pskillen merged 1 commit into
mainfrom
chore/pskillen/consolidate-cursor-skills

Conversation

@pskillen
Copy link
Copy Markdown
Owner

@pskillen pskillen commented Jun 3, 2026

Summary

Consolidates the per-repo Cursor skills and rules into the shared MeshFlow umbrella workspace (~/IdeaProjects/MeshFlow/.cursor/) to remove cross-repo duplication. The meshflow-git-workflow skill in particular was duplicated (with only minor variations) across meshflow-api, meshflow-bot, meshflow-ui and meshflow-rf-propagation.

This PR removes the following from meshflow-api (now living in the umbrella):

  • Skills: meshflow-git-workflow, mf-feature-docs, progress-tracking
  • Rules: django-dont-install-stuff, mf-feature-docs

References in AGENTS.md (pre-prod / preprod-database skill) and docs/features/meshcore/README.md (progress-tracking skill) are updated to point at the umbrella location.

Background

The shared skills are only auto-discovered when the MeshFlow umbrella folder is part of the Cursor workspace (same pattern already used by the existing preprod-database and push-to-dev skills). Opening a single repo standalone will no longer surface these skills.

Testing performed

  • Verified .cursor/ is fully removed from the repo and the consolidated copies exist in the umbrella.
  • No application code changed.

Skills (meshflow-git-workflow, mf-feature-docs, progress-tracking) and rules
(django-dont-install-stuff, mf-feature-docs) are now consolidated in the
MeshFlow umbrella workspace (~/IdeaProjects/MeshFlow/.cursor) to remove
cross-repo duplication. Update AGENTS.md and meshcore docs references.
@pskillen pskillen merged commit 347a35c into main Jun 3, 2026
2 checks passed
@pskillen pskillen deleted the chore/pskillen/consolidate-cursor-skills branch June 3, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants