Menú
Build a believable mid-2000s Web Forms portal shell that fronts older sidecar web apps without collapsing them into one surface.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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 | legacy-web-portal-shell |
| description | Build a believable mid-2000s Web Forms portal shell that fronts older sidecar web apps without collapsing them into one surface. |
| domain | web-forms |
| confidence | medium |
| source | earned |
Use this when a legacy sample needs a main intranet or partner portal, but the repo already contains more specialized Web Forms or MVC applications. The portal should feel like a polished front door layered on top of an already messy estate.
/CustomerHub/..., /FranchisePortal/..., /Storefront/) instead of pretending everything lives in one clean application.DataTable binding in the before-state unless a work item explicitly asks for deeper service/data integration.