agentleFS
fabioc-alohafabioc-aloha/Alex_ACT_ONE/skills/bootstrap-project/SKILL.md

bootstrap-project

Skill0 starsChanged 9 days agoMITView on GitHub

Previews and applies this plugin's repository scaffold, portable workspace QoL settings, and project Copilot settings while preserving project-owned files. Use for new repositories, missing AGENTS/HANDOFF/episodic files, or project .vscode setup.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After explicit repository consent, rerun with --apply.

    line 27
  2. Very specific:

    Do not create MEMORY.md, README, license, framework, package manager, or Git.

    line 55
  3. Distinctive:

    Do not edit VS Code user settings or configure shared continuity.

    line 56
  4. Distinctive:

    Use one explicit repository root.

    line 74

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bootstrap Project

Set up one repository with this plugin's project-local guidance and a portable VS Code workspace baseline. The baseline covers editor, diff, Markdown, file/search, terminal, and Git QoL preferences. Its PowerShell profile keys are Windows-scoped and are ignored on macOS, where the system default shell applies. It never edits user settings, configures extensions, or configures shared continuity.

Preview First

node <this-skill>/scripts/bootstrap-project.cjs --repository-root <path>

The preview classifies agent guidance, nested contracts, missing scaffold files, settings additions and .gitignore changes. It writes nothing.

Apply After Consent

After explicit repository consent, rerun with --apply. Existing files are preserved. Settings are additive: missing keys and nested map entries are added, while project values remain authoritative. Markdown Preview uses VS Code's user-level defaults; optional personal styling belongs in the user profile, not project configuration.

The minimal scaffold is AGENTS.md, thin Claude/Gemini adapters, HANDOFF.md, .github/episodic/README.md, .vscode/settings.json, and a narrow .gitignore exception for the managed settings file.

New AGENTS.md scaffolds include repository artifact storage guidance derived from the shared contract. Existing guidance remains preserved; propose a scoped manual merge rather than silently overwriting it. Project adoption is not global instruction activation. For GitHub HTTPS remotes where multiple gh accounts are used, also preview repository Git auth pinning so non-interactive agent pushes do not fail on global account switches.

Boundaries

  • One explicit repository root per invocation.
  • Divergent root AGENT.md and AGENTS.md block apply.
  • A lone legacy AGENT.md also blocks apply pending an explicit migration decision; bootstrap does not create a competing AGENTS.md.
  • Existing handoff, episodic, agent, and settings files are preserved.
  • Post-apply verification must be unblocked with no pending scaffold, settings, or .gitignore changes.
  • Comment-rich JSONC requiring changes fails closed for manual merge.
  • Do not create MEMORY.md, README, license, framework, package manager, or Git.
  • Do not edit VS Code user settings or configure shared continuity.

Anti-Patterns

Anti-patternCorrection
Route this through another pluginThis plugin owns required project setup
Replace custom project settingsAdd only missing baseline entries
Configure a project Markdown stylesheetUse VS Code's user-level defaults instead
Configure shared continuityKeep work in repository continuity until a separately approved capability exists

Would Revise If

Revise if project bytes are overwritten, a second preview is not idempotent, user settings are touched, or the baseline proves non-portable.

Compatibility command constraints: bootstrap-project

Use one explicit repository root. Preview first; preserve existing project files and settings. Apply only after repository consent.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.