Skip to content

feat: Add skill for creating plugin in reusable monorepo pattern#160

Open
slesaad wants to merge 2 commits into
developmentfrom
feat/reusable-skill
Open

feat: Add skill for creating plugin in reusable monorepo pattern#160
slesaad wants to merge 2 commits into
developmentfrom
feat/reusable-skill

Conversation

@slesaad

@slesaad slesaad commented Jun 18, 2026

Copy link
Copy Markdown
Member

No description provided.

@github-actions

Copy link
Copy Markdown

🤖 Version Auto-Bumped

The version has been automatically incremented to 4.2.12-20260618

This commit was added to your PR branch. When you merge this PR, the new version will be included.


If you want a different version, update package.json manually and push to this PR.

@slesaad
slesaad marked this pull request as ready for review July 6, 2026 20:03
Comment on lines +14 to +23
Invoke when the user asks to:

- "Refactor `<Tool>` to the monorepo pattern"
- "Convert this tool to TypeScript + the new layout"
- "Build a new tool called `<Foo>` that does X" (use greenfield mode)
- "Make this look like CardDetailed in the monorepo"
- "Apply the tinacms standards to `<path>`"
- Anything where the user references **the monorepo pattern**, **BEM + blocks-**, **modern tool pattern**, or **the LayerManager pattern**

Don't invoke for unrelated MMGIS work (other tool features, bug fixes, config-only changes).

@CarsonDavis CarsonDavis Jul 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by the time an agent reads this, it will have already loaded the skill into the conversation and polluted the context window. the front matter at the top should ideally embed any when to use the skill and prevent innapropriate actuations. some of the advice, especially when not to use, could be condensed and added in the top.

@@ -0,0 +1,822 @@
---
name: mmgis-monorepo-tool-pattern
description: Use when refactoring an MMGIS tool in src/essence/Tools/ to the tinacms-portal-monorepo conventions, OR when building a new MMGIS tool from scratch in those conventions. Covers TypeScript per-component dirs, BEM with `blocks-` prefix, global Sass (not CSS Modules), USWDS theme tokens, the MMGIS adapter pattern, modern-tool-pattern config, and React 19 `createRoot` mounting.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right now this covers writing or refactoring. can we add a to trigger when planning new work relevant to these areas? (so that it is triggered when doing issue creation)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe a little bit of extra wording throughout the skill relevant to planning too? lmk what you think

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