cokit-cli 1.2.6 → 1.3.0

package/skills/ship/references/ship-workflow.md

@@ -0,0 +1,241 @@
+# Ship Workflow — Detailed Steps
+
+## Step 1: Pre-flight
+
+1. Check current branch: `git branch --show-current`
+   - If on target branch (main/master/dev): **ABORT** — "Ship from a feature branch, not the target branch."
+2. Determine ship mode from arguments:
+   - `official` → target = auto-detect default branch (main/master)
+   - `beta` → target = auto-detect dev branch (dev/beta/develop)
+   - No argument → infer from branch name:
+     - `feature/* hotfix/* bugfix/*` → official
+     - `dev/* beta/* experiment/*` → beta
+     - Unclear → asking the user with options: "Official (main)", "Beta (dev)"
+3. Auto-detect target branch:
+   ```bash
+   # For official: detect default branch
+   git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
+   # Fallback
+   git rev-parse --verify origin/main 2>/dev/null && echo "main" || echo "master"
+
+   # For beta: detect dev branch
+   for b in dev beta develop; do
+     git rev-parse --verify origin/$b 2>/dev/null && echo "$b" && break
+   done
+   ```
+4. Run `git status` (never use `-uall`). Uncommitted changes are always included.
+5. Run `git diff <target>...HEAD --stat` and `git log <target>..HEAD --oneline` to understand what's being shipped.
+6. If `--dry-run`: output what would happen at each step and stop here.
+
+## Step 2: Link Issues
+
+Find or create related GitHub issues for traceability.
+
+1. Search for related open issues by keywords from branch name and commit messages:
+   ```bash
+   # Extract keywords from branch name
+   BRANCH=$(git branch --show-current)
+   KEYWORDS=$(echo "$BRANCH" | sed 's/[^a-zA-Z0-9]/ /g' | tr '[:upper:]' '[:lower:]')
+
+   # Search existing issues
+   gh issue list --state open --limit 10 --search "$KEYWORDS"
+   ```
+
+2. Also check if any issues are referenced in commit messages:
+   ```bash
+   git log <target>..HEAD --oneline | grep -oE '#[0-9]+' | sort -u
+   ```
+
+3. **If related issues found:** Note issue numbers for PR linking.
+
+4. **If NO related issues found:** Create a new issue with structured format:
+   ```bash
+   gh issue create --title "<type>: <summary from commits>" --body "$(cat <<'EOF'
+   ## Problem Statement
+   <infer from diff and commit messages>
+
+   ## Proposal
+   <summarize the implementation approach>
+
+   ## How It Works
+   <describe key changes with bullet points>
+
+   ### Architecture
+   ```
+   <ASCII diagram of component interactions>
+   ```
+
+   ## Challenges
+   - <potential edge cases or risks>
+
+   ## Plan & Phases
+   - [x] Implementation complete
+   - [x] Tests passing
+   - [ ] Code review approved
+   - [ ] Merged to <target>
+
+   ## Human Review Tasks
+   - [ ] Verify business logic correctness
+   - [ ] Check for edge cases not covered by tests
+   - [ ] Validate UX/API contract changes (if any)
+   EOF
+   )"
+   ```
+
+5. Store issue numbers for Step 12 (PR creation).
+
+## Step 3: Merge target branch
+
+Fetch and merge so tests run against the merged state:
+
+```bash
+git fetch origin <target> && git merge origin/<target> --no-edit
+```
+
+- **If merge conflicts:** Try auto-resolve simple ones (lockfiles, version files). For complex conflicts, **STOP** and show them.
+- **If already up to date:** Continue silently.
+
+## Step 4: Run Tests
+
+**Skip if:** `--skip-tests` flag.
+
+1. Auto-detect test command (see `auto-detect.md`)
+2. Delegate to `tester` subagent — don't inline test execution
+3. Check pass/fail from agent result
+
+- **If any test fails:** Show failures and **STOP**. Do not proceed.
+- **If all pass:** Note counts briefly and continue.
+- **If no test runner detected:** Use asking the user — "No test runner detected. Skip tests or provide command?"
+
+## Step 5: Pre-Landing Review
+
+**Skip if:** `--skip-review` flag.
+
+1. Run `git diff origin/<target>` to get the full diff
+2. Delegate to `code-reviewer` subagent with the diff
+3. Two-pass model:
+   - **Pass 1 (CRITICAL):** Security, injection, race conditions, auth bypass
+   - **Pass 2 (INFORMATIONAL):** Dead code, magic numbers, test gaps, style
+
+4. **Output findings:**
+   ```
+   Pre-Landing Review: N issues (X critical, Y informational)
+   ```
+
+5. **If critical issues found:** For EACH critical issue, ask the user:
+   - Problem description with `file:line`
+   - Recommended fix
+   - Options: A) Fix now (recommended), B) Acknowledge and ship, C) False positive — skip
+
+6. **If user chose Fix (A):** Apply fixes, commit fixed files, then **re-run tests** (Step 4) before continuing.
+7. **If only informational:** Include in PR body, continue.
+8. **If no issues:** Output "No issues found." and continue.
+
+## Step 6: Version Bump (conditional)
+
+1. Auto-detect version source (see `auto-detect.md`)
+2. If no version file found: **skip silently**
+3. Auto-decide bump level from diff size:
+   - **< 50 lines:** patch bump
+   - **50+ lines:** patch bump (default safe choice)
+   - **Major feature or breaking change:** Use asking the user — "This looks like a significant change. Bump minor or patch?"
+4. For beta mode: use prerelease suffix (e.g., `1.2.4-beta.1`)
+5. Write new version to detected file
+
+## Step 7: Changelog (conditional)
+
+1. Check for CHANGELOG.md or CHANGES.md
+2. If not found: **skip silently**
+3. Auto-generate entry from ALL commits on branch:
+   - `git log <target>..HEAD --oneline` for commit list
+   - `git diff <target>...HEAD` for full diff context
+4. Categorize into: Added, Changed, Fixed, Removed
+5. Insert after file header, dated today
+6. Format: `## [X.Y.Z] - YYYY-MM-DD`
+
+**Do NOT ask user to describe changes.** Infer from diff and commits.
+
+## Step 8: Journal (background)
+
+**Skip if:** `--skip-journal` flag.
+
+Write a technical journal entry capturing this ship session. Run as **background task** to not block pipeline.
+
+1. Invoke `/ck-journal` skill via `journal-writer` subagent in background:
+   - Topic: summary of shipped changes (from commit messages + diff stats)
+   - Include: what was shipped, key decisions, technical challenges encountered
+   - Output: saved to `./docs/journals/` directory
+2. Don't wait for completion — continue to next step immediately.
+
+## Step 9: Docs Update (conditional, background)
+
+**Skip if:** `--skip-docs` flag OR ship mode is `beta`.
+
+Update project documentation for official releases. Run as **background task**.
+
+1. Invoke `/ck-docs update` skill via `docs-manager` subagent in background:
+   - Analyzes code changes since last release
+   - Updates relevant docs in `./docs/` directory
+2. Don't wait for completion — continue to next step immediately.
+
+## Step 10: Commit
+
+1. Stage all changes: `git add -A`
+2. Security check: scan staged diff for secrets (API keys, tokens, passwords)
+   - If secrets found: **STOP**, warn user, suggest `.gitignore`
+3. Compose commit message:
+   - Format: `type(scope): description`
+   - Infer type from changes (feat/fix/refactor/chore)
+   - If version + changelog present, include in same commit
+4. Commit:
+
+```bash
+git commit -m "$(cat <<'EOF'
+type(scope): description
+
+Brief body describing the changes.
+EOF
+)"
+```
+
+## Step 11: Push
+
+```bash
+git push -u origin $(git branch --show-current)
+```
+
+- **Never force push.**
+- If push rejected: suggest `git pull --rebase` and retry once.
+
+## Step 12: Create PR
+
+Check if `gh` CLI is available:
+```bash
+which gh 2>/dev/null || echo "MISSING"
+```
+
+If missing: output "Install GitHub CLI (gh) to auto-create PRs" and stop after push.
+
+Create PR targeting the correct branch:
+```bash
+gh pr create --base <target-branch> --title "<type>: <summary>" --body "$(cat <<'EOF'
+<PR body from pr-template.md>
+EOF
+)"
+```
+
+**Link issues** collected from Step 2:
+```bash
+# If issues were found/created, add closing keywords in PR body
+# e.g., "Closes #42, Relates to #43"
+```
+
+**Output the PR URL** — this is the final output the user sees.
+
+If PR already exists for this branch, update it instead:
+```bash
+gh pr edit --title "<type>: <summary>" --body "$(cat <<'EOF'
+<PR body>
+EOF
+)"
+```

package/skills/test/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: test
+description: "Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports."
+argument-hint: "[context] OR ui [url]"
+---
+
+# Testing & Quality Assurance
+
+Comprehensive testing framework covering code-level testing (unit, integration, e2e), UI/visual testing via browser automation, coverage analysis, and structured QA reporting.
+
+## Default (No Arguments)
+
+If invoked with context (test scope), proceed with testing. If invoked WITHOUT arguments, ask the user to present available test operations:
+
+| Operation | Description |
+|-----------|-------------|
+| `(default)` | Run unit/integration/e2e tests |
+| `ui` | Run UI tests on a website |
+
+Present as options by asking the user with header "Test Operation", question "What would you like to do?".
+
+## Core Principle
+
+**NEVER IGNORE FAILING TESTS.** Fix root causes, not symptoms. No mocks/cheats/tricks to pass builds.
+
+## When to Use
+
+- **After implementation**: Validate new features or bug fixes
+- **Coverage checks**: Ensure coverage meets project thresholds (80%+)
+- **UI verification**: Visual regression, responsive layout, accessibility
+- **Build validation**: Verify build process, dependencies, CI/CD compatibility
+- **Pre-commit/push**: Final quality gate
+
+## Workflows
+
+### 1. Code Testing (`references/test-execution-workflow.md`)
+
+Execute test suites, analyze results, generate coverage. Supports JS/TS (Jest/Vitest/Mocha), Python (pytest), Go, Rust, Flutter. Includes working process, quality standards, and tool commands.
+
+**Load when:** Running unit/integration/e2e tests, checking coverage, validating builds
+
+### 2. UI Testing (`references/ui-testing-workflow.md`)
+
+Browser-based visual testing via `chrome-devtools` (if available) skill. Screenshots, responsive checks, accessibility audits, form automation, console error collection. Includes auth injection for protected routes.
+
+**Load when:** Visual regression testing, UI bugs, responsive layout checks, accessibility audits
+
+### 3. Report Format (`references/report-format.md`)
+
+Structured QA report template: test results overview, coverage metrics, failed tests, performance, build status, recommendations.
+
+**Load when:** Generating test summary reports
+
+## Quick Reference
+
+```
+Code tests     → test-execution-workflow.md
+  npm test / pytest / go test / cargo test / flutter test
+  Coverage: npm run test:coverage / pytest --cov
+
+UI tests       → ui-testing-workflow.md
+  Screenshots, responsive, a11y, forms, console errors
+  Auth: inject-auth.js for protected routes
+
+Reports        → report-format.md
+  Structured QA summary with metrics & recommendations
+```
+
+## Working Process
+
+1. Identify testing scope from recent changes or requirements
+2. Run typecheck/analyze commands to catch syntax errors first
+3. Execute appropriate test suites
+4. Analyze results — focus on failures
+5. Generate coverage reports if applicable
+6. For frontend: run UI tests via `chrome-devtools` (if available) skill
+7. Produce structured summary report
+
+## Tools Integration
+
+- **Test runners**: Jest, Vitest, Mocha, pytest, go test, cargo test, flutter test
+- **Coverage**: Istanbul/c8/nyc, pytest-cov, go cover
+- **Browser**: `chrome-devtools` (if available) skill for UI testing (screenshots, ARIA, console, network)
+- **Analysis**: `ai-multimodal` (if available) skill for screenshot analysis
+- **Debugging**: `debug` skill when tests reveal bugs requiring investigation
+- **Thinking**: `sequential-thinking` skill for complex test failure analysis
+
+## Quality Standards
+
+- All critical paths must have test coverage
+- Validate happy path AND error scenarios
+- Ensure test isolation — no interdependencies
+- Tests must be deterministic and reproducible
+- Clean up test data after execution
+- Never ignore failing tests to pass the build
+
+## Report Output
+**IMPORTANT:** Invoke "/ck-project-organization" skill to organize the outputs.
+
+Use naming pattern from `## Naming` section injected by hooks.
+
+## Team Mode
+
+When operating as teammate:
+1. On start: check `TaskList`, claim assigned/next unblocked task via `TaskUpdate`
+2. Read full task description via `TaskGet` before starting
+3. Wait for blocked tasks (implementation) to complete before testing
+4. Respect file ownership — only create/edit test files assigned
+5. When done: `TaskUpdate(status: "completed")` then `SendMessage` results to lead
+
+**Fallback:** Task tools (`TaskList`/`TaskUpdate`/`TaskGet`) are CLI-only — unavailable in VSCode extension. If they error, use `TodoWrite` for progress tracking and coordinate via `SendMessage` only.

package/skills/test/references/report-format.md

@@ -0,0 +1,58 @@
+# Test Report Format
+
+Structured QA report template. Sacrifice grammar for concision.
+
+## Template
+
+```markdown
+# Test Report — {date} — {scope}
+
+## Test Results Overview
+- **Total**: X tests
+- **Passed**: X | **Failed**: X | **Skipped**: X
+- **Duration**: Xs
+
+## Coverage Metrics
+| Metric   | Value | Threshold | Status |
+|----------|-------|-----------|--------|
+| Lines    | X%    | 80%       | PASS/FAIL |
+| Branches | X%    | 70%       | PASS/FAIL |
+| Functions| X%    | 80%       | PASS/FAIL |
+
+## Failed Tests
+### `test/path/file.test.ts` — TestName
+- **Error**: Error message
+- **Stack**: Relevant stack trace (truncated)
+- **Cause**: Brief root cause analysis
+- **Fix**: Suggested resolution
+
+## UI Test Results (if applicable)
+- **Pages tested**: X
+- **Screenshots**: ./screenshots/
+- **Console errors**: none | [list]
+- **Responsive**: checked at [viewports] | skipped
+- **Performance**: LCP Xs, FID Xms, CLS X
+
+## Build Status
+- **Build**: PASS/FAIL
+- **Warnings**: none | [list]
+- **Dependencies**: all resolved | [issues]
+
+## Critical Issues
+1. [Blocking issue description + impact]
+
+## Recommendations
+1. [Actionable improvement with priority]
+
+## Unresolved Questions
+- [Any open questions, if any]
+```
+
+## Guidelines
+
+- Include ALL failed tests with error messages — don't summarize away details
+- Coverage: highlight specific uncovered files/functions, not just percentages
+- Screenshots: embed paths directly in report for easy access
+- Recommendations: prioritize by impact (critical > high > medium > low)
+- Keep report under 200 lines — split into sections if larger scope needed
+- Save report using naming pattern from `## Naming` section injected by hooks

package/skills/test/references/test-execution-workflow.md

@@ -0,0 +1,103 @@
+# Test Execution Workflow
+
+## Step 1: Identify Scope
+
+Determine what to test based on recent changes:
+- New feature → full test suite + new test cases
+- Bug fix → regression tests + targeted fix validation
+- Refactor → existing test suite (no new tests unless gaps found)
+- Coverage check → full suite with coverage flags
+
+## Step 2: Pre-flight Checks
+
+Run syntax/type checks before tests to catch compile errors early:
+
+```bash
+# JavaScript/TypeScript
+npx tsc --noEmit          # TypeScript check
+npx eslint .              # Lint check
+
+# Python
+python -m py_compile file.py
+flake8 .
+
+# Flutter
+flutter analyze
+
+# Go
+go vet ./...
+
+# Rust
+cargo check
+```
+
+## Step 3: Execute Tests
+
+### JavaScript/TypeScript
+```bash
+npm test                    # or yarn test / pnpm test / bun test
+npm run test:coverage       # with coverage
+npx vitest run              # Vitest
+npx jest --coverage         # Jest with coverage
+```
+
+### Python
+```bash
+pytest                      # basic
+pytest --cov=src --cov-report=term-missing  # with coverage
+python -m unittest discover # unittest
+```
+
+### Go / Rust / Flutter
+```bash
+go test ./... -cover        # Go with coverage
+cargo test                  # Rust
+flutter test --coverage     # Flutter
+```
+
+## Step 4: Analyze Results
+
+Focus on:
+1. **Failing tests** — read error messages and stack traces carefully
+2. **Flaky tests** — tests that pass/fail intermittently indicate race conditions or state leaks
+3. **Slow tests** — identify bottlenecks (>5s per test is suspicious)
+4. **Skipped tests** — ensure skips are intentional, not hiding failures
+
+## Step 5: Coverage Analysis
+
+Thresholds:
+- **80%+** line coverage — standard minimum
+- **70%+** branch coverage — acceptable for most projects
+- Focus on critical paths: auth, payment, data mutations
+
+Identify gaps:
+- Uncovered error handlers
+- Missing edge case branches
+- Untested utility functions
+
+## Step 6: Build Verification
+
+```bash
+npm run build               # JS/TS production build
+python setup.py build       # Python
+go build ./...              # Go
+cargo build --release       # Rust
+flutter build               # Flutter
+```
+
+Check for:
+- Build warnings or deprecation notices
+- Unresolved dependencies
+- Production config correctness
+
+## Quality Checklist
+
+- [ ] All tests pass (zero failures)
+- [ ] Coverage meets project threshold
+- [ ] No flaky tests detected
+- [ ] Build completes without errors
+- [ ] Error scenarios tested
+- [ ] Test isolation verified (no shared state)
+- [ ] Test data cleaned up after execution
+- [ ] Mocks/stubs properly configured
+- [ ] Environment variables correctly set

package/skills/test/references/ui-testing-workflow.md

@@ -0,0 +1,65 @@
+# UI Testing Workflow
+
+Activate the ck:chrome-devtools (if available) skill.
+
+## Purpose
+Run comprehensive UI tests on a website and generate a detailed report.
+
+## Arguments
+- $1: URL - The URL of the website to test
+- $2: OPTIONS - Optional test configuration (e.g., --headless, --mobile, --auth)
+
+## Testing Protected Routes (Authentication)
+
+### Step 1: User Manual Login
+Instruct the user to:
+1. Open the target site in their browser
+2. Log in manually with their credentials
+3. Open browser DevTools (F12) → Application tab → Cookies/Storage
+
+### Step 2: Extract Auth Credentials
+Ask the user to provide one of:
+- **Cookies**: Copy cookie values (name, value, domain)
+- **Access Token**: Copy JWT/Bearer token from localStorage or cookies
+- **Session Storage**: Copy relevant session keys
+
+### Step 3: Inject Authentication
+Use the `inject-auth.js` script:
+
+```bash
+cd $SKILL_DIR  # chrome-devtools scripts (if available)
+
+# Option A: Inject cookies
+node inject-auth.js --url https://example.com --cookies '[{"name":"session","value":"abc123","domain":".example.com"}]'
+
+# Option B: Inject Bearer token
+node inject-auth.js --url https://example.com --token "Bearer eyJhbGciOi..." --header Authorization --token-key access_token
+
+# Option C: Inject localStorage
+node inject-auth.js --url https://example.com --local-storage '{"auth_token":"xyz","user_id":"123"}'
+```
+
+### Step 4: Run Tests
+After auth injection, run tests normally:
+```bash
+node navigate.js --url https://example.com/dashboard
+node screenshot.js --url https://example.com/profile --output profile.png
+```
+
+## Workflow
+- Use `plan` skill to organize the test plan & report
+- All screenshots saved in the same report directory
+- Browse URL, discover all pages, components, endpoints
+- Create test plan based on discovered structure
+- Use multiple `tester` subagents in parallel for: pages, forms, navigation, user flows, accessibility, responsive layouts, performance, security, seo
+- Use `ai-multimodal` (if available) to analyze all screenshots
+- Generate comprehensive Markdown report
+- Ask user if they want to preview with `/ck-preview`
+
+## Output Requirements
+- Clear, structured Markdown with headers, lists, code blocks
+- Include test results summary, key findings, screenshot references
+- Ensure token efficiency while maintaining high quality
+- Sacrifice grammar for concision
+
+**Do not** start implementing fixes.

package/skills/ui-styling/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: ui-styling
 description: Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
+license: MIT
+argument-hint: "[component or layout]"
 ---
 
 # UI Styling Skill

package/skills/web-testing/SKILL.md

@@ -1,52 +1,25 @@
 ---
 name: web-testing
-description: Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Multi-language support (JS/TS, Python, Go, Rust, Flutter). Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
+description: Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
+license: Apache-2.0
+argument-hint: "[test-type] [target]"
 ---
 
 # Web Testing Skill
 
-Comprehensive testing: unit, integration, E2E, load, security, visual regression, accessibility. Multi-language workflow orchestration with structured QA reporting.
-
-## Core Principle
-
-**NEVER IGNORE FAILING TESTS.** Fix root causes, not symptoms. No mocks/cheats/tricks to pass builds.
+Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.
 
 ## Quick Start
 
 ```bash
-# JavaScript/TypeScript
 npx vitest run                    # Unit tests
 npx playwright test               # E2E tests
-npm run test:coverage             # Coverage
-
-# Python
-pytest --cov=src                  # Unit + coverage
-
-# Go / Rust / Flutter
-go test ./... -cover              # Go
-cargo test                        # Rust
-flutter test --coverage           # Flutter
-
-# Web Quality
+npx playwright test --ui          # E2E with UI
 k6 run load-test.js               # Load tests
-npx @axe-core/cli https://...    # Accessibility
-npx lighthouse https://...       # Performance
+npx @axe-core/cli https://example.com  # Accessibility
+npx lighthouse https://example.com     # Performance
 ```
 
-## Workflows
-
-Three orchestrated workflows — load the relevant reference when needed:
-
-| Workflow | Reference | Use When |
-|----------|-----------|----------|
-| Code Testing | `./references/test-execution-workflow.md` | Running unit/integration/e2e, checking coverage, validating builds |
-| UI Testing | `./references/ui-testing-workflow.md` | Visual regression, responsive checks, accessibility audits, form automation |
-| Report Format | `./references/report-format.md` | Generating structured QA summary reports |
-
-**Code Testing Process:** Identify scope → Pre-flight checks → Execute tests → Analyze results → Coverage analysis → Build verification → Report
-
-**UI Testing Process:** Discovery → Visual capture → Console errors → Network validation → Responsive testing → Form testing → Performance metrics → Report
-
 ## Testing Strategy (Choose Your Model)
 
 | Model | Structure | Best For |
@@ -55,15 +28,10 @@ Three orchestrated workflows — load the relevant reference when needed:
 | Trophy | Integration-heavy | Modern SPAs |
 | Honeycomb | Contract-centric | Microservices |
 
-> `./references/testing-pyramid-strategy.md`
+→ `./references/testing-pyramid-strategy.md`
 
 ## Reference Documentation
 
-### Workflows & Reports
-- `./references/test-execution-workflow.md` - Orchestrated code testing (multi-language)
-- `./references/ui-testing-workflow.md` - Browser-based visual testing via `agent-browser`
-- `./references/report-format.md` - Structured QA report template
-
 ### Core Testing
 - `./references/unit-integration-testing.md` - Vitest, browser mode, AAA
 - `./references/e2e-testing-playwright.md` - Fixtures, sharding, selectors
@@ -98,17 +66,6 @@ Three orchestrated workflows — load the relevant reference when needed:
 - `./references/pre-release-checklist.md` - Complete release checklist
 - `./references/functional-testing-checklist.md` - Feature testing
 
-## Tools Integration
-
-- **Test runners**: Vitest, Jest, Mocha, pytest, go test, cargo test, flutter test
-- **Coverage**: Istanbul/c8/nyc, pytest-cov, go cover
-- **E2E**: Playwright (multi-browser, sharding)
-- **Load**: k6
-- **Browser**: `agent-browser` skill for UI testing
-- **Analysis**: `ai-multimodal` skill (if available) for screenshot analysis
-- **Debugging**: `debug` skill when tests reveal bugs
-- **Thinking**: `sequential-thinking` skill for complex test failure analysis
-
 ## Scripts
 
 ### Initialize Playwright Project
@@ -137,12 +94,3 @@ jobs:
       - run: npm run test:a11y      # Accessibility
       - run: npx lhci autorun       # Performance
 ```
-
-## Quality Standards
-
-- All critical paths must have test coverage
-- Validate happy path AND error scenarios
-- Ensure test isolation — no interdependencies
-- Tests must be deterministic and reproducible
-- Clean up test data after execution
-- Coverage: 80%+ lines, 70%+ branches minimum