Agent skill

React Container Presentation Component Skill

This GitHub skill scaffolds a React component with the Container and Presentation pattern, asking for the name and type first, then creating files that follow your repository rules.

Install
git clone https://github.com/github/awesome-copilot.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

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.