Menu
Anchor top-level before/after/foundation folders with short README files so later work extends the intended seam instead of guessing.
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 | seam-guide-readmes |
| description | Anchor top-level before/after/foundation folders with short README files so later work extends the intended seam instead of guessing. |
| domain | repository-structure |
| confidence | medium |
| source | earned |
Use this pattern when a repo is deliberately split into top-level seams such as before, after, foundation, or shared data folders. It is most useful early in a project, when the directory structure exists but downstream contributors still need a crisp rule for where new material belongs.
README.md at the root of each major seam (docs, docs\foundation, src, data\sqlserver, and similar roots).docs\README.md explains the split between legacy, target-state, and foundation documentation.docs\foundation\README.md states that scenario, naming, and package baselines live there.src\README.md makes the migration-state split explicit so before and after do not collapse into one code tree.