universal-dev-standards 4.2.0 → 5.0.0-beta.10

package/bundled/skills/claude-code/commands/derive-bdd.md

@@ -1,158 +0,0 @@
----
-description: Derive BDD Gherkin scenarios from approved SDD specification
-allowed-tools: Read, Write, Grep, Glob
-argument-hint: "<spec-file> [--output-dir <dir>] [--dry-run]"
----
-
-# Derive BDD Scenarios from Specification | 從規格推演 BDD 場景
-
-Transform approved SDD specification's Acceptance Criteria into BDD Gherkin scenarios.
-
-將已批准的 SDD 規格驗收條件轉換為 BDD Gherkin 場景。
-
-## Workflow | 工作流程
-
-```
-┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
-│  Read SPEC      │───▶│ Parse AC        │───▶│ Generate        │
-│  讀取規格        │    │ 解析驗收條件     │    │ Gherkin         │
-└─────────────────┘    └─────────────────┘    │ 生成 Gherkin    │
-                                              └────────┬────────┘
-                                                       │
-                                                       ▼
-                       ┌─────────────────┐    ┌─────────────────┐
-                       │  Human Review   │◀───│ Write .feature  │
-                       │  人類審查        │    │ 寫入 .feature   │
-                       └─────────────────┘    └─────────────────┘
-```
-
-## Anti-Hallucination Compliance | 反幻覺合規
-
-**CRITICAL**: Output MUST strictly follow 1:1 AC mapping.
-
-**關鍵**：輸出必須嚴格遵循 1:1 AC 對應。
-
-```
-Input:  SPEC with N Acceptance Criteria
-Output: Exactly N Gherkin Scenarios
-
-If output count ≠ input count → VIOLATION
-```
-
-## Steps | 步驟
-
-### 1. Read Specification | 讀取規格
-
-Read the approved specification file and identify:
-- SPEC ID (e.g., SPEC-001)
-- Feature title and summary
-- Acceptance Criteria section
-
-讀取已批准的規格文件並識別：
-- 規格 ID（例如 SPEC-001）
-- 功能標題和摘要
-- 驗收條件章節
-
-### 2. Parse Acceptance Criteria | 解析驗收條件
-
-Extract AC in one of these formats:
-
-#### Given-When-Then Format (Direct)
-```markdown
-### AC-1: User Login
-**Given** a registered user
-**When** the user submits valid credentials
-**Then** the user is logged in
-```
-
-#### Bullet Format (Transform)
-```markdown
-### AC-1: User Login
-- User can login with email and password
-- Login redirects to dashboard on success
-```
-
-### 3. Generate Gherkin | 生成 Gherkin
-
-Transform each AC to a Scenario:
-
-將每個 AC 轉換為 Scenario：
-
-**Transformation Rules | 轉換規則**:
-
-| AC Pattern | Gherkin Step |
-|------------|--------------|
-| Condition/state | Given |
-| User action | When |
-| System response | Then |
-| Additional outcome | And |
-
-### 4. Apply Source Attribution | 套用來源標註
-
-Every scenario MUST include:
-- `@SPEC-XXX` tag at feature level
-- `@AC-N` tag at scenario level
-- Source comment with file reference
-
-## Output Format | 輸出格式
-
-```gherkin
-# Generated from: specs/SPEC-001.md
-# Generator: /derive-bdd v1.0.0
-# Generated at: [timestamp]
-
-@SPEC-001
-Feature: [Title from SPEC]
-  [Summary from SPEC]
-
-  @AC-1 @happy-path
-  Scenario: [AC-1 Title]
-    # [Source] From SPEC-001 AC-1
-    Given [precondition]
-    When [action]
-    Then [expected result]
-
-  @AC-2 @error-handling
-  Scenario: [AC-2 Title]
-    # [Source] From SPEC-001 AC-2
-    Given [precondition]
-    When [action]
-    Then [expected result]
-```
-
-## Parameters | 參數
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `--output-dir` | Output directory | `./features` |
-| `--dry-run` | Preview without creating files | `false` |
-
-## Usage Examples | 使用範例
-
-```bash
-# Basic usage
-/derive-bdd specs/SPEC-001.md
-
-# Specify output directory
-/derive-bdd specs/SPEC-001.md --output-dir ./features/auth
-
-# Preview without creating file
-/derive-bdd specs/SPEC-001.md --dry-run
-```
-
-## Limitations | 限制
-
-This command **CANNOT**:
-
-此命令**無法**：
-
-- Generate scenarios beyond AC count
-- Implement step definitions
-- Infer requirements not in specification
-- Modify existing feature files
-
-## Reference | 參考
-
-- Full skill guide: [forward-derivation](../forward-derivation/SKILL.md)
-- Core standard: [forward-derivation-standards.md](../../../core/forward-derivation-standards.md)
-- BDD format: [behavior-driven-development.md](../../../core/behavior-driven-development.md)

package/bundled/skills/claude-code/commands/derive-tdd.md

@@ -1,259 +0,0 @@
----
-description: Derive TDD test skeletons from approved SDD specification
-allowed-tools: Read, Write, Grep, Glob
-argument-hint: "<spec-file> [--lang <language>] [--framework <framework>] [--output-dir <dir>] [--dry-run]"
----
-
-# Derive TDD Test Skeletons from Specification | 從規格推演 TDD 測試骨架
-
-Generate TDD test skeleton files from approved SDD specification's Acceptance Criteria.
-
-從已批准的 SDD 規格驗收條件生成 TDD 測試骨架檔案。
-
-## Workflow | 工作流程
-
-```
-┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
-│  Read SPEC      │───▶│ Parse AC        │───▶│ Generate Test   │
-│  讀取規格        │    │ 解析驗收條件     │    │ Skeleton        │
-└─────────────────┘    └─────────────────┘    │ 生成測試骨架     │
-                                              └────────┬────────┘
-                                                       │
-                                                       ▼
-                       ┌─────────────────┐    ┌─────────────────┐
-                       │  Fill [TODO]    │◀───│ Write Test File │
-                       │  填寫 [TODO]    │    │ 寫入測試檔案     │
-                       └─────────────────┘    └─────────────────┘
-```
-
-## Anti-Hallucination Compliance | 反幻覺合規
-
-**CRITICAL**: Output MUST strictly follow 1:1 AC mapping.
-
-**關鍵**：輸出必須嚴格遵循 1:1 AC 對應。
-
-```
-Input:  SPEC with N Acceptance Criteria
-Output: Exactly N describe blocks (test groups)
-
-If output count ≠ input count → VIOLATION
-```
-
-## Steps | 步驟
-
-### 1. Read Specification | 讀取規格
-
-Read the approved specification file and identify:
-- SPEC ID and title
-- Acceptance Criteria with IDs
-
-### 2. Determine Language/Framework | 決定語言/框架
-
-Auto-detect or use specified parameters:
-
-| Language | Frameworks | File Extension |
-|----------|------------|----------------|
-| TypeScript | vitest, jest | `.test.ts` |
-| JavaScript | vitest, jest, mocha | `.test.js` |
-| Python | pytest, unittest | `_test.py` or `test_*.py` |
-| Java | junit, testng | `Test.java` |
-| Go | go test | `_test.go` |
-
-### 3. Generate Test Structure | 生成測試結構
-
-For each AC, generate:
-- describe block with AC reference
-- it block with behavior description
-- AAA comments (Arrange-Act-Assert)
-- Placeholder assertion
-- [TODO] markers for implementation
-
-## Output Formats | 輸出格式
-
-### TypeScript (Vitest/Jest)
-
-```typescript
-/**
- * Tests for SPEC-001: [Title]
- * Generated from: specs/SPEC-001.md
- * Generated at: [timestamp]
- * AC Coverage: AC-1, AC-2
- */
-
-import { describe, it, expect } from 'vitest';
-
-describe('SPEC-001: [Title]', () => {
-  describe('AC-1: [AC Title]', () => {
-    it('should [expected behavior]', async () => {
-      // Arrange
-      // [TODO] Set up test data
-
-      // Act
-      // [TODO] Call method under test
-
-      // Assert
-      // [TODO] Add assertions
-      expect(true).toBe(true); // Placeholder
-    });
-  });
-
-  describe('AC-2: [AC Title]', () => {
-    it('should [expected behavior]', async () => {
-      // Arrange
-      // [TODO] Set up test data
-
-      // Act
-      // [TODO] Call method under test
-
-      // Assert
-      // [TODO] Add assertions
-      expect(true).toBe(true); // Placeholder
-    });
-  });
-});
-```
-
-### Python (pytest)
-
-```python
-"""
-Tests for SPEC-001: [Title]
-Generated from: specs/SPEC-001.md
-Generated at: [timestamp]
-AC Coverage: AC-1, AC-2
-"""
-
-import pytest
-
-
-class TestSPEC001:
-    """SPEC-001: [Title]"""
-
-    class TestAC1:
-        """AC-1: [AC Title]"""
-
-        def test_should_expected_behavior(self):
-            # Arrange
-            # [TODO] Set up test data
-
-            # Act
-            # [TODO] Call method under test
-
-            # Assert
-            # [TODO] Add assertions
-            assert True  # Placeholder
-
-    class TestAC2:
-        """AC-2: [AC Title]"""
-
-        def test_should_expected_behavior(self):
-            # Arrange
-            # [TODO] Set up test data
-
-            # Act
-            # [TODO] Call method under test
-
-            # Assert
-            # [TODO] Add assertions
-            assert True  # Placeholder
-```
-
-### Java (JUnit 5)
-
-```java
-/**
- * Tests for SPEC-001: [Title]
- * Generated from: specs/SPEC-001.md
- * Generated at: [timestamp]
- * AC Coverage: AC-1, AC-2
- */
-
-import org.junit.jupiter.api.*;
-import static org.junit.jupiter.api.Assertions.*;
-
-class SPEC001Test {
-
-    @Nested
-    @DisplayName("AC-1: [AC Title]")
-    class AC1Test {
-
-        @Test
-        @DisplayName("should [expected behavior]")
-        void shouldExpectedBehavior() {
-            // Arrange
-            // [TODO] Set up test data
-
-            // Act
-            // [TODO] Call method under test
-
-            // Assert
-            // [TODO] Add assertions
-            assertTrue(true); // Placeholder
-        }
-    }
-
-    @Nested
-    @DisplayName("AC-2: [AC Title]")
-    class AC2Test {
-
-        @Test
-        @DisplayName("should [expected behavior]")
-        void shouldExpectedBehavior() {
-            // Arrange
-            // [TODO] Set up test data
-
-            // Act
-            // [TODO] Call method under test
-
-            // Assert
-            // [TODO] Add assertions
-            assertTrue(true); // Placeholder
-        }
-    }
-}
-```
-
-## Parameters | 參數
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `--lang` | Target language: ts, js, python, java, go | `typescript` |
-| `--framework` | Test framework | `vitest` |
-| `--output-dir` | Output directory | `./tests` |
-| `--dry-run` | Preview without creating files | `false` |
-
-## Usage Examples | 使用範例
-
-```bash
-# Basic usage (TypeScript/Vitest)
-/derive-tdd specs/SPEC-001.md
-
-# Python with pytest
-/derive-tdd specs/SPEC-001.md --lang python --framework pytest
-
-# Java with JUnit
-/derive-tdd specs/SPEC-001.md --lang java --framework junit
-
-# Specify output directory
-/derive-tdd specs/SPEC-001.md --output-dir ./src/__tests__
-
-# Preview without creating file
-/derive-tdd specs/SPEC-001.md --dry-run
-```
-
-## Limitations | 限制
-
-This command **CANNOT**:
-
-此命令**無法**：
-
-- Generate test groups beyond AC count
-- Implement actual test logic
-- Fill in assertions automatically
-- Run the generated tests
-
-## Reference | 參考
-
-- Full skill guide: [forward-derivation](../forward-derivation/SKILL.md)
-- Core standard: [forward-derivation-standards.md](../../../core/forward-derivation-standards.md)
-- TDD workflow: [test-driven-development.md](../../../core/test-driven-development.md)

package/bundled/skills/claude-code/commands/docs.md

@@ -1,75 +0,0 @@
----
-description: Create or update project documentation structure
-allowed-tools: Read, Write, Grep, Glob
-argument-hint: "[document type: readme|api|contributing | 文件類型]"
----
-
-# Documentation Assistant | 文件助手
-
-Create and maintain well-structured project documentation.
-
-建立和維護結構良好的專案文件。
-
-## Workflow | 工作流程
-
-1. **Assess current state** - Check existing documentation
-2. **Identify gaps** - What documentation is missing?
-3. **Generate templates** - Create appropriate document templates
-4. **Fill content** - Add project-specific information
-5. **Validate links** - Ensure all references work
-
-## Document Types | 文件類型
-
-| Type | Purpose | 用途 |
-|------|---------|------|
-| **README.md** | Project overview | 專案概述 |
-| **CONTRIBUTING.md** | Contribution guide | 貢獻指南 |
-| **CHANGELOG.md** | Version history | 版本歷史 |
-| **API.md** | API documentation | API 文件 |
-| **docs/** | Detailed guides | 詳細指南 |
-
-## README Structure | README 結構
-
-```markdown
-# Project Name
-
-Brief description.
-
-## Features
-- Feature 1
-- Feature 2
-
-## Installation
-```bash
-npm install package
-```
-
-## Usage
-[Examples]
-
-## Contributing
-See CONTRIBUTING.md
-
-## License
-MIT
-```
-
-## Documentation Checklist | 文件檢查清單
-
-- [ ] README has clear project description
-- [ ] Installation instructions are accurate
-- [ ] Usage examples are provided
-- [ ] API is documented (if applicable)
-- [ ] Contributing guidelines exist
-- [ ] License is specified
-
-## Usage | 使用方式
-
-- `/docs` - Audit current documentation
-- `/docs readme` - Generate/update README
-- `/docs api` - Generate API documentation
-
-## Reference | 參考
-
-- Full standard: [documentation-guide](../../documentation-guide/SKILL.md)
-- Core guide: [documentation-standards](../../../../core/documentation-standards.md)

package/bundled/skills/claude-code/commands/release.md

@@ -1,50 +0,0 @@
----
-description: Guide through release process with semantic versioning
-allowed-tools: Read, Grep, Glob, Bash(git:*), Bash(npm version:*), Bash(gh release:*)
-argument-hint: "[version type: major|minor|patch|beta | 版本類型]"
----
-
-# Release Assistant | 發布助手
-
-Guide through the complete release process following semantic versioning standards.
-
-引導完整的發布流程，遵循語義化版本標準。
-
-## Workflow | 工作流程
-
-1. **Pre-release checks** - Run tests, linting, verify git status
-2. **Determine version** - Based on changes since last release
-3. **Update CHANGELOG** - Document all changes
-4. **Update version** - Bump version in package.json
-5. **Create tag** - Git tag with version number
-6. **Push changes** - Commit and push to remote
-7. **Create release** - GitHub release (triggers npm publish)
-
-## Version Types | 版本類型
-
-| Type | When to Use | Example |
-|------|-------------|---------|
-| `major` | Breaking changes | 1.0.0 → 2.0.0 |
-| `minor` | New features (backward compatible) | 1.0.0 → 1.1.0 |
-| `patch` | Bug fixes | 1.0.0 → 1.0.1 |
-| `beta` | Pre-release testing | 1.0.0 → 1.1.0-beta.1 |
-| `alpha` | Early testing | 1.0.0 → 1.1.0-alpha.1 |
-
-## Pre-release Checklist | 發布前檢查
-
-- [ ] All tests pass
-- [ ] Linting passes
-- [ ] Git working directory is clean
-- [ ] On correct branch (main for stable)
-- [ ] CHANGELOG is updated
-
-## Usage | 使用方式
-
-- `/release` - Interactive release wizard
-- `/release patch` - Create patch release
-- `/release beta` - Create beta pre-release
-
-## Reference | 參考
-
-- Full standard: [release-standards](../../release-standards/SKILL.md)
-- Workflow guide: [release-workflow](../../release-standards/release-workflow.md)