Last Updated: December 16, 2025 Status: Active Project Version: 0.6.0 (Beta)
This is the central hub for all Synaptic Canvas documentation. Use this index to navigate to the specific information you need.
- Getting Started - Project overview and quick start guide
- Installation Guide - How to install Synaptic Canvas
- Quick Examples - Common usage patterns
PLUGIN DEVELOPMENT PATH — Use this checklist when building a plugin:
- ✓ Architecture Guidelines — Skill/agent design patterns
- ✓ Plugin Storage Conventions — Logs (
.claude/state/logs/<pkg>/), settings (.sc/<pkg>/settings.yaml), outputs - ✓ Security Scanning Guide — Validate before release
- ✓ Versioning Strategy — Version management
- ✓ CONTRIBUTING.md — PR process
Quick Questions?
- "Where do I store logs?" → Storage Conventions
- "How do I cache settings?" → Storage Conventions
- "What goes in
manifest.yaml?" → Architecture Guidelines
- Marketplace Infrastructure Guide - Complete guide to creating and operating Claude Code marketplaces
- Registry Schema - Central package registry
- Registry Documentation - Registry structure and usage
| Document | Purpose | Audience |
|---|---|---|
| README.md | Project overview, key features, quick start | Everyone |
| WARP.md | Warp terminal integration and startup | Terminal users |
| Document | Purpose | Audience |
|---|---|---|
| Architecture Guidelines | Two-tier pattern, state management, response contracts | Plugin Developers |
| Plugin Storage Conventions | Normative: Logs, settings, outputs paths and formats | Plugin Developers |
| Versioning Strategy | Three-layer versioning system, SemVer policy | Maintainers |
| CONTRIBUTING.md | Contribution guidelines, dev setup, code standards | Contributors |
| Document | Purpose | Location |
|---|---|---|
| Plugin Storage Conventions | NORMATIVE: Logs, settings, outputs paths/formats (all plugins) | docs/PLUGIN-STORAGE-CONVENTIONS.md |
| Marketplace Infrastructure | Complete guide to building and operating Claude Code marketplaces | docs/MARKETPLACE-INFRASTRUCTURE.md |
| Agent Runner | Complete guide: features, benefits, integration | docs/agent-runner-comprehensive.md |
| NuGet Integration | NuGet-specific documentation | docs/nuget/ |
| Registry Metadata | Package registry and discovery | docs/registries/nuget/ |
Each package in packages/*/ maintains its own documentation:
| Package | Version | Purpose | Key Files |
|---|---|---|---|
| sc-delay-tasks | 0.4.0 | Delayed/polled task execution | README |
| sc-git-worktree | 0.4.0 | Git worktree management | README |
| sc-manage | 0.4.0 | Synaptic Canvas package manager | README |
| sc-repomix-nuget | 0.4.0 | NuGet context generation | README |
| sc-roslyn-diff | 0.7.0 | Semantic .NET diffs with roslyn-diff | README |
→ See each package's README.md for details on usage, features, and skills
- Marketplace Platform: 0.4.0 (Beta) — See
version.yaml - All Packages: 0.4.0 (Beta) — Synchronized for marketplace consistency
- Versioning Strategy - Complete versioning policy
- Version Audit Script - Verify version consistency
- Version Management Script - Set package versions and regenerate registries
- [Version Compare Tool](.python3 scripts/compare-versions.py) - Show versions by package
- Marketplace:
CHANGELOG.md(at repo root) - Platform release history - Packages:
packages/*/CHANGELOG.md- Per-package release history (coming soon)
Located in scripts/:
| Script | Purpose | Usage |
|---|---|---|
audit-versions.py |
Verify version consistency across all artifacts | ./scripts/audit-versions.py |
set-package-version.py |
Set package versions and regenerate registries | python3 scripts/set-package-version.py NAME X.Y.Z |
compare-versions.py |
Compare versions by package | python3 scripts/compare-versions.py --by-package |
| Script | Purpose | Location |
|---|---|---|
validate-agents.py |
Validate agent frontmatter | scripts/validate-agents.py |
synaptic-canvas/
├── docs/ # Documentation hub
│ ├── DOCUMENTATION-INDEX.md # This file
│ ├── versioning-strategy.md # Versioning policy
│ ├── registries/ # Registry metadata
│ ├── nuget/ # NuGet integration docs
│ └── ...
├── packages/ # Installable packages
│ ├── sc-delay-tasks/ # Package 1
│ ├── sc-git-worktree/ # Package 2
│ ├── sc-manage/ # Package 3
│ └── sc-repomix-nuget/ # Package 4
├── scripts/ # Utility scripts
│ ├── audit-versions.py
│ ├── set-package-version.py
│ ├── compare-versions.py
│ └── ...
├── .claude/ # Claude Code configuration
│ ├── commands/ # Global commands
│ ├── skills/ # Global skills
│ ├── agents/ # Global agents
│ └── scripts/ # Global helper scripts
├── .archive/ # Historical/deprecated docs
│ ├── docs/ # Old documentation
│ └── versioned-docs/ # Historical versions
└── version.yaml # Marketplace platform version
The project uses three synchronized version layers:
- Marketplace Version (
version.yaml) - Platform/CLI infrastructure - Package Versions (
packages/*/manifest.yaml) - Per-package releases - Artifact Versions (frontmatter in
.mdfiles) - Individual components
→ See Versioning Strategy for details
Building a new plugin:
- Start with Architecture Guidelines
- Review Plugin Storage Conventions for where to read/write data
- Use the verification checklist
Installing a package:
python3 tools/sc-install.py install sc-delay-tasks --localDebugging plugin storage:
# Find logs
ls .claude/state/logs/<package-name>/
cat .claude/state/logs/<package-name>/*.json | jq .
# Find settings
ls .sc/<package-name>/settings.yaml
cat .sc/<package-name>/settings.yaml
# Find outputs
ls -R .sc/<package-name>/output/Checking version consistency:
./scripts/audit-versions.pyUpdating package version:
python3 scripts/set-package-version.py sc-git-worktree 0.5.0Running tests:
pytest -qSetting up development environment:
- See CONTRIBUTING.md
- Create a feature branch:
git worktree create feature/branch-name - Make changes and test
- Submit PR against
main
Adding a new package:
- Create
packages/new-package/ - Add
manifest.yamlwith version field - Create
commands/,skills/,agents/as needed - Update this index with package info
- Add CHANGELOG.md
- Commit and test installation
Releasing a new version:
- Update package version in
packages/*/manifest.yaml - Run
python3 scripts/set-package-version.py name X.Y.Z - Update
packages/*/CHANGELOG.md - Run
./scripts/audit-versions.pyto verify - Commit with clear message
- Create git tag:
git tag v0.5.0
- Claude Code - Official Claude Code documentation (
.claude/commands) - Claude Agent SDK - Agent development reference
- Git Worktrees - Git documentation on worktree functionality
- Issues - GitHub Issues for bug reports and features
- Discussions - GitHub Discussions for questions and ideas
- Contributing - See CONTRIBUTING.md
Old or deprecated documentation is moved to .archive/:
-
When to Archive:
- Documents superseded by newer versions
- Deprecated guides or outdated patterns
- Old versions of evolving documents
-
How to Archive:
- Move to
.archive/appropriate subdirectory - Update this index with note
- Add cross-reference in current docs linking to archived version
- Commit with clear archival message
- Move to
See .archive/README.md for full archival details.
This documentation is versioned alongside the marketplace platform:
- Changes to docs trigger versioning audit in CI/CD
- Major doc revisions should correspond to version bumps
- See Versioning Strategy for policy
Can't find what you're looking for?
- Search this index for keywords
- Check CONTRIBUTING.md for development questions
- Review package READMEs in
packages/*/ - Look in .archive/ for historical information
- Check GitHub Issues for known problems
Want to contribute documentation?
- Read CONTRIBUTING.md
- Edit relevant documentation files
- Ensure consistency with this index
- Submit PR with clear description
| Section | Status | Last Updated |
|---|---|---|
| Project Overview | ✅ Current | Nov 30, 2025 |
| Development Setup | ✅ Current | Nov 30, 2025 |
| Versioning System | ✅ Current | Dec 2, 2025 |
| Plugin Storage Conventions | ✅ NEW | Jan 22, 2026 |
| Package Documentation | ✅ Current | Dec 1, 2025 |
| Archive Structure | ✅ Current | Dec 2, 2025 |
| Tools & Scripts | ✅ Current | Dec 2, 2025 |
| Marketplace Infrastructure | ✅ Current | Dec 16, 2025 |
See something outdated? Please open an issue or submit a PR to keep documentation current!