prompt-suite 1.0.2 → 1.0.3

package/flows/ps.0-gen-rules.prompt.md

@@ -2,7 +2,7 @@
 description: Initialize workflow rules for project (requirement, design, code, test)
 ---
 
-# /df.0-gen-rules
+# /ps.0-gen-rules
 
 ## Description
 Create workflow rules for all SDLC steps. Each step has 2 rules: gen-rule (for generation) and rev-rule (for review).
@@ -18,8 +18,8 @@ Create workflow rules for all SDLC steps. Each step has 2 rules: gen-rule (for g
 
 **Input Type: File Path (Required)**
 - Provides path to a text file containing Step, Stack, Architecture, etc.
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
-- Template file available at: `/devflow-prompts/templates/gen-rule-template.txt`
+- **File can be located anywhere** (not limited to `/prompt-suite`)
+- Template file available at: `/prompt-suite/templates/gen-rule-template.txt`
 - Format inside file:
   ```text
   Step: ...
@@ -48,82 +48,82 @@ Create workflow rules for all SDLC steps. Each step has 2 rules: gen-rule (for g
 ## Output Format
 
 ### Output Location:
-- **Base directory**: `<repo_root>/devflow-prompts/rules/`
+- **Base directory**: `<repo_root>/prompt-suite/rules/`
 - **Auto-creation**: Directory will be created automatically if it doesn't exist
 - **File handling**: Existing files will be overwritten. **Review carefully before running.**
 
 ### Rules Structure:
 ```
-/devflow-prompts/rules/
-├── df.1-gen-requirement.rule.md
-├── df.1-rev-requirement.rule.md
-├── df.2-gen-design.rule.md
-├── df.2-rev-design.rule.md
-├── df.3-gen-code.rule.md
-├── df.3-rev-code.rule.md
-├── df.4-gen-test-plan.rule.md
-├── df.4-rev-test-plan.rule.md
-├── df.5-gen-test-code.rule.md
-└── df.5-rev-test-code.rule.md
+/prompt-suite/rules/
+├── ps.1-gen-requirement.rule.md
+├── ps.1-rev-requirement.rule.md
+├── ps.2-gen-design.rule.md
+├── ps.2-rev-design.rule.md
+├── ps.3-gen-code.rule.md
+├── ps.3-rev-code.rule.md
+├── ps.4-gen-test-plan.rule.md
+├── ps.4-rev-test-plan.rule.md
+├── ps.5-gen-test-code.rule.md
+└── ps.5-rev-test-code.rule.md
 ```
 
 ### Rule Content by Step:
 
 **Step 1 (Requirement):**
-- `df.1-gen-requirement.rule.md`: Guidelines for converting raw request → requirement document
+- `ps.1-gen-requirement.rule.md`: Guidelines for converting raw request → requirement document
   - What to include, what to avoid
   - Template structure requirements
   - Acceptance criteria format
   - Edge case documentation
-- `df.1-rev-requirement.rule.md`: Checklist for reviewing requirement documents
+- `ps.1-rev-requirement.rule.md`: Checklist for reviewing requirement documents
   - Completeness checks
   - Clarity verification
   - Testability assessment
   - Common mistakes to catch
 
 **Step 2 (Design):**
-- `df.2-gen-design.rule.md`: Guidelines for creating tech design from requirement
+- `ps.2-gen-design.rule.md`: Guidelines for creating tech design from requirement
   - Architecture principles (Clean Architecture, etc.)
   - Security requirements
   - API specification format
   - Data model design rules
-- `df.2-rev-design.rule.md`: Checklist for reviewing tech design
+- `ps.2-rev-design.rule.md`: Checklist for reviewing tech design
   - Architecture compliance
   - Security verification
   - API completeness
   - Implementation feasibility
 
 **Step 3 (Code):**
-- `df.3-gen-code.rule.md`: Coding standards and conventions
+- `ps.3-gen-code.rule.md`: Coding standards and conventions
   - Backend/Frontend coding rules
   - Layer separation
   - Error handling patterns
   - Security implementation
-- `df.3-rev-code.rule.md`: Code review checklist
+- `ps.3-rev-code.rule.md`: Code review checklist
   - Code quality checks
   - Security verification
   - Performance considerations
   - Test coverage requirements
 
 **Step 4 (Test Plan):**
-- `df.4-gen-test-plan.rule.md`: Guidelines for creating test plans
+- `ps.4-gen-test-plan.rule.md`: Guidelines for creating test plans
   - Test level strategy (unit/integration/E2E)
   - Coverage requirements
   - Test case format
   - Mock/stub guidelines
-- `df.4-rev-test-plan.rule.md`: Test plan review checklist
+- `ps.4-rev-test-plan.rule.md`: Test plan review checklist
   - Coverage verification
   - Test case quality
   - Edge case inclusion
   - Feasibility assessment
 
 **Step 5 (Test Code):**
-- `df.5-gen-test-code.rule.md`: Test code writing standards
+- `ps.5-gen-test-code.rule.md`: Test code writing standards
   - Test structure conventions
   - Assertion best practices
   - Test data management
   - Deterministic test requirements
-- `df.5-rev-test-code.rule.md`: Test code review checklist
+- `ps.5-rev-test-code.rule.md`: Test code review checklist
   - Test quality verification
   - Coverage confirmation
   - Reliability checks
@@ -150,7 +150,7 @@ INSTRUCTIONS:
    - The user will provide a file path.
    - USE `view_file` tool to read its content.
    - **Fallback**: If the tool is unavailable or fails, ask the user to paste the file content directly.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Parse Information**:
    - Extract **Step** (required): Which step/rule to generate
@@ -164,8 +164,8 @@ TASK:
 Generate gen-rule and rev-rule files based on STEP parameter:
 - If Step = `1`, `2`,... → Generate BOTH gen-rule and rev-rule for that step.
 - If Step = `all` → Generate ALL 10 files.
-- If Step = `X-gen` → Generate ONLY `df.X-gen-....rule.md`.
-- If Step = `X-rev` → Generate ONLY `df.X-rev-....rule.md`.
+- If Step = `X-gen` → Generate ONLY `ps.X-gen-....rule.md`.
+- If Step = `X-rev` → Generate ONLY `ps.X-rev-....rule.md`.
 
 Follow the 9-section template structure defined below.
 
@@ -201,23 +201,23 @@ COMMON REQUIREMENTS (apply to ALL steps):
 
 STEP-SPECIFIC FOCUS (only the delta for each step):
 
-**Step 1 (Requirement) - Files: df.1-gen-requirement.rule.md, df.1-rev-requirement.rule.md**
+**Step 1 (Requirement) - Files: ps.1-gen-requirement.rule.md, ps.1-rev-requirement.rule.md**
 - gen: Acceptance criteria format, edge case documentation, error scenarios, what to avoid (inventing requirements, vague criteria)
 - rev: Testability assessment, ambiguity checks, contradiction detection
 
-**Step 2 (Design) - Files: df.2-gen-design.rule.md, df.2-rev-design.rule.md**
+**Step 2 (Design) - Files: ps.2-gen-design.rule.md, ps.2-rev-design.rule.md**
 - gen: Architecture principles (based on specified approach), security patterns, API specs (endpoints, request/response, errors), data model (migrations, indexes), observability (logs, metrics, tracing)
 - rev: Architecture compliance, security verification, API completeness, data model safety, implementation feasibility
 
-**Step 3 (Code) - Files: df.3-gen-code.rule.md, df.3-rev-code.rule.md**
+**Step 3 (Code) - Files: ps.3-gen-code.rule.md, ps.3-rev-code.rule.md**
 - gen: Layer separation (domain/application/infrastructure), naming conventions (classes, functions, variables), error handling patterns, security implementation, performance best practices
 - rev: Code quality (readability, maintainability), architecture compliance, security vulnerabilities, performance considerations, test coverage, code smells
 
-**Step 4 (Test Plan) - Files: df.4-gen-test-plan.rule.md, df.4-rev-test-plan.rule.md**
+**Step 4 (Test Plan) - Files: ps.4-gen-test-plan.rule.md, ps.4-rev-test-plan.rule.md**
 - gen: Test strategy (unit/integration/E2E), coverage requirements, test case format, mock/stub guidelines, test data requirements
 - rev: Coverage verification (all use cases covered?), test case quality, edge case inclusion, feasibility
 
-**Step 5 (Test Code) - Files: df.5-gen-test-code.rule.md, df.5-rev-test-code.rule.md**
+**Step 5 (Test Code) - Files: ps.5-gen-test-code.rule.md, ps.5-rev-test-code.rule.md**
 - gen: Test structure (AAA pattern), assertion best practices, test data management, deterministic tests (no flaky tests), mocking guidelines
 - rev: Test quality, coverage confirmation, reliability (no flaky tests), maintainability
 
@@ -237,7 +237,7 @@ STRICT OUTPUT RULE:
 
 SELF-CHECK BEFORE OUTPUT:
 1. Verify all required files for the Step are generated.
-2. Verify filenames match exactly (e.g., `df.1-gen-requirement.rule.md`).
+2. Verify filenames match exactly (e.g., `ps.1-gen-requirement.rule.md`).
 3. Verify all 9 sections are present in every file.
 ```
 
@@ -304,8 +304,8 @@ SELF-CHECK BEFORE OUTPUT:
 
 ### Example 1: Generate all rules
 ```bash
-/df.0-gen-rules /path/to/my-project-rules.txt
-# → Generates all 10 files in /devflow-prompts/rules/ (step1-5, each with gen + rev)
+/ps.0-gen-rules /path/to/my-project-rules.txt
+# → Generates all 10 files in /prompt-suite/rules/ (step1-5, each with gen + rev)
 ```
 
 ⚠️ **Warning**: This will overwrite existing rule files. Commit your changes first!
@@ -313,23 +313,23 @@ SELF-CHECK BEFORE OUTPUT:
 ### Example 2: Generate only step 1 rules (Requirement)
 ```bash
 # In your input file: Step: 1
-/df.0-gen-rules /path/to/step1-rules.txt
-# → Generates: df.1-gen-requirement.rule.md, df.1-rev-requirement.rule.md
+/ps.0-gen-rules /path/to/step1-rules.txt
+# → Generates: ps.1-gen-requirement.rule.md, ps.1-rev-requirement.rule.md
 ```
 
 ### Example 3: Generate step 2 rules (Design)
 ```bash
 # In your input file: Step: 2
-/df.0-gen-rules /path/to/step2-rules.txt
-# → Generates: df.2-gen-design.rule.md, df.2-rev-design.rule.md
+/ps.0-gen-rules /path/to/step2-rules.txt
+# → Generates: ps.2-gen-design.rule.md, ps.2-rev-design.rule.md
 ```
 
 ### Example 4: Generate step 3 rules (Code) in Vietnamese
 ```bash
 # In your input file: Language: vi
-/df.0-gen-rules /path/to/step3-vi-rules.txt
-# → Generates: df.3-gen-code.rule.md, df.3-rev-code.rule.md (in Vietnamese)
+/ps.0-gen-rules /path/to/step3-vi-rules.txt
+# → Generates: ps.3-gen-code.rule.md, ps.3-rev-code.rule.md (in Vietnamese)
 ```
 
 ## Next Steps
-After generating workflow rules → run `/df.0-rev-rules` to review and improve
+After generating workflow rules → run `/ps.0-rev-rules` to review and improve

package/flows/ps.0-rev-rules.prompt.md

@@ -2,7 +2,7 @@
 description: Review and improve workflow rules for consistency
 ---
 
-# /df.0-rev-rules
+# /ps.0-rev-rules
 
 ## Description
 Review and improve workflow rules for all SDLC steps. Detect contradictions, gaps, and suggest improvements.
@@ -19,9 +19,9 @@ Review and improve workflow rules for all SDLC steps. Detect contradictions, gap
 **Input Type: File Path OR Directory Path (Required)**
 - **File Path**: Reviews that specific rule file.
 - **Directory Path**: Reviews ALL rule files (`*.rule.md`) in that directory.
-- **Files/Dirs can be located anywhere** (not limited to `/devflow-prompts`)
-- Example File: `/path/to/df.1-gen-requirement.rule.md`
-- Example Dir: `/path/to/devflow-prompts/rules/`
+- **Files/Dirs can be located anywhere** (not limited to `/prompt-suite`)
+- Example File: `/path/to/ps.1-gen-requirement.rule.md`
+- Example Dir: `/path/to/prompt-suite/rules/`
 - AI will automatically read the files
 
 ## Input Validation
@@ -30,7 +30,7 @@ Review and improve workflow rules for all SDLC steps. Detect contradictions, gap
 - **Rule Content**:
   - If Directory: Must contain valid `.rule.md` files.
   - If File: Must be a valid `.rule.md` file (or text file with rule definitions).
-- **Step Identification**: AI must be able to infer the Step ID (1-5) from the filename (e.g., `df.1-...`) or content.
+- **Step Identification**: AI must be able to infer the Step ID (1-5) from the filename (e.g., `ps.1-...`) or content.
 
 **If validation fails**: Stop immediately and output error message.
 
@@ -125,12 +125,12 @@ STRICT OUTPUT RULE:
 
 ### Option 1: Review Single File
 ```bash
-/df.0-rev-rules /path/to/df.1-gen-requirement.rule.md
+/ps.0-rev-rules /path/to/ps.1-gen-requirement.rule.md
 ```
 
 ### Option 2: Review Directory (All Rules)
 ```bash
-/df.0-rev-rules /path/to/devflow-prompts/rules/
+/ps.0-rev-rules /path/to/prompt-suite/rules/
 # → Finds and reviews all *.rule.md files in that folder
 ```
 
@@ -153,4 +153,4 @@ STRICT OUTPUT RULE:
 - "Never use if-else" → too extreme
 
 ## Next Steps
-After reviewing and improving workflow rules → Start using them with `/df.1-gen-requirement`
+After reviewing and improving workflow rules → Start using them with `/ps.1-gen-requirement`

package/flows/ps.1-gen-requirement.prompt.md

@@ -2,7 +2,7 @@
 description: Convert raw customer request to structured requirement document
 ---
 
-# /df.1-gen-requirement
+# /ps.1-gen-requirement
 
 ## Description
 
@@ -30,7 +30,7 @@ Convert raw customer request into a structured, clear, and testable requirement
 - If Mode is `UPDATE`, provide current business rules or code snippets to be modified.
 
 **Rule File** (optional but recommended):
-- `df.1-gen-requirement.rule.md` from `/devflow-prompts/rules/` - Guidelines for generating requirements
+- `ps.1-gen-requirement.rule.md` from `/prompt-suite/rules/` - Guidelines for generating requirements
 
 ## Input Validation
 
@@ -47,7 +47,7 @@ File markdown: `{#task-id}-requirement.md`
 **Folder Structure**: All feature artifacts must be stored in:
 
 ```
-/devflow-prompts/specs/{#task-id}/
+/prompt-suite/specs/{#task-id}/
 ├── {#task-id}-requirement.md
 ├── {#task-id}-design.md
 ├── {#task-id}-test.md
@@ -55,7 +55,7 @@ File markdown: `{#task-id}-requirement.md`
 └── {#task-id}-test.patch
 ```
 
-Example: `/devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md`
+Example: `/prompt-suite/specs/FEAT-001/FEAT-001-requirement.md`
 
 ## Template
 
@@ -147,7 +147,7 @@ INSTRUCTIONS:
    - The user will provide a file path.
    - USE `view_file` tool to read its content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
    **Behave based on Mode (if specified in file or prompt)**:
    - **IF Mode is UPDATE**:
@@ -191,7 +191,7 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.1-gen-requirement ~/Desktop/FEAT-001-request.txt
+/ps.1-gen-requirement ~/Desktop/FEAT-001-request.txt
 ```
 
 ## Common Mistakes to Avoid
@@ -276,4 +276,4 @@ Raw request: "メール/パスワードでログインできるようにした
 
 ## Next Steps
 
-After requirement is ready → run `/df.1-rev-requirement` to review
+After requirement is ready → run `/ps.1-rev-requirement` to review

package/flows/ps.1-rev-requirement.prompt.md

@@ -2,7 +2,7 @@
 description: Review requirement document for completeness and clarity
 ---
 
-# /df.1-rev-requirement
+# /ps.1-rev-requirement
 
 ## Description
 Review requirement document to detect gaps, ambiguities, contradictions, and suggest improvements.
@@ -14,7 +14,7 @@ Review requirement document to detect gaps, ambiguities, contradictions, and sug
 - **Filename MUST contain task-id** (e.g., `FEAT-001-requirement.md`, `FEAT-001.md`, `my-FEAT-001-spec.md`)
   - Task-id is needed to name output files
   - Can be anywhere in filename, any format: `TASK-123`, `FEAT-001`, `BUG-456`
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
+- **File can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/Desktop/FEAT-001-requirement.md` ✅
   - `/tmp/TASK-123-spec.md` ✅
@@ -23,7 +23,7 @@ Review requirement document to detect gaps, ambiguities, contradictions, and sug
 - AI will automatically read file and extract task-id from filename
 
 **Rule File** (optional but recommended):
-- `df.1-rev-requirement.rule.md` from `/devflow-prompts/rules/` (for quality checklist)
+- `ps.1-rev-requirement.rule.md` from `/prompt-suite/rules/` (for quality checklist)
 
 
 
@@ -64,7 +64,7 @@ INSTRUCTIONS:
    - The user will provide a file path.
    - USE `view_file` tool to read its content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filename using pattern: `[A-Z]+-[0-9]+`
@@ -141,7 +141,7 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.1-rev-requirement /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md
+/ps.1-rev-requirement /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
 ```
 
 ## Common Issues Found
@@ -203,4 +203,4 @@ Error/Edge cases:
 ```
 
 ## Next Steps
-After clarifying → run `/df.2-gen-design` to create technical design
+After clarifying → run `/ps.2-gen-design` to create technical design

package/flows/ps.2-gen-design.prompt.md

@@ -1,7 +1,7 @@
 ---
 description: Create technical design from requirement (architecture, API, data model)
 ---
-# /df.2-gen-design
+# /ps.2-gen-design
 
 ## Description
 
@@ -14,7 +14,7 @@ Create technical design document from requirement and coding rules, including ar
 - **Filename MUST contain task-id** (e.g., `FEAT-001-requirement.md`, `TASK-123.md`)
   - Task-id is needed to name output design file
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
+- **File can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/Documents/FEAT-001-requirement.md` ✅
   - `/tmp/TASK-123-spec.md` ✅
@@ -26,10 +26,10 @@ Create technical design document from requirement and coding rules, including ar
 - `NEW`: Designing a new feature.
 - `UPDATE`: Modifying existing design/code. **Requires strict impact analysis.**
 
-**Coding Rule Files** (from `/devflow-prompts/rules/`):
-- `df.2-gen-design.rule.md` (required) - Architecture, API, Security guidelines. 
+**Coding Rule Files** (from `/prompt-suite/rules/`):
+- `ps.2-gen-design.rule.md` (required) - Architecture, API, Security guidelines. 
 **MUST define project structure/roots.**
-- `df.3-gen-code.rule.md` (optional) - For implementation context
+- `ps.3-gen-code.rule.md` (optional) - For implementation context
 
 **Language** (optional): Output language (default: `en`)
 
@@ -37,7 +37,7 @@ Create technical design document from requirement and coding rules, including ar
 
 - **Requirement file**: Required, must exist
 - **File name**: MUST contain task-id pattern `[A-Z]+-[0-9]+` (e.g., `FEAT-001-req.md`, `TASK-123.md`)
-- **Coding rules**: `df.2-gen-design.rule.md` is required
+- **Coding rules**: `ps.2-gen-design.rule.md` is required
 - **Language**: If specified, must be one of: `en`, `vi`, `ja`, `ko`
 
 **If validation fails**: Stop immediately and output error message.
@@ -46,10 +46,10 @@ Create technical design document from requirement and coding rules, including ar
 
 File markdown: `{#task-id}-design.md`
 
-**Folder Structure**: Save in `/devflow-prompts/specs/{#task-id}/`
+**Folder Structure**: Save in `/prompt-suite/specs/{#task-id}/`
 
 ```
-/devflow-prompts/specs/{#task-id}/{#task-id}-design.md
+/prompt-suite/specs/{#task-id}/{#task-id}-design.md
 ```
 
 ## Template
@@ -155,7 +155,7 @@ INSTRUCTIONS:
    - Use available file-reading tool (e.g. `view_file`) to read content.
    - **Fallback**: If tool is unavailable, ask user to paste content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filename using pattern: `[A-Z]+-[0-9]+`
@@ -209,9 +209,9 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.2-gen-design /devflow-prompts/specs/FEAT-001/FEAT-001-requirement.md
+/ps.2-gen-design /prompt-suite/specs/FEAT-001/FEAT-001-requirement.md
 ```
 
 ## Next Steps
 
-After tech design is ready → run `/df.2-rev-design` to review
+After tech design is ready → run `/ps.2-rev-design` to review

package/flows/ps.2-rev-design.prompt.md

@@ -2,7 +2,7 @@
 description: Review technical design for implementability and edge cases
 ---
 
-# /df.2-rev-design
+# /ps.2-rev-design
 
 ## Description
 Review technical design to detect gaps, unhandled edge cases, and conflicts with coding rules.
@@ -14,7 +14,7 @@ Review technical design to detect gaps, unhandled edge cases, and conflicts with
 - **Filename MUST contain task-id** (e.g., `FEAT-001-design.md`, `TASK-123.md`)
   - Task-id is needed to name output files
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
+- **File can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/work/FEAT-001-design.md` ✅
   - `/tmp/TASK-123-spec.md` ✅
@@ -22,13 +22,13 @@ Review technical design to detect gaps, unhandled edge cases, and conflicts with
   - `~/design.md` ❌ (no task-id)
 - AI will read file and extract task-id from filename
 
-**Rule File**: `df.2-rev-design.rule.md` from `/devflow-prompts/rules/` (Design review checklist)
+**Rule File**: `ps.2-rev-design.rule.md` from `/prompt-suite/rules/` (Design review checklist)
 
 ## Input Validation
 
 - **Design file**: Required, must exist
 - **File name**: MUST contain task-id pattern `[A-Z]+-[0-9]+` (e.g., `FEAT-001-design.md`, `TASK-123.md`)
-- **Coding rules**: `df.2-rev-design.rule.md` is required
+- **Coding rules**: `ps.2-rev-design.rule.md` is required
 
 **If validation fails**: Stop immediately and output error message.
 
@@ -56,7 +56,7 @@ INSTRUCTIONS:
    - Use available file-reading tool (e.g. `view_file`) to read content.
    - **Fallback**: If tool is unavailable, ask user to paste content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filename using pattern: `[A-Z]+-[0-9]+`
@@ -125,8 +125,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.2-rev-design /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+/ps.2-rev-design /prompt-suite/specs/FEAT-001/FEAT-001-design.md
 ```
 
 ## Next Steps
-After review is done → run `/df.3-gen-code` to generate code
+After review is done → run `/ps.3-gen-code` to generate code

package/flows/ps.3-gen-code.prompt.md

@@ -2,7 +2,7 @@
 description: Generate feature code from technical design (git patch format)
 ---
 
-# /df.3-gen-code
+# /ps.3-gen-code
 
 ## Description
 Generate feature source code from technical design, output as git unified diff (patch).
@@ -14,7 +14,7 @@ Generate feature source code from technical design, output as git unified diff (
 - **Filename MUST contain task-id** (e.g., `FEAT-001-design.md`, `TASK-123.md`)
   - Task-id is needed to name output patch file
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
+- **File can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/projects/FEAT-001-design.md` ✅
   - `/tmp/TASK-123-spec.md` ✅
@@ -22,20 +22,20 @@ Generate feature source code from technical design, output as git unified diff (
   - `~/design.md` ❌ (no task-id)
 - AI will read file and extract task-id from filename
 
-**Rule File**: `df.3-gen-code.rule.md` from `/devflow-prompts/rules/` (Coding standards)
+**Rule File**: `ps.3-gen-code.rule.md` from `/prompt-suite/rules/` (Coding standards)
 
 **Task Mode (Optional, Default: NEW)**
 - `NEW`: Generating code for a new feature.
 - `UPDATE`: Updating or refactoring existing code.
 
 **Coding Rule Files**:
-- `df.3-gen-code.rule.md` (required). **MUST define project structure/roots.**
+- `ps.3-gen-code.rule.md` (required). **MUST define project structure/roots.**
 
 ## Input Validation
 
 - **Design file**: Required, must exist
 - **File name**: Must match pattern `{task-id}-design.md`
-- **Coding rules**: `df.3-gen-code.rule.md` is required
+- **Coding rules**: `ps.3-gen-code.rule.md` is required
 - **Task Mode**: Must be `NEW` or `UPDATE` (case-insensitive)
 
 **If validation fails**: Stop immediately and output error message.
@@ -44,7 +44,7 @@ Generate feature source code from technical design, output as git unified diff (
 
 **Git unified diff (patch)** - NOT markdown!
 
-**Save to**: `/devflow-prompts/specs/{#task-id}/{#task-id}-feature.patch`
+**Save to**: `/prompt-suite/specs/{#task-id}/{#task-id}-feature.patch`
 
 Format:
 ```diff
@@ -89,7 +89,7 @@ INSTRUCTIONS:
    - The user will provide a file path.
    - USE `view_file` tool to read its content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 3. **Extract Task ID** (for file path input):
    - Extract task-id from filename using pattern: `[A-Z]+-[0-9]+`
@@ -103,7 +103,7 @@ INSTRUCTIONS:
      - Identify existing patterns (API handlers, services, repos) in the files related to the design.
      - Reuse existing abstractions.
 
-INPUT 2: Coding rules (df.3-gen-code.rule.md)
+INPUT 2: Coding rules (ps.3-gen-code.rule.md)
 <<<
 {paste coding rules}
 >>>
@@ -148,8 +148,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.3-gen-code /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+/ps.3-gen-code /prompt-suite/specs/FEAT-001/FEAT-001-design.md
 ```
 
 ## Next Steps
-After applying patch → run `/df.3-rev-code` to review
+After applying patch → run `/ps.3-rev-code` to review

package/flows/ps.3-rev-code.prompt.md

@@ -2,7 +2,7 @@
 description: Review generated code patch for quality and correctness
 ---
 
-# /df.3-rev-code
+# /ps.3-rev-code
 
 ## Description
 Review generated code patch to check correctness, quality, and alignment with tech doc.
@@ -14,14 +14,14 @@ Review generated code patch to check correctness, quality, and alignment with te
 - **At least one filename MUST contain task-id** (e.g., `FEAT-001-design.md`)
   - Task-id is needed to name output files
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **Files can be located anywhere** (not limited to `/devflow-prompts`)
+- **Files can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/FEAT-001-design.md ~/feature.patch` ✅
   - `/tmp/TASK-123-spec.md /tmp/code.diff` ✅
   - `./design.md ./patch.diff` ❌ (no task-id)
 - AI will read both files and extract task-id from filenames
 
-**Rule File**: `df.3-rev-code.rule.md` from `/devflow-prompts/rules/` (Code review checklist)
+**Rule File**: `ps.3-rev-code.rule.md` from `/prompt-suite/rules/` (Code review checklist)
 
 **Task Mode (Optional, Default: NEW)**
 - `NEW`: Reviewing new feature code.
@@ -31,7 +31,7 @@ Review generated code patch to check correctness, quality, and alignment with te
 
 - **Design file**: Required, must exist
 - **Generated patch**: Required, must be valid git diff format
-- **Coding rules**: `df.3-rev-code.rule.md` is required
+- **Coding rules**: `ps.3-rev-code.rule.md` is required
 
 **If validation fails**: Stop immediately and output error message.
 
@@ -66,7 +66,7 @@ INSTRUCTIONS:
    - The user will provide file paths.
    - USE `view_file` tool to read them.
    - IF inputs are NOT file paths, ask user to provide file paths.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filenames using pattern: `[A-Z]+-[0-9]+`
@@ -143,8 +143,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.3-rev-code /devflow-prompts/specs/FEAT-001/FEAT-001-design.md /devflow-prompts/specs/FEAT-001/FEAT-001-feature.patch
+/ps.3-rev-code /prompt-suite/specs/FEAT-001/FEAT-001-design.md /prompt-suite/specs/FEAT-001/FEAT-001-feature.patch
 ```
 
 ## Next Steps
-After reviewing code → run `/df.4-gen-test-plan` to create test plan
+After reviewing code → run `/ps.4-gen-test-plan` to create test plan

package/flows/ps.4-gen-test-plan.prompt.md

@@ -2,7 +2,7 @@
 description: Create test plan from technical design (unit/integration/E2E)
 ---
 
-# /df.4-gen-test-plan
+# /ps.4-gen-test-plan
 
 ## Description
 Create test plan document from technical design and coding rules, covering unit/integration/E2E tests.
@@ -14,7 +14,7 @@ Create test plan document from technical design and coding rules, covering unit/
 - **Filename MUST contain task-id** (e.g., `FEAT-001-design.md`, `TASK-123.md`)
   - Task-id is needed to name output test plan file
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
+- **File can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/Documents/FEAT-001-design.md` ✅
   - `/tmp/TASK-123-spec.md` ✅
@@ -26,8 +26,8 @@ Create test plan document from technical design and coding rules, covering unit/
 - `NEW`: Test plan for new feature.
 - `UPDATE`: Test plan for feature update (Focus on regression).
 
-**Coding Rule Files** (from `/devflow-prompts/rules/`):
-- `df.4-gen-test-plan.rule.md` (required) - Test guidelines. **MUST define specific test folder structure.**
+**Coding Rule Files** (from `/prompt-suite/rules/`):
+- `ps.4-gen-test-plan.rule.md` (required) - Test guidelines. **MUST define specific test folder structure.**
 
 **Language** (optional): Output language (default: `en`)
 
@@ -35,7 +35,7 @@ Create test plan document from technical design and coding rules, covering unit/
 
 - **Design file**: Required, must exist
 - **File name**: Must match pattern `{task-id}-design.md`
-- **Coding rules**: `df.4-gen-test-plan.rule.md` is required
+- **Coding rules**: `ps.4-gen-test-plan.rule.md` is required
 - **Language**: If specified, must be one of: `en`, `vi`, `ja`, `ko`
 
 **If validation fails**: Stop immediately and output error message.
@@ -43,9 +43,9 @@ Create test plan document from technical design and coding rules, covering unit/
 ## Output Format
 File markdown: `{#task-id}-test.md`
 
-**Folder Structure**: Save in `/devflow-prompts/specs/{#task-id}/`
+**Folder Structure**: Save in `/prompt-suite/specs/{#task-id}/`
 ```
-/devflow-prompts/specs/{#task-id}/{#task-id}-test.md
+/prompt-suite/specs/{#task-id}/{#task-id}-test.md
 ```
 
 ## Template
@@ -120,7 +120,7 @@ INSTRUCTIONS:
    - The user will provide a file path.
    - USE `view_file` tool to read its content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filename using pattern: `[A-Z]+-[0-9]+`
@@ -164,8 +164,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.4-gen-test-plan /devflow-prompts/specs/FEAT-001/FEAT-001-design.md
+/ps.4-gen-test-plan /prompt-suite/specs/FEAT-001/FEAT-001-design.md
 ```
 
 ## Next Steps
-After test plan is ready → run `/df.4-rev-test-plan` to review
+After test plan is ready → run `/ps.4-rev-test-plan` to review

package/flows/ps.4-rev-test-plan.prompt.md

@@ -2,7 +2,7 @@
 description: Review test plan for coverage and edge cases
 ---
 
-# /df.4-rev-test-plan
+# /ps.4-rev-test-plan
 
 ## Description
 Review test plan to check coverage, traceability to tech doc, and missing edge cases.
@@ -14,20 +14,20 @@ Review test plan to check coverage, traceability to tech doc, and missing edge c
 - **At least one filename MUST contain task-id** (e.g., `FEAT-001-design.md`)
   - Task-id is needed to name output files
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **Files can be located anywhere** (not limited to `/devflow-prompts`)
+- **Files can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/FEAT-001-design.md ~/FEAT-001-test.md` ✅
   - `/tmp/TASK-123-spec.md /tmp/tests.md` ✅
   - `./design.md ./tests.md` ❌ (no task-id)
 - AI will read both files and extract task-id from filenames
 
-**Rule File**: `df.4-rev-test-plan.rule.md` from `/devflow-prompts/rules/` (Test plan review checklist)
+**Rule File**: `ps.4-rev-test-plan.rule.md` from `/prompt-suite/rules/` (Test plan review checklist)
 
 ## Input Validation
 
 - **Design file**: Required, must exist
 - **Test plan file**: Required, must exist
-- **Coding rules**: `df.4-rev-test-plan.rule.md` is required
+- **Coding rules**: `ps.4-rev-test-plan.rule.md` is required
 
 **If validation fails**: Stop immediately and output error message.
 
@@ -60,7 +60,7 @@ INSTRUCTIONS:
    - The user will provide file paths.
    - USE `view_file` tool to read them.
    - IF inputs are NOT file paths, ask user to provide file paths.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filenames using pattern: `[A-Z]+-[0-9]+`
@@ -117,8 +117,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.4-rev-test-plan /devflow-prompts/specs/FEAT-001/FEAT-001-design.md /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+/ps.4-rev-test-plan /prompt-suite/specs/FEAT-001/FEAT-001-design.md /prompt-suite/specs/FEAT-001/FEAT-001-test.md
 ```
 
 ## Next Steps
-After review is done → run `/df.5-gen-test-code` to generate test code
+After review is done → run `/ps.5-gen-test-code` to generate test code

package/flows/ps.5-gen-test-code.prompt.md

@@ -2,7 +2,7 @@
 description: Generate test code from test plan (git patch format)
 ---
 
-# /df.5-gen-test-code
+# /ps.5-gen-test-code
 
 ## Description
 Generate test code from test plan, output as git unified diff (patch).
@@ -14,7 +14,7 @@ Generate test code from test plan, output as git unified diff (patch).
 - **Filename MUST contain task-id** (e.g., `FEAT-001-test.md`, `TASK-123.md`)
   - Task-id is needed to name output test code patch
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **File can be located anywhere** (not limited to `/devflow-prompts`)
+- **File can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/Documents/FEAT-001-test.md` ✅
   - `/tmp/TASK-123-spec.md` ✅
@@ -27,13 +27,13 @@ Generate test code from test plan, output as git unified diff (patch).
 - `UPDATE`: Updating tests for modified code.
 - AI will extract task-id from filename
 
-**Rule File**: `df.5-gen-test-code.rule.md` from `/devflow-prompts/rules/` (Test code writing standards)
+**Rule File**: `ps.5-gen-test-code.rule.md` from `/prompt-suite/rules/` (Test code writing standards)
 
 ## Input Validation
 
 - **Test plan file**: Required, must exist
 - **File name**: Must match pattern `{task-id}-test.md`
-- **Coding rules**: `df.5-gen-test-code.rule.md` is required
+- **Coding rules**: `ps.5-gen-test-code.rule.md` is required
 
 **If validation fails**: Stop immediately and output error message.
 
@@ -41,7 +41,7 @@ Generate test code from test plan, output as git unified diff (patch).
 
 **Git unified diff (patch)** - NOT markdown!
 
-**Save to**: `/devflow-prompts/specs/{#task-id}/{#task-id}-test.patch`
+**Save to**: `/prompt-suite/specs/{#task-id}/{#task-id}-test.patch`
 
 ## Prompt
 
@@ -60,7 +60,7 @@ INSTRUCTIONS:
    - The user will provide a file path.
    - USE `view_file` tool to read its content.
    - IF input is NOT a file path, ask user to provide a file path.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filename using pattern: `[A-Z]+-[0-9]+`
@@ -74,7 +74,7 @@ INSTRUCTIONS:
    - **IF Mode is NEW**:
      - Focus on coverage for the new feature.
 
-INPUT 2: Test coding rules (df.5-gen-test-code.rule.md)
+INPUT 2: Test coding rules (ps.5-gen-test-code.rule.md)
 <<<
 {paste test coding rules}
 >>>
@@ -107,8 +107,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.5-gen-test-code /devflow-prompts/specs/FEAT-001/FEAT-001-test.md
+/ps.5-gen-test-code /prompt-suite/specs/FEAT-001/FEAT-001-test.md
 ```
 
 ## Next Steps
-After applying patch → run `/df.5-rev-test-code` to review
+After applying patch → run `/ps.5-rev-test-code` to review

package/flows/ps.5-rev-test-code.prompt.md

@@ -2,7 +2,7 @@
 description: Review test code patch for reliability and correctness
 ---
 
-# /df.5-rev-test-code
+# /ps.5-rev-test-code
 
 ## Description
 Review test code patch to check correctness, reliability, and alignment with test plan.
@@ -14,20 +14,20 @@ Review test code patch to check correctness, reliability, and alignment with tes
 - **At least one filename MUST contain task-id** (e.g., `FEAT-001-test.md`)
   - Task-id is needed to name output files
   - Can be anywhere in filename: `FEAT-001`, `TASK-123`, `BUG-456`
-- **Files can be located anywhere** (not limited to `/devflow-prompts`)
+- **Files can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/FEAT-001-test.md ~/test.patch` ✅
   - `/tmp/TASK-123-spec.md /tmp/test-code.diff` ✅
   - `./tests.md ./patch.diff` ❌ (no task-id)
 - AI will read both files and extract task-id from filenames
 
-**Rule File**: `df.5-rev-test-code.rule.md` from `/devflow-prompts/rules/` (Test code review checklist)
+**Rule File**: `ps.5-rev-test-code.rule.md` from `/prompt-suite/rules/` (Test code review checklist)
 
 ## Input Validation
 
 - **Test plan file**: Required, must exist
 - **Generated test patch**: Required, must be valid git diff format
-- **Coding rules**: `df.5-rev-test-code.rule.md` is required
+- **Coding rules**: `ps.5-rev-test-code.rule.md` is required
 
 **If validation fails**: Stop immediately and output error message.
 
@@ -59,7 +59,7 @@ INSTRUCTIONS:
    - The user will provide file paths.
    - USE `view_file` tool to read them.
    - IF inputs are NOT file paths, ask user to provide file paths.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (for file path input):
    - Extract task-id from filenames using pattern: `[A-Z]+-[0-9]+`
@@ -124,8 +124,8 @@ RULES:
 ## Usage Example
 
 ```bash
-/df.5-rev-test-code /devflow-prompts/specs/FEAT-001/FEAT-001-test.md /devflow-prompts/specs/FEAT-001/FEAT-001-test.patch
+/ps.5-rev-test-code /prompt-suite/specs/FEAT-001/FEAT-001-test.md /prompt-suite/specs/FEAT-001/FEAT-001-test.patch
 ```
 
 ## Next Steps
-After reviewing test code → run `/df.6-analyze` to validate entire flow
+After reviewing test code → run `/ps.6-analyze` to validate entire flow

package/flows/ps.6-analyze.prompt.md

@@ -2,7 +2,7 @@
 description: Validate requirement → design → code → test flow, find inconsistencies
 ---
 
-# /df.6-analyze
+# /ps.6-analyze
 
 ## Description
 Validate the entire flow from requirement → tech design → code → test, detect inconsistencies and gaps.
@@ -14,7 +14,7 @@ Validate the entire flow from requirement → tech design → code → test, det
 - **Task-id extraction**: AI will try to extract from filenames (optional)
   - If found, will be used in analysis report
   - If not found, analysis will proceed without task-id reference
-- **Files can be located anywhere** (not limited to `/devflow-prompts`)
+- **Files can be located anywhere** (not limited to `/prompt-suite`)
 - Examples:
   - `~/FEAT-001-req.md ~/FEAT-001-design.md ~/FEAT-001-test.md` ✅ (with task-id)
   - `/tmp/requirement.txt /tmp/spec.md /tmp/tests.md` ✅ (without task-id)
@@ -79,7 +79,7 @@ INSTRUCTIONS:
    - The user will provide file paths.
    - USE `view_file` tool to read them.
    - IF inputs are NOT file paths, ask user to provide file paths.
-   - File paths can be anywhere in the filesystem, not limited to `/devflow-prompts`.
+   - File paths can be anywhere in the filesystem, not limited to `/prompt-suite`.
 
 2. **Extract Task ID** (optional, for file path input):
    - Try to extract task-id from filenames using pattern: `[A-Z]+-[0-9]+`
@@ -161,7 +161,7 @@ OUTPUT:
 
 ```bash
 # 1. Run with file paths (can be anywhere in filesystem)
-/df.6-analyze \
+/ps.6-analyze \
   /path/to/FEAT-001-requirement.md \
   /path/to/FEAT-001-design.md \
   /path/to/FEAT-001-test.md

package/index.js

@@ -1,4 +1,4 @@
 #!/usr/bin/env node
 
-console.log("DevFlow Prompts is a CLI tool. Please run 'npx devflow-prompts init' or see README.md for usage.");
+console.log("Prompt Suite Prompts is a CLI tool. Please run 'npx prompt-suite init' or see README.md for usage.");
 module.exports = {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prompt-suite",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Prompt Suite - Prompt Engineering & Workflow Automation",
   "main": "index.js",
   "bin": {

package/scripts/setup-ps-chat-antigravity.sh

@@ -13,7 +13,7 @@ GREEN='\033[0;32m'
 BLUE='\033[0;36m'
 NC='\033[0m' # No Color
 
-echo -e "${BLUE}Starting DevFlow Chat Setup for Antigravity...${NC}"
+echo -e "${BLUE}Starting Prompt Suite Chat Setup for Antigravity...${NC}"
 
 # Check source directory
 if [ ! -d "$WORKFLOWS_DIR" ]; then

package/scripts/setup-ps-chat-vscode.sh

@@ -13,7 +13,7 @@ GREEN='\033[0;32m'
 BLUE='\033[0;36m'
 NC='\033[0m' # No Color
 
-echo -e "${BLUE}Starting DevFlow Chat Setup for VSCode...${NC}"
+echo -e "${BLUE}Starting Prompt Suite Chat Setup for VSCode...${NC}"
 
 # Check source directory
 if [ ! -d "$WORKFLOWS_DIR" ]; then