con un clic
new-component
Scaffold a new React component following project conventions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Scaffold a new React component following project conventions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Build and optionally serve the Gatsby production site
Build with Contentful preview API to test draft content
Start the Gatsby development server with TypeScript checking
Scaffold a new Gatsby page template with GraphQL query
Run TypeScript type checking on the project without emitting files
Basado en la clasificación ocupacional SOC
| name | new-component |
| description | Scaffold a new React component following project conventions |
| argument-hint | [ComponentName] |
Create a new React component named $ARGUMENTS following this project's conventions.
File header: Every file starts with:
/************************
* Author: [MR FERRY™] *
* <Month Year> *
************************/
Use the current month and year.
TypeScript: All components use .tsx extension with typed props.
Props interfaces: Define props interfaces in src/types/DataTypes.ts if they will be shared, or inline if
component-specific.
Imports: Use named imports. Import React explicitly.
Component style: Use function components (arrow functions), not class components. Export as default.
Styling: Use plain CSS with class names (Bootstrap 5 available). Place CSS in src/components/ alongside the
component.
Gatsby features: Use <Slice> for reusable layout parts, useStaticQuery + graphql for component-level data,
gatsby-plugin-image for responsive images.
src/components/$ARGUMENTS.tsxsrc/types/DataTypes.ts if props are sharedgit add on all new filesbun run typecheck to verify