omgkit 2.22.9 → 2.22.11

package/README.md

@@ -589,18 +589,21 @@ Build complete applications from idea to deployment.
 
 ### Artifacts System
 
-Provide project context:
+Provide project context with reference documents:
 
 ```
 .omgkit/artifacts/
-├── data/       # Sample data, schemas
-├── docs/       # Requirements, user stories
-├── knowledge/  # Glossary, business rules
-├── research/   # Competitor analysis
-├── assets/     # Images, templates
-└── examples/   # Code samples
+├── README.md   # How to use artifacts
+├── data/       # Sample data, schemas, data dictionaries
+├── docs/       # Requirements, user stories, PRDs
+├── knowledge/  # Glossary, business rules, domain knowledge
+├── research/   # Competitor analysis, market research
+├── assets/     # Reference images, templates, mockups
+└── examples/   # Code samples, reference implementations
 ```
 
+**Note:** Artifacts are **reference materials only**, NOT execution instructions. They help AI understand your project context.
+
 ---
 
 ## Project Structure
@@ -619,11 +622,16 @@ your-project/
 │   ├── docs/            # Generated docs
 │   ├── logs/            # Activity logs
 │   ├── devlogs/         # Development logs (git-ignored)
+│   │   └── README.md
 │   ├── stdrules/        # Project standards
+│   │   ├── README.md
 │   │   ├── BEFORE_COMMIT.md
-│   │   └── SKILL_STANDARDS.md
-│   └── artifacts/       # Project context
-└── OMEGA.md             # Project context file
+│   │   ├── SKILL_STANDARDS.md
+│   │   └── TESTING_STANDARDS.md
+│   └── artifacts/       # Project context (reference only)
+│       └── README.md
+├── OMEGA.md             # Project context file
+└── CLAUDE.md            # Claude Code instructions
 ```
 
 ---

package/lib/cli.js

@@ -373,7 +373,8 @@ export function initProject(options = {}) {
     '.omgkit/docs',
     '.omgkit/logs',
     '.omgkit/devlogs',
-    '.omgkit/stdrules'
+    '.omgkit/stdrules',
+    '.omgkit/artifacts'
   ];
 
   dirs.forEach(dir => {
@@ -397,7 +398,8 @@ export function initProject(options = {}) {
     { src: 'stdrules/README.md', dest: '.omgkit/stdrules/README.md' },
     { src: 'stdrules/SKILL_STANDARDS.md', dest: '.omgkit/stdrules/SKILL_STANDARDS.md' },
     { src: 'stdrules/BEFORE_COMMIT.md', dest: '.omgkit/stdrules/BEFORE_COMMIT.md' },
-    { src: 'stdrules/TESTING_STANDARDS.md', dest: '.omgkit/stdrules/TESTING_STANDARDS.md' }
+    { src: 'stdrules/TESTING_STANDARDS.md', dest: '.omgkit/stdrules/TESTING_STANDARDS.md' },
+    { src: 'artifacts/README.md', dest: '.omgkit/artifacts/README.md' }
   ];
 
   templates.forEach(({ src, dest }) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omgkit",
-  "version": "2.22.9",
+  "version": "2.22.11",
   "description": "Omega-Level Development Kit - AI Team System for Claude Code. 41 agents, 151 commands, 151 skills, 67 workflows.",
   "keywords": [
     "claude-code",

package/plugin/commands/sprint/init.md

@@ -17,10 +17,35 @@ Create `.omgkit/` directory structure.
 │   └── backlog.yaml
 ├── plans/
 ├── docs/
-└── logs/
+├── logs/
+├── devlogs/
+│   └── README.md
+├── stdrules/
+│   ├── README.md
+│   ├── BEFORE_COMMIT.md
+│   ├── SKILL_STANDARDS.md
+│   └── TESTING_STANDARDS.md
+└── artifacts/
+    └── README.md
 OMEGA.md
+CLAUDE.md
 ```
 
+## Artifacts Folder
+
+The `.omgkit/artifacts/` folder stores **reference documents** that provide context for AI-assisted development:
+
+| Subfolder | Purpose |
+|-----------|---------|
+| `data/` | Sample data, schemas, data dictionaries |
+| `docs/` | Requirements, user stories, PRDs |
+| `knowledge/` | Glossary, business rules, domain knowledge |
+| `research/` | Competitor analysis, market research |
+| `assets/` | Reference images, templates, mockups |
+| `examples/` | Code samples, reference implementations |
+
+> **Note:** Artifacts are **reference materials only**, NOT execution instructions. They help AI understand your project context.
+
 ## Next Steps
 1. `/vision:set` - Set your product vision
 2. `/sprint:new` - Create first sprint

package/plugin/registry.yaml

@@ -1,9 +1,9 @@
 # OMGKIT Component Registry
 # Single Source of Truth for Agents, Skills, Commands, Workflows, and MCPs
-# Version: 2.22.9
+# Version: 2.22.10
 # Updated: 2026-01-03
 
-version: "2.22.9"
+version: "2.22.10"
 
 # =============================================================================
 # OPTIMIZED ALIGNMENT PRINCIPLE (OAP)

package/templates/CLAUDE.md

@@ -15,17 +15,20 @@ This project uses **OMGKIT** - an AI Team System for Claude Code with 41 Agents,
 ├── stdrules/         # Standards and rules (MUST READ)
 │   ├── TESTING_STANDARDS.md   # Testing methodology
 │   └── BEFORE_COMMIT.md       # Pre-commit checklist
+├── artifacts/        # Project context documents (reference only)
+│   └── README.md     # How to use artifacts
 ├── devlogs/          # Development logs (git-ignored)
 └── settings.json     # Local settings
 ```
 
 ## MANDATORY: Read Before Tasks
 
-| Task Type | Read First |
-|-----------|------------|
-| Writing Tests | `.omgkit/stdrules/TESTING_STANDARDS.md` |
-| Before Commit | `.omgkit/stdrules/BEFORE_COMMIT.md` |
-| New Feature | `.omgkit/config.yaml` for project settings |
+| Task Type | Read First | Also Consider |
+|-----------|------------|---------------|
+| Writing Tests | `.omgkit/stdrules/TESTING_STANDARDS.md` | Spawn `tester` agent for complex tests |
+| Before Commit | `.omgkit/stdrules/BEFORE_COMMIT.md` | Run `/quality:test-omega` |
+| New Feature | `.omgkit/config.yaml` | Use `/dev:tdd` for TDD approach |
+| Security Testing | `.omgkit/stdrules/TESTING_STANDARDS.md` | Run `/quality:test-security` |
 
 ## Development Workflow Rules
 
@@ -38,6 +41,15 @@ This project uses **OMGKIT** - an AI Team System for Claude Code with 41 Agents,
 
 This folder is git-ignored and should NEVER be committed to the repository.
 
+### `.omgkit/artifacts/` Folder
+**REFERENCE CONTEXT**: This folder contains project initialization documents that provide context for development:
+- Brainstorming notes and initial plans
+- Project specs and requirements
+- Research documents and analysis
+- Sample data and schemas
+
+These are **reference materials only**, NOT execution instructions. Read them to understand project context.
+
 ### Documentation (`docs/`)
 The `docs/` folder is for public documentation only:
 - User-facing documentation
@@ -94,6 +106,20 @@ Before completing any task:
 
 ## AUTOMATIC RULES: Testing (Always Apply)
 
+### Quick Reference - Testing Commands
+When user asks about testing, suggest these commands:
+- `/dev:test-write <function>` - Write comprehensive tests (RECOMMENDED)
+- `/dev:tdd <feature>` - Test-driven development
+- `/quality:test-omega` - Run full 4D testing suite
+- `/quality:test-property` - Property-based testing
+- `/quality:test-security` - Security testing
+- `/quality:test-mutate` - Mutation testing
+
+### Agent & Workflow
+For complex testing tasks, spawn the `tester` agent or run workflow:
+- Agent: `tester` - Comprehensive testing specialist
+- Workflow: `testing/comprehensive-testing`
+
 When writing ANY test, Claude MUST automatically apply these rules:
 
 ### 1. Minimum Test Coverage (MANDATORY)

package/templates/OMEGA.md

@@ -50,6 +50,16 @@ OMGKIT provides 23 specialized agents organized into teams:
 - API documentation required
 - Architecture decisions in ADRs
 
+## Project Artifacts
+
+Reference documents in `.omgkit/artifacts/` provide context:
+- **data/**: Sample data, schemas, data dictionaries
+- **docs/**: Requirements, user stories, PRDs
+- **knowledge/**: Glossary, business rules, domain knowledge
+- **research/**: Competitor analysis, market research
+
+See `.omgkit/artifacts/README.md` for details.
+
 ## Current Sprint
 
 See `.omgkit/sprints/current.yaml`

package/templates/artifacts/README.md

@@ -0,0 +1,87 @@
+# Project Artifacts
+
+This folder contains **reference documents** that provide context for AI-assisted development.
+
+## Purpose
+
+Artifacts are **input context** for Claude Code and OMGKIT to understand your project. They are NOT execution instructions - they help AI understand the background, goals, and constraints of your project.
+
+## What Goes Here
+
+| Subfolder | Content | Examples |
+|-----------|---------|----------|
+| `data/` | Sample data, schemas, data dictionaries | `schema.sql`, `sample-users.json`, `data-dictionary.md` |
+| `docs/` | Requirements, user stories, PRDs | `prd.md`, `user-stories.md`, `requirements.docx` |
+| `knowledge/` | Glossary, business rules, domain knowledge | `glossary.md`, `business-rules.md`, `domain-model.md` |
+| `research/` | Competitor analysis, market research | `competitors.md`, `market-analysis.pdf` |
+| `assets/` | Reference images, templates, mockups | `wireframes/`, `logos/`, `templates/` |
+| `examples/` | Code samples, reference implementations | `api-example.py`, `integration-sample/` |
+
+## How AI Uses These Artifacts
+
+When you run OMGKIT commands, the AI team will:
+
+1. **Read artifacts** to understand project context
+2. **Reference business rules** when making implementation decisions
+3. **Follow naming conventions** from glossary and data dictionaries
+4. **Align with requirements** in PRDs and user stories
+5. **Use examples** as reference for coding patterns
+
+## Artifacts vs Other Folders
+
+| Folder | Purpose | Git Status | AI Usage |
+|--------|---------|------------|----------|
+| **artifacts/** | Reference context (input) | Committed | Read for understanding |
+| **devlogs/** | Development work logs | Git-ignored | Internal tracking |
+| **plans/** | Formal implementation plans | Committed | Execution guidance |
+| **docs/** | Generated documentation | Committed | Output documentation |
+
+## Best Practices
+
+### 1. Keep It Organized
+
+Create subfolders for different types of content:
+
+```
+artifacts/
+├── data/
+│   ├── sample-users.json
+│   └── schema.sql
+├── docs/
+│   ├── prd.md
+│   └── user-stories.md
+├── knowledge/
+│   ├── glossary.md
+│   └── business-rules.md
+└── research/
+    └── competitor-analysis.md
+```
+
+### 2. Use Clear Naming
+
+- Descriptive filenames: `user-authentication-requirements.md`
+- Date prefix for versioned docs: `2024-12-prd-v2.md`
+- Keep extensions consistent: `.md` for markdown, `.json` for data
+
+### 3. Keep It Relevant
+
+- Remove outdated documents
+- Update artifacts when requirements change
+- Link related documents together
+
+### 4. Don't Put Execution Work Here
+
+Execution work belongs elsewhere:
+- Implementation plans go in `plans/`
+- Development logs go in `devlogs/`
+- Generated docs go in `docs/`
+
+## Quick Start
+
+1. Copy your project documents into appropriate subfolders
+2. Run `/context:index` to refresh codebase context
+3. AI will automatically reference these when executing commands
+
+---
+
+*Artifacts provide the "why" and "what" - AI handles the "how".*

package/templates/config.yaml

@@ -33,6 +33,7 @@ output:
   plans_dir: .omgkit/plans
   docs_dir: .omgkit/docs
   logs_dir: .omgkit/logs
+  artifacts_dir: .omgkit/artifacts
   verbose: false
 
 # MCP settings