Organize project marketing assets with ak:assets-organizing

Use ak:assets-organizing to choose consistent paths and filenames for marketing files under a project-owned assets/ tree. The Skill supplies naming, date, directory, and asset-type conventions for new outputs and for an approved reorganization of existing files.

It is a convention and file-organization workflow. It does not upload assets, publish them, validate their content, deduplicate by file contents, or manage a digital-asset platform.

Choose ak:assets-organizing for local file structure

Use ak:assets-organizing when

• A new marketing output needs a predictable project-local destination.
• Existing assets need a proposed mapping into assets/ categories.
• A campaign or multi-file deliverable should remain self-contained.
• You need consistent kebab-case slugs, date prefixes, variants, platform folders, or scene numbering.

Choose another workflow when

• You need to create or edit the asset itself. Use the relevant writing, design, image, video, audio, or analysis Skill.
• You need cloud sync, CDN publication, provider metadata, rights management, or a remote asset catalog.
• You need binary deduplication, checksums, media validation, or a reversible migration tool. This Skill ships no dedicated organizing script.
• You cannot review exact source and destination paths before files change.

Prepare the project and authority boundary

Before running the Skill:

• Complete Onboarding and install Marketing Kit for the current runtime and scope.
• Open the project whose assets/ directory you intend to inspect.
• Preserve unrelated and untracked work.
• State whether the run is preview-only or may create directories, move files, or rename files after approval.
• Define collision behavior. The safe default is never overwrite, delete, or replace an existing path.
• Identify sensitive, licensed, client-owned, or source-controlled files that must not be moved or exposed.

See Runtime adapters for component-level differences.

Start with a preview-only mapping

/ak:assets-organizing Audit ./incoming-assets and propose target paths under assets/. Return a source-to-destination table. Do not create, move, rename, delete, or overwrite any file until I approve the exact mapping

/ak:assets-organizing Audit ./incoming-assets and propose target paths under assets/. Return a source-to-destination table. Do not create, move, rename, delete, or overwrite any file until I approve the exact mapping

$ak:assets-organizing Audit ./incoming-assets and propose target paths under assets/. Return a source-to-destination table. Do not create, move, rename, delete, or overwrite any file until I approve the exact mapping

The public argument hint is [directory or asset-type]. Always add the desired outcome and mutation boundary; a directory alone does not say whether you want an audit, a proposed structure, or approved file changes.

Apply the canonical naming rules

The packaged references conflict on article dating: the quick path uses assets/articles/{date}-{slug}/, while the asset-type guidance calls articles evergreen and says to omit the date prefix. Do not silently choose. Ask the owner whether the article is time-bound, then record the selected convention.

Use the smallest useful path pattern

Do not create every listed directory preemptively. Create only the parent and children required by the approved deliverable. If an intentionally empty directory must be tracked in Git, the source convention uses .gitkeep, which is another file creation to review.

Understand the stages

1. Inventory the requested scope. List source files, types, sizes, current locations, and relevant relationships without reading or moving unrelated content.
2. Classify each deliverable. Choose the narrowest asset class and determine whether it is a single file, multi-file bundle, campaign group, or platform-specific output.
3. Generate names. Apply the approved slug, date, variant, and scene rules.
4. Check collisions. Compare every destination with existing files and identify case-only, extension, version, and folder conflicts.
5. Present a mapping. Show source, proposed destination, rule used, and any unresolved choice. No mutation occurs in preview-only mode.
6. Apply only approved changes. Create the minimum directories, then write, move, or rename only the accepted paths without overwriting.
7. Verify. Confirm every expected file exists at its destination and report unchanged sources, skipped conflicts, and any partial failure.

Keep file effects safe and reversible

• Preview is read-only. Directory creation, file creation, rename, move, copy, overwrite, and delete are separate mutations.
• Default to copy-and-verify or version-control-backed moves when recovery is important. Do not delete the source as part of an unreviewed cleanup.
• Search for references to every moved path and update them only within the approved scope.
• Preserve file bytes, metadata that matters to the workflow, and unrelated user changes. A naming convention is not permission to rewrite contents.
• Organization is local only. It does not authorize upload, publication, provider requests, account changes, or spend.

Verify outputs and evidence

A complete run should provide:

• A source-to-destination mapping with the chosen naming rule for every file.
• A list of created directories and changed paths.
• Collision decisions and skipped files.
• Evidence that expected destination files exist and required references still resolve.
• A list of source files intentionally preserved or removed, with approval for any removal.
• Remaining ambiguities, especially the article date convention or an unknown asset type.

Troubleshoot or continue

Continue with Projects, artifacts, and checkpoints before recovery, or return to the Marketing Kit overview.

Know the current limits

• The Skill supplies conventions but no dedicated script for atomic moves, rollback, checksums, content deduplication, or reference rewriting.
• Several source examples still use legacy command names. Treat the canonical runtime Skill name as ak:assets-organizing and use examples only as path guidance.
• Asset-type references contain broad templates with placeholder claims, metrics, pricing, and ROI fields. Never fill those with invented data.