Refreshed Audit ยท 2026-07-01 14:48 PDT

ForgeFX Brand Cleanup

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.

Current Verdict
Pass

The active brand package now defers to the design system instead of competing with it.

Cleanup Shape
22

Brand-package files were simplified, redirected, or relabeled as legacy material.

Example Review
47

Historical example, preview, and UI-kit files were reviewed and grouped by keep / migrate / archive.

What Changed

Fixed

Wrapper, Not Manual

forgefx-brand now says: use forgefx-design-system. It no longer tries to carry its own full brand system.

Fixed

High-Level Voice

The remaining guidance is intentionally broad: industrial, warm, practical, confident, real training contexts, clear hierarchy, restrained accent color.

Fixed

Compatibility Only

Old CSS and JSON files are now wrappers or migration notes, not alternate palettes, font rules, or source-of-truth documents.

Historical Examples: Keep / Migrate / Archive

AreaRecommendationReasonNext Move
Industrial imagery setKeepUseful 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 imageKeepGood 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 headerMigrateUseful 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 pagesMigrateGood demonstration shape, but they are older than the current design-system token layer.Replace with design-system examples, then archive these.
Text-on-orange comparisonMigrateStill 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 specimenArchive / DeleteIt 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 pagesArchive / DeleteThe 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 kitsArchive / DeleteThey 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 decksKeep SelectivelySome 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 exampleMigratePotentially 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 imageRemove From Brand ExamplesGeneric brand examples should not carry sensitive or meeting-derived working material.Move out of the public/example path or delete if no longer needed.

Practical Cleanup Plan

Do Now

Keep the wrapper as-is, then remove or archive only the most misleading examples: old typography, duplicate previews, and legacy UI kits.

Do After Link Check

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.

Verification

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.