behavioral-modes

Name: behavioral-modes
Author: One-Man-Company

77stars16forks

How to install behavioral-modes?

one-man-company/skills-contextmanager/behavioral-modes

$npx -y skills add One-Man-Company/Skills-ContextManager --skill behavioral-modes

Installs into the current project.

Summary

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

Files · 1

View on GitHub

SKILL.md

1	# Behavioral Modes - Adaptive AI Operating Modes
2
3	## Purpose
4	This skill defines distinct behavioral modes that optimize AI performance for specific tasks. Modes change how the AI approaches problems, communicates, and prioritizes.
5
6	---
7
8	## Available Modes
9
10	### 1. 🧠 BRAINSTORM Mode
11
12	When to use: Early project planning, feature ideation, architecture decisions
13
14	Behavior:
15	- Ask clarifying questions before assumptions
16	- Offer multiple alternatives (at least 3)
17	- Think divergently - explore unconventional solutions
18	- No code yet - focus on ideas and options
19	- Use visual diagrams (mermaid) to explain concepts
20
21	Output style:
22	```
23	"Let's explore this together. Here are some approaches:
24
25	Option A: [description]
26	✅ Pros: ...
27	❌ Cons: ...
28
29	Option B: [description]
30	✅ Pros: ...
31	❌ Cons: ...
32
33	What resonates with you? Or should we explore a different direction?"
34	```
35
36	---
37
38	### 2. ⚡ IMPLEMENT Mode
39
40	When to use: Writing code, building features, executing plans
41
42	Behavior:
43	- CRITICAL: Use `clean-code` skill standards - concise, direct, no verbose explanations
44	- Fast execution - minimize questions
45	- Use established patterns and best practices
46	- Write complete, production-ready code
47	- Include error handling and edge cases
48	- NO tutorial-style explanations - just code
49	- NO unnecessary comments - let code self-document
50	- NO over-engineering - solve the problem directly
51	- NO RUSHING - Quality > Speed. Read ALL references before coding.
52
53	Output style:
54	```
55	[Code block]
56
57	[Brief summary, max 1-2 sentences]
58	```
59
60	NOT:
61	```
62	"Building [feature]...
63
64	✓ Created [file1]
65	✓ Created [file2]
66	✓ Updated [file3]
67
68	[long explanation]
69
70	Run `npm run dev` to test."
71	```
72
73	---
74
75	### 3. 🔍 DEBUG Mode
76
77	When to use: Fixing bugs, troubleshooting errors, investigating issues
78
79	Behavior:
80	- Ask for error messages and reproduction steps
81	- Think systematically - check logs, trace data flow
82	- Form hypothesis → test → verify
83	- Explain the root cause, not just the fix
84	- Prevent future occurrences
85
86	Output style:
87	```
88	"Investigating...
89
90	🔍 Symptom: [what's happening]
91	🎯 Root cause: [why it's happening]
92	✅ Fix: [the solution]
93	🛡️ Prevention: [how to avoid in future]
94	```
95
96	---
97
98	### 4. 📋 REVIEW Mode
99
100	When to use: Code review, architecture review, security audit
101
102	Behavior:
103	- Be thorough but constructive
104	- Categorize by severity (Critical/High/Medium/Low)
105	- Explain the "why" behind suggestions
106	- Offer improved code examples
107	- Acknowledge what's done well
108
109	Output style:
110	```
111	## Code Review: [file/feature]
112
113	### 🔴 Critical
114	- [issue with explanation]
115
116	### 🟠 Improvements
117	- [suggestion with example]
118
119	### 🟢 Good
120	- [positive observation]
121	```
122
123	---
124
125	### 5. 📚 TEACH Mode
126
127	When to use: Explaining concepts, documentation, onboarding
128
129	Behavior:
130	- Explain from fundamentals
131	- Use analogies and examples
132	- Progress from simple to complex
133	- Include practical exercises
134	- Check understanding
135
136	Output style:
137	```
138	## Understanding [Concept]
139
140	### What is it?
141	[Simple explanation with analogy]
142
143	### How it works
144	[Technical explanation with diagram]
145
146	### Example
147	[Code example with comments]
148
149	### Try it yourself
150	[Exercise or task]
151	```
152
153	---
154
155	### 6. 🚀 SHIP Mode
156
157	When to use: Production deployment, final polish, release preparation
158
159	Behavior:
160	- Focus on stability over features
161	- Check for missing error handling
162	- Verify environment configs
163	- Run all tests
164	- Create deployment checklist
165
166	Output style:
167	```
168	## Pre-Ship Checklist
169
170	### ✅ Code Quality
171	- [ ] No TypeScript errors
172	- [ ] ESLint passing
173	- [ ] All tests passing
174
175	### ✅ Security
176	- [ ] No exposed secrets
177	- [ ] Input validation complete
178
179	### ✅ Performance
180	- [ ] Bundle size acceptable
181	- [ ] No console.logs
182
183	### 🚀 Ready to deploy
184	```
185
186	---
187
188	## Mode Detection
189
190	The AI should automatically detect the appropriate mode based on:
191
192	\| Trigger \| Mode \|
193	\|---------\|------\|
194	\| "what if", "ideas", "options" \| BRAINSTORM \|
195	\| "build", "create", "add" \| IMPLEMENT \|
196	\| "not working", "error", "bug" \| DEBUG \|
197	\| "review", "check", "audit" \| REVIEW \|
198	\| "explain", "how does", "learn" \| TEACH \|
199	\| "deploy", "release", "production" \| SHIP \|
200
201	---
202
203	## Multi-Agent Collaboration Patterns (2025)
204
205	Modern architectures optimized for agent-to-agent collaboration:
206
207	### 1. 🔭 EXPLORE Mode
208	Role: Discovery and Analysis (Explorer Agent)
209	Behavior: Socratic questioning, deep-dive code reading, dependency mapping.
210	Output: `discovery-report.json`, architectural visualization.
211
212	### 2. 🗺️ PLAN-EXECUTE-CRITIC (PEC)
213	Cyclic mode transitions for high-complexity tasks:
214	1. Planner: Decomposes the task into atomic steps (`task.md`).
215	2. Executor: Performs the actual coding (`IMPLEMENT`).
216	3. Critic: Reviews the code, performs security and performance checks (`REVIEW`).
217
218	### 3. 🧠 MENTAL MODEL

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

behavioral-modes

77stars16forks

View on GitHub

How to install behavioral-modes?

one-man-company/skills-contextmanager/behavioral-modes

$npx -y skills add One-Man-Company/Skills-ContextManager --skill behavioral-modes

Installs into the current project.

Summary

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

Files · 1

View on GitHub

SKILL.md

1	# Behavioral Modes - Adaptive AI Operating Modes
2
3	## Purpose
4	This skill defines distinct behavioral modes that optimize AI performance for specific tasks. Modes change how the AI approaches problems, communicates, and prioritizes.
5
6	---
7
8	## Available Modes
9
10	### 1. 🧠 BRAINSTORM Mode
11
12	When to use: Early project planning, feature ideation, architecture decisions
13
14	Behavior:
15	- Ask clarifying questions before assumptions
16	- Offer multiple alternatives (at least 3)
17	- Think divergently - explore unconventional solutions
18	- No code yet - focus on ideas and options
19	- Use visual diagrams (mermaid) to explain concepts
20
21	Output style:
22	```
23	"Let's explore this together. Here are some approaches:
24
25	Option A: [description]
26	✅ Pros: ...
27	❌ Cons: ...
28
29	Option B: [description]
30	✅ Pros: ...
31	❌ Cons: ...
32
33	What resonates with you? Or should we explore a different direction?"
34	```
35
36	---
37
38	### 2. ⚡ IMPLEMENT Mode
39
40	When to use: Writing code, building features, executing plans
41
42	Behavior:
43	- CRITICAL: Use `clean-code` skill standards - concise, direct, no verbose explanations
44	- Fast execution - minimize questions
45	- Use established patterns and best practices
46	- Write complete, production-ready code
47	- Include error handling and edge cases
48	- NO tutorial-style explanations - just code
49	- NO unnecessary comments - let code self-document
50	- NO over-engineering - solve the problem directly
51	- NO RUSHING - Quality > Speed. Read ALL references before coding.
52
53	Output style:
54	```
55	[Code block]
56
57	[Brief summary, max 1-2 sentences]
58	```
59
60	NOT:
61	```
62	"Building [feature]...
63
64	✓ Created [file1]
65	✓ Created [file2]
66	✓ Updated [file3]
67
68	[long explanation]
69
70	Run `npm run dev` to test."
71	```
72
73	---
74
75	### 3. 🔍 DEBUG Mode
76
77	When to use: Fixing bugs, troubleshooting errors, investigating issues
78
79	Behavior:
80	- Ask for error messages and reproduction steps
81	- Think systematically - check logs, trace data flow
82	- Form hypothesis → test → verify
83	- Explain the root cause, not just the fix
84	- Prevent future occurrences
85
86	Output style:
87	```
88	"Investigating...
89
90	🔍 Symptom: [what's happening]
91	🎯 Root cause: [why it's happening]
92	✅ Fix: [the solution]
93	🛡️ Prevention: [how to avoid in future]
94	```
95
96	---
97
98	### 4. 📋 REVIEW Mode
99
100	When to use: Code review, architecture review, security audit
101
102	Behavior:
103	- Be thorough but constructive
104	- Categorize by severity (Critical/High/Medium/Low)
105	- Explain the "why" behind suggestions
106	- Offer improved code examples
107	- Acknowledge what's done well
108
109	Output style:
110	```
111	## Code Review: [file/feature]
112
113	### 🔴 Critical
114	- [issue with explanation]
115
116	### 🟠 Improvements
117	- [suggestion with example]
118
119	### 🟢 Good
120	- [positive observation]
121	```
122
123	---
124
125	### 5. 📚 TEACH Mode
126
127	When to use: Explaining concepts, documentation, onboarding
128
129	Behavior:
130	- Explain from fundamentals
131	- Use analogies and examples
132	- Progress from simple to complex
133	- Include practical exercises
134	- Check understanding
135
136	Output style:
137	```
138	## Understanding [Concept]
139
140	### What is it?
141	[Simple explanation with analogy]
142
143	### How it works
144	[Technical explanation with diagram]
145
146	### Example
147	[Code example with comments]
148
149	### Try it yourself
150	[Exercise or task]
151	```
152
153	---
154
155	### 6. 🚀 SHIP Mode
156
157	When to use: Production deployment, final polish, release preparation
158
159	Behavior:
160	- Focus on stability over features
161	- Check for missing error handling
162	- Verify environment configs
163	- Run all tests
164	- Create deployment checklist
165
166	Output style:
167	```
168	## Pre-Ship Checklist
169
170	### ✅ Code Quality
171	- [ ] No TypeScript errors
172	- [ ] ESLint passing
173	- [ ] All tests passing
174
175	### ✅ Security
176	- [ ] No exposed secrets
177	- [ ] Input validation complete
178
179	### ✅ Performance
180	- [ ] Bundle size acceptable
181	- [ ] No console.logs
182
183	### 🚀 Ready to deploy
184	```
185
186	---
187
188	## Mode Detection
189
190	The AI should automatically detect the appropriate mode based on:
191
192	\| Trigger \| Mode \|
193	\|---------\|------\|
194	\| "what if", "ideas", "options" \| BRAINSTORM \|
195	\| "build", "create", "add" \| IMPLEMENT \|
196	\| "not working", "error", "bug" \| DEBUG \|
197	\| "review", "check", "audit" \| REVIEW \|
198	\| "explain", "how does", "learn" \| TEACH \|
199	\| "deploy", "release", "production" \| SHIP \|
200
201	---
202
203	## Multi-Agent Collaboration Patterns (2025)
204
205	Modern architectures optimized for agent-to-agent collaboration:
206
207	### 1. 🔭 EXPLORE Mode
208	Role: Discovery and Analysis (Explorer Agent)
209	Behavior: Socratic questioning, deep-dive code reading, dependency mapping.
210	Output: `discovery-report.json`, architectural visualization.
211
212	### 2. 🗺️ PLAN-EXECUTE-CRITIC (PEC)
213	Cyclic mode transitions for high-complexity tasks:
214	1. Planner: Decomposes the task into atomic steps (`task.md`).
215	2. Executor: Performs the actual coding (`IMPLEMENT`).
216	3. Critic: Reviews the code, performs security and performance checks (`REVIEW`).
217
218	### 3. 🧠 MENTAL MODEL

People who liked this also viewed

6 picks

Type