agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/artifact-system-designer/SKILL.md

artifact-system-designer

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to design, reorganize, clean up, structure, govern, or create the operating model for a document or artifact system. Use for documentation repositories, knowledge bases, governance libraries, strategy packs, project evidence rooms, SOP libraries, audit folders, client file systems, reusable document operating models, folder systems, naming standards, metadata schemas, artifact indexes, source-of-truth models, versioning rules, review states, approval flows, archives, lifecycle rules, routing rules, and maintenance discipline. Use when the user asks what should go in each folder, which file should be authoritative, how to prevent duplicates or stale files, how to organize project documents, how to build a controlled library, or how to make artifacts reusable and searchable. Do not use for drafting a single standalone SOP, policy, memo, PRD, board update, contract, or report unless the user also asks for the surrounding artifact system. If the primary task is drafting a controlled artifact, use ssot-drafter. If the primary task is documenting one recurring process, use process-docs or ssot-drafter. If the primary task is validation, acceptance checks, defect logs, evidence requirements, or pass/fail readiness, use artifact-validation-workflow. If the primary task is delivery sequencing, roadmap, issue tree, dependency tree, or WBS, use wbs-artifact-planner. If the primary task is a source-backed dossier for an entity, decision, risk, client, project, or product, use dossier-builder.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free