he-init

Initialize a pristine Heracles project by configuring structure and templates.

Updated Jul 23, 2025
One-click install
npx skills add https://github.com/data-players/Marker-OCR-API --skill he-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: he-init
Source: https://github.com/data-players/Marker-OCR-API/tree/main/.heracles/agents/skills/he-init
Command: npx skills add https://github.com/data-players/Marker-OCR-API --skill he-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initializes a pristine Heracles project by dialoguing on architecture, creating the project constitution, architecture specs, and initial folder structure.

Core Features & Use Cases

  • Interactive architecture planning: guides the user through choosing a stack and architecture.
  • Constitution & PRD generation: creates baseline project rules and a product requirements document.
  • Project scaffolding: builds the initial directory layout and template placeholders to start development.

Quick Start

Guide the user to choose an architecture and stack, then scaffold the new Heracles project structure.

Frequently Asked Questions about he-init

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

FAQPage Schema
How do I scaffold a new project with architecture and conventions defined upfront?

Project scaffolding interactively guides you through choosing a stack, generating a baseline constitution and PRD, and creating the initial directory layout and template placeholders to establish conventions before development begins.

What is included in the initial project setup for a fresh codebase?

Initial project setup includes interactive architecture planning, baseline constitution and PRD generation, and project scaffolding to build a ready-to-run directory layout with template placeholders from a virgin state.

Can I use this project initialization tool on an existing codebase with established files?

This project initialization tool applies to virgin projects only, where architecture, stack, and conventions must be defined from scratch before development begins, rather than integrating into an existing codebase.

What's the best way to define project architecture and stack before starting development?

The best way to define project architecture is through an interactive dialogue that chooses the stack and architecture, generates a project constitution and PRD, and produces an initial ready-to-run project state.

Do I need to manually create directories and templates during project setup?

You do not need to manually create directories and templates. The setup automatically configures the project structure, copies templates, and produces an initial ready-to-run state by dialoguing on architecture.