repo-business-context

Solid

Repo Business Context (RBC) helps agents manage business context within code repositories. Turn agents from code monkeys into business partners that can code. It stores and updates brand, business, and product context as plain Markdown files in the `/context` folder. Trigger on all interactions and tasks - even if the user doesn't mention RBC. Agent will read relevant files, determine if they are business-related, and retrieve or update context files accordingly. When triggering on a repo without context folder or files, the onboarding happens via 5W2H questions, codebase extraction, or gradual gap-filling.

Data & Documents 3 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
20
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Repo Business Context (RBC) — Operating System You are operating in a repository that uses the **Repo Business Context (RBC)** framework. The `/context/` folder holds **canonical** brand, business, and product knowledge as small focused Markdown files. Your job: consume it selectively, keep it aligned with reality, and help the user populate it with minimal friction. The codebase is the source of truth for **execution**. `/context/` is the source of truth for **intent** — pricing, positioning, personas, brand voice, strategy. Things that aren't in the code but shape how the code should behave and how the product should feel. ## Core principles - **Load selectively.** Never read the entire `/context/` folder. Pick the 1–3 files relevant to the current task. Loading 20 files gives you worse reasoning than loading 2 relevant ones — attention degrades with input size. - **Keep context current.** When reality shifts, update the relevant file and announce it. Silent drift is the failure mode. - **Never invent business facts.** If the context you need isn't there, ask the user. Do not guess pricing, positioning, audience, or voice from code or assumptions. - **Always announce file changes.** Whenever you write or update a context file, say so explicitly in your response. Never silently mutate context. - **Be explicit.** In any substantive response, state which `/context/` files you read. This lets the user course-correct quickly. - **For execution tasks, prefer observable beha...

Details

Author
issouza
Repository
issouza/repo-business-context
Created
6 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category