Files
dss/dss-claude-plugin/docs/context_compiler.md
Digital Production Factory 276ed71f31 Initial commit: Clean DSS implementation
Migrated from design-system-swarm with fresh git history.
Old project history preserved in /home/overbits/apps/design-system-swarm

Core components:
- MCP Server (Python FastAPI with mcp 1.23.1)
- Claude Plugin (agents, commands, skills, strategies, hooks, core)
- DSS Backend (dss-mvp1 - token translation, Figma sync)
- Admin UI (Node.js/React)
- Server (Node.js/Express)
- Storybook integration (dss-mvp1/.storybook)

Self-contained configuration:
- All paths relative or use DSS_BASE_PATH=/home/overbits/dss
- PYTHONPATH configured for dss-mvp1 and dss-claude-plugin
- .env file with all configuration
- Claude plugin uses ${CLAUDE_PLUGIN_ROOT} for portability

Migration completed: $(date)
🤖 Clean migration with full functionality preserved
2025-12-09 18:45:48 -03:00

861 B

Context Compiler Architecture (Phase 1)

Overview

The DSS Context Compiler transforms the application from a simple token extractor into a context-aware system. It uses a 3-layer cascade to resolve the final design system context.

Layer Cascade

  1. Base Layer (skins/base.json): Universal tokens (white, black, system stacks).
  2. Skin Layer (skins/[name].json): Thematic definitions (Workbench, Classic).
  3. Project Layer (ds.config.json): Project-specific overrides.

Safe Boot Protocol

If the JSON parser fails or files are missing, the compiler falls back to an in-memory EMERGENCY_SKIN to prevent crash loops.

Integration

MCP Tools should now use the with_context wrapper or interact via the 5 new context tools:

  1. get_active_context
  2. resolve_token
  3. validate_manifest
  4. list_skins
  5. get_compiler_status