- Never commit docs created for planning. If confused, ask which new
.mdfiles should be committed. - Keep the GitHub-facing repo limited to source, tests, package metadata, examples, and polished user documentation.
- Do not add or stage planning, research, marketing, agent-workflow, or task-tracking artifacts. This includes
.sisyphus/,.agents/,tasks/,marketing/,docs/plans/,docs/superpowers/,front-facing-api.md,docs/RESEARCH_*.md, and one-off comprehensive guide drafts. - If a planning or research note contains still-useful public information, move only the polished, verified content into
README.md, DocC, or the VitePress docs. Do not commit the working note itself. - Before committing, check staged files and untracked files for internal artifacts. Remove or ignore them rather than adding them to git.
- Plans must match the actual package layout, targets, and paths (e.g.,
WaxCore/Wax) and the Swift Testing framework (Testing). Avoid legacy names likeMemvidCoreorXCTestunless explicitly requested. - When updating docs/examples, ensure API names reflect current Conduit types (e.g.,
GeneratedContent,GenerationSchema,Tool,Transcript) and remove legacyStructuredContent/Schema/AIToolwording. - Before editing Conduit, confirm you are in the real repo path (not
.build/checkouts) and within writable roots; setworkdirto the repo root before changes. - If referencing external specs or legacy docs, cross-check with current implementation to avoid mismatches.
- Build:
swift build - Full test suite:
swift test - Documentation examples only:
swift test --filter DocumentationExamplesTests - Text embedding cache tests:
swift test --filter TextEmbeddingCacheTests - JsonRepair tests:
swift test --filter JsonRepairTests - Anthropic integration tests (skips without key):
swift test --filter AnthropicIntegrationTests - Anthropic integration tests (live):
ANTHROPIC_API_KEY=sk-ant-... swift test --filter AnthropicIntegrationTests