forge-setup

Detects platforms, scaffolds directories, and installs enforcement hooks for ValidationForge setup.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/krzemienski/validationforge --skill forge-setup-krzemienski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-setup
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/forge-setup/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill forge-setup-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize ValidationForge for a project by detecting platforms, scaffolding directories, installing enforcement hooks, and configuring validation posture to ensure consistent governance from the first run.

Core Features & Use Cases

  • Platform detection to identify web, API, or CLI projects and tailor the setup.
  • Directory scaffolding to create .validationforge/ and e2e-evidence/ with initial state.
  • Rules installation to deploy standard enforcement workflows to .claude/rules/.
  • Verification steps to confirm setup and readiness for validation journeys.
  • Use Case: Start a new project and automatically prepare the environment for end-to-end governance.

Quick Start

Run the forge initialization script to set up ValidationForge in a new project.

Frequently Asked Questions about forge-setup

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

FAQPage Schema
How do I scaffold validation directories and enforcement hooks for a new project?

To scaffold validation directories, run the initialization script to detect your project platform, create .validationforge/ and e2e-evidence/ folders, and wire enforcement hooks into .claude/rules/ automatically.

What is platform detection for project validation setup and when do I need it?

Platform detection for project validation setup identifies whether your codebase is a web, API, or CLI project to tailor directory scaffolding and enforcement rule installation accordingly.

Can I use this initialization process for both API and CLI codebases?

Yes, the initialization process supports web, API, and CLI codebases by detecting the platform type and tailoring the validation directory scaffolding and rules installation to match.

How do I verify that enforcement rules and validation hooks are installed correctly?

Verify enforcement rules installation by running the built-in verification checklist, which validates the strict config schema, confirms generated files exist, and checks readiness for validation journeys.

What's the best way to configure governance and validation posture from the first run?

The best way to configure governance from the first run is bootstrapping setup with an initialization script that applies a strict config schema, scaffolds required directories, and installs standard enforcement workflows.

Why does my validation setup require scaffolding specific directories like .validationforge/ and e2e-evidence/?

Validation setup requires scaffolding .validationforge/ and e2e-evidence/ directories to establish initial state and store end-to-end governance evidence, ensuring consistent validation posture across the project lifecycle.