How do I install the Module New skill?

Run npx skillmds@latest add phel-lang/module-new in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Module New skill do?

Module New It is listed under Coding & Dev Tools on SkillMD.

Is Module New safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Module New?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Module New free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Module New?

phel-lang (@phel-lang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Module New by phel-lang — Agent Skill

Name: Module New
Author: phel-lang

File contents

New Gacela Module

Scaffolds a new module under src/php/<ModuleName>/ following the project Gacela pattern.

Context

!ls src/php/

Instructions

Validate $ARGUMENTS: must be PascalCase, not clash with an existing dir. If missing, ask.
Read a reference module (pick a small one, e.g. src/php/Filesystem/ or src/php/Formatter/) to mirror its layout. Record:
- Facade method shape
- #[ServiceMap(...)] pillar mappings
- #[Provides(...)] dependency keys
- CLAUDE.md section order

Create the following files under src/php/<ModuleName>/:

<ModuleName>Facade.php          # final class extending \Gacela\Framework\AbstractFacade
<ModuleName>Factory.php         # final class extending AbstractFactory (only if module needs internal wiring)
<ModuleName>Provider.php           # only if the module depends on another module's Facade
Domain/                         # pure business logic (no framework deps)
Infrastructure/                 # adapters, CLI commands, IO
CLAUDE.md                       # one-line purpose, Gacela pattern, public API, deps, structure, constraints

Facade contract: every public call must return from the Factory; never instantiate dependencies inline in the Facade.
Explicit pillar services: import Gacela\Framework\ServiceResolver\ServiceMap and declare:
- Facade: #[ServiceMap(method: 'getFactory', className: <ModuleName>Factory::class)]
- Factory: #[ServiceMap(method: 'getConfig', className: <ModuleName>Config::class)]
- Provider: the same getConfig mapping; use AbstractConfig::class only when the module intentionally has no custom Config

CLAUDE.md template (keep scannable — no prose):

# <ModuleName>

<one-line purpose>

## Gacela pattern

Facade → Factory → Domain

## Public API

- `<ModuleName>Facade::method()` — <one line>

## Dependencies

- `<OtherFacadeInterface>::class` (via Provider)

## Structure

<ModuleName>/
  Domain/
  Infrastructure/

## Constraints

- <key invariant or rule>

Do not register the module anywhere — Gacela auto-discovers via PSR-4.
Run static analysis on the new files only:
```
composer test-quality
```

Constraints

No classes instantiated across module boundaries — always go through another module's Facade.
Do not rely on Gacela's deprecated source/docblock service-resolution fallback; every inherited pillar accessor has an explicit #[ServiceMap].
Provider entries use Gacela 2.0 #[Provides(...)]; key facade dependencies by the consumer-facing interface when one exists.
Mark classes final unless inheritance is explicitly justified.
Use readonly properties where possible (per .claude/rules/php.md).

---name: module-newdescription: Module New---# New Gacela ModuleScaffolds a new module under `src/php/<ModuleName>/` following the project Gacela pattern.## Context!`ls src/php/`## Instructions1. **Validate `$ARGUMENTS`**: must be PascalCase, not clash with an existing dir. If missing, ask.2. **Read a reference module** (pick a small one, e.g. `src/php/Filesystem/` or `src/php/Formatter/`) to mirror its layout. Record: - Facade method shape - `#[ServiceMap(...)]` pillar mappings - `#[Provides(...)]` dependency keys - CLAUDE.md section order3. **Create the following files** under `src/php/<ModuleName>/`: ``` <ModuleName>Facade.php # final class extending \Gacela\Framework\AbstractFacade <ModuleName>Factory.php # final class extending AbstractFactory (only if module needs internal wiring) <ModuleName>Provider.php # only if the module depends on another module's Facade Domain/ # pure business logic (no framework deps) Infrastructure/ # adapters, CLI commands, IO CLAUDE.md # one-line purpose, Gacela pattern, public API, deps, structure, constraints ```4. **Facade contract**: every public call must return from the Factory; never instantiate dependencies inline in the Facade.5. **Explicit pillar services**: import `Gacela\Framework\ServiceResolver\ServiceMap` and declare: - Facade: `#[ServiceMap(method: 'getFactory', className: <ModuleName>Factory::class)]` - Factory: `#[ServiceMap(method: 'getConfig', className: <ModuleName>Config::class)]` - Provider: the same `getConfig` mapping; use `AbstractConfig::class` only when the module intentionally has no custom Config6. **CLAUDE.md template** (keep scannable — no prose): ```markdown # <ModuleName> <one-line purpose> ## Gacela pattern Facade → Factory → Domain ## Public API - `<ModuleName>Facade::method()` — <one line> ## Dependencies - `<OtherFacadeInterface>::class` (via Provider) ## Structure <ModuleName>/ Domain/ Infrastructure/ ## Constraints - <key invariant or rule> ```7. **Do not** register the module anywhere — Gacela auto-discovers via PSR-4.8. **Run static analysis** on the new files only: ```bash composer test-quality ```## Constraints- No classes instantiated across module boundaries — always go through another module's Facade.- Do not rely on Gacela's deprecated source/docblock service-resolution fallback; every inherited pillar accessor has an explicit `#[ServiceMap]`.- Provider entries use Gacela 2.0 `#[Provides(...)]`; key facade dependencies by the consumer-facing interface when one exists.- Mark classes `final` unless inheritance is explicitly justified.- Use `readonly` properties where possible (per `.claude/rules/php.md`).

Frequently asked questions

Module New