What is the react-container-presentation-component skill?
React-container-presentation-component is a skill in the github/awesome-copilot repository. It asks for a PascalCase component name and a type, ui or features, then scaffolds the files, runs build and lint, and reports why the component was classified that way.
It is a user-invocable skill in the github/awesome-copilot repository. Run it as a slash command with a component name and a type, and it creates a React component under src/components that follows the Container and Presentation pattern.
What changes in your agent's output
- It asks questions first if the name or type is missing, with ui and features offered as options and a PascalCase name required.
- It checks whether the component folder already exists and does not overwrite it without confirming.
- A ui component gets index.tsx, index.module.scss and index.stories.tsx.
- A features component gets index.tsx, a use hook file, presentation.tsx, types.ts, a presentation SCSS module and a stories file.
- If a ui request includes state, side effects, async work or business logic, it is reclassified as features after you confirm.
What it reports at the end
The output contract asks for the list of created files, one usage example, whether Storybook was run or skipped, why the component is ui or features, where state and rendering live, and any dependency direction violations or unresolved items.
Who the skill is for
Best for
- React and TypeScript repositories that already split components into ui and features folders.
- Teams with Storybook and SCSS modules who want every new component to arrive with stories.
- Reviewers who want each component's state, effects and rendering responsibilities written down.
Not for
- Projects without src/components, Storybook or SCSS modules, since the file layout assumes them.
- One-off quick components where a full scaffold is more than you need.
- Visual design decisions. It scaffolds structure and does not choose colors or layout.
After scaffolding, style the component with tailwind-design-system if you use Tailwind, or review the result with frontend-design-review. Both are separate skills.
How to install React Container Presentation Component
git clone https://github.com/github/awesome-copilot.gitThe repository README warns that its customizations come from third-party developers, so read the skill before installing it.Clone the repository
Run
git clone https://github.com/github/awesome-copilot.git. The skill is the skills/react-container-presentation-component folder.Copy the skill folder
Copy the folder, including its references folder with component-architecture.md and typescript-and-scss-rules.md, into your agent's skills folder.
Check your repository layout
The skill expects src/components with ui and features folders, TypeScript, Storybook and SCSS modules.
Run the command
Run /react-container-presentation-component with a name and type, for example a PascalCase name and ui.
Check that it loaded
Run the command with a name and the ui type. The agent should create the three ui files, run build and lint, and ask before running Storybook.
Key features
- Slash command entryRuns from the react-container-presentation-component command, with an argument hint of component name and type.
- Question firstUses ask_user to collect the component name, the type and whether to replace existing components.
- Existing folder checkLooks for the ui or features folder before creating files and asks how to proceed if it exists.
- ui file setCreates index.tsx, index.module.scss and index.stories.tsx for presentational components.
- features file setCreates index.tsx, a use hook, presentation.tsx, types.ts, a presentation SCSS module and stories.
- Reclassification ruleTreats a ui request with state, side effects, async processing, context or store updates, or business logic as features.
- Optional replacementWith approval, swaps direct Mantine or other UI library use in existing features for the new ui component.
- Build and lintRuns build and lint and fixes issues introduced by the new files.
- Storybook choiceAsks whether to run Storybook and states in the report if it was skipped.
Frequently asked questions
What is the react-container-presentation-component skill?
It is a skill in github/awesome-copilot that scaffolds React components using the Container and Presentation pattern. It asks for the name and whether the component is ui or features, then creates files that follow the repository's TypeScript, Storybook and SCSS conventions.
How do I install it?
Clone github/awesome-copilot and copy the skills/react-container-presentation-component folder, along with its references, into your agent's skills folder. The repository README describes a plugin install for bundles, but this skill lives in the skills folder.
What is the difference between ui and features here?
A ui component is presentational and gets three files. A features component has a hook, a presentation file and types. If a ui request needs state, effects, async work or business logic, the skill asks you to create it as features.
Does it overwrite existing components?
No. It checks for a ui or features folder under src/components with the same component name first. If that folder exists it does not overwrite anything and asks you to confirm the approach you prefer.
Does it run Storybook automatically?
No. It asks you through ask_user whether to run Storybook and starts npm run storybook only if you choose to run it. If you skip, the final report says Storybook execution was skipped.
Can I use it without Storybook or SCSS?
The skill is written for a repository with Storybook and SCSS modules and its file lists include both. You can adapt the SKILL.md and its two reference files to your own conventions before you install it.
What should I use for the styling afterwards?
This skill sets structure only and leaves the look to you. For utility class patterns see tailwind-css-patterns, and for a final visual pass use polish. Neither is needed for the scaffold itself.


