Basinfy/Basinfy-SaaS-Studio / .claude/skills/saas-asset-audit
saas-asset-audit
VerifiedAudit UI assets, SVGs, and bundles for naming, budget, and orphan compliance.
Asset Audit
Locale & User Profile: Match
locale(pt-BR→ natural Brazilian Portuguese questions/options, overriding English examples;en→ English) anduser_profile(founder→ plain business language with(Recomendado)first, zero tech jargon;developer→ technical). Keep code/tests in English.
Measuring file sizes and formats requires Bash
This skill's report asks for file sizes against budgets, texture dimensions
(power-of-two), audio sample rates, and last-modified times for orphan
detection. None of those are obtainable from Read/Glob/Grep — they need
stat or a binary header read, so the read-only measuring commands (stat,
file, od, wc, du) are pre-approved above; list files with Glob. Anything
else asks first.
If you cannot take a measurement, the cell is NOT ASSESSED, never an
estimate. A size budget table filled from guesses is worse than an empty one:
it looks like evidence. This is a live fabrication vector even on a project full
of real assets: if the template demands tables of numbers the tool allowlist
cannot produce, the only way to complete it is to invent them.
Insufficient input — check this before producing any report
If the inputs this skill needs do not exist, the answer is "could not run" — not a filled-in report. Check first, and stop if the check fails.
- List the inputs this skill reads (data files, prior reports, profiler output, test results, registries, source code).
- For each, record
FOUNDorABSENT— not "assumed present". - If any input required for a section is ABSENT, that section is
NOT ASSESSED — NO DATA. Do not estimate it, do not infer it from an adjacent artifact, and do not leave a mandated cell to be filled by whoever reads the template next. - If every required input is ABSENT, stop and report
NOT ASSESSED — NO DATAas the whole verdict, naming what was missing and which skill produces it.
A verdict of NOT ASSESSED is a success. It is the correct, useful answer to
"what does the data say?" when there is no data. The failure mode this prevents is
specific: a report whose verdict enum has no "could not run" state produces
false clean passes — an asset audit returning COMPLIANT on a project with no
assets and no standards, or a performance profile reporting ">99% headroom against
a 16.67ms budget" with zero profiler data and no budget ever set.
Absence of evidence is never evidence of absence. A scan that finds no matches because there are no files to scan has not verified anything. Say which of the two happened — a reader cannot tell from a green result.
Phase 1: Read Standards
Read the design tokens / asset spec's Asset Standards section (design/tokens/design-tokens.md) and any
asset standards in the relevant design docs — size budgets and format rules come
from there. The naming patterns are the ones in Phase 3 below, unless the design
tokens spec states its own. Read the design tokens / asset spec by section: find the heading with
the Basinfy Protocol (basinfy_search / basinfy_read if .basinfy/ exists) or the Basinfy Protocol (basinfy_search / basinfy_read if .basinfy/ exists) or the Grep tool (pattern ^#, content mode) and Read that range with offset and limit.
If neither states a size budget — or there is no design tokens / asset spec — the Size section is
NOT ASSESSED — no size budget set, and the report names /saas-design-tokens, whose
Asset Standards section sets budgets, formats and the naming convention.
Phase 2: Scan Asset Directories
Assets live under the engine's asset root: assets/ on Next.js, Assets/ on
FastAPI, Content/ on Cloudflare. Resolve the engine and its code root per
.claude/docs/code-root-resolution.md; that code root is the one Phase 3's
orphan and missing-asset searches read. If it is unresolved, stop:
NOT ASSESSED — engine unresolved, naming /saas-setup-stack.
Scan the asset root using Glob:
- Next.js —
public/**/*,src/assets/**/* - FastAPI —
static/**/*,app/static/**/*, leaving out backend source (*.py,*.pyc) and cache files - Cloudflare —
public/**/*.{svg,png,webp,woff2}
The files matched are Total assets scanned. If there are none, the checks on
scanned files — Naming, Size, Format, Orphaned — are
NOT ASSESSED — no assets under <asset root>; the missing-asset search still runs.
Phase 3: Run Compliance Checks
Naming conventions:
- Art:
[category]_[name]_[variant]_[size].[ext] - Audio:
[category]_[context]_[name]_[variant].[ext] - All files must be lowercase with underscores
These are Next.js's conventions. FastAPI and Cloudflare use kebab-case or snake_case, so on
those engines check names against the naming rule the design tokens / asset spec states; with
none, Naming is NOT ASSESSED — no naming rule for <engine> (name /saas-design-tokens).
File standards:
- Images & Icons: Modern web formats (SVG, WebP, PNG, AVIF), within size budget
- Static Media: Correct dimensions, modern web formats, within bundle size limits.
- Data: Valid JSON/YAML, schema-compliant
On web/SaaS platforms an asset file does not keep legacy binary format or dimensions, so Format is NOT ASSESSED there; its size is still measured.
Orphaned assets: Search the code root for references to each asset file. Flag any with no references.
Missing assets: Search the code root for asset references and verify the files exist.
Both searches need code: if the code root holds no source files, Orphaned and
Missing are NOT ASSESSED — no code to search. On backend-only stacks where asset
references live in HTML templates, emails, or markdown rather than code, an
asset no code names may still be in use: Orphaned is NOT ASSESSED there.
Phase 4: Output Audit Report
# Asset Audit Report -- [Category] -- [Date]
## Summary
- **Total assets scanned**: [N]
- **Naming violations**: [N]
- **Size violations**: [N]
- **Format violations**: [N]
- **Orphaned assets**: [N]
- **Missing assets**: [N]
- **Sections not assessed**: [none | each section and why]
## Naming Violations
| File | Expected Pattern | Issue |
|------|-----------------|-------|
## Size Violations
| File | Budget | Actual | Overage |
|------|--------|--------|---------|
## Format Violations
| File | Expected Format | Actual Format |
|------|----------------|---------------|
## Orphaned Assets (no code references found)
| File | Last Modified | Size | Recommendation |
|------|-------------|------|---------------|
## Missing Assets (referenced but not found)
| Reference Location | Expected Path |
|-------------------|---------------|
## Recommendations
[Prioritized list of fixes, one per violation, each naming the change — the
target resolution or compression for a size violation, the corrected name for a
naming violation, the target format for a format violation]
## Verdict: [NOT ASSESSED / COMPLIANT / WARNINGS / NON-COMPLIANT]
Choose the verdict by the findings, first match wins:
- NON-COMPLIANT — any size violation, or any asset that code references but that does not exist
- WARNINGS — only naming, format or orphaned-asset findings
- NOT ASSESSED — the audit did not cover its scope: no data at all (the path
above), zero assets scanned, or any section
NOT ASSESSED— name which. It ranks below the two finding verdicts, because a measured violation is more actionable than a gap, and above COMPLIANT - COMPLIANT — at least one asset scanned, every section assessed, no findings
This skill is read-only — it produces a report but does not write files.
Phase 5: Next Steps
- Fix naming violations using the Phase 3 patterns (or the design tokens / asset spec's, where it states its own).
- If standards were missing, run
/saas-design-tokensto write its Asset Standards section. - Delete confirmed orphaned assets after manual review.
- Run
/saas-content-auditto cross-check asset counts against PRD-specified requirements.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |