Added component scaffold skill#39
Merged
Merged
Conversation
feat: TaskGrid enhancements, Dataverse extensions & refactors
…de instructions; enhance agent productivity documentation
…ponent override instructions
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
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.
Add
scaffold-component-skillCopilot skillAdds a new Copilot skill at
.github/skills/scaffold-component-skill/SKILL.mdthat scaffolds new React component folders according to this repository's coding conventions.What the skill does
Invoke it with:
The skill creates a new component subfolder (kebab-case) inside the current folder and generates the canonical files:
overridableUino<ComponentName>.tsx,styles.ts,index.tsyescomponents/components.tsx,components/index.tsConventions encoded in the skill
I<ComponentName>Props, defined in the main.tsxfilemergeStyleSetsfrom@fluentui/react, factory exported asget<ComponentName>Styles, called insideuseMemoI<ComponentName>Componentsinterface + default mappings object; merged in component body as{ ...DefaultComponents, ...props.components }index.tsre-exporting the componentany, no fake business logic in generated scaffoldsWhy
Ensures every new component starts from the same structural baseline and enforces repository conventions (naming, styling, overridable UI pattern) without having to remember them or look them up.