agentleFS
peter-tu-zynkrpeter-tu-zynkr/zynkr-skill-builder/skills/1-brand-marketing/slide-arch-diagram/SKILL.md

slide-arch-diagram

Skill21 starsChanged 51 days agoNo licenceView on GitHub

Turn an ideated business workflow into a slide-ready FE/BE/DB architecture diagram: three horizontal lanes (前端 Front End · 後端 Back End · 資料庫 Database) with the workflow's IPO units stitched LEFT→RIGHT across them — human inputs drop ↓ from the FE lane into dark octagon process nodes chained → across the BE lane, stored knowledge feeds ↑ from the DB lane, and the output document rises ↑ back to FE at the far right, closed by exactly ONE orange 'law line' verdict bottom-right. Trigger when the user hands over a workflow (free text, an IPO breakdown, or a SLIDE_PACKET ▸ Pages entry) and says 'draw this as an architecture diagram', 'draw the FE/BE/DB view', 'architecture slide for this workflow', '畫成架構圖', '畫 FE/BE/DB', '前後端架構圖', '工作流架構圖', '把這個流程畫上簡報', or when slide-visual-selector routes an architecture-flavoured process-diagram page here. Boundaries: renders HTML/CSS slide pages (artifact decks) — for the same FE/BE/DB convention drawn into Lucid charts use product-flow-design; for generic per-page layout selection use slide-visual-selector; this skill does not write storylines, paginate, or render .pptx.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 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.

  • 2

    Very specific

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

No licence file, so all rights are reserved — 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 372,429 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.