family-sync
Skill1 starsChanged 7 days agoMITView on GitHub
How a shared change is carried to all five Lean Mean Clean Apps templates - which folders are shared, the namespace swap, opening the same branch everywhere, keeping repository and maintainer skills out of the package, and proving the copies match. Use when you have changed the Application or Infrastructure layers, their tests, shared skills, AGENTS.md, the pipeline or repository setup.
- Deletes or force-pushes
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-a-use-caseSkill
- api-conventionsSkill
- branches-and-pull-requestsSkill
- cancellationSkill
- ci-for-your-solutionSkill
- ci-pipelineSkill
- clean-architecture-layersSkill
- configuration-and-environmentsSkill
- coverageSkill
- csharp-house-styleSkill
- data-access-ef-coreSkill
- database-migrationsSkill
- docker-and-composeSkill
- docs-and-voiceSkill
- errors-and-exceptionsSkill
- expose-a-use-caseSkill
- health-checksSkill
- integration-testsSkill
- json-serializationSkill
- mapping-with-mapperlySkill
- mcp-inspectorSkill
- mediatorSkill
- optional-token-authSkill
- packages-and-dependenciesSkill
- pagingSkill
- presentation-integration-testsSkill
- releasesSkill
- sample-dataSkill
- security-findingsSkill
- serilogSkill
- telemetrySkill
- template-authoringSkill
- test-designSkill
- time-providerSkill
- unit-testsSkill
- validationSkill
- writing-a-skillSkill
- xml-docs-and-openapiSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Run in each copy, after the build:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Family sync
The rule
The five templates share everything except the Presentation layer. A shared change is made and reviewed in CleanMinimalApi first, then the same branch is opened in the other four with the same title, in this order: MCP, GraphQL, Web API, Lambda Function.
| Shared, copied as is (with the name swapped) | Per template |
src/Application, src/Infrastructure | src/Presentation |
tests/Application.Tests.Unit, tests/Infrastructure.Tests.Integration | tests/Presentation.Tests.* |
.agents/agents/jacques.md and every skill whose scope is shared, repository or maintainer | Skills whose scope is presentation |
AGENTS.md, except the Presentation rows and the presentation skills | Those rows |
.github/workflows, .github/actions, community files, Directory.Build.props, .editorconfig | .template.config/, README.md, NUGET.md |
| Template | Repository and namespace |
| Minimal API | CleanMinimalApi |
| MCP | CleanModelContextProtocol |
| GraphQL | CleanGraphQLApi |
| Web API | CleanWebApi |
| Lambda Function | CleanLambdaFunction |
Steps
- Merge-ready in CleanMinimalApi first.
For each other template, on the same branch name, copy the shared folders over and swap the name (no rsync needed):
SRC=../CleanMinimalApi; NAME=CleanWebApi for d in src/Application src/Infrastructure tests/Application.Tests.Unit tests/Infrastructure.Tests.Integration; do rm -rf "$d" && (cd "$SRC" && tar cf - "$d") | tar xf - done grep -rl CleanMinimalApi src/Application src/Infrastructure tests/Application.Tests.Unit tests/Infrastructure.Tests.Integration \ | xargs sed -i "s/CleanMinimalApi/$NAME/g"- Copy the shared skills and the persona the same way, then edit the Presentation rows of
AGENTS.mdby hand. A newrepositoryormaintainerskill also goes in theRepositorySkillslist intemplate/template.csproj, so it stays out of the package. A presentation skill with the same name in every template (expose-a-use-case,json-serialization,presentation-integration-tests) is written for each template's own code, never copied. - Prove they match with the commands under Check. There should be no differences.
- Build and test every template. Open the pull requests with the same title and description.
Don't
- Change a shared file in one template only.
- Merge the copies before the CleanMinimalApi pull request is approved.
- Copy
bin/orobj/folders.
Check
Run in each copy, after the build:
SRC=../CleanMinimalApi; NAME=CleanWebApi; SHARED="src/Application src/Infrastructure tests/Application.Tests.Unit tests/Infrastructure.Tests.Integration"
tmp=$(mktemp -d); tar cf - --exclude=bin --exclude=obj $SHARED | (cd "$tmp" && tar xf -)
grep -rl "$NAME" "$tmp" | xargs sed -i "s/$NAME/CleanMinimalApi/g"
for d in $SHARED; do diff -r --exclude=bin --exclude=obj "$SRC/$d" "$tmp/$d"; done # expect no output
dotnet build && dotnet testDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

