6e6ee37da0
Completes the bootstrap repo migration with remaining files: - PowerShell scripts (.ps1) for Windows support (bin/ + tools/) - Runtime adapters (claude, codex, generic, pi) - Guides (17 .md files) and profiles (domains, tech-stacks, workflows) - Wizard test suite (6 test files from bootstrap tests/) - Memory placeholder, audit history Bootstrap repo (mosaic/bootstrap) is now fully superseded: - All 335 files accounted for - 5 build config files (package.json, tsconfig, etc.) not needed — monorepo has its own at packages/mosaic/ - skills-local/ superseded by monorepo skills/ with mosaic-* naming - src/ already lives at packages/mosaic/src/
23 lines
797 B
Markdown
23 lines
797 B
Markdown
# Mosaic Profiles
|
|
|
|
Profiles are runtime-neutral context packs that can be consumed by any agent runtime.
|
|
|
|
## Layout
|
|
|
|
- `domains/`: regulated-domain and security context (HIPAA, fintech, crypto, etc.)
|
|
- `tech-stacks/`: stack-specific conventions and quality checks
|
|
- `workflows/`: reusable execution workflows
|
|
|
|
## Runtime Split
|
|
|
|
- Runtime-neutral content belongs here under `~/.config/mosaic/profiles`.
|
|
- Runtime-specific settings belong under `~/.config/mosaic/runtime/<runtime>/...`.
|
|
|
|
Current runtime overlay example:
|
|
|
|
- `~/.config/mosaic/runtime/claude/settings-overlays/jarvis-loop.json`
|
|
|
|
## Claude Compatibility
|
|
|
|
`mosaic-link-runtime-assets` prunes legacy preset symlink trees from `~/.claude` so Mosaic remains canonical and Claude uses runtime overlays that reference Mosaic paths directly.
|