claudeers.
// Claude Skills

Foreman

A build playbook that turns your coding agent into the foreman of a website build. It interviews you, forces the design and scope decisions, locks a visual s…

Actively maintained
98/100
last commit 7 days ago
last release none
releases 0
open issues 2

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up Foreman (claude-plugin project) into my current project.
Found on https://claudeers.com/foreman-2
Repo: https://github.com/Turki-Sh/Foreman
Homepage/docs: http://foreman.turkialshuaibi.com
Detected install method: claude-plugin → /plugin install foreman@Turki-Sh/Foreman
Category: skills. Platforms: cli, api, web.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
active; community-verified: false. Confirm the source before running anything.
// or install directly (claude-plugin)
/plugin marketplace add Turki-Sh/Foreman
/plugin install foreman@Turki-Sh/Foreman
// or clone
git clone https://github.com/Turki-Sh/Foreman

// compatibility

Platformscli, api, web
Operating systems
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageHTML

Foreman

A build playbook for shipping real websites with coding agents. Not tied to any one agent: it is a folder of markdown, so it runs on Claude Code, Cursor, Windsurf, Codex, Copilot, Gemini CLI, or a chat window with no skills support at all.

foreman.turkialshuaibi.com

The Foreman site: a technical sheet on white paper, with a hand-drawn wireframe annotated with the decisions the interview forces.

Foreman's own site, built by running Foreman. If the playbook cannot produce one good page, it is not worth installing.

Coding agents removed the cost of writing a site. They did not remove the cost of deciding what it should be. So the internet now has thousands of sites that were built in an afternoon and look like each other: the same cream background, the same serif hero, the same three cards, the same accent, no domain, no metadata, no 404.

Foreman is the missing half. It turns the agent you are already talking to into a foreman: it interviews you, forces the decisions you would have delegated, locks a visual system before any code exists, writes one high-quality build brief, hands that brief to a coding agent, and then walks you through verification, DNS, and indexing until the thing is actually live.

You do not read Foreman. Your agent does.

Install

Foreman is one folder of markdown. Nothing compiles, nothing runs, so it installs anywhere an agent reads files.

Claude Code. Both lines, in this order.

/plugin marketplace add Turki-Sh/Foreman
/plugin install foreman@alshuaibi

Claude apps. Download foreman.skill and upload it as a skill.

Cursor, Windsurf, Codex, Copilot, Gemini CLI, Cline, or any other coding agent. Clone the repo and copy the skill folder where your agent looks for skills or rules.

git clone https://github.com/Turki-Sh/Foreman.git
cp -r Foreman/plugins/foreman/skills/foreman ~/.agents/skills/

Common destinations: ~/.agents/skills/, ~/.cursor/rules/, ~/.codex/skills/, or a .github/ folder in the project. See AGENTS.md for per-tool paths and for what to do if your agent has no skills directory at all.

Any assistant with no skills support, including the web chat you already have open. Paste SKILL.md into the conversation and say "run this on me." The phases work without the references; the references only deepen them.

Then say

help me build my portfolio

The agent should answer with two questions, not with code. That is the whole point.

What changes

Without ForemanWith Foreman
First moveGenerates a pageAsks what the site is for and who reads it
CopyWritten by the modelExtracted from you, with numbers
DesignWhatever the model defaults toLocked tokens you chose from three variants
ScopeEverything it can think ofExplicit non-goals, written before the build
DoneIt renders on your laptop375px, keyboard, Lighthouse, incognito, real 404
Live"Deployed"DNS, SSL, sitemap, Open Graph, submitted and indexed

What is in the box

Session flow. Seven phases with gates, written for the agent, not for you. It does not advance until each gate is met.

Nine references, loaded only when the phase arrives: content interview, design direction, stack choice, the build brief, performance and accessibility, metadata and 404, bilingual and RTL, verify and ship, and a full worked example.

Six fillable assets: a brand harness with three variants, a head metadata block with Open Graph and JSON-LD, a custom 404, robots.txt, sitemap.xml, and llms.txt.

No executable code. Foreman ships no scripts, no hooks, no MCP servers, and no slash commands. It is markdown and fill-in-the-blank templates, so you can read every line of it before you trust it. The one <script> tag in the repo is a type="application/ld+json" structured data block inside assets/head-metadata.html: inert JSON meant for your site's <head>, not code that runs when you install this.

See it run before you install it. The worked example is a full session from the first question to a frozen brief, including the thing that went wrong afterwards.

The three ideas it enforces

  1. The agent's ceiling is your brief. Model choice is a rounding error next to the quality of the specification.
  2. Non-goals are the highest-leverage lines you will write. Agents over-build by default, and one line prevents it.
  3. Decisions are yours, typing is theirs. Delegate the implementation. Delegating the judgment is what produces the default look.

Contributing

Contributions are open in some areas and closed in others. CONTRIBUTING.md says which.

The most useful thing you can send is a failure the playbook did not intercept: your build broke, and Foreman never asked the question that would have prevented it. Post it on the meta thread. The most useful pull request is an install path for an agent I cannot test.

Author

Built by Turki Alshuaibi, AI engineer. Everything in it came from shipping, and from watching capable engineers get stuck in the same nine places, which are the nine listed at the end of the skill.

License

MIT. Use it, fork it, teach with it, ship client work with it.

MIT does require attribution: the copyright notice travels with any copy or substantial portion. Beyond that legal minimum, if Foreman shaped a site you are proud of, a line in your README or a link in the post is the thing that actually helps. Credit costs you nothing and it is how a playbook finds the next person who needs it.

// faq

What is Foreman?

A build playbook that turns your coding agent into the foreman of a website build. It interviews you, forces the design and scope decisions, locks a visual system, writes the build brief, then verifies, ships, and indexes the site. Claude Code plugin and Agent Skill. Markdown only, no scripts.. It is open-source on GitHub.

Is Foreman free to use?

Foreman is open-source under the MIT license, so it is free to use.

What category does Foreman belong to?

Foreman is listed under skills in the Claudeers registry of Claude-compatible tools.

3 views
23 stars
unclaimed
updated 11 days ago

// embed badge

Foreman on Claudeers
[![Claudeers](https://claudeers.com/api/badge/foreman-2.svg)](https://claudeers.com/foreman-2)

// retro hit counter

Foreman hit counter
[![Hits](https://claudeers.com/api/counter/foreman-2.svg)](https://claudeers.com/foreman-2)

// reviews

// guestbook

0/500

// related in Claude Skills

🔓

An agentic skills framework & software development methodology that works.

// skillsobra/Shell272,506MIT[ claude ]
🔓

Public repository for Agent Skills

// skillsanthropics/Python169,406[ claude ]
🔓

💫 Toolkit to help you get started with Spec-Driven Development

// skillsgithub/Python129,208MIT[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// skillsGraphify-Labs/Python106,387MIT[ claude ]
→ see how Foreman connects across the ecosystem