Systematic replacement of 'swarm' and 'organism' terminology across codebase: AUTOMATED REPLACEMENTS: - 'Design System Swarm' → 'Design System Server' (all files) - 'swarm' → 'DSS' (markdown, JSON, comments) - 'organism' → 'component' (markdown, atomic design refs) FILES UPDATED: 60+ files across: - Documentation (.md files) - Configuration (.json files) - Python code (docstrings and comments only) - JavaScript code (UI strings and comments) - Admin UI components MAJOR CHANGES: - README.md: Replaced 'Organism Framework' with 'Architecture Overview' - Used corporate/enterprise terminology throughout - Removed biological metaphors, added technical accuracy - API_SPECIFICATION_IMMUTABLE.md: Terminology updates - dss-claude-plugin/.mcp.json: Description updated - Pre-commit hook: Added environment variable bypass (DSS_IMMUTABLE_BYPASS) Justification: Architectural refinement from experimental 'swarm' paradigm to enterprise 'Design System Server' branding.
3.1 KiB
3.1 KiB
DSS Corporate Terminology Glossary
Quick Reference: Enterprise terminology for the Design System Server
Atomic Design Hierarchy (5 Levels)
| Level | Term | Description | Examples |
|---|---|---|---|
| 1 | Tokens | Design variables - raw values | --color-primary, --spacing-md, --font-size-base |
| 2 | Primitives | Base UI elements - indivisible | Button, Input, Icon, Badge, Label |
| 3 | Components | Composite UI - combining primitives | FormField (label+input+error), Card (image+title+actions) |
| 4 | Layouts | Page structure patterns | PageShell, DashboardGrid, SidebarLayout |
| 5 | Views | Complete screens with content | TokenExplorer, FigmaSync, ComponentAudit |
Architecture Layers (7 Layers)
| Layer | Name | Code Modules | Responsibility |
|---|---|---|---|
| 1 | Core | storage/, settings.py |
Configuration, schemas, database, event bus |
| 2 | Ingestion | ingest/ |
File parsing, token extraction (CSS, Figma, JSON, Tailwind) |
| 3 | Validation | validators/ |
Schema checking, linting, error detection |
| 4 | State | models/ |
Token models, stores, data flow |
| 5 | Processing | tools/, analyze/ |
Transformations, analysis, style-dictionary |
| 6 | Presentation | storybook/, admin-ui/ |
UI components, documentation, Storybook |
| 7 | Integration | api/, MCP server |
APIs, MCP tools, webhooks, CLI |
Term Translations
From Legacy Biological to Corporate
| Deprecated Term | Corporate Term | Context |
|---|---|---|
| component | module | Complex UI section |
| molecule | component | Composite UI element |
| atom | primitive / token | Base element or variable |
| heart | core / database | Persistent storage layer |
| brain | analyzer / validation | Pattern detection and quality |
| nervous system | integration layer | APIs, MCP, webhooks |
| digestive system | ingestion pipeline | Token extraction from sources |
| circulatory system | token distribution / state | Data flow through system |
| metabolic system | transformation engine / processing | Format conversion |
| endocrine system | theme controller | Theming and adaptation |
| immune system | validation guard | Quality assurance |
| sensory organs | asset manager | Icons, images, visual assets |
| skin | presentation layer | UI, Storybook, docs |
| skeleton | schema framework | Naming conventions, structure |
Quick Phrases
Instead of... Say...
| Don't Say | Say Instead |
|---|---|
| "Feed the component" | "Ingest tokens" |
| "Check the immune system" | "Run validation" |
| "The heart is healthy" | "Database is operational" |
| "Nervous system response" | "API response" |
| "The brain detected a pattern" | "Analyzer detected a pattern" |
| "Organism health check" | "System status check" |
See Also
- First Principles - 7 foundational truths
- Architecture Overview - 7-layer system design
- Atomic Hierarchy - Composition rules