@laxture/vibe-pm 0.1.0

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 vibe-pm contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,120 @@
+# vibe-pm
+
+![NPM Version](https://img.shields.io/npm/v/@laxture/vibe-pm)
+![Test](https://github.com/hank-cp/opencode-vibe-pm/workflows/CI%20Test/badge.svg)
+![GitHub](https://img.shields.io/github/license/hank-cp/opencode-vibe-pm)
+![GitHub last commit](https://img.shields.io/github/last-commit/hank-cp/opencode-vibe-pm.svg)
+
+> **Structured development workflows for OpenCode.**
+>
+> vibe-pm is a OpenCode plugin. It keeps vibe-coding on rails.
+
+## Why vibe-pm?
+
+The problem:
+
+- `AGENTS.md` and `rules/*.md` are force-loaded into every message, **wasting context window**
+- Existing auto-trimming tools are **opaque** — you never know what was dropped or why
+- Forgetting gets worse, not better — important context vanishes silently
+
+vibe-pm solves this by injecting **only what the current step needs** — no more, no less. Every task is driven by three artifacts:
+
+| Artifact | Answers |
+|----------|---------|
+| **Spec** | What to build |
+| **Task Plan** | How to build it |
+| **Task State** | Where we are now |
+
+Key checkpoints require human approval. No silent drift.
+
+## Features
+
+1. Inject workflow control into LLM context — the plugin ensures **stable, controlled** vibe-coding sessions
+2. Teams **customize their own workflows** and continuously refine them over time
+3. **Spec + Task-driven**: every session is anchored by Spec → Plan → State
+4. Key steps enforce **human approval** — your Coding Agent never drifts off-course
+5. **Native language support** — vibe-code in your own language with a unified dictionary to eliminate naming ambiguity
+6. Collect **real-time Token usage statistics**, and display in TUI sidebar
+
+This project is built entirely with vibe-pm and Chinese as the development language.
+
+## Installation
+
+```bash
+# Install globally
+opencode plugin @laxture/vibe-pm@latest --global
+```
+
+## Quick Start
+
+```
+# Initialize configuration
+/pm-config init
+
+# Install a workflow template
+/pm-install-flow bug-fix
+
+# Start a task
+/pm-bug-fix "Login returns 500 after password reset"
+```
+
+## Use Cases
+
+```
+# Research a topic
+/pm-research Analyze migration from REST to GraphQL
+
+# Write a Spec
+/pm-design-spec Add bank card payment support
+
+# New feature (full spec-driven workflow)
+/pm-spec-driven-dev Implement feature per @docs/spec/spec-new-feature.md
+
+# Modify existing feature
+/pm-spec-driven-dev Check inventory before payment, block if stock insufficient
+
+# Bug fix (with root cause analysis)
+/pm-bug-fix Login returns 500 after password reset
+
+# Large-scale refactor (with impact assessment)
+/pm-large-refactor Extract payment module into microservice
+
+# Refine a workflow
+/pm-refine-flow Modify the bug-fix flow to require a bug ID if not provided
+```
+
+## Who's It For?
+
+- **Detail-oriented control freaks** — you want precise control over every technical decision, not leaving everything to the LLM
+- **Experienced software engineers and architects** — you likely need traditional project management experience to effectively project your management philosophy onto your Coding Agent (treat it as your loyal but dim-witted employee)
+
+If you've been haunted by "did the AI skip a step?" or "where did that decision come from?" — vibe-pm is for you.
+
+## Built-in Flow Templates
+
+| Template | Command | Use Case |
+|----------|---------|----------|
+| `design-spec` | `/pm-design-spec` | Progressive Spec design |
+| `spec-driven-dev` | `/pm-spec-driven-dev` | New feature development & feature changes (sync Spec) |
+| `bug-fix` | `/pm-bug-fix` | Bug fix with root cause analysis and fix plan review |
+| `large-refactor` | `/pm-large-refactor` | Large-scale refactoring |
+| `side-job` | `/pm-side-job` | Quick turnaround (must confirm plan before execution) |
+| `research` | `/pm-research` | General research — output findings first, then decide next steps |
+
+## Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/pm-config` | View / edit plugin config; `init` to start setup wizard |
+| `/pm-install-flow` | Install a workflow from the template library |
+| `/pm-uninstall-flow` | Remove a workflow |
+| `/pm-task-set-step` | Jump to a specific step |
+| `/pm-task-close` | Close task → trigger analysis |
+| `/pm-task-current-step` | Show current step |
+| `/pm-task-refresh` | Re-inject context for the current step |
+
+Workflow-specific commands (e.g. `/pm-research`, `/pm-bug-fix`) are auto-generated when you install a flow template.
+
+## License
+
+Apache 2.0

package/README.zh-CN.md

@@ -0,0 +1,119 @@
+# vibe-pm
+
+![NPM Version](https://img.shields.io/npm/v/@laxture/vibe-pm)
+![Test](https://github.com/hank-cp/opencode-vibe-pm/workflows/CI%20Test/badge.svg)
+![GitHub](https://img.shields.io/github/license/hank-cp/opencode-vibe-pm)
+![GitHub last commit](https://img.shields.io/github/last-commit/hank-cp/opencode-vibe-pm.svg)
+
+> **OpenCode 的结构化开发工作流插件。**
+>
+> vibe-pm是一个OpenCode插件, 它能让 vibe-coding 不跑偏。
+
+## 为什么需要 vibe-pm？
+
+当前痛点：
+
+- `AGENTS.md` 和 `rules/*.md` 强制全量加载，**浪费上下文窗口**
+- 现有的自动裁剪工具**过程不透明** — 你不知道什么被丢弃了、为什么
+- 遗忘越来越严重 — 重要上下文悄无声息地消失
+
+vibe-pm 的解法：**只注入当前步骤所需的内容** — 不多不少。每个任务由三个要素驱动：
+
+| 要素 | 回答 |
+|------|------|
+| **Spec** | 要做什么 |
+| **Task Plan** | 怎么做 |
+| **Task State** | 做到哪了 |
+
+关键节点需要人工确认，杜绝无声漂移。
+
+## 功能
+
+1. 将任务流程控制引入LLM上下文，通过插件保证 vibe-coding 过程**稳定受控**
+2. 团队可按需**定制任务流程**，并持续调整优化
+3. **Spec+任务驱动**：每次对话以 Spec → Plan → State 锚定
+4. 关键步骤强制人工审核, 确保Coding Agent每一步都不会偏离预期
+5. 支持使用**本地语言**进行vibe-coding, 通过一个统一的字典文档消除命名歧义
+6. 实时统计Token用量并在TUI侧边栏显示
+
+本项目完全使用vibe-pm插件和中文语言开发.
+
+## 适合哪些人
+
+- **细节控和控制狂** — 希望准确把控每个技术细节和决策, 而不是任由LLM自由发挥
+- **经验丰富的软件工程师和架构师** — 你可能需要经历过传统项目开发管理，有相当程度的项目管理理解, 才能更好地将你的项目管理理念投射到Coding Agent身上 (将其视为你忠诚而愚笨的员工)，
+
+如果你曾被过"AI 是不是跳过了某一步"或"这个决策是怎么来的"这类问题困扰过 — vibe-pm 就是为你准备的。
+
+## 安装
+
+```bash
+# 全局安装
+opencode plugin @laxture/vibe-pm@latest --global
+```
+
+## 快速开始
+```
+# 初始化配置
+/pm-config init
+
+# 安装流程模板
+/pm-install-flow bug-fix
+
+# 启动流程
+/pm-bug-fix "重置密码后登录报 500 错误"
+```
+
+## 典型用例
+
+```
+# 梳理需求、调研分析
+/pm-research 分析从 REST 迁移到 GraphQL 的方案
+
+# 撰写 Spec
+/pm-design-spec 需要支持用户通过银行卡支付
+
+# 新功能开发（全流程 Spec 驱动）
+/pm-spec-driven-dev 根据 @docs/spec/spec-new-feature.md 执行开发
+
+# 修改功能
+/pm-spec-driven-dev 用户支付前, 检查可用库存量, 如果不足完成订单, 则阻止支付
+
+# Bug 修复（含根因分析）
+/pm-bug-fix 重置密码后登录报 500 错误
+
+# 大规模重构（含影响评估）
+/pm-large-refactor "将支付模块拆分为独立微服务"
+
+# 流程优化
+/pm-refine-flow 修改bug-fix流程, 如果我没有提供Bug编号, 要求我必须提供
+```
+
+## 内置流程模板
+
+| 模板                | 命令                    | 适用场景                                |
+|-------------------|-----------------------|-------------------------------------|
+| `design-spec`     | `/pm-design-spec`     | 渐进式 Spec 设计                         |
+| `spec-driven-dev` | `/pm-spec-driven-dev` | 新功能开发 与 功能变更(同步更新Spec)              |
+| `bug-fix`         | `/pm-bug-fix`         | 与期望不符的 Bug 修复, 含根因分析和修复方案评审         |
+| `large-refactor`  | `/pm-large-refactor`  | 大规模重构                               |
+| `side-job`        | `/pm-side-job`        | 快速任务(执行前需确认方案)                      |
+| `research`        | `/pm-research`        | 通用调研任务, 可将分析报告输出到临时位置, 再根据分析报告进行下一步 |
+
+## 命令
+
+| 命令 | 用途 |
+|------|------|
+| `/pm-config` | 查看/修改插件配置，`init` 启动初始化向导 |
+| `/pm-install-flow` | 从模板库安装流程 |
+| `/pm-uninstall-flow` | 移除流程 |
+| `/pm-task-set-step` | 手动跳转到指定步骤 |
+| `/pm-task-close` | 关闭任务，触发分析 |
+| `/pm-task-current-step` | 查看当前步骤 |
+| `/pm-task-refresh` | 为当前步骤重新注入上下文 |
+
+流程专用命令（如 `/pm-research`、`/pm-bug-fix`）会在安装对应流程模板后自动生成。
+
+## License
+
+Apache 2.0

package/dist/core/commands.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Command Registration
+ *
+ * Registers all 8 /pm-* commands via the config hook (declarative) and
+ * tool hook (executable). Uses the @opencode-ai/plugin SDK tool() factory.
+ * Executable commands invoke FlowEngine and MemorySystem for real business logic.
+ */
+import { Config, IPluginContext, ToolDefinition } from './types.js';
+import type { FlowEngine } from '../engine';
+import type { MemorySystem } from '../memory';
+export declare function registerCommands(opencodeConfig: Config): void;
+export declare function registerFlowCommands(opencodeConfig: Config, projectDir: string): void;
+/**
+ * Create tool registry using the SDK tool() factory + Zod schemas.
+ */
+export declare function registerTools(ctx: IPluginContext, engine: FlowEngine, memory: MemorySystem): Record<string, ToolDefinition>;
+export declare function registerFlowTools(ctx: IPluginContext, engine: FlowEngine): Record<string, ToolDefinition>;

package/dist/core/config.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Configuration Management
+ *
+ * Loads vibe-pm/config.json from the project directory. Supports defaults,
+ * merge override, and graceful fallback on parse errors.
+ * Auto-creates a default config file on startup.
+ */
+import type { PluginConfig } from './types.js';
+export declare const DEFAULT_CONFIG: PluginConfig;
+export declare function loadConfig(projectDir: string): PluginConfig;
+export declare function writeConfig(projectDir: string, config: PluginConfig): void;
+export declare function ensureDefaultConfig(projectDir: string): boolean;

package/dist/core/index.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Plugin Core Unified Exports
+ */
+export { VibePMPlugin } from './plugin.js';
+export { loadConfig, DEFAULT_CONFIG, writeConfig, ensureDefaultConfig } from './config.js';
+export { registerCommands, registerTools } from './commands.js';
+export { logger } from './logger.js';
+export type * from './types.js';

package/dist/core/logger.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Logging Utility
+ *
+ * Writes to the host log system via the OpenCode SDK's app.log().
+ * Public interface unchanged: logger.debug / info / warn / error.
+ */
+import type { ILogger } from './types.js';
+interface LogClient {
+    app: {
+        log(options: {
+            body?: {
+                service: string;
+                level: 'debug' | 'info' | 'warn' | 'error';
+                message: string;
+                extra?: Record<string, unknown>;
+            };
+        }): Promise<unknown>;
+    };
+}
+export declare function initLogger(c: LogClient): void;
+export declare function setLogEnabled(v: boolean): void;
+export declare const logger: ILogger;
+export {};

package/dist/core/plugin.d.ts

@@ -0,0 +1,2 @@
+import type { Plugin } from './types.js';
+export declare const VibePMPlugin: Plugin;

package/dist/core/types.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Plugin Core Type Definitions
+ *
+ * OpenCode interaction types are imported via the @opencode-ai/plugin SDK.
+ * Project-specific domain types are defined here.
+ */
+/** Subset of hooks a module can contribute, types from SDK */
+import type { ToolDefinition } from '@opencode-ai/plugin';
+import type { OpencodeClient } from '@opencode-ai/sdk';
+export type { Plugin, PluginInput, Hooks, Config, ToolContext, ToolDefinition, } from '@opencode-ai/plugin';
+export { tool } from '@opencode-ai/plugin';
+export interface PluginConfig {
+    language: string;
+    dataDir: string;
+    autoAnalyze: boolean;
+    /** List of project programming languages analyzed by LLM, cached after first analysis. Prioritized during flow installation. */
+    programmingLanguages?: string[];
+    contextInjection: {
+        /** Max context injection tokens per step, 0 means no limit */
+        maxStepTokens: number;
+        pruneIrrelevant: boolean;
+    };
+    debug?: {
+        /** Output full request context at end of system.transform (default false) */
+        logFullRequest?: boolean;
+    };
+}
+export interface IPluginContext {
+    readonly config: PluginConfig;
+    readonly projectDir: string;
+    readonly dataDir: string;
+    readonly client: OpencodeClient;
+}
+export interface ILogger {
+    debug(...args: unknown[]): void;
+    info(...args: unknown[]): void;
+    warn(...args: unknown[]): void;
+    error(...args: unknown[]): void;
+}
+export type ToolDefinitionWithKey = ToolDefinition & {
+    toolKey: string;
+};

package/dist/docs/template/_coding_style/general.md

@@ -0,0 +1,114 @@
+# General Coding Style
+
+> This file is the general coding standard for unsupported languages. When the project's language has no specific style guide, this file serves as the baseline.
+
+## General Format
+
+- Use UTF-8 encoding, LF line endings
+- Use the project's designated formatter
+- Indentation follows project convention (recommended 2 or 4 spaces)
+- Line length should not exceed 100 characters
+- Keep one blank line at end of file
+
+## File Organization
+
+### Naming
+
+- Source files use project convention (recommended `kebab-case` or `snake_case`)
+- Directory names use project convention (recommended `kebab-case`)
+- Test file naming follows project convention
+
+### Import / Dependency Resolution
+
+1. Standard library / built-in modules
+2. Third-party dependencies
+3. Project internal modules
+
+### File Structure
+
+- Prefer one primary export per file
+- Use named exports for helper types/functions
+- Expose a clean public API from each module
+
+## Naming Conventions
+
+### Variables
+
+- Use project convention (recommended `camelCase` or `snake_case`)
+- Short scope → short names
+- Long scope → descriptive names
+- Boolean variables use question-word prefixes
+- Do not use Hungarian notation
+
+### Constants
+
+- Use project convention (recommended `UPPER_SNAKE_CASE`)
+
+### Functions
+
+- Use project convention (recommended `camelCase` or `snake_case`)
+- Start with a verb
+
+### Types / Interfaces / Classes
+
+- Use project convention (recommended `PascalCase`)
+- Do not prefix interface/type names
+
+### Enums / Union Types
+
+- Follow project convention
+
+## Type Safety
+
+- Avoid dynamic types / any-type
+- Prefer type annotations / type hints
+- Explicit error handling; never swallow exceptions
+
+## Function Design
+
+### Parameters
+
+- Use object/struct parameters when exceeding 3 parameters
+
+### Return Values
+
+- Prefer returning concrete types
+- For nullable scenarios, use project convention (e.g., `Result<T, E>`, `Optional<T>`, `(T, error)`)
+
+## Control Flow
+
+- Prefer early returns to reduce nesting depth
+
+## Async Handling
+
+- Use the language/framework's recommended async pattern
+
+## Error Handling
+
+- All errors must be handled explicitly
+- Validate inputs at system boundaries
+- Do not add "impossible" error handling in internal logic
+
+## Logging
+
+- Use the project's unified logging module
+- Log messages in English
+- Record info/debug logs on critical paths
+
+## Comments & Documentation
+
+- Code comments in English
+- Add doc comments to public APIs
+- Add explanatory comments for complex logic
+
+## Placeholder Code
+
+```
+// TODO(username): needs API integration — expected v1.1
+// FIXME(username): potential data race under concurrency — needs locking
+// HACK(username): temporary workaround — replace after v1.0
+```
+
+## Export Conventions
+
+Use the language/framework's recommended visibility control