276ed71f31
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
1.3 KiB
1.3 KiB
ADR Template - Copy This File to Create New ADRs
Copy this file and rename to NNN-short-title.md where NNN is the next sequential number.
---
id: NNN
title: Short, descriptive title of the decision
date: YYYY-MM-DD
author(s): Your Name
status: Proposed | Accepted | Deprecated | Superseded by ADR-XXX
principles: [List relevant principles from PRINCIPLES.md]
related:
- doc: Link to related documentation
- adr: Link to related ADRs
- ticket: Link to related issue/ticket
---
Context
Describe the issue or problem that motivated this decision. Include:
- What is the problem?
- Why does it matter?
- What constraints or requirements are we working under?
- What alternatives were considered and why were they rejected?
Decision
State the decision clearly and concisely.
- What did we decide to do?
- Why this specific approach?
Include implementation details if relevant:
# Example code or pseudocode here
Consequences
Describe the implications of this decision.
Positive:
- List expected benefits
- List advantages
Negative:
- List trade-offs
- List expected costs
Related Principles
How does this decision support or reinforce the DSS Core Principles?
- [Principle Name]: Explain connection
- [Principle Name]: Explain connection