NE

new-demo-module

Quickly create new module structures in the repository.

Install

mkdir -p .claude/skills/new-demo-module && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12665" && unzip -o skill.zip -d .claude/skills/new-demo-module && rm skill.zip

Installs to .claude/skills/new-demo-module

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Scaffold a compact module-style demo boundary aligned with this repo's modular layout
85 charsno explicit “when” trigger
Beginner

Key capabilities

  • Scaffold a compact module-style demo boundary
  • Inspect existing shared-layer and module structure
  • Present a concise implementation plan
  • Create a local safety commit before implementation
  • Build the solution and run architecture tests

How it works

The skill scaffolds a new module directory structure, following specific layout rules and performing checks like building the solution and running architecture tests.

Inputs & outputs

You give it
ModuleName as argument-hint
You get back
Scaffolded module directory structure under src/Modules/<ModuleName>/ and src/Web.App/Pages/Modules/<ModuleName>/

When to use new-demo-module

  • Adding a new module for a demo
  • Creating a feature module
  • Structuring new service boundaries

About this skill

New Demo Module

Create a compact module-style boundary for $0.

Workflow Gate

Before editing files:

  1. inspect the existing shared-layer and module structure
  2. present a concise implementation plan
  3. ask one combined approval question, for example: If you approve the plan, I'll create a local safety commit first and proceed with the implementation.
  4. treat go or do it as approval plus a local safety commit
  5. if the user explicitly says to continue without the commit, skip the commit
  6. if the reply is unclear, ask again before editing files

If the user later asks to push to Git:

  1. prepare one compact final commit text
  2. show that text to the user and ask for approval
  3. after approval, squash local commits into one commit and use the approved text

If a helper script is useful for analysis or structure checks, place it under .artifacts/codex-scripts/ so it stays out of Git and can be reused later.

Target Layout

src/Modules/$0/
  $0/
    Domain/
    Application/
    DependencyInjection.cs
    $0.csproj
  $0.Infrastructure/
    Persistence/
    DependencyInjection.cs
    $0.Infrastructure.csproj

src/Web.App/Pages/Modules/$0/

Rules

  • follow the compact module layout from .codex/rules/modules.md
  • keep layer dependencies inward
  • if the module is still too small to justify dedicated projects, stop and keep the feature in the shared layers instead
  • if you add dedicated projects, register them from Web.App

Minimum Checks

  1. Build the solution.
  2. Run architecture tests.
  3. Confirm the new module folder does not bypass the shared-layer dependency flow.

When not to use it

  • When the module is too small to justify dedicated projects
  • When the user does not want a module-style demo boundary

Limitations

  • If the module is still too small to justify dedicated projects, stop and keep the feature in the shared layers instead
  • Keep layer dependencies inward

How it compares

This skill automates the creation of a modular project structure with predefined conventions and checks, ensuring architectural consistency compared to manual directory creation.

Compared to similar skills

new-demo-module side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
new-demo-module (this skill)04moNo flagsBeginner
software-architecture3336moNo flagsIntermediate
codex322moReviewAdvanced
game-development706moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

333868

codex

Lucklyric

Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.

32238

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

70195

senior-fullstack

davila7

Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.

35110

command-name

anthropics

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

697

python-project-structure

wshobson

Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.

860

Search skills

Search the agent skills registry