Claude-skill-registry add-entity-field
Add a new field to an existing entity/model with related service and endpoint updates
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/add-entity-field" ~/.claude/skills/majiayu000-claude-skill-registry-add-entity-field && rm -rf "$T"
manifest:
skills/data/add-entity-field/SKILL.mdsource content
Add Entity Field Skill
Add a new field to an existing entity/model in the NovaTune project.
Steps
-
Identify the entity file
- Location:
src/NovaTuneApp/NovaTuneApp.ApiService/Models/ - File naming:
{EntityName}.cs
- Location:
-
Add the property to the entity class
public required string NewFieldName { get; set; } // Or for optional fields: public string? OptionalFieldName { get; set; } -
Update related services
- Check
for services that use this entitysrc/NovaTuneApp/NovaTuneApp.ApiService/Services/ - Update DTOs if they exist
- Update any mapping logic
- Check
-
Update endpoints
- Check
for affected endpointssrc/NovaTuneApp/NovaTuneApp.ApiService/Endpoints/ - Update request/response models if needed
- Check
-
Update RavenDB indexes if applicable
- Location:
src/NovaTuneApp/NovaTuneApp.ApiService/Infrastructure/RavenDb/ - Add field to index if it will be queried
- Location:
-
Add tests
- Unit tests:
src/unit_tests/ - Integration tests:
src/NovaTuneApp/NovaTuneApp.Tests/
- Unit tests:
Code Style
- Use
for mandatory fieldsrequired - Use nullable reference types (
) for optional fields? - PascalCase for property names
- Add XML documentation comments for public APIs