What problem does it solve? Adding a new Feature or Foundation module to an existing SharpPS Sitecore solution normally requires the Visual Studio "Sitecore MVC" project template wizard, whose conventions (naming, target paths, SharpPS.config token mapping, automatic Foundation ProjectReference) are undocumented inside a generated solution. This Skill captures those conventions so a new module project can be scaffolded correctly without running the wizard. ## Core Features & Use Cases - Convention-driven scaffolding: Resolves project name ($solutionpathformat$.{Layer}.<Name>), location (src\feature\<Name> or src\foundation\<Name>), and the full list of scaffolded files (Area configs, controllers, ServiceConfiguration, Web.config variants). - SharpPS.config integration: Reads version, url, area, publishpath, framework, core, and foundationpath from the solution-root SharpPS.config instead of prompting, mirroring the wizard's LoadFromConfig behavior. - Foundation reference wiring: Feature projects automatically get a <ProjectReference> to the Foundation project and no direct NuGet packages; Foundation projects get the full package list. - Use Case: A developer needs to add a new Search Feature module to an existing SharpPS Sitecore solution without Visual Studio. The Skill guides copying a sibling Feature project, renaming namespaces per the naming convention, wiring the Foundation ProjectReference, and adding the project to the solution file. ## Quick Start Add a new Feature project named Search to this SharpPS Sitecore solution following the Sitecore MVC template conventions.
