/wbSetup — Live Demo ()
What /wbSetup would actually do on wb-labs right now. The package state below — bootstrapped vs un-bootstrapped — reflects the live workspace.
1. Live target
| Field | Live value |
|---|---|
Existing packages in core2/packages/ | wb-core, wb-dataviewer, wbc-ui2-cdn, wbc-ui2 (per memory) and possibly more |
| Bootstrapped status | None obvious — no .agents/workflows/ directories visible in current workspace state |
| Memory rules to inherit | feedback_wbCode_dev_only.md, feedback_model_selection.md, project_docs_edition.md (english-only docs), feedback_no_git.md (no git ops) |
| Sibling-package convention source | wb-core if it had a context.md, but it doesn't — full bootstrap from memory |
| Most-likely setup target if user runs now | A new package the user is creating; existing core2 packages are the un-bootstrapped state, but bootstrapping them retroactively is also valid |
The "no .agents/workflows/ directories visible" reality is interesting: /wbSetup would treat every existing core2 package as "not yet bootstrapped" and offer to set them up. That's a real onboarding ritual the user could run as a follow-up to the docs sync.
2. What each input form would resolve to today
| Input | Live resolution |
|---|---|
/wbSetup core2/packages/wb-core/ | Standard setup. Inherits conventions from memory. |
/wbSetup core2/packages/wbc-ui2-cdn/ | Setup permitted but memory caution: package has parked tech debt. Setup proceeds; the conventions file would name the parked items as "what NOT to touch." |
/wbSetup core2/packages/<new>/ | Standard setup, no inherited package state. |
/wbSetup "a new auth lib" | Halt — free-text. |
/wbSetup core2/packages/wb-core/ --focus="agent-context" | Subset setup; only scaffolds the agentic layer. |
/wbSetup core2/packages/wb-core/ --scope="global" | Halt — global scope is for repo-wide setup, not a single package. |
3. Per-flag behavior, applied live
| Flag combination | Live result |
|---|---|
| (no flag) | Full setup of target package. |
--focus="agent-context" | Only .agents/workflows/ and wbc: metadata. |
--focus="i18n" | Only i18n/en.json stub. |
--focus="dev-gate" | Only the WBC_DEV pattern boilerplate (per memory rule). |
--scope="global" | Halt unless a global-scope target makes sense (rare). |
4. Pipelines
/wbSetup Live Execution Simulator
Retroactive setup of wb-core
/wbSetup core2/packages/wb-core/> /wbSetup core2/packages/wb-core/[SYSTEM] Target: core2/packages/wb-core/
[CHECK] package.json exists? Yes.
[CHECK] Already bootstrapped? No (.agents/workflows/ missing).
[CONTEXT] Reading memory:
- feedback_wbCode_dev_only.md (3-mode __WBC_DEV__ gating)
- feedback_model_selection.md (the agent/the agent declaration)
- feedback_wbCode_rule.md (:wbCode="false" in examples)
- project_docs_edition.md (the documentation docs)
[CONTEXT] No sibling package has a context.md to inherit from; full
memory-based bootstrap.
[PROPOSAL] Full setup will create:
1. core2/packages/wb-core/.agents/workflows/context.md
— initial context (will be richer than fresh because the package
has 6 days of history; existing src/, tests/ scanned).
2. core2/packages/wb-core/.agents/workflows/conventions.md
— inherited rules:
* __WBC_DEV__ 3-mode gating (full / dev / hidden)
* Examples use :wbCode="false"
* Model declaration: the agent (simple) / the agent (complex)
* English-only docs convention for any added .md
3. core2/packages/wb-core/i18n/en.json
— empty stub (UI-bearing per package role).
4. core2/packages/wb-core/.gitignore
— appended: dist*, .agents/cache/, i18n/*.tmp.json
5. core2/packages/wb-core/package.json
— added "wbc:" metadata block:
{
"wbc": {
"role": "core component library",
"devGate": "WBC_DEV",
"i18n": { "source": "en", "targets": [] },
"tier": "foundation",
"agentic": true
}
}
[CONFIRM] Proceed? [y/N] > y
[CREATE] context.md (uses /wbContext logic for content)
[CREATE] conventions.md (rules from memory)
[CREATE] i18n/en.json (empty {})
[EDIT] .gitignore (appended)
[EDIT] package.json (wbc: block added)
[OK] wb-core bootstrapped.
[NEXT STEPS]
1. /wbContext core2/packages/wb-core/ --refresh
(immediate refresh produces a richer context.md with the existing
src/ scan)
2. /wbPlan would now resolve to wb-core context if invoked there.
3. Repeat for siblings:
/wbSetup core2/packages/wb-dataviewer/
/wbSetup core2/packages/wbc-ui2-cdn/ (memory caution applies)
⚠️ Note: The most useful live invocation: bootstrap the existing wb-core package's agentic layer.
💠 Pipeline Retroactive setup of wb-core
The most useful live invocation: bootstrap the existing wb-core package's agentic layer.
💠 Pipeline Memory-aware setup of a parked package
💠 Pipeline --focus="agent-context" for an existing manual setup
A user has already manually set up wb-core's i18n and gitignore, and just wants the agentic layer:
💠 Pipeline The "already bootstrapped" notice
After Pipeline A, running /wbSetup again on wb-core:
5. What would refuse today
| Trigger | Live response |
|---|---|
/wbSetup (no target) | Halt. |
/wbSetup "an idea I have" | Halt — free-text. |
/wbSetup core2/packages/<missing>/ | Halt — directory doesn't exist. |
/wbSetup core2/packages/<exists-but-no-package.json>/ | Halt — not a package shape. |
/wbSetup on already-bootstrapped target | Notice + suggest /wbContext --refresh. |
/wbSetup --focus="<unknown>" | Halt — lists supported focus areas. |
/wbSetup --scope="global" on a single package | Halt — scope/target mismatch. |
| Setup on a parked package (wbc-ui2-cdn) | Permitted with cautious convention output. |
| Setup proposed creates files that already exist | Asks per-file: keep or overwrite? |
The pattern: /wbSetup is one-time-per-package agentic-layer bootstrapping. It refuses fuzzy targets, refuses to silently re-run on bootstrapped packages, refuses to overwrite manual setup without confirmation. Memory awareness is at its strongest here — the conventions file inherits every relevant rule, and parked items appear prominently in the "What NOT to touch" section. The output sets up the package for everything that follows: /wbContext, /wbPlan, /wbWork, all of which read what /wbSetup writes.