feat(skill): make react-clean-architecture-add-component self-contained with local references#1910
Conversation
…ed with local references
🔍 Skill Validator Results
Summary
Full validator output |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new /add-component skill with supporting references to standardize how React components are scaffolded under src/components.
Changes:
- Introduces the
react-clean-architecture-add-componentskill definition and procedure. - Adds reference docs for component architecture and TypeScript/SCSS rules used by the skill.
- Registers the new skill in
docs/README.skills.md.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| skills/react-clean-architecture-add-component/references/typescript-and-scss-rules.md | Documents TypeScript + SCSS constraints for the scaffolding skill. |
| skills/react-clean-architecture-add-component/references/component-architecture.md | Defines component classification, file layout, and dependency rules. |
| skills/react-clean-architecture-add-component/SKILL.md | Implements the /add-component skill workflow and output contract. |
| docs/README.skills.md | Adds the new skill to the published skills index. |
|
|
||
| ### Style Constraints | ||
|
|
||
| - Prefer Mantine first; use SCSS for gaps only. |
| - `presentation.stories.tsx` (when needed) | ||
| - `presentation.module.scss` (when needed) |
aaronpowell
left a comment
There was a problem hiding this comment.
This skill seems like it might be missing some overall context around "clean architecture" as it really seems to be focusing on a thin slice of how to define a component for React with only somewhat narrow uplift in model skill.
|
|
||
| ## When To Use | ||
|
|
||
| - When the user runs `/add-component` |
There was a problem hiding this comment.
This is incorrect based on the name of the skill and could result in the skill running at an incorrect time, or triggering another skill inadvertently.
|
|
||
| ## Required Questions | ||
|
|
||
| If any of the following information is missing, ask using `vscode_askQuestions`. |
There was a problem hiding this comment.
Use ask_user so it is not VS Code specific.
| - Do not use `any`. | ||
| - Use `type` for props instead of `interface`. | ||
| - Explicitly annotate function return types. | ||
| - Prefer `@` alias imports and avoid deep relative imports. |
There was a problem hiding this comment.
These would be better with examples for the agent to follow.
There was a problem hiding this comment.
Addressed in bae1b9d . Added code examples to the TypeScript rules reference.
…de specific dependency
06524d2 to
bae1b9d
Compare
Thank you for the feedback. I've renamed the skill to react-container-presentation-component to better reflect its scope, and added design intent, layer responsibilities, and Container/Presentation separation rules (including anti-patterns and examples) to the reference file to provide the broader design context that was missing. |
|
The README needs to be updated with the change to the skill description. Run |
|
@aaronpowell |
Pull Request Checklist
Description
Adds a new skill, react-clean-architecture-add-component, to scaffold React components under src/components with clear ui/features boundaries and strict repository conventions.
This contribution includes:
Validation performed:
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.