WhyBuddy: Instructions file for Kiro

.kiro/steering/web-aigc-node-spec-template-constraints.md

WhyBuddy web-aigc-node-spec-template-constraints.md is an instructions file for Kiro from xiaojilele-glitch/WhyBuddy. It costs 2,357 tokens per session, scanned A, original, MIT.

A writing template and set of naming rules for specifications describing Web-AIGC workflow nodes. Each specification uses requirements, design, and task documents with consistent names, inputs, outputs, states, and observation details.

In plain words
What is it for?
Use it when creating or reviewing node specifications, especially the requirements, design, and task documents that define how a node starts, runs, fails, recovers, and is observed.
Why use it?
Without a shared format, similar nodes can describe the same concepts differently, making their documents harder to compare, implement, and maintain.

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/web-aigc-node-spec-template-constraints.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 web-aigc-node-spec-template-constraints.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/web-aigc-node-spec-template-constraints/github.svg)](https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/web-aigc-node-spec-template-constraints)
Your own site
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/web-aigc-node-spec-template-constraints"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/web-aigc-node-spec-template-constraints/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 web-aigc-node-spec-template-constraints.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/web-aigc-node-spec-template-constraints"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/web-aigc-node-spec-template-constraints.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,357 This file is loaded in full into every session.
When invoked 2,357 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.02357 $0.02357
Opus 5.5 $0.00943 $0.00943
Sonnet 5.5 $0.00471 $0.00471
Haiku 4.5 $0.00236 $0.00236

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

Security

Grade A, and why

WhyBuddy web-aigc-node-spec-template-constraints.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/web-aigc-node-spec-template-constraints.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Web-AIGC 节点 Spec 统一模板约束

目的

本文档约束后续 52 个 web-aigc 节点 spec 的统一写法,避免每个节点各自定义命名、状态、输入输出、观测事件和承接边界。

本文档是 .kiro/specs/web-aigc-platform-domain-model 的直接落地产物,面向后续所有节点 spec 编写者使用。

适用范围

  • 适用于所有 web-aigc-node-* spec。
  • 适用于 requirements.md、design.md、tasks.md 三件套。
  • 不适用于平台总模型 spec、观测总模型 spec、安全治理总模型 spec 这类“平台级总前提”文档。

强制命名约束

spec 目录命名

  • 目录名必须使用 web-aigc-node-<node_type>。
  • node_type 必须与共享领域模型中的节点类型一致。
  • 不允许在目录名中引入实现细节、团队缩写或临时版本号。

文档标题命名

  • requirements.md 标题格式必须为:# 需求文档:<节点中文名>
  • design.md 标题格式必须为:# 设计文档:<节点中文名>
  • tasks.md 标题格式必须为:# 任务清单:<节点中文名>

节点类型命名

  • 文档中引用节点类型时,统一使用反引号包裹的源节点标识,例如:user_input
  • 不允许在不同节点 spec 中为同一节点创造别名。

三件套统一结构

requirements.md 结构约束

每个节点 spec 的 requirements.md 必须包含以下部分,且顺序保持一致:

  1. # 需求文档:<节点中文名>
  2. ## 目标
  3. ## 需求
  4. 至少 3 条 ### 需求 N:...

每条需求必须满足:

  • 只描述外部可观察能力,不写实现细节。
  • 必须使用“系统应...”或“节点应...”句式。
  • 必须覆盖以下三类中的至少三项:
    • 节点进入条件或等待条件
    • 输入/配置/输出行为
    • 恢复、分支、失败、审计、观测中的至少一项

design.md 结构约束

每个节点 spec 的 design.md 必须包含以下部分,且顺序保持一致:

  1. # 设计文档:<节点中文名>
  2. ## 设计概述
  3. ## 接口映射
  4. ## 运行流程

如节点复杂度较高,可在末尾追加:

  • ## 状态与分支
  • ## 观测与审计
  • ## 风险与边界

接口映射强制项

## 接口映射 中至少要写清楚:

  • web-aigc 原节点名
  • Cube 承接入口
  • 若涉及人工输入,必须写出 server/routes/tasks.ts
  • 若涉及观测、审计、回放,必须写出对应承接面,例如 replay / audit / monitoring

运行流程强制项

## 运行流程 必须使用编号列表,且至少覆盖:

  1. 节点何时进入执行或等待
  2. 输入/判断/选择如何发生
  3. 如何产出输出或决策结果
  4. 如何恢复、推进或分流

tasks.md 结构约束

每个节点 spec 的 tasks.md 必须满足:

  • 只写可以被证明完成的实现任务,不写空泛目标。
  • 每个任务项必须能映射到代码、测试或文档产物。
  • 默认控制在 3 到 6 项。
  • 任务措辞统一使用动词开头,例如:
    • 定义...
    • 复用...
    • 写入...
    • 接入...
    • 验证...

勾选规则

  • 只有在当前主工作区已有明确产物时才能勾选。
  • “代码存在但未形成闭环”不能勾选。
  • “只有契约,无路由/运行时/测试”不能勾选“接入”或“验证”类任务。
  • “验证”类任务原则上要求至少有可追溯测试或明确的端到端证明。

统一领域模型约束

后续 52 个节点 spec 都必须复用平台领域模型,不允许自创第二套模型。

必须复用的统一实体

  • 定义态:graph_definition / graph_version / node_schema / edge_schema
  • 运行态:graph_instance / node_run / edge_transition / session_link
  • 投影态:workflow_link / mission_link / replay_link / audit_link

Read the full file on GitHub · 287 lines

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 · 287 lines · 2,357 tokens per session scan A cdbeec58b4ca

Subscribe to this mod's changes

WhyBuddy web-aigc-node-spec-template-constraints.md is an instructions file published in the GitHub repository xiaojilele-glitch/WhyBuddy (380 stars, last pushed 1mo ago), licensed MIT. It adds 2,357 tokens to every session, about $0.0094 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 web-aigc-node-spec-template-constraints.md compared with instructions from other repositories

WhyBuddy web-aigc-node-spec-template-constraints.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
WhyBuddy web-aigc-node-spec-template-constraints.mdxiaojilele-glitch/WhyBuddyInstructions file3801mo agoMITA2,357Kiro
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode