new-module

Orchestrate sub-skills to implement a vertical slice across models, permissions, and admin UI.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/weiloon1234/Forge-Starter --skill new-module-weiloon1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-module
Source: https://github.com/weiloon1234/Forge-Starter/tree/main/.claude/skills/new-module
Command: npx skills add https://github.com/weiloon1234/Forge-Starter --skill new-module-weiloon1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating complex feature work across backend, permissions, admin UI, and ancillary services to deliver a cohesive vertical slice.

Core Features & Use Cases

  • Orchestrates a complete feature cycle by delegating to narrower skills (new-permission, new-model, admin-datatable, admin-badge, new-event-listener, jobs-and-notifications, i18n) in the correct order.
  • Ensures dependencies are wired correctly so a new model exists before admin components, permissions gate routes, and UI actions trigger side effects.
  • Typical use cases include adding a new TopUps or KYC-style module that spans schema, backend logic, admin UI, and optional events/notifications.

Quick Start

Plan the feature as a vertical slice and use this skill to orchestrate the end-to-end module wiring across models, permissions, UI, and side effects.

Frequently Asked Questions about new-module

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate a full-stack feature module across backend models, admin UI, and permissions?

To orchestrate a full-stack feature module, you coordinate sub-skills in a strict sequence: permissions, model, admin-datatable, admin-badge, event listeners, and jobs, ensuring correct dependencies and i18n integration.

What is the correct execution order for wiring backend models, migrations, and admin UI components?

The required execution order for wiring backend models and admin UI components is permissions first, then model, admin-datatable, admin-badge, event listeners, and finally jobs, validating TypeScript types throughout.

When do I need to coordinate end-to-end vertical slices for new features like KYC modules?

You coordinate end-to-end vertical slices for new features like KYC or TopUps modules when a single feature spans database schema, backend logic, admin UI, permissions, and optional events or notifications.

Can I add new admin UI components before creating the underlying backend models and migrations?

No, you cannot add admin UI components before backend models because feature module orchestration enforces dependency wiring, requiring the new model and permissions to exist prior to admin-datatable and admin-badge implementation.

How do I validate i18n and TypeScript types when building a new feature module?

You validate i18n and TypeScript types during feature module orchestration by enforcing integration checks after sequencing permissions, models, admin UI, event listeners, and jobs to ensure type safety and localization.

What's the best way to manage dependencies for feature modules that include events and jobs?

The best way to manage dependencies for feature modules with events and jobs is through vertical slice orchestration, which delegates to narrower skills and ensures UI actions correctly trigger side effects only after backend setup.