HumbleDaanHumbleDaan/fabric-project-structure/.github/skills/workspace-bootstrap/SKILL.md

workspace-bootstrap

Skill0 starsChanged 2 months agoMITView on GitHub

Add a new Fabric workspace to this repository and connect it to Git. Use when the user says "new workspace", "onboard a workspace", "connect a workspace to Git", "add a project", or is setting up a new domain, project or environment in Fabric.

Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

JetXu-LLM/DocMasontheir own version, first seen Oct 8, 2026
seco/declawtheir own version, first seen Apr 4, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
JetXu-LLM/DocMason★ 152same name
seco/declaw★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- business-glossarySkill
- naming-checkSkill
- skill-nameSkill

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:
Commit and push before touching Fabric — the branch must exist remotely for Fabric to offer it.
line 56

≈ “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.

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

Files

SKILL.md

Workspace Bootstrap

Creates the repository side of a new Fabric workspace and walks the user through the Fabric side. The repo half is automatable; the Fabric half is deliberately not — connecting a workspace to Git is an action with real consequences and a human should press the button.

When to use

A new project needs its first workspace
An existing project needs another stage (test, prod) or a developer workspace
Someone asks where a new workspace folder should go

When not to use

Creating Fabric items inside an existing workspace — that happens in Fabric, then gets committed
Deployment / promotion between stages — see ../../standards/branching-and-workspaces.md

Procedure

1. Settle the names first

Derive both names from ../../standards/naming-conventions.md:

Thing	Pattern	Example
Fabric workspace	`<org>-<domain>-<stage>`	`contoso-sales-dev`
Repo directory	`ws-<workspace-name-without-org>`	`ws-sales-dev`

Confirm with the user before creating anything. Renaming a Git-connected directory later means disconnecting and reconnecting the workspace.

2. Decide project-level or new project

Workspace belongs to an existing project → projects/<project>/workspaces/
New business area → copy projects/_template/ to projects/<new-project>/ first, and fill in README.md and project-context.md. Do not leave template placeholders behind.

3. Create the repo side

projects/<project>/workspaces/
├── README.md                    ← add a row to the mapping table
├── <workspace-name>.md          ← workspace notes, OUTSIDE the synced directory
└── ws-<workspace-name>/         ← empty; Fabric fills this
    └── .gitkeep

Workspace documentation goes next to the directory, never inside it. Keep ws-*/ limited to what Fabric manages, so the diff on the first commit is only Fabric items.

Commit and push before touching Fabric — the branch must exist remotely for Fabric to offer it.

4. Hand the Fabric side to the user

Give them these steps; do not attempt them yourself:

Fabric workspace → Workspace settings → Git integration
Choose the provider (GitHub or Azure DevOps), then organisation/owner, repository, branch
Set Git folder to projects/<project>/workspaces/ws-<workspace-name>
Connect and sync
Direction on first sync:
- Workspace already has content → commit workspace → Git
- Directory already has content → update Git → workspace

Requirements to flag: the user needs workspace Admin and write access to the repo, and the workspace must sit on a Fabric capacity (F or trial), not a Pro workspace.

5. Verify

Workspace settings shows the branch and the correct folder
The first commit lands only inside ws-<workspace-name>/
Each item folder is named {DisplayName}.{Type} and contains a .platform
scripts/validate-structure.ps1 passes
projects/<project>/workspaces/README.md lists the new workspace

Failure modes

Symptom	Cause	Fix
Branch not listed in Fabric	Branch only exists locally	`git push -u origin <branch>`
Fabric commits files at repo root	Git folder left blank on connect	Disconnect, reconnect with the folder path set
Item folders named as GUIDs	Display name has forbidden characters, a trailing space/dot, or is >256 chars	Rename the item in Fabric, commit again
First sync shows conflicts	Both sides had content	Pick a direction deliberately; don't merge generated files by hand
Git integration greyed out	Not on Fabric capacity, or tenant setting disabled	Fabric admin: capacity assignment + Git integration tenant setting

../../standards/branching-and-workspaces.md — which branch this workspace should use
../../../docs/02-connect-a-workspace.md — the same walkthrough for humans
Get started with Git integration — Microsoft Learn

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.

Check your setup, free