Run any Skill in Manus with one click

new-sample-feature

Stars0

Forks0

UpdatedApril 14, 2026 at 09:18

Guide for adding new features (or aggregates) to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new features, aggregates or CRUD endpoints to the Samples or Sample projects.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

synonms

synonms/structur

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	new-sample-feature
description	Guide for adding new features (or aggregates) to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new features, aggregates or CRUD endpoints to the Samples or Sample projects.

Consider the following skills when adding new features to a consuming project:

/new-aggregate-root - for adding new aggregate roots.
/new-aggregate-member - for adding new aggregate members.
/new-value-object - for adding new value objects.
/new-domain-event-handlers - for adding new in-process domain event handlers.
/new-projection - for adding new aggregate projections.
/new-integration-tests - for adding integration tests for the new feature.

To add new features to the Sample projects, follow this process:

Determine the aggregate name (singular) and collection name (plural) for the new feature. For example, if you are adding a "Employee" feature, the aggregate name would be "Employee" and the collection name (used for the URL root path) would be "products".
Determine the target consuming API project and Client API project for the new feature. For example, Synonms.Structur.Sample.Api and Synonms.Structur.Sample.ClientApi respectively.
If it does not already exist, create a destination folder for the new feature in the consuming Client API project as {ClientApiProject}/Features/{CollectionName}. For example, Synonms.Structur.Sample.ClientApi/Features/Employees. This will contain the shared backend/frontend code. In this folder:
- Create any client resources as required by the feature.
If it does not already exist, create a destination folder for the new feature in the consuming API project as {ApiProject}/Features/{CollectionName}. For example, Synonms.Structur.Sample.Api/Features/Employees. This will contain the backend code. In this folder:
- Create any Value Objects and Aggregate Members along with the Aggregate Root as required by the feature.
- Create any domain events, event handlers and projections as required to support the feature.
If it does not already exist, create a destination folder for the new feature integration tests in the consuming Integration Test project as {IntegrationTestProject}/Features/{CollectionName}. For example, Synonms.Structur.Sample.Tests.Integration/Features/Employees. This will contain the integration test code. In this folder:
- Create any integration tests as required by the feature.

More from this repository

same repository

new-aggregate-root

synonms/structur

Guide for adding new Aggregate Roots to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new aggregates or aggregate roots to any consuming projects.

2026-04-220

new-value-object

synonms/structur

Guide for adding new Value Object classes to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new features, aggregates or CRUD endpoints to any consuming projects and a new value object is required, or if asked to add a new value object to an existing aggregate.

2026-04-220

new-aggregate-member

synonms/structur

Guide for adding new Aggregate Members to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new features, aggregates or CRUD endpoints to any consuming projects and a new aggregate member is required, or if asked to add an aggregate member to an existing aggregate.

2026-04-140

new-domain-event-handlers

synonms/structur

Guide for adding new in-process domain event handlers to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new domain event handlers to the Samples or Sample projects.

2026-04-140

new-integration-tests

synonms/structur

Guide for adding integration tests for aggregate features in the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new integration tests for features, aggregates or CRUD endpoints in the Samples or Sample projects.

2026-04-140

new-projection

synonms/structur

Guide for adding new aggregate projections to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new projections to the Samples or Sample projects.

2026-04-140

name	new-sample-feature
description	Guide for adding new features (or aggregates) to the internal Sample projects or to any projects consuming the Structur framework. Use this when asked to add new features, aggregates or CRUD endpoints to the Samples or Sample projects.

Consider the following skills when adding new features to a consuming project:

/new-aggregate-root - for adding new aggregate roots.
/new-aggregate-member - for adding new aggregate members.
/new-value-object - for adding new value objects.
/new-domain-event-handlers - for adding new in-process domain event handlers.
/new-projection - for adding new aggregate projections.
/new-integration-tests - for adding integration tests for the new feature.

To add new features to the Sample projects, follow this process:

Determine the aggregate name (singular) and collection name (plural) for the new feature. For example, if you are adding a "Employee" feature, the aggregate name would be "Employee" and the collection name (used for the URL root path) would be "products".
Determine the target consuming API project and Client API project for the new feature. For example, Synonms.Structur.Sample.Api and Synonms.Structur.Sample.ClientApi respectively.
If it does not already exist, create a destination folder for the new feature in the consuming Client API project as {ClientApiProject}/Features/{CollectionName}. For example, Synonms.Structur.Sample.ClientApi/Features/Employees. This will contain the shared backend/frontend code. In this folder:
- Create any client resources as required by the feature.
If it does not already exist, create a destination folder for the new feature in the consuming API project as {ApiProject}/Features/{CollectionName}. For example, Synonms.Structur.Sample.Api/Features/Employees. This will contain the backend code. In this folder:
- Create any Value Objects and Aggregate Members along with the Aggregate Root as required by the feature.
- Create any domain events, event handlers and projections as required to support the feature.
If it does not already exist, create a destination folder for the new feature integration tests in the consuming Integration Test project as {IntegrationTestProject}/Features/{CollectionName}. For example, Synonms.Structur.Sample.Tests.Integration/Features/Employees. This will contain the integration test code. In this folder:
- Create any integration tests as required by the feature.