Menu
Choose a descriptive repository name while keeping a stronger business/domain name for the sample scenario inside the repo.
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.
Based on SOC occupation classification
Squad branching model: main-only workflow with feature branches
{what this skill teaches agents}
Wire legacy .NET Framework service hosts through Enterprise Library-flavored appSettings so Unity, service location, exception policies, logging, and database aliases all hang off one configuration seam.
Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.
Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.
Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders.
| name | repo-vs-scenario-naming |
| description | Choose a descriptive repository name while keeping a stronger business/domain name for the sample scenario inside the repo. |
| domain | architecture |
| confidence | high |
| source | earned |
Use this pattern when a repository is both a delivery container and a branded sample system. It applies when the repo must explain its modernization or migration purpose, but the system inside it needs a memorable domain identity for solution, project, UI, and database naming.
EnterpriseModernizationSampleFabrikam Enterprise PizzaFabrikamPizza.StoreOps, FabrikamPizza.CustomerHub, FabrikamPizza_Reporting