marcelpetrick

DarkFactory — Development skill for Claude Code

Development community

Reusable "dark factory" prompt for agentic coding harnesses (Claude Code, Codex, Pi): from a vision.md to a tested, dockerized, CI-green product with atomic commits, semver and ≥95% coverage.

How to install DarkFactory

This entry records only its repository, not the path inside it, so there is no exact command to give. Open marcelpetrick/DarkFactory and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What DarkFactory does

Reusable "dark factory" prompt for agentic coding harnesses (Claude Code, Codex, Pi): from a vision.md to a tested, dockerized, CI-green product with atomic commits, semver and ≥95% coverage.

Alternatives in Development

Ralph Loop — Autonomous coding loop — works through tasks, commits, repeats 14k ★
Agentic Stack — One brain, many harnesses 2.2k ★
Harnessrouter — HarnessRouter Community Edition: the self-hosted, Apache-2.0 edition of the unified interface for agent harnes 618 ★

README

DarkFactory

[![Markdown Lint](https://github.com/marcelpetrick/DarkFactory/actions/workflows/markdownlint.yml/badge.svg)](https://github.com/marcelpetrick/DarkFactory/actions/workflows/markdownlint.yml)

dark factory instructions for agentic software engineering. Brief and customized

Before

prepare a vision.md with the specs and requirements (is this spec-driven development?!)
prepare a Git repo and clone it locally
run your favorite harness (Codex, Claude Code, Pi ..)

Prompt

check `visions.md` and understand the goal. make a plan and implement everything described there. make decisions yourself and keep working until the whole vision is processed and we have a working product.

work directly on `main`. use git properly. atomic commits, conventional commit messages, semver. every commit bumps the patch version, major features bump the minor version. every commit must be green before commit and push. push continuously.

set up `localPipeline.sh` as early as possible, with all testing, linting, formatting, type/static checks, coverage, builds, and later e2e + docker checks. keep test coverage at least 95%. make github actions mirror the local pipeline and keep everything green.

write small reusable scripts for repetitive tasks. document all scripts properly.

first make the local version work, then dockerize it. add github actions for docker build and publish the image to ghcr.

use GPLv3. add the proper `LICENSE` file and copyright/license headers where appropriate.

update `README.md` with badges like in `cullendula` or `mylastfmplayer` under `~/repos` (or https://github.com/marcelpetrick/myLastFmPlayer). document setup, testing, pipeline, docker, and usage. include at least one real screenshot of the UI.

use unit, integration, and end-to-end tests where appropriate. do not skip requirements.

before finishing, run `/reviewBranch`, fix all issues, then run `/githubAbout`. do a final check against every item in `visions.md`, r