What is WhyBuddy project-overview.md?

A product overview for SlideRule, now branded 端云 / SlideRule, describing a project-first AI work system. It covers the shift from individual task automation toward projects that move through clarification, specifications, routes, role-based execution, evidence, and deliverables.

Use it to understand the main product flow, branding boundaries, project-based work, task autopilot, runtime defaults, and role-based execution.

It explains the product direction and how edge execution, such as in a browser or on a laptop, can work alongside shared cloud services. It also gives developers a common model for connecting project, task, runtime, and evidence features.

How xiaojilele-glitch/WhyBuddy configures Kiro

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/project-overview.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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/project-overview/github.svg)](https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/project-overview)

Your own site

<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/project-overview"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/project-overview/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/project-overview"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/project-overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12,263 This file is loaded in full into every session.

When invoked 12,263 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.

Model	Per session	Once invoked
Fable 5.1	$0.12263	$0.12263
Opus 5.5	$0.04905	$0.04905
Sonnet 5.5	$0.02453	$0.02453
Haiku 4.5	$0.01226	$0.01226

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

Security

Grade A, and why

WhyBuddy project-overview.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/project-overview.md · 657 lines

How it starts

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

inclusion: auto

2026-05-28 Rebrand: 端云 / SlideRule

This project's user-facing brand has changed from SlideRule to 端云 / SlideRule. Strategy is alias-first, not big-bang rename:

User-visible touchpoints (HTML title, login, loading, README hero, package.json name) consume shared/brand.ts.
Internal symbols (file names, module identifiers, audit / lineage event families, the 287 spec dirs, this steering file's older sections) keep their existing strings; a future sliderule-internal-rename spec will carry out the coordinated sweep.
The legacy package name lives on as BRAND_PACKAGE_LEGACY in shared/brand.ts for places that still need to reference the old token.

The name expands to 端 (edge / endpoint) + 云 (cloud) — workloads run at the edge when they can (browser runtime, native sandbox, your laptop's Docker), and fall back to the cloud when they need shared coordination (LLM, MCP servers, the Lobster Executor service).

2026-04-30 Project-first next phase

This project overview now treats Project-first as the next product mainline above the closed Task Autopilot Phase 1 baseline.

The user-facing chain is:

Project -> Clarification -> Spec -> Route -> Execution -> Evidence

Project is the first durable product object and the user's return point for intent, messages, specs, routes, missions, artifacts, and evidence.
Clarification is project-scoped and resolves missing context, constraints, permissions, acceptance criteria, and risk boundaries.
Spec turns clarified project intent into an inspectable, versioned contract for scope, deliverables, acceptance criteria, and evidence expectations.
Route is planned through FSD role packages, including main, conservative, fallback, and takeover paths.
Execution continues to run through the existing Mission / Workflow / Runtime / Executor stack; Project-first does not introduce a parallel runtime.
Evidence writes artifacts, logs, decisions, replay records, audit facts, and delivery review back to the project context.

Read the full file on GitHub · 657 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.

1mo ago First seen · 657 lines · 12,263 tokens per session scan A 4415e27d6b93

Subscribe to this mod's changes

WhyBuddy project-overview.md is an instructions file published in the GitHub repository xiaojilele-glitch/WhyBuddy (380 stars, last pushed 1mo ago), licensed MIT. It adds 12,263 tokens to every session, about $0.0491 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.

Building agents Project management ai ai-agent ai-agents anthropic chatgpt claude

WhyBuddy project-overview.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
WhyBuddy project-overview.mdxiaojilele-glitch/WhyBuddy	Instructions file	380	1mo ago	MIT	A	12,263	Kiro
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

WhyBuddy: Instructions file for Kiro