You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README.skills.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -298,7 +298,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
298
298
| [quality-playbook](../skills/quality-playbook/SKILL.md)<br />`gh skills install github/awesome-copilot quality-playbook` | Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'. | `LICENSE.txt`<br />`agents`<br />`phase_prompts`<br />`quality_gate.py`<br />`references/challenge_gate.md`<br />`references/code-only-mode.md`<br />`references/constitution.md`<br />`references/defensive_patterns.md`<br />`references/exploration_patterns.md`<br />`references/functional_tests.md`<br />`references/iteration.md`<br />`references/orchestrator_protocol.md`<br />`references/requirements_pipeline.md`<br />`references/requirements_refinement.md`<br />`references/requirements_review.md`<br />`references/review_protocols.md`<br />`references/run_state_schema.md`<br />`references/schema_mapping.md`<br />`references/spec_audit.md`<br />`references/verification.md` |
299
299
|[quasi-coder](../skills/quasi-coder/SKILL.md)<br />`gh skills install github/awesome-copilot quasi-coder`| Expert 10x engineer skill for interpreting and implementing code from shorthand, quasi-code, and natural language descriptions. Use when collaborators provide incomplete code snippets, pseudo-code, or descriptions with potential typos or incorrect terminology. Excels at translating non-technical or semi-technical descriptions into production-quality code. | None |
300
300
|[react-audit-grep-patterns](../skills/react-audit-grep-patterns/SKILL.md)<br />`gh skills install github/awesome-copilot react-audit-grep-patterns`| Provides the complete, verified grep scan command library for auditing React codebases before a React 18.3.1 or React 19 upgrade. Use this skill whenever running a migration audit - for both the react18-auditor and react19-auditor agents. Contains every grep pattern needed to find deprecated APIs, removed APIs, unsafe lifecycle methods, batching vulnerabilities, test file issues, dependency conflicts, and React 19 specific removals. Always use this skill when writing audit scan commands - do not rely on memory for grep syntax, especially for the multi-line async setState patterns which require context flags. |`references/dep-scans.md`<br />`references/react18-scans.md`<br />`references/react19-scans.md`<br />`references/test-scans.md`|
301
-
|[react-clean-architecture-add-component](../skills/react-clean-architecture-add-component/SKILL.md)<br />`gh skills install github/awesome-copilot react-clean-architecture-add-component`| Create a new React component in src/components by asking component name and type (ui or features), then scaffold files that follow this repository rules, TypeScript strict typing, and Storybook/SCSS structure. Use when user types /add-component or asks to add a component. |`references/component-architecture.md`<br />`references/typescript-and-scss-rules.md`|
301
+
|[react-container-presentation-component](../skills/react-container-presentation-component/SKILL.md)<br />`gh skills install github/awesome-copilot react-container-presentation-component`| Create a new React component in src/components by asking component name and type (ui or features), then scaffold files that follow this repository rules, TypeScript strict typing, and Storybook/SCSS structure. Use when user types /add-component or asks to add a component. |`references/component-architecture.md`<br />`references/typescript-and-scss-rules.md`<br />`skill-additions-ja.md`|
302
302
|[react18-batching-patterns](../skills/react18-batching-patterns/SKILL.md)<br />`gh skills install github/awesome-copilot react18-batching-patterns`| Provides exact patterns for diagnosing and fixing automatic batching regressions in React 18 class components. Use this skill whenever a class component has multiple setState calls in an async method, inside setTimeout, inside a Promise .then() or .catch(), or in a native event handler. Use it before writing any flushSync call - the decision tree here prevents unnecessary flushSync overuse. Also use this skill when fixing test failures caused by intermediate state assertions that break after React 18 upgrade. |`references/batching-categories.md`<br />`references/flushSync-guide.md`|
|[react18-enzyme-to-rtl](../skills/react18-enzyme-to-rtl/SKILL.md)<br />`gh skills install github/awesome-copilot react18-enzyme-to-rtl`| Provides exact Enzyme → React Testing Library migration patterns for React 18 upgrades. Use this skill whenever Enzyme tests need to be rewritten - shallow, mount, wrapper.find(), wrapper.simulate(), wrapper.prop(), wrapper.state(), wrapper.instance(), Enzyme configure/Adapter calls, or any test file that imports from enzyme. This skill covers the full API mapping and the philosophy shift from implementation testing to behavior testing. Always read this skill before rewriting Enzyme tests - do not translate Enzyme APIs 1:1, that produces brittle RTL tests. |`references/async-patterns.md`<br />`references/enzyme-api-map.md`|
Copy file name to clipboardExpand all lines: skills/react-container-presentation-component/SKILL.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
name: react-clean-architecture-add-component
2
+
name: react-container-presentation-component
3
3
description: "Create a new React component in src/components by asking component name and type (ui or features), then scaffold files that follow this repository rules, TypeScript strict typing, and Storybook/SCSS structure. Use when user types /add-component or asks to add a component."
4
4
argument-hint: "componentName type(ui|features)"
5
5
user-invocable: true
@@ -79,4 +79,7 @@ Question requirements:
79
79
- If replacements were performed, report the list of changed files and replacement details.
80
80
- Provide one usage example of the created component.
81
81
- Report whether Storybook verification was executed (run/skip), and if run, include the command used.
82
+
- Explain why the component was classified as `ui` or `features`.
83
+
- Summarize where state, side effects, and rendering responsibilities were placed.
84
+
- Confirm whether there were any dependency direction violations.
0 commit comments