Mern kit

Skill edfenton/claude-skills/mern/mern-kit

A collection of Claude Code skills for iOS, MERN, NEAN, and shared development workflows

Install

npx -y skills add edfenton/claude-skills --skill mern-kit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Startup runbook for MERN projects. Establishes stack decisions, scaffolds the project, configures GitHub security, and confirms governing constraints.

SKILL.md

3.2 KB, as published. Nobody here has run it

Purpose

Initialize a new MERN project with the standard stack, scaffolding, GitHub security, and constraints.

Input: <app-name> (optional, default: "app"). Use . to scaffold in the current (empty) directory.

Startup sequence (run in order)

1. Confirm stack decisions

/mern-stack

Establishes: toolchain, monorepo layout, Next.js conventions, database approach, environments.

2. Scaffold the project

/mern-scaffold <app-name> [--github]

Creates: build-green baseline with CI, tests, shared packages, server utilities, tooling.

The scaffold step includes git init at the end.

3. Set up local Git hooks

Prerequisite: The scaffold step must have completed git init first.

/github-hooks --platform mern

Installs: Husky + lint-staged, pre-commit validation (lint, format, secrets), commit message enforcement, pre-push tests.

4. Configure GitHub security (if --github was used)

/github-secure

Applies: branch protection, Dependabot alerts, auto-merge. Skips files already created by scaffold.

5. Verify constraints are active

Confirm these always-on skills are enabled:

mern-sec — security policy
mern-nfr — non-functional requirements
mern-std — coding standards
mern-styleguide — design/UX standards

6. Verify CI passes (if --github)

Trigger CI and wait for it to complete:

gh workflow run ci.yml --ref main (or wait for push-triggered run)
gh run watch --exit-status — blocks until complete, exits non-zero on failure

If failed: a. Read logs: gh run view --log-failed b. Fix the issue locally c. If push to main is blocked by branch protection, temporarily disable enforcement:

REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
gh api -X PATCH "/repos/$REPO/branches/main/protection/enforce_admins" -f enforcement=false
git push
gh api -X POST "/repos/$REPO/branches/main/protection/enforce_admins"

d. Push and re-run: gh run watch --exit-status

Repeat step 3 until CI is green
Do NOT mark kit complete until CI is green

Quality workflows (invoke as needed)

/mern-unit-test — run tests, report failures, fix with approval
/mern-code-review — review against policies, fix with approval
/mern-design-review — visual review with Playwright, fix with approval

Additional workflows (invoke as needed)

/mern-add-feature — scaffold new features
/mern-add-auth — add authentication
/mern-deploy — prepare for deployment
/mern-e2e — E2E test management
/mern-api-docs — generate API documentation
/mern-deps — dependency management
/mern-teardown — tear down project and optionally delete GitHub repo

Output

After running this kit, confirm:

Stack decisions applied
Project scaffolded and building
Local Git hooks installed (pre-commit, commit-msg, pre-push)
GitHub security configured (if --github)
CI passes on GitHub (if --github)
Governing constraints active
Quality workflows available