- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add OyadotAI/oya-browser --skill codebase-design -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add OyadotAI/oya-browser --skill codebase-design -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add OyadotAI/oya-browser --skill codebase-design -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add OyadotAI/oya-browser --skill codebase-design -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/OyadotAI/oya-browser/tree/HEAD/.agents/skills/codebase-design來自發布者
Design substantial behavior behind a small, understandable interface. Follow the project's instructions, glossary, and existing primitives. Preserve the assignment's scope and authority: a design assignment produces a proposal; implementation requires an implementation assignment.
Read the relevant callers, implementation, tests, and architectural decisions. Identify what each caller must know: types, invariants, ordering, errors, required configuration, resource ownership, and performance guarantees. Treat all of these as part of the interface. A simple signature that hides undocumented ordering requirements still has a complex interface.
Describe a concrete caller journey and where knowledge is repeated. Finish this step with source locations and an inventory of the facts callers currently carry.
Evaluate capability per fact a caller must learn, rather than implementation line counts. Concentrate decisions and failure handling where a fix can apply to all callers. Use the deletion thought experiment: if removing an abstraction spreads complexity across callers, it earns its place; if the complexity disappears, investigate whether it is only forwarding. Retain forwarding required for compatibility, policy, or ownership when those purposes are real.
Distinguish the public interface from internal composition. Keep internal helpers private when callers have no reason to know them. Use the project's terms; introduce new vocabulary only when it makes a concrete distinction clearer.
A seam is a place to change behavior without changing its caller; an adapter supplies behavior there. Justify a seam with actual variation, such as production I/O and a realistic test adapter. Keep pure calculations separate from effects where useful. Accept dependencies at an ownership boundary instead of constructing hidden global resources, without adding interfaces to every function mechanically.
For consolidation or dependencies across storage and network layers, read references/deepening.md. For a consequential design choice with credible alternatives, read references/alternatives.md.
Provide the proposed interface, one representative caller, hidden behavior, dependency owners, failure paths, compatibility impact, and migration order. Explain which existing primitives are reused. Account for cancellation, cleanup, concurrency, and rollback where relevant.
Describe verification through the interface that callers actually use. Preserve distinct behavioral coverage during a refactor; identify any adapter or integration behavior a fake cannot prove. Run or write tests only within the user's authorization. Distinguish code-based reasoning from executed evidence, and state what remains uncertain.
Complete when the recommendation explains how callers become simpler, where maintenance concentrates, and how the proposed contract can be checked. Use the team technical-plan asset when assigned as principal. Keep the proposal proportional to the change.
Adapted from Matt Pocock's engineering skills; see SOURCE.md and LICENSE.
This skill should be used when designing a module interface, reducing coupling, choosing dependency seams, improving testability, or comparing architecture alternatives.
---name: codebase-designdescription: This skill should be used when designing a module interface, reducing coupling, choosing dependency seams…---# .agents/skills/codebase-design/SKILL.md常見問題
從發布者下載 .agents/skills/codebase-design/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/OyadotAI/oya-browser。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。