dify-workflow-architect
Skill1 starsChanged 3 months agoNo licenceView on GitHub
设计 Dify AI 工作流的系统化方法论 - 帮助 Tom 从产品需求出发，设计 LLM + Code 协作的多节点工作流。覆盖文档处理类需求（PRD/合同/会议纪要 → 结构化产出，如埋点表/任务卡/用户故事）、跨平台集成（Lark/飞书/Notion API、Web Hook）、错误处理与兜底、迭代式版本管理、PM 与开发协作的最佳实践。触发时机（宁可多触发也不要漏触发）：- 用户说"做个 Dify 工作流"、"AI 工作流"、"自动化处理 X 文档"、"PRD 转 X"、"自动生成 Y 表" - 用户在迭代现有 Dify 工作流（修改节点、调整 prompt、加新分支）- 用户讨论 LLM + Code 配对、节点架构、工作流分层 - 用户对接 Lark/飞书/Notion/Jira 等外部平台到 Dify - 用户讨论 Dify workflow yml / DSL / 节点输入输出 - 用户问"这个工作流怎么设计"、"流程跑不通"、"plugin 报错" 不要用于：单纯写 LLM prompt（用 prompt-engineering 类 skill），简单的一次性 LLM 调用脚本，数据科学项目（用 alpha-lab），文档创作（用 ealy-pitch 等）。
In this repository43 other files it gives its agents.
- alpha-labSkill
- binance-trader-scraperSkill
- chrome-cdpSkill
- codex-auditSkill
- comparison-dashboardSkill
- data-request-kitSkill
- decision-deckSkill
- demo-video-kitSkill
- dev-plannerSkill
- docsSkill
- docxSkill
- ealy-pitchSkill
- ego-messengerSkill
- exec-proposalSkill
- friction-playbookSkill
- git-cleanupSkill
- google-workspaceSkill
- group-sync-messengerSkill
- import-memorySkill
- jira-card-kitSkill
- lark-docx-authoringSkill
- mexc-daily-insightSkill
- mexc-infographicSkill
- morningSkill
- okr-reportSkill
- pdfSkill
- pm-interview-prepSkill
- polymarket-execution-auditSkill
- pptxSkill
- prd-authoring-kitSkill
- prd-kit-releaseSkill
- prd-reviewerSkill
- prd-writerSkill
- proposal-deckSkill
- proposal-playbookSkill
- pvp-team-designerSkill
- quant-code-reviewSkill
- session-memorySkill
- showcase-demoSkill
- skill-creatorSkill
- user-research-reportSkill
- video-makingSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
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 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
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.