op-component-factory

Automates creation of new components with customizable options and built-in validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MiguelAguiarDEV/baymax --skill op-component-factory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: op-component-factory
Source: https://github.com/MiguelAguiarDEV/baymax/tree/main/skills/op-component-factory
Command: npx skills add https://github.com/MiguelAguiarDEV/baymax --skill op-component-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of new components (skills, agents, commands, modes) within the OpenCode ecosystem, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Automated Scaffolding: Generates boilerplate code and configuration files for new components.
  • Consistent Templating: Ensures all new components follow a standardized structure.
  • Integrated Validation: Prompts for and guides users through necessary checks and sync processes.
  • Use Case: A developer needs to quickly create a new skill to process user feedback. They use the component factory to generate the basic structure, then fill in the specific logic and run validation checks.

Quick Start

Use the op-component-factory skill to create a new skill named 'user-feedback-processor' with the description 'Processes incoming user feedback'.

Frequently Asked Questions about op-component-factory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold new OpenCode components like skills and agents?

To scaffold new OpenCode components, use predefined templates to generate boilerplate code and configuration files. This ensures all new skills, agents, commands, and modes follow a standardized structure and adhere to naming conventions.

What is the best way to automate component creation for OpenCode?

Automating component creation involves using scaffolding scripts that generate boilerplate code with integrated validation workflows. This facilitates consistent development practices by prompting users through necessary checks and frontmatter requirements during generation.

How does component scaffolding enforce consistent code generation practices?

Component scaffolding enforces consistent code generation by applying predefined templates and validation workflows. It ensures adherence to required naming conventions and frontmatter rules, guiding developers through necessary sync and doctor script checks.

Can I use scaffolding scripts to generate boilerplate code for custom commands?

Yes, you can use scaffolding scripts to generate boilerplate code for custom commands. The factory creates the basic component structure, allowing you to fill in specific logic and run validation checks for OpenCode commands and modes.

Do I need to run validation workflows after scaffolding new components?

Yes, you need to run validation workflows after scaffolding new components. The process integrates with existing sync and doctor scripts, prompting you through necessary checks to ensure frontmatter requirements and naming conventions are met.

What are the limitations of using predefined templates for component creation?

Using predefined templates for component creation limits structural customization to standardized boilerplate code. While it ensures consistent development practices and naming conventions, developers must manually fill in specific logic after generating the basic component structure.