bundle-author

To scaffold a new ycc skill, use this automation to generate standardized templates under ycc/skills/, ycc/commands/, and ycc/agents/. It reads scaffolding templates and outputs file paths for SKILL.md, command.md, and agent.md with post-scaffold instructions.

Automating ycc directory setup reduces manual errors by enforcing name validation and collision checks before generating files. This ensures consistent frontmatter and references across new skills, commands, and agents without accidental overwrites.

You do not need to manually check for name collisions when creating ycc commands and agents. The scaffolding process automatically enforces name validation and collision checks to prevent conflicts and accidental overwrites.

Template validation works by enforcing name validation and collision checks before generating a new ycc skill skeleton. It reuses templates to ensure consistent frontmatter, references, and emits exact follow-up commands to sync and validate.

Yes, you can generate optional slash commands and agents alongside a new ycc skill. The scaffolding process optionally creates a matching slash command under ycc/commands/ and an agent under ycc/agents/ if requested.

When scaffolding multiple ycc surfaces, the strict name validation and collision checks prevent creating surfaces with matching names. This limitation protects existing files in the ycc/ directory from accidental overwrites during automated generation.