artifacts

Scaffold runnable artifacts and generate artifact.toml metadata in a monorepo.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/YSheldon/Prompt-Log --skill artifacts-ysheldon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifacts
Source: https://github.com/YSheldon/Prompt-Log/tree/main/.local/skills/artifacts
Command: npx skills add https://github.com/YSheldon/Prompt-Log --skill artifacts-ysheldon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and bootstrap runnable artifacts within a monorepo by scaffolding new artifacts and producing artifact.toml metadata.

Core Features & Use Cases

  • Bootstraps artifacts under artifacts/<slug>/ and writes artifact.toml with metadata
  • Scaffolds project files, wires the shared backend, and allocates service ports for preview
  • Use cases include web, mobile, slides, video, and data-visualization artifacts

Quick Start

Call createArtifact() with artifactType, slug, previewPath, and title to bootstrap a new artifact.

Frequently Asked Questions about artifacts

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

FAQPage Schema
How do I bootstrap runnable artifacts in a monorepo with proper metadata?

To bootstrap runnable artifacts in a monorepo, scaffold new projects under artifacts/<slug>/ and generate an artifact.toml metadata file. This process wires the shared backend, allocates service ports for preview, and configures frontend scaffolding.

What is the best way to scaffold new web, mobile, or data-visualization artifacts in a monorepo?

Scaffolding new web, mobile, slides, video, or data-visualization artifacts is best handled by a bootstrap workflow that requires artifactType, slug, previewPath, and title to initialize projects and generate artifact.toml metadata.

What metadata fields are required to initialize artifacts and configure a previewPath?

Initializing artifacts and configuring a previewPath requires the metadata fields artifactType, slug, previewPath, and title. This bootstrap workflow generates the artifact.toml file needed to run the project within the monorepo.

Can I wire optional resources like scripts, references, and assets when scaffolding a new artifact?

Yes, when scaffolding a new artifact, you can wire optional resources under the scripts/, references/, and assets/ directories. This allows you to include supporting code, documentation, and media alongside the runnable project files.

Does the artifact scaffolding workflow support multiple artifact types like slides and video?

The artifact scaffolding workflow supports multiple artifact types including web, mobile, slides, video, and data-visualization. It enforces a bootstrap process that writes artifact.toml metadata and configures preview paths for each type.

Why does my artifact bootstrap workflow fail without a slug or title in the monorepo?

The artifact bootstrap workflow fails without a slug or title because it enforces mandatory fields to initialize artifacts. artifactType, slug, previewPath, and title are all required to produce the artifact.toml metadata and scaffold the project correctly.