@tungvivas/angular-vibe-kit 0.1.0 → 0.3.0

package/templates/docs/srs/README.md

@@ -0,0 +1,29 @@
+# SRS (source requirements)
+
+Drop your **already-split** SRS excerpts here — one file per module/feature, not the whole
+multi-module document. If your SRS is a Word doc converted via `pandoc` into one large Markdown
+file with an images folder, extract just the section you're about to build and save it here,
+keeping any image references relative and valid.
+
+## Convention
+
+```
+docs/srs/
+├── module-5-order-management.md
+├── module-6-invoicing.md
+└── images/                        # keep paths relative to match what pandoc generated
+```
+
+## Usage
+
+This folder is **not** auto-read — `/plan` doesn't scan it on its own. Point to the file
+explicitly when you start planning:
+
+```
+/plan
+
+Đọc yêu cầu từ docs/srs/module-5-order-management.md
+```
+
+Keep these files committed — they're the record of what was actually asked for each module,
+useful when a later module needs to know how an earlier one was scoped.

package/templates/rules/project-rules.md

@@ -49,11 +49,27 @@ When guidance conflicts, follow this order top to bottom:
 ## Coding Rules
 > /init will generate concrete rules based on Angular version + what the project does.
 
+## Component Wrapper Priority
+- ALWAYS check `docs/DESIGN_SYSTEM.md` → **Wrapped Components** before importing a UI library
+- If a wrapper exists for the need → import the wrapper (e.g. `import { AppSelectComponent } from '@shared/components/select'`), NEVER the raw library (`p-dropdown`)
+- If no wrapper exists → use the library directly and log a warning to the user: `> ⚠️ No wrapper for <X> — using library directly. Consider creating one in shared/components/`
+- If unsure whether a wrapper exists → ASK the team before writing the import
+- This rule is enforced by `/review-pr` (🔴 BLOCKER if violated in new code)
+
 ## DO NOT
 - Do NOT use `any`
 - Do NOT call HttpClient from components
 - Do NOT store tokens in localStorage
 - Do NOT hardcode the backend URL
+- Do NOT import UI library components directly in features when a wrapper exists in `shared/components/`
+
+## Commit Convention
+> Read by the `git-commit` skill and the `angular-git-workflow` agent. /init fills this from `git log`.
+- **Prefix**: {{none}}  <!-- prepended before <type>, e.g. "VIVAS_"; default: none -->
+- **Language**: {{vi}}  <!-- subject/body language for commits AND /explain output; default: vi -->
+- **Format**: `<prefix><type>(<scope>): <subject>`
+- **Scope source**: top-level folder under {{src/app/features | src/app/modules | ...}} of the changed files; multiple modules → omit scope
+- **Types**: feat, fix, refactor, docs, style, test, chore, perf, ci, build, revert
 
 ## Reference Examples
 > /init fills this with the best existing files to copy patterns from.