11 KiB
11 KiB
Nova Cards v3 Audit Checklist
Audit date: 2026-03-28
Source of truth reviewed:
.vscode/agents/skinbase-nova-cards-system_v3.md- Nova Cards controllers, services, models, routes, React Studio UI, migrations, and feature tests
Validation status:
- Verified with
php artisan test tests/Feature/NovaCards - Result: 72 passing tests, 489 assertions
Follow-up roadmap:
docs/nova-cards-v3-priority-roadmap.md
Status legend:
[x]Implemented end to end or clearly present[-]Partially implemented or scaffolded[ ]No clear implementation found during audit
Important note:
- The v3 agent file is a roadmap/spec, not a strict shipping checklist. Several sections describe target-state product direction rather than features that are already expected to exist in full.
1. v3 schema versioning and normalization
schema_versionis stored and normalized for v3 cards- New projects normalize to v3 shape
- Legacy v1/v2 projects are detected and upgraded
- Save flow rewrites cards into the newer project structure
- Compatibility behavior is covered by feature tests
- [-] Explicit admin rerender/backfill tooling for migrated cards was not found
Notes:
- Implemented via migration,
NovaCardProjectNormalizer, and v3 tests.
2. Advanced editor architecture improvements
- Structured project JSON exists with major v3 sections like
canvas,background,text_blocks,frame,effects,export_preferences, andsource_context - Multiple text blocks are supported
- Additional body and caption blocks can be added and edited
- Layout presets, alignment, position, padding, max width, typography, frame, effects, background modes, overlays, focal position, and packs are exposed in the Studio UI
- Background upload works through the draft API
- Mobile step-based flow exists for Studio
- Version history and version restore exist
- Block reordering UI now exists for text blocks
- Compare versions UI now exists at a useful summary level
- Dedicated quick mode versus advanced mode switch now exists
- [-] The editor is structured and block-based, but not a full layer tool
- [-] Visibility toggles exist for text blocks through the
enabledflag, but not as a broader layer system - Snap guides were not found
- Safe-zone editing helpers beyond stored config were not found
- Lock/unlock controls for editable elements were not found
Notes:
- This area is materially beyond MVP, and the recent Studio usability pass closed the highest-value gaps around quick/full mode, block reorder, and version compare. It still does not match the full “advanced studio” vision in the spec.
3. Creator presets
- Creator presets table and model exist
- Preset CRUD API exists
- Presets can be captured from an existing card
- Presets can be applied back to a card as project patches
- Default preset behavior exists
- Studio UI exposes preset browsing, apply, capture, and delete actions
- Preset logic is covered by tests
4. Discovery and ranking surfaces
- Public cards index includes featured, trending, latest, and rising content
- Rising service exists and is tested
- Related cards service exists and is tested
- Remixed cards page exists
- Lineage page exists
- Challenge listing and challenge detail pages exist
- Template packs page exists
- Creator page exists
- Dedicated style-family feed now exists
- Dedicated palette-family feed now exists
- Best-remixes discovery surface now exists
- Dedicated mood feed now exists through config-backed tag mappings
- Dedicated editorial landing page now exists
- Dedicated seasonal landing page now exists
- [-] Discovery includes several meaningful surfaces, but not the full matrix described by the spec
- Remix-tree browsing surface beyond lineage was not found
Notes:
- Discovery is solid for core launch surfaces, but it is not yet the full “discovery intelligence” product outlined in the spec.
5. Creator identity and profile integration
- Creator-specific public page exists for cards by user
- Creator page now exposes public summary stats and creator highlight cards
- Creator page now exposes featured works and featured collections
- Top categories and top tags are surfaced on creator pages
- Studio analytics page exists for a creator’s own card with views, likes, saves, remixes, shares, downloads, and related counters
- Style family and palette family are stored on cards
- [-] Creator identity exists at the card/creator listing level, but richer creator-card identity features are not complete
- Featured card rail now exists on creator pages as featured works
- Featured collection rail now exists on creator pages
- Dedicated Nova Cards creator portfolio page now exists
- Creator pages now surface signature themes, challenge history, most remixed works, most liked works, remix branch activity, a remix graph summary, creator preference signals, and a recent creator timeline
- [-] Deeper creator identity modules are still incomplete beyond the current public portfolio summary; stronger interactive remix graphing and richer persistent preference identity are still missing
- Creator spotlight eligibility/featured creators now exist for Nova Cards editorial surfacing
6. Social, remix, collection, challenge, and editorial support
- Like, favorite, save, remix, duplicate, and challenge submission flows exist
- Remix lineage is preserved and visible
- Public collection detail page exists
- Official collections and admin management for Nova Cards exist
- Challenge admin management exists
- Challenge entry visibility rules are covered by tests
- Best-remixes public surface exists
- Nova Cards editorial landing surfaces exist
- Seasonal or themed card hubs specific to Nova Cards exist
- Featured creators workflow specific to Nova Cards now exists
- [-] Editorial and community support is present, but the richer “ecosystem” layer remains incomplete
7. AI assistance hooks and optional UI
- AI assist endpoint exists
- AI assist service exists
- Studio UI exposes AI suggestion requests
- Suggestions include tags, mood, layout suggestions, and readability fixes
- Suggestions are optional and creator-controlled
- [-] The AI assist layer appears primarily rule-based/fallback-driven rather than a deep external AI composition system
- More advanced assist actions from the spec, such as “convert to story format” or “create wallpaper version” as explicit AI actions, were not found
8. Export system improvements
- Export request API exists
- Export status polling exists
- Export queue job exists
- Multiple export formats exist: preview, hires, square, story, wallpaper, and OG
- Export permissions are enforced via
allow_export - Studio UI exposes export requests
- [-] Core export foundation is implemented, but richer policy/output features remain open
- Watermark policy controls were not found
- Advanced export preset management beyond format choice was not found
9. Trust, moderation, and rights
- Card moderation status exists on the model
- Reporting supports cards, comments, challenges, and challenge entries
- Moderation queue/report summary integration exists
- Ownership and remix-related rights flags exist, including
allow_remix,allow_background_reuse, andallow_export - Background upload validation is enforced
- API throttles and write-protection middleware are wired on key Nova Cards endpoints
- [-] Trust/moderation foundations are real, but the full anti-abuse roadmap is not complete
- Publish-time duplicate-content heuristic flagging now exists for Nova Cards
- Publish-time self-remix-loop heuristic flagging now exists for Nova Cards
- Staff admin/reporting surfaces now expose persisted Nova Card publish heuristic reasons
- Staff moderation overrides now persist actor/source metadata on Nova Cards
- Staff overrides now persist moderation disposition codes like cleared/escalated/rejected
- Staff moderation UI now allows selecting custom review dispositions per action
- Challenge branch freeze / remix-branch intervention tooling was not found
10. Backward-compatible migration strategy and rerender tooling
- Migration for v3 schema additions exists
- Legacy project JSON is normalized at load/use time
- Older cards remain editable through normalization paths
- Tests verify upgrade behavior
- [-] Compatibility is present, but operational migration tooling is incomplete
- Admin rerender tool for migrated cards was not found
- Backfill job for schema versions was not found
11. Acceptance criteria summary
Studio/editor
- Structured multi-block project model exists
- Creator presets exist and can be reused
- Versioned schema and normalization work
- Exports are functional
- Mobile Studio flow is usable
- Studio usability pass now covers quick/full mode, text-block reorder, and version compare summaries
- [-] Full advanced editor capability set from the spec is not complete
Social/community
- Remix chains are preserved and visible
- Collections are integrated into card flows
- Challenge flows exist
- [-] Stronger creator identity exists only in a limited form
Discovery
- Rising and related content work
- Creator, collection, challenge, and template public surfaces exist
- [-] Broader discovery matrix and editorial surfacing are incomplete
AI assistance
- Optional assistive suggestions exist
- Creator remains in control
- [-] AI assistance is limited compared with the long-term vision
Moderation/trust
- Reporting and moderation hooks are in place
- Attribution and basic rights controls are preserved
- [-] Anti-abuse depth from the spec is incomplete
Technical
- v1 and v2 content remain compatible through normalization
- Schema migration is safe and test-covered
- Render/export pipeline supports v3 features currently in use
- [-] Future-ready operational tooling is only partially present
12. Bottom line
- Nova Cards v3 foundation is implemented
- The core shipping slice is real: schema versioning, Studio improvements, presets, AI assist, exports, rising, related cards, remix lineage, challenge integration, moderation/reporting, and public browsing
- [-] Several roadmap areas are only partially implemented
- The full spec in
.vscode/agents/skinbase-nova-cards-system_v3.mdis not fully implemented end to end
13. Highest-value missing areas
- Advanced editor depth beyond the recent usability pass: lock/unlock, snap guides, safe-zone helpers, and broader layer controls
- [-] Rich creator identity surfaces: featured works, featured collections, and featured creators now exist, but portfolio depth and creator-history surfaces are still missing
- Broader discovery surfaces now include style, palette, mood, best-remix, editorial, and seasonal pages
- [-] Stronger editorial tooling exists for cards, collections, challenges, and creators, but broader packaging and workflow depth are still limited
- Operational rerender/backfill tooling for long-term schema evolution