dev-init

Generate a standard project skeleton with Docker templates and logging conventions.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/jacksen-ng/claude-workflow --skill dev-init-jacksen-ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-init
Source: https://github.com/jacksen-ng/claude-workflow/tree/main/plugins/harness-kit/skills/dev-init
Command: npx skills add https://github.com/jacksen-ng/claude-workflow --skill dev-init-jacksen-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized project structure, Docker configuration templates, and development logging conventions to reduce setup time and ensure consistency across projects. It automatically applies when initializing new projects, setting up development environments, or generating developer logs.

Core Features & Use Cases

  • Standard project skeleton including backend/ and frontend/ directories with conventional layouts and documentation templates.
  • Docker configuration templates including a full docker-compose.yml, backend and frontend Dockerfiles, and environment variable guidance.
  • Development logs and changelog scaffolding (logs/ with daily, monthly and changelog.md) to maintain traceability.
  • Usage notes and templates to accelerate project bootstrap and maintain consistency across teams.

Quick Start

Run the harness-init workflow to generate a self-contained project scaffold in your repository.

Frequently Asked Questions about dev-init

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

FAQPage Schema
How do I automatically generate a standard project skeleton with Docker templates?

You can run the harness-init workflow to automatically generate a standard project skeleton. This creates predefined backend and frontend directories, Docker configuration templates, docker-compose files, and environment settings to reduce manual setup time.

What is included in a standard project scaffold for backend and frontend directories?

A standard project scaffold includes conventional backend and frontend directory layouts, documentation templates, Docker configuration files, and a logs directory with daily, monthly, and changelog markdown files for traceability.

How do I set up Docker configuration and environment variables for a new project?

Docker configuration setup is handled by applying predefined templates for a full docker-compose.yml, backend and frontend Dockerfiles, and environment variable guidance during project initialization to ensure consistency across teams.

What's the best way to maintain development logs and changelog traceability across projects?

The best way to maintain development logs is by using a predefined logs directory structure. This includes daily, monthly, and changelog markdown templates that automatically scaffold traceability documentation for your project.

Can I use this project scaffolding tool for existing documentation tasks or only new projects?

This scaffolding tool applies to both new projects and documentation tasks. It generates development logging conventions and changelog scaffolding that can be integrated into existing repositories to standardize traceability.

Do I need any dependencies installed to create a project scaffold with development logging conventions?

No external dependencies are required to create a project scaffold with development logging conventions. The skill is self-contained and generates the standard file structure, Docker templates, and logs directly in your repository.