@stilero/bankan 1.2.0 → 1.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/server/src/config.js +32 -5
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@stilero/bankan",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Run AI coding agents like a Kanban board. Plan, implement, review and ship code using parallel AI agents across your local repositories.",
|
|
6
6
|
"license": "MIT",
|
package/server/src/config.js
CHANGED
|
@@ -92,11 +92,38 @@ Key rules:
|
|
|
92
92
|
- Ask for clarification only when a blocking unknown cannot be resolved from the repository context
|
|
93
93
|
- Do not ask for approval in free-form prose; the human approval flow happens outside your response
|
|
94
94
|
- Keep the plan specific, implementation-ready, and grounded in the current codebase`,
|
|
95
|
-
implementation: `Follow the plan step by step
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
-
|
|
99
|
-
-
|
|
95
|
+
implementation: `Follow the plan step by step. Execute each step fully before moving on.
|
|
96
|
+
|
|
97
|
+
## Use Subagents to Stay Focused
|
|
98
|
+
- Use subagents liberally to keep the main context window clean
|
|
99
|
+
- Offload research, exploration, file search, and parallel analysis to subagents
|
|
100
|
+
- Reserve the main context for implementation decisions and code changes
|
|
101
|
+
|
|
102
|
+
## Be Autonomous
|
|
103
|
+
- When given a task: just do it. Don't ask for hand-holding.
|
|
104
|
+
- If something goes wrong, investigate logs, errors, and failing tests — then resolve them.
|
|
105
|
+
- Fix failing tests without being told how.
|
|
106
|
+
- If required tools or dependencies are missing in the workspace, install them before continuing.
|
|
107
|
+
|
|
108
|
+
## Core Principles
|
|
109
|
+
- **Simplicity First**: Make every change as simple as possible. Impact minimal code.
|
|
110
|
+
- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
|
|
111
|
+
- **Minimal Impact**: Only touch what's necessary. No side effects with new bugs.
|
|
112
|
+
- **Demand Elegance (Balanced)**: For non-trivial changes, pause and ask "is there a more elegant way?" Skip this for simple, obvious fixes — don't over-engineer.
|
|
113
|
+
|
|
114
|
+
## Mandatory Test Verification
|
|
115
|
+
- Follow TDD when practical: create or update the failing test first, implement the change second, then rerun the suite.
|
|
116
|
+
- Run existing tests after implementation to verify nothing broke.
|
|
117
|
+
- Run the linter before finishing.
|
|
118
|
+
|
|
119
|
+
## Definition of Done
|
|
120
|
+
- All plan steps are completed.
|
|
121
|
+
- Code compiles/runs without errors.
|
|
122
|
+
- Relevant tests pass (new and existing).
|
|
123
|
+
- Linter passes with no new violations.
|
|
124
|
+
- Commit after each logical unit of work with descriptive commit messages.
|
|
125
|
+
- Version bump if applicable, following the repository's versioning conventions.
|
|
126
|
+
- After all work is done, make a final commit if there are any uncommitted changes.`,
|
|
100
127
|
review: `You are an expert code reviewer.
|
|
101
128
|
|
|
102
129
|
Step 1 — Gather the diff
|