lean-core: encode naming and single-source-of-truth rules in lean-contribute#12
Merged
Merged
Conversation
…tribute Two new rules in `lean-contribute` Path 3 / Plugin shape notes, prompted by review feedback on the lean-anti-ai-slop PR (#11): - Naming: kebab-case slug must carry a prefix. `<vertical>-<scope>` for plugins tied to a vertical (backend, flutter, pmo, …); `lean-<scope>` for cross-vertical or vertical-agnostic plugins (matching `lean-core`, `lean-anti-ai-slop`). Bare slugs are no longer acceptable. - Single source of truth: setup/configuration docs live canonically in the plugin README; other surfaces reference it rather than restating it. Inline copies are allowed only for runtime-printed setup, and must declare that intent. Both rules close gaps that contributors (including me, on PR #11) hit because the previous guidance was suggestive rather than prescriptive. Bumps `lean-core` to 0.3.0 (MINOR: new behavioral rules added to an existing skill). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
wzslr321
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #11 (lean-anti-ai-slop) per @wzslr321's review. Two new rules in
lean-contributeso the next contributor does not have to guess:<vertical>-<scope>for vertical-bound plugins (backend, flutter, pmo, …) orlean-<scope>for cross-vertical / vertical-agnostic plugins (matchinglean-core,lean-anti-ai-slop). Bare slugs are no longer acceptable. The previous text suggestedvertical-<scope>as "a good shape" without addressing what to do for cross-vertical plugins.README.md; other surfaces (usage SKILL, workhorse skills, top-level README) reference it rather than restating it. Inline copies are allowed only for runtime-printed setup and must declare that intent. This closes the three-way drift that bit PR anti-ai-slop: add new plugin for voice-matched writing #11 acrossREADME.md/<plugin>-usage/SKILL.md/ the drafting SKILL.Env-var naming guidance was deliberately left out per Wiktor's clarification on PR #11 — it is a per-plugin consistency concern, not systemic guidance.
lean-corebumped to 0.3.0 (MINOR: new behavioral rules added to an existing skill).Plugin shape
plugins/lean-core/.claude-plugin/plugin.jsonand.cursor-plugin/plugin.json— version 0.3.0 in syncplugins/lean-core/CHANGELOG.md— new 0.3.0 entryplugins/lean-core/skills/lean-contribute/SKILL.md— Path 3 step 1 expanded; new bullet in Plugin shape notes🤖 Generated with Claude Code