Skip to content

Move the AI skills to Fallout.Workbench and slim AGENTS.md - #712

Draft
ChrisonSimtian wants to merge 3 commits into
Fallout-build:developfrom
ChrisonSimtian:migrate-ai-material-to-workbench
Draft

ChrisonSimtian wants to merge 3 commits into
Fallout-build:developfrom
ChrisonSimtian:migrate-ai-material-to-workbench

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Collaborator

Move this repo's AI skills to Fallout.Workbench, so the core repo holds less AI material.

What changed

  • Remove .agents/ and the skills, agent and command under .claude/. The four generic items already exist in Workbench. The six core-specific skills now live in its fallout-core plugin (Workbench feat(ci): trunk-based migration — main as the only long-lived branch #10, merged).
  • Keep .claude/settings.json.
  • Shrink AGENTS.md from 12 KB to 2 KB. It now says where the rules and skills are, what the project is, and the build commands. CLAUDE.md still imports it.
  • Move the rules that people need too into CONTRIBUTING.md: backwards compatibility, no per-file license headers, plain English, and the former-maintainer rule. The other rules were already there.
  • Point the PR template, release.yml, docs/ and the .gitignore comment at Workbench.
  • Leave the ADRs alone. Two still mention .agents/. They are history.

Notes

Verification

  • git grep finds no .agents/ references outside the ADRs.
  • The six skill URLs resolve on Workbench main.

https://claude.ai/code/session_01E3qCCdUU8nWPydrxPVCLWW

The four generic items already exist there as generalised copies. The six
core-specific skills moved to its fallout-core plugin. The shared Claude Code
settings stay.

Claude-Session: https://claude.ai/code/session_01E3qCCdUU8nWPydrxPVCLWW
AGENTS.md now holds only what an AI tool needs to start: where the rules and
skills are, what the project is, and the build commands. The rules that
people need too are in CONTRIBUTING.md.

Claude-Session: https://claude.ai/code/session_01E3qCCdUU8nWPydrxPVCLWW
@ChrisonSimtian ChrisonSimtian added documentation Improvements or additions to documentation target/vCurrent Targets the current version labels Oct 15, 2026
@ChrisonSimtian ChrisonSimtian self-assigned this Oct 15, 2026
@ITaluone

Copy link
Copy Markdown
Contributor

Hmm.. if this merges, everyone with non-claude is "locked out" of these rules.

E.g. we use cursor.. cursor won't install claude plugins

@ChrisonSimtian

Copy link
Copy Markdown
Collaborator Author

Hmm.. if this merges, everyone with non-claude is "locked out" of these rules.

yep, I realised that after I raised the PR yesterday. Hence the draft status. This still needs a lot more work and claude plugins might not the best approach.

How does that work with cursor? Do they have a plugin system? How do you load external skills and agents?

@ChrisonSimtian ChrisonSimtian added skip-changelog Dont add to the Github Release Notes Dont Merge This cant be merged for various reasons (i.e. its being hold back, its broken, etc) and removed documentation Improvements or additions to documentation target/vCurrent Targets the current version labels Oct 15, 2026
@ITaluone

Copy link
Copy Markdown
Contributor

How does that work with cursor? Do they have a plugin system? How do you load external skills and agents?

I asked cursor: it got me (almost identical vs claude) plugin definitions (Fallout-build/Fallout.Workbench#11)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dont Merge This cant be merged for various reasons (i.e. its being hold back, its broken, etc) skip-changelog Dont add to the Github Release Notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants