Wrapper, Not Manual
forgefx-brand now says: use forgefx-design-system. It no longer tries to carry its own full brand system.
The brand skill is now cleaned up into a high-level wrapper. It recognizes brand intent, points to the design system, and keeps old files only as compatibility material. The old hyper-specific duplicate guidance has been stripped back.
The active brand package now defers to the design system instead of competing with it.
Brand-package files were simplified, redirected, or relabeled as legacy material.
Historical example, preview, and UI-kit files were reviewed and grouped by keep / migrate / archive.
forgefx-brand now says: use forgefx-design-system. It no longer tries to carry its own full brand system.
The remaining guidance is intentionally broad: industrial, warm, practical, confident, real training contexts, clear hierarchy, restrained accent color.
Old CSS and JSON files are now wrappers or migration notes, not alternate palettes, font rules, or source-of-truth documents.
| Area | Recommendation | Reason | Next Move |
|---|---|---|---|
| Industrial imagery set | Keep | Useful subject-matter references: equipment, forge/anvil mood, devices, 3D work, and training-adjacent scenes. | Keep as inspiration, but point users to the design system for layout and brand rules. |
| Craftsmanship palette image | Keep | Good mood reference for the ForgeFX feel without becoming a rule book. | Keep in examples or move to design-system uploads if it is still used. |
| Business card, letterhead, email header | Migrate | Useful formats, but visuals should inherit the design system rather than old wrapper variables. | Restyle when needed; keep until replacement templates exist. |
| Dark and light demo pages | Migrate | Good demonstration shape, but they are older than the current design-system token layer. | Replace with design-system examples, then archive these. |
| Text-on-orange comparison | Migrate | Still useful as a focused contrast study, but should live under the design-system review material if kept. | Move or rebuild under design-system references. |
| Old typography specimen | Archive / Delete | It explicitly presents the old font pairing and can mislead future agents. | Delete after confirming no one depends on it, or replace with a stub pointing to the design system. |
| Preview specimen pages | Archive / Delete | The active design system has the current specimen set. Keeping two preview folders invites drift. | Delete the legacy preview folder after checking for links. |
| Legacy UI kits | Archive / Delete | They are old experiments and use older visual assumptions. The design system now owns the real examples. | Move to an archive folder or delete after link checks. |
| Old presentation decks | Keep Selectively | Some decks may be useful for structure, pacing, or historical client context; they should not be brand references. | Keep only decks with active business value. Move client/project-specific decks out of the generic brand skill. |
| Document example | Migrate | Potentially useful as a document-format starter, but should be regenerated with design-system guidance. | Keep until a replacement exists, then archive. |
| Private/internal whiteboard-style image | Remove From Brand Examples | Generic brand examples should not carry sensitive or meeting-derived working material. | Move out of the public/example path or delete if no longer needed. |
Keep the wrapper as-is, then remove or archive only the most misleading examples: old typography, duplicate previews, and legacy UI kits.
Before deleting larger decks or images, check whether any scripts, docs, or apps still reference them. Move useful client/project material to a better home instead of leaving it in the brand skill.
The refreshed state passed skill loading, JSON parsing, CSS import-path checks, whitespace checks, and targeted searches for the most misleading old-rule phrases.
forgefx-brand now behaves as a high-level entry point. forgefx-design-system remains the detailed authority.