Smart Content Diet | Tiny Tool Development

// PRODUCT WALKTHROUGH

Visual orientation backed by the product facts below.

Use the gallery as quick orientation, then inspect mechanics, actions, outputs, integrations, and boundaries.

Smart Content Diet Overview slide — Overview **Content health review for growing Unreal projects**
Find stale, duplicate, heavy, or risky assets before cleanup becomes release work.

// THE PAIN

Before the plugin enters the chat.

The Content Browser grows; nobody knows what is safe to cut.

PAIN

Folders accumulate experiments, one-off materials, and assets nobody has referenced in months. Packaging size creeps up. Review week surfaces duplicates nobody claimed.

Without a structured inventory, cleanup stays a heroic Friday task, postponed every sprint until it becomes a release risk.

What that feels like

Stale and overweight content hides until packaging or audit week.
Nobody owns a repeatable review pass across the Content Browser.
Leads lack reports to decide what to cut versus what is still in flight.

// WHAT YOU GET

After — in the editor, not in a slide deck.

A visible workflow to surface growth and cleanup candidates before they block a ship date.

GAIN

Smart Content Diet is in publishment for inventory, review, analyzer evidence, reporting, preview-safe actions, and governance stages that separate pipeline assets from cleanup candidates.

Analyzer-backed inventory and review stages aimed at stale, duplicate, risky, and oversized content.
Cleanup candidates separated from assets still in the pipeline.
Governance and report surfaces for leads deciding what to act on, not solo Friday tidying.

// HOW IT WORKS

The product architecture, inspected from the plugin surface.

These are the moving parts I would place on the page so buyers can understand what they are actually getting beyond the slide narrative.

01 / Scan

AssetRegistry-first inventory finds health signals.

The analyzer suite covers textures, geometry, LOD, memory, materials, Nanite, animation, Blueprints, landscapes, levels, data/UI, UVs, and special content.

02 / Explain

Findings carry evidence, not just warnings.

Finding explanation, health evidence, similarity groups, governance snapshots, and trend views help leads decide what matters.

03 / Act

Safe previews and fixes separate advice from mutation.

Preview-safe and apply-safe routes let operators inspect cleanup actions before approved fixes run through the queue.

// FIT

Who actually reaches for this.

UE projects where asset growth, unused content, duplication, review debt, and cleanup candidates should become visible before they turn into release work.

Smart Content Diet is in publishment. Its product surface is grounded in analyzer coverage, role-aware review text, UCM route notes, and preview/apply-safe cleanup boundaries.

// SURFACE

Where it lives in Unreal.

Role-aware editor shell, analyzer panels, finding detail, optimization queue, governance snapshots, trend panels, evidence export, and UCM route-oriented outputs.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

Grouped from plugin modules, public APIs, automation hooks, and documented workflow surfaces.

Analyzer coverage

The plugin is larger than a stale-asset list; it is a broad content health surface.

Texture, geometry, LOD, material, memory, Nanite, and animation analyzers.
Blueprint, landscape, level, data/UI, special content, and UV analyzers.
Similarity ingest and grouping for duplicate-style review.
Health snapshots that summarize project-wide signals.

Evidence and governance

Cleanup decisions need proof, especially when assets belong to other teams.

Finding details and explanations for individual issues.
Health evidence snapshots for review.
Governance snapshots and CI policy direction.
Evidence exporter and trend panels for lead review.

Controlled action

Smart Content Diet separates discovery from safe fixes.

Preview safe actions before applying.
Apply safe operations through explicit routes.
Run jobs through a queue rather than blocking the editor.
Use QuickFix paths where the analyzer can support them.

// PRODUCT DOSSIER

The deeper buyer questions, answered from the actual product surface.

This section exists for products where a feature list is still too shallow: roles, scenarios, technical surfaces, decision rules, and concrete evaluation signals.

// WHO GETS VALUE

The page has to answer different buyer questions, not one generic cleanup promise.

Smart Content Diet is useful because producers, technical artists, engineers, and content leads ask different questions about the same Content Browser. The product page now spells out those questions directly.

Producer

What is the release risk right now?

A producer does not need every analyzer message first; they need a governance view that turns asset health into planning language.

Health snapshot summarizes the current project state.
Governance snapshot separates debt count, impact, analyzed assets, and trend signals.
CI policy direction supports release conversations instead of one-off cleanup days.
Trend panels show whether content health is improving or drifting.

Tech artist

Which asset deserves attention, and why?

A technical artist needs finding detail, analyzer evidence, safety level, and a path to a fix or a decision.

Findings rows carry analyzer names, severity, queue rows, and safety flags.
Finding explanations connect messages back to content-health evidence.
QuickFix actions appear where a finding is specific enough to support them.
Re-scan after action is part of the intended loop.

Engineer

Can this run without turning into editor guesswork?

The implementation exposes route-style result builders and commandlet/CI direction so the workflow can be repeated.

Capability Mesh endpoints return structured JSON for scans, findings, evidence, governance, similarity, preview, and apply paths.
Job/status surfaces make long operations observable.
AssetRegistry-first scanning keeps broad inventory work cheaper before deeper survivor loading.
Interface module exposes health source and similarity provider contracts.

Content lead

What is actually safe to clean?

The product is designed to keep candidates, safe actions, review-required cases, and destructive-disabled cases apart.

Optimization queue rows expose bucket, safety level, can-apply-now, requires-review, and destructive-disabled fields.
Similarity groups support duplicate-style review without pretending every match is safe to delete.
Preview Safe exists before Apply Safe.
Governance entries keep ownership decisions visible.

// ANALYZER SURFACE

What the scan actually inspects across the project.

The value is not one stale-asset check. The code surface shows a family of analyzers and models that cover asset size, rendering cost, structural risk, and content ownership signals.

Texture / Material

Rendering-cost and material hygiene signals.

Texture and material analyzers give the scan concrete rendering-oriented findings instead of generic asset-age warnings.

Texture Resolution Analyzer.
Material analyzer and material alpha checks.
UV analyzer for content layout issues.
Nanite analyzer for modern geometry/rendering state.

Geometry / LOD

Mesh and level-structure pressure points.

Geometry, LOD, landscape, level, and memory analyzers help identify assets that can quietly inflate project cost.

Geometry analyzer.
LOD analyzer.
Landscape and level analyzers.
Memory analyzer and impact dimensions.

Blueprint / Animation

Gameplay-adjacent content is not ignored.

Smart Content Diet includes analyzers for content that is not just static art.

Blueprint analyzer.
Animation analyzer.
DataAsset analyzer.
Cross-asset analyzer interface for relationships beyond one file.

Special content

Project-specific asset classes can still enter the review.

Special content analysis covers Unreal asset families that often live outside simple texture/mesh cleanup rules.

Chaos / Groom / PCG / Decal analyzer.
SmartAssetTagReader for tag and metadata context.
SmartAssetMetadataCache for scan-side metadata reuse.
SmartDeepScanService for deeper passes when needed.

Similarity

Duplicate review is evidence-weighted, not just name matching.

Similarity contracts model exact, metadata, and provider-backed similarity with explicit confidence signals.

FSmartSimilarityRequest, FSmartSimilarityGroup, and FSmartSimilarityResult.
ISmartSimilarityProvider slot for external providers.
Exact hash similarity provider.
Similarity confidence and destructive-awareness helpers.

// EDITOR SURFACE

The UI is a workflow shell, not a single report window.

The page should show that Smart Content Diet has multiple panels and role-aware depth, because this affects how teams adopt it.

Shell

Role-aware entry point.

The README describes Beginner, Engineer, and Producer depth, while the code exposes shell tabs and panel view models.

SSmartContentDietWidget.
SSmartAudienceSelector.
SmartShellTabModel with findings, trend, governance, and external similarity state.
Beginner / Engineer / Producer framing for how much detail is shown.

Findings

From list to explanation.

Findings are not just red rows. They can carry analyzer summaries, queue metadata, and detail/explainability views.

SSmartFindingsPanel.
SSmartFindingDetailPanel.
SmartFindingsViewModel and SmartFindingDetailViewModel.
SmartExplainability for why a finding matters.

Optimize

Preview, queue, apply, audit.

The optimization surface is where review becomes action, so the product page must show the control path.

SSmartOptimizationQueuePanel.
SmartOptimizationQueueViewModel and Runner.
SmartQuickFix and SmartQuickFixAuditReport.
Reduction dialog and reduction engine for selected cleanup paths.

Governance

Lead-level interpretation.

Governance panels turn raw analyzer output into ownership and release-readiness signals.

SSmartContentDietGovernancePanel.
SmartGovernanceViewModel.
SSmartHealthOverviewPanel.
SmartHealthSnapshotBuilder.

Trend

Measure whether cleanup is working.

Trend tracking gives the page a stronger value story than a one-time scan.

SSmartTrendPanel.
SmartTrendPanelViewModel.
SmartTrendTracking with metrics snapshots and comparisons.
SmartReleaseGate regression checks.

// AUTOMATION SURFACE

What local tools and route clients can ask the product to produce.

The product page should show the JSON-facing surfaces because they are the bridge between editor workflow, UCM route use, local agent clients, and CI-style checks.

Analysis

Scan and findings endpoints.

The analysis endpoint file serializes issues, analyzer summaries, queue rows, governance summaries, and finding detail.

BuildScanRunResultJson.
BuildFindingsGetResultJson.
BuildFindingExplainResultJson.
Analyzer names, severity, message count, bucket, safety, review flags.

Health

Snapshot and evidence endpoints.

Health endpoints make project state and evidence exportable rather than trapped in a panel.

BuildHealthSnapshotResultJson.
BuildHealthEvidenceResultJson.
FSmartHealthEvidenceManifest.
ISmartContentHealthSource evidence provider contract.

Similarity

Duplicate-style review endpoints.

Similarity routes keep duplicate candidates separate from safe deletion decisions.

BuildSimilarityGroupsResultJson.
BuildSimilarityIngestResultJson.
SmartSimilarityContracts and provider registry.
Similarity awareness checks before destructive decisions.

Optimize

Preview and apply endpoints.

Apply paths are valuable only because preview paths exist first.

BuildPreviewSafeResultJson.
BuildApplySafeResultJson.
BuildApplyFixResultJson.
QuickFix backup, undo, audit report, and post-action re-analysis hooks.

Jobs

Long operations stay observable.

The job surface makes automation more credible for scans or apply stages that should not feel invisible.

SmartContentDietJobStatus.
SmartContentDietJobStatusAdapter.
Capability Mesh jobs endpoint file.
Structured status over hidden editor waits.

// DECISION RULES

How the product helps decide instead of merely reporting.

A useful content-health tool must separate immediate action, review, governance, and explicit no-go cases.

Can apply now

Low-risk findings can move to previewed action.

The queue exposes whether an item can be applied now, which makes the page more concrete than saying 'safe fixes'.

Queue row has can_apply_now.
Preview Safe shows the plan first.
Apply Safe acts only after approval.
Re-scan verifies whether the action helped.

Requires review

Ambiguous findings stay in human decision space.

Not every finding should become a quick fix. Review flags protect active pipeline assets from automated cleanup.

Queue row has requires_review.
Governance view supports ownership discussion.
Finding detail explains why the item was flagged.
Similarity groups can remain advisory.

Needs full scan

Some answers need deeper project context.

The page should admit when fast inventory is not enough and a deeper pass is the right next step.

Queue row has requires_full_scan.
AssetRegistry-first pass can identify candidates before deeper loading.
Deep scan service exists for heavier inspection.
Findings can escalate from quick surface to detailed evidence.

Destructive disabled

No-go paths are product value too.

A safe product needs to show when it refuses or blocks mutation.

Queue row has destructive_disabled.
QuickFix enablement can return an error.
Similarity awareness can block destructive actions.
Backups and undo are part of the fix contract where action is allowed.

Measure after

The loop ends with evidence, not hope.

The core loop is scan -> review -> apply safe fixes -> re-scan -> measure.

Trend snapshots compare metrics over time.
Release gate detects regression types.
Audit reports record QuickFix outcomes.
Governance and health snapshots provide follow-up evidence.

// BUYER EVALUATION

How a serious buyer should judge whether Smart Content Diet is a fit.

The page should help a buyer evaluate adoption risk before downloading or wiring automation around it.

First result

A useful first run should produce a readable health picture.

The first buyer expectation is not a perfect cleanup. It is a scan result that names issues, evidence, and next decisions.

Health overview is populated.
Findings include analyzer and severity context.
Governance summary gives lead-level numbers.
Queue rows separate safe, review, and blocked work.

Trust test

The buyer should see why a finding exists.

A vague 'asset is bad' message is not enough. Findings need evidence and explanation.

Finding explain endpoint exists.
Health evidence can be exported.
Analyzer summaries include section and message count.
Inspection basis maps claims back to code surfaces.

Safety test

The buyer should know what can mutate before clicking.

The strongest selling point is controlled action, not blind automation.

Preview Safe comes before Apply Safe.
QuickFix checks eligibility.
Backup and undo paths exist where supported.
Destructive-disabled and requires-review flags are visible.

Scale test

The product should still make sense when the project is large.

Large projects need inventory, grouping, job status, and governance rather than hand-sorted lists.

AssetRegistry-first inventory.
Similarity groups cluster related candidates.
Job status keeps long work observable.
Trend and release-gate surfaces help across multiple scans.

Boundary test

The page should say what the plugin is not.

Smart Content Diet is not a one-click deletion tool, a hosted service, or an AI dependency.

No AI model, Python, Node.js, or external runtime is required.
Mutating actions require backed-up/source-controlled workspace expectations.
Ownership decisions remain with the project team.
Unsafe or ambiguous cleanup remains review work.

// OPERATOR TOOLS

Concrete actions, expected result, and mutation boundary.

This is the part that keeps product marketing honest: buyers can see which buttons, APIs, or MCP tools matter and what they change.

// ACTION

BuildScanRunResultJson

Why it matters: Runs or represents a content health scan.
Operator result: Project findings become structured result JSON.
Change surface: Scan-oriented; mutation depends on selected route.

// ACTION

BuildFindingExplainResultJson

Why it matters: Explains a specific finding with context.
Operator result: Reviewers can understand why the issue exists.
Change surface: Read-only explanation.

// ACTION

BuildPreviewSafeResultJson

Why it matters: Shows what a safe action would do.
Operator result: Operators can approve or reject the plan.
Change surface: Read-only preview.

// ACTION

BuildApplyFixResultJson

Why it matters: Applies an approved fix path.
Operator result: A finding can move from advice to action.
Change surface: Applies selected content changes.

// ACTION

BuildHealthEvidenceResultJson

Why it matters: Collects the evidence behind health signals.
Operator result: A reviewer can see why a finding or snapshot deserves attention.
Change surface: Read-only evidence export.

// ACTION

BuildSimilarityGroupsResultJson

Why it matters: Groups likely duplicate or related assets for review.
Operator result: Cleanup conversations move from guesses to inspectable clusters.
Change surface: Read-only grouping result.

// ACTION

BuildGovernanceSnapshotResultJson

Why it matters: Summarizes content health in a lead-friendly governance view.
Operator result: Project owners get a planning surface instead of raw asset warnings.
Change surface: Read-only snapshot result.

// ACTION

Queue jobs

Why it matters: Runs heavy analysis or safe actions as managed work.
Operator result: Long scans do not disappear into a blocking editor moment.
Change surface: Updates job state; apply jobs mutate only selected safe targets.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Run a scan and review analyzer findings, health evidence, and similarity groups.

02

Use preview-safe and queue-based workflows before applying supported cleanup actions.

03

Export governance or evidence views for lead review and downstream tooling.

// PROOF AND BOUNDARIES

Signals that make the product specific, plus the limits worth saying out loud.

Each card turns implementation facts into buyer-facing proof without pretending the tool solves the wrong problem.

Analyzer set Texture, geometry, LOD, memory, material, Nanite, animation, Blueprint, landscape, level, data/UI, UV

Surfaces Panels, queue, QuickFix, governance, trend, evidence exporter

Routes Scan, findings, explain, evidence, preview safe, apply safe, apply fix

Strategy AssetRegistry-first before deeper survivor loading

Similarity review Similarity ingest and grouping paths for duplicate-style decisions

Governance Health snapshots, governance snapshots, trends, CI policy direction

Fix model Preview-safe and apply-safe paths separate recommendation from mutation

Analyzer breadth Content type coverage spans rendering, memory, structure, gameplay data, and UI/data assets

Outputs

What the plugin leaves behind when the workflow is doing useful work.

Scan run result
Structured inventory of current content health.
Findings and explanations
Actionable issues with evidence and reasoning.
Governance snapshot
Lead-level state for cleanup planning and policy.
Health evidence
The underlying evidence behind a warning or score.
Similarity groups
Clusters of likely duplicate or review-worthy related assets.
Safe action preview
A mutation plan that can be approved or rejected before apply.
Trend material
Signals for whether content health is improving or drifting.

Inspection basis

The concrete code, API, and tool surfaces used to shape this product page.

Analyzer files
Texture, geometry, LOD, memory, material, Nanite, animation, Blueprint, landscape, level, data/UI, special content, and UV analyzer surfaces were inspected.
Result builders
BuildScanRunResultJson, findings, explain, health, evidence, governance, similarity, preview-safe, apply-safe, and apply-fix functions shape the route story.
Editor surfaces
Panels, queue, QuickFix, governance, trend, evidence exporter, and CI policy direction are part of the product scope.
Scan strategy
AssetRegistry-first scanning before deeper survivor loading explains the performance and safety posture.
Action boundary
Preview-safe/apply-safe separation shows where content mutation is intentionally gated.

Integrations

Where the product connects without losing ownership of its own domain.

Unreal Capability Mesh
Scan and job routes can be exposed for shared tool visibility.
Unified MCP Server
Local agents can inspect findings through governed tool routes.
CI policy
Governance data can inform release and size gates.
Asset Registry
The scan path starts from registry metadata before expensive deeper loads.
Lead review workflow
Governance and trend outputs make content health a planning conversation.
QuickFix pipeline
Selected findings can move into previewed and approved fix paths.

Safety model

The boundaries that make the tool understandable before automation enters.

Evidence before action
Findings can be explained before anyone changes content.
Preview-safe route
Potential actions can be inspected before apply.
Queued operations
Long-running work is treated as jobs rather than hidden editor stalls.
AssetRegistry-first
Broad scans can avoid deep-loading everything before the tool knows what deserves deeper inspection.
Governance layer
Snapshots and trend data help separate cleanup candidates from active pipeline assets.
Fix gating
QuickFix/apply paths are framed as selected actions, not automatic mass cleanup.

Not for

The cases where the product promise would be the wrong expectation.

Teams that want a one-click cleanup without review.
Projects where content ownership is not defined enough for governance decisions.
Small prototypes where analyzer setup would cost more than manual inspection.
Pipelines that cannot tolerate tool-driven content mutation even after preview.

// PRODUCT MEDIA

Tutorial and platform embeds stay attached to product context.

YouTube, Discord, LinkedIn, and Fab widgets are reserved for product presentation, explanation, support context, or tutorials. No third-party widget loads automatically.

Tutorial video

YouTube

Product walkthroughs, setup explanations, and tutorial material.

Embed source pending. No third-party widget is loaded here.

Open platform

Primary support context

Discord

Discord-first product support, quick questions, setup discussion, and community context.

Embed source pending. No third-party widget is loaded here.

Open platform

Professional context

LinkedIn

Company background, provider identity, project credibility, and listing context.

Embed source pending. No third-party widget is loaded here.

Open platform

Marketplace context

Fab

Product listing context, license details, purchase route, and marketplace availability.

Embed source pending. No third-party widget is loaded here.

Open platform

// INFORMATION

All essential product signals in one place.

Status In Publishment

Category Editor Tools

Unreal Engine 5.4; current descriptor/build line UE 5.8

Source state SmartContentDiet.uplugin VersionName 1.0.6 / Version 5

Primary surface Role-aware editor shell, analyzer panels, finding detail, optimization queue, governance snapshots, trend panels, evidence export, and UCM route-oriented outputs.

Marketplace No product checkout linked

Direct sales None on this website

Support route Discord first; product context lives on this page

Listing context Fab for marketplace, LinkedIn for public provider identity

Fact surface 3 functions / 3 settings / 3 failure modes / 1 bridge

Boundary Safety-forward content-health analysis, review, preview, and guarded optimization workflow for Unreal assets.

Primary workflow Open Smart Content Diet, run a Quick Safe scan, review findings, preview the safe queue, apply only reviewed safe fixes, and re-scan to measure improvement.

// NOTES

Practical boundaries.

Smart Content Diet is in publishment; no product-specific Fab checkout is linked from this site yet.

Documentation tracks analyzer coverage, AssetRegistry-first scanning, UCM job route visibility, and safe action boundaries.

The product is not a one-click deletion tool; review, preview, and governance boundaries are part of the value.

// LEGAL / PRIVACY

Static information page.

Purchases, downloads, marketplace accounts, and platform-specific license details are handled outside this website. Product or tutorial widgets are loaded only after activation, where configured.

Provider details are listed in the legal notice. The current site template does not set first-party cookies and does not load analytics scripts.

Legal Notice Privacy Policy

// RESOURCES

Open the channel that matches the next question.

Fab seller profile

No product-specific Fab listing is linked yet. The public seller profile remains available.

Open

GitHub documentation

Manuals, quickstarts, settings references, troubleshooting, technical notes, and release material live in GitHub.

Open

Discord support (primary)

Start quick questions, setup help, support context, and product-fit discussion on Discord.

Open

Plugin support email

Formal plugin support requests can be sent to the dedicated support mailbox.

Open

LinkedIn company context

Company background, public provider identity, and listing context are available on LinkedIn; support still starts on Discord.

Open

// RELATED