| name | yo-project-workflow |
| description | Build, test, scaffold, and manage Yo projects. Use this when working with yo init, build.yo, yo build, yo compile, yo test, yo install, yo fetch, yo version, or cross-platform Yo project setup. |
| argument-hint | [project task or command] |
Yo Project Workflow
Use this skill for repository setup, build and test execution, and authoring build.yo in normal Yo projects.
If a repository wraps the Yo CLI in scripts, verify the wrapper first but keep the underlying yo workflow in mind.
When to use this skill
Use this skill when you need to:
- scaffold a new Yo project
- understand or edit
build.yo
- choose between
yo build, yo compile, and yo test
- manage dependencies with
yo install or yo fetch
- pin or manage Yo versions with
yo version
- install AI agent skill files with
yo skills install
- generate API documentation with
yo doc or build.doc()
- reason about targets, compilers, or cross-platform setup
Workflow
- If the repository has
build.yo, prefer yo build and named steps for whole-project work.
- For single-file experiments or reproductions, use
yo compile.
- For tests, use
yo test [path] and narrow to a file or pattern before broad runs.
- To pin the project to a specific Yo version, use
yo version pin.
- Consult the workflow cheatsheet for command shapes, project layout, and a minimal
build.yo.
High-signal rules
yo init scaffolds build.yo, deps.yo, src/, and tests/.build.yo is Yo code that imports std/build; build functions register compile-time steps.yo build run and yo build test are the standard project entry points.yo test ./tests/some.test.yo --parallel 1 is the focused single-file test pattern.- Use
yo install and yo fetch for git or path dependencies.
- Use
yo version pin to create a .yo-version file for reproducible builds.
- Use
yo skills install to copy Yo skill files into all agent config directories in the project.
- Prefer symbolic build APIs and target constants in
build.yo instead of ad-hoc shell logic.
Resource
