In short:
ak-assets-organizingsettles the path once, in order: the place you name, then the repo's existing convention, and only then the fallbackassets/folder tree. It can also tidy a whole messy folder. It does not rename or move existing files unless you ask.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you are about to create a post, a banner set or a report and need to know where to write the file and what to name it, or when an export folder has become a mess.
flowchart LR
A["Marketing content to save"] --> B["ak-assets-organizing"]
C["Messy asset folder"] --> B
B --> D["Settled path and name"]
B --> E["Source-to-destination table, fixed links"]
D --> F["Write the file to the right place"]Four concepts to know:
| Concept | Question | Example |
|---|---|---|
| Path order | Where does this file go? | You say "save to docs/emails/" and it uses exactly that; otherwise it follows the repo's usual place; if the repo has nothing, it uses assets/copy/emails/ |
| Keep what exists | May it rename, move old files or change links? | Banner Final.png keeps that name; only when you say "rename to the standard" does it change |
| One file or a whole set | What does a small job check, and what does a big one add? | Saving one email: check for name clashes, then write. Tidying 40 files: a source-to-destination table, a plan for name clashes, link fixes within scope |
| Default names and dates | How are files named when the repo has no convention? | A lowercase hyphenated slug of at most 50 characters, with a YYMMDD-HHmm date prefix, for example 261021-1430-email-subject-line-tips.md |
Multi-file assets (video, storyboard, campaign) share their own folder. Single-file assets stay flat.
Sample prompt for saving a new asset:
/ak-assets-organizing I am about to write the first welcome email in the onboarding sequence
for <product name>. Pick the path and file name for me, then create an empty file.This skill has no flags.
Below is the detailed version: the run flow, 5 situations with prompts, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-assets-organizing: settle where marketing files go and what they are called" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-assets-organizing". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-assets-organizing
