WhyBuddy: Instructions file for Kiro

.kiro/steering/competitive-landscape-2026-04-21.md

WhyBuddy competitive-landscape-2026-04-21.md is an instructions file for Kiro from xiaojilele-glitch/WhyBuddy. It costs 600 tokens per session, scanned A, original, MIT.

A research note about competing platforms for visual AI workflows and agents, including Dify, Flowise, Langflow, and n8n. It compares their overlap with SlideRule and records where SlideRule may differ.

In plain words
What is it for?
Use it to inform product strategy, market comparisons, and wording for public documentation. It is a landscape snapshot rather than an implementation guide.
Why use it?
It prevents product decisions from relying on the false idea that no similar tools exist. The note helps define a more accurate position based on combined workflow, task, audit, and replay capabilities.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is xiaojilele-glitch/WhyBuddy's own configuration. It tells Kiro how to work on WhyBuddy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WhyBuddy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xiaojilele-glitch/WhyBuddy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xiaojilele-glitch/WhyBuddy/main/.kiro/steering/competitive-landscape-2026-04-21.md
Clone the repo
git clone --depth 1 https://github.com/xiaojilele-glitch/WhyBuddy

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for WhyBuddy competitive-landscape-2026-04-21.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/competitive-landscape-2026-04-21/github.svg)](https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/competitive-landscape-2026-04-21)
Your own site
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/competitive-landscape-2026-04-21"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/competitive-landscape-2026-04-21/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for WhyBuddy competitive-landscape-2026-04-21.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/competitive-landscape-2026-04-21"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/competitive-landscape-2026-04-21.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 600 This file is loaded in full into every session.
When invoked 600 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00600 $0.00600
Opus 5.5 $0.00240 $0.00240
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 1mo ago against content hash 7ee35787b8c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WhyBuddy competitive-landscape-2026-04-21.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.kiro/steering/competitive-landscape-2026-04-21.md · 61 lines

What it actually says

竞争格局快照(2026-04-21)

文档目的

这份说明文档用于澄清平台定位。目标不是声称 GitHub 上完全没有类似开源平台,而是明确 SlideRule 真正还能形成差异化的位置。

市场现实

目前 GitHub 上已经存在不少覆盖相邻问题空间的开源项目,例如:

  • Dify:应用构建、工作流编排、知识库、Agent 能力
  • Flowise:可视化 LLM 工作流与 Agent 构建器
  • Langflow:面向 LLM 系统的可视化流程编辑
  • n8n:通用自动化平台,正在持续增强 AI 工作流能力
  • LangGraph 生态:图式 / 状态化 Agent 编排
  • AutoGen 生态:多 Agent 协作与编排
  • RAGFlow:偏 RAG 和知识处理的平台
  • Mastra / CrewAI 一类生态:强调 Agent 与工作流运行时抽象

Cube 仍然可以形成的差异化

SlideRule 可以占据一个更少见的组合位置:

  • 图式编排能力 + mission-native 执行模型
  • 内建 replay、audit、lineage 与 operator control
  • 更偏 office / task operating model,而不是单纯开发者画布
  • 多模态、RAG、权限治理、外部执行器链路一体化
  • 可以把 graph instance 投影进已经存在的 mission / task runtime

战略结论

更准确、更稳妥的说法应该是:

“相邻平台已经存在,但真正同时把图式 Agent 编排、mission 运行时、回放、审计、operator control、office-native 执行壳整合到一套系统中的平台并不多。”

这个判断,比“GitHub 上完全没有这种平台”更准确,也更有说服力。

对文档体系的启发

超细文档仍然是优势,但前提是:

  • 能体现集成深度
  • 能维护整体架构一致性
  • 能真正指导迁移执行
  • 不是简单堆一批互不相关的 Markdown

这也是为什么 50+ 文档体系必须采用分层结构,而不能平铺。

对外表达建议

以后在路线图或对外描述里,建议:

  • 避免绝对化的“全球首创 / GitHub 无同类”表述
  • 强调平台集成深度,而不是只强调节点数量
  • 强调 replay、governance、operator-facing runtime 这些组合能力
  • 把 web-aigc 迁移表述为“能力增强”,而不是“整个平台克隆”
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 61 lines · 600 tokens per session scan A 7ee35787b8c7

Subscribe to this mod's changes

WhyBuddy competitive-landscape-2026-04-21.md is an instructions file published in the GitHub repository xiaojilele-glitch/WhyBuddy (380 stars, last pushed 1mo ago), licensed MIT. It adds 600 tokens to every session, about $0.0024 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.

Related

WhyBuddy competitive-landscape-2026-04-21.md compared with instructions from other repositories

WhyBuddy competitive-landscape-2026-04-21.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
WhyBuddy competitive-landscape-2026-04-21.mdxiaojilele-glitch/WhyBuddyInstructions file3801mo agoMITA600Kiro
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode