codex-genesis-harness 0.1.0 → 0.1.1

package/.codex/skills/release-skill/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: release-skill
+description: Prepare Codex harness package releases with version checks, package dry-runs, npm publish readiness, release notes, verification evidence, and rollback notes. Use before publishing or tagging releases.
+---
+
+# Release Skill
+
+## Purpose
+Ensure package releases are verified, reproducible, and reversible.
+
+## When to use
+Use before npm publish, version bumps, release notes, or release automation changes.
+
+## When NOT to use
+Do not use for local-only edits that will not be packaged or released.
+
+## Inputs required
+Target version, changed files, verification output, package contents, and publish credentials status.
+
+## Outputs required
+Release checklist, package dry-run evidence, release notes, known risks, and rollback instructions.
+
+## Required tests
+Run verify, eval, package dry-run, and CLI smoke tests.
+
+## Required fixtures
+Update release fixtures or package content expectations when packaging changes.
+
+## Required contract updates
+Update public contract docs when release changes CLI or skill behavior.
+
+## Required codebase map updates
+Update current state and known problems after release preparation.
+
+## Token saving rules
+Read package metadata and release memory first; do not re-scan unchanged skill bodies.
+
+## Acceptance criteria
+Tarball contents are correct and release notes explain behavior, tests, and risks.
+
+## Common mistakes
+Publishing cache files, missing executable scripts, and omitting npm 2FA/token readiness.
+
+## Recovery workflow
+If publish fails, capture error, update known problems, do not change version until root cause is fixed.
+

package/.codex/skills/release-skill/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Release Skill"
+  short_description: "Prepare verified npm releases"
+  default_prompt: "Use $release-skill to verify package contents and release readiness."
+policy:
+  allow_implicit_invocation: true
+

package/.codex/skills/release-skill/checklists/checklist.md

@@ -0,0 +1,8 @@
+# Release Checklist
+
+- [ ] Verify passed.
+- [ ] Evals passed.
+- [ ] Pack dry-run inspected.
+- [ ] Version confirmed.
+- [ ] Publish credentials ready.
+

package/.codex/skills/release-skill/examples/example.md

@@ -0,0 +1,4 @@
+# Example
+
+Before `npm publish`, run verify, eval, pack dry-run, inspect tarball contents, then document publish risks.
+

package/.codex/skills/release-skill/templates/release-checklist-template.md

@@ -0,0 +1,9 @@
+# Release Checklist Template
+
+## Version
+## Verification
+## Package Contents
+## Release Notes
+## Risks
+## Rollback
+

package/.codex/skills/research-skill/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: research-skill
+description: Run local and external research for Codex harness decisions with source attribution, repository evidence, assumptions, and reusable research notes. Use before adopting APIs, SDKs, architecture patterns, or uncertain implementation approaches.
+---
+
+# Research Skill
+
+## Purpose
+Ground decisions in repository evidence and current authoritative sources.
+
+## When to use
+Use when facts may be stale, external APIs are involved, or implementation direction is uncertain.
+
+## When NOT to use
+Do not use when local code already answers the question and no external fact is needed.
+
+## Inputs required
+Research question, decision needed, local files, external source constraints, and acceptance criteria.
+
+## Outputs required
+Research note with local evidence, external citations, recommendation, rejected options, and follow-up tests.
+
+## Required tests
+Translate research into failing tests or contract checks before implementation.
+
+## Required fixtures
+Create fixtures for researched API examples or edge cases.
+
+## Required contract updates
+Update contracts if research changes public behavior or schemas.
+
+## Required codebase map updates
+Update memory files with durable conclusions and source dates.
+
+## Token saving rules
+Search targeted files first; summarize sources and avoid pasting long excerpts.
+
+## Acceptance criteria
+Decision is supported by evidence and converted into testable work.
+
+## Common mistakes
+Researching broadly without a decision, trusting stale docs, and failing to encode findings in tests.
+
+## Recovery workflow
+If research conflicts, prefer primary sources, document uncertainty, and choose the smallest reversible test.
+

package/.codex/skills/research-skill/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Research Skill"
+  short_description: "Ground harness decisions in evidence"
+  default_prompt: "Use $research-skill to gather evidence before choosing an implementation path."
+policy:
+  allow_implicit_invocation: true
+

package/.codex/skills/research-skill/checklists/checklist.md

@@ -0,0 +1,7 @@
+# Research Checklist
+
+- [ ] Local evidence checked.
+- [ ] Primary sources used.
+- [ ] Recommendation testable.
+- [ ] Memory updated.
+

package/.codex/skills/research-skill/examples/example.md

@@ -0,0 +1,4 @@
+# Example
+
+Research a provider SDK version, capture official docs, then create a contract fixture for the expected response.
+

package/.codex/skills/research-skill/templates/research-note-template.md

@@ -0,0 +1,9 @@
+# Research Note Template
+
+## Question
+## Local Evidence
+## External Evidence
+## Recommendation
+## Rejected Options
+## Tests To Add
+

package/.codex/skills/ui-ux-test-skill/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: ui-ux-test-skill
+description: Create UI smoke, e2e, interaction, validation, API synchronization, and visual regression tests before frontend changes. Use for screens, flows, forms, dashboards, and UI regressions.
+---
+
+# UI UX Test Skill
+
+## Purpose
+Make UI quality measurable through Playwright and fixture-backed tests.
+
+## When to use
+Use before implementing or upgrading UI routes, states, interactions, or visual behavior.
+
+## When NOT to use
+Do not use for non-UI changes.
+
+## Inputs required
+Route, role, viewport, API fixture, user actions, expected UI states, and visual references.
+
+## Outputs required
+Playwright test plan, fixtures, visual regression expectations, and API sync assertions.
+
+## Required tests
+Load, interaction, validation, API synchronization, and visual regression tests.
+
+## Required fixtures
+Create route fixtures under `playwright/fixtures/`.
+
+## Required contract updates
+Update `contracts/ui/` for every changed screen state.
+
+## Required codebase map updates
+Update `.codebase/UI_ROUTES.md` and `TEST_MATRIX.md`.
+
+## Token saving rules
+Read UI route map and fixture first; inspect only the route and components under test.
+
+## Acceptance criteria
+The UI has automated coverage for key workflows and visual states.
+
+## Common mistakes
+Testing only page load, skipping mobile, and ignoring API synchronization.
+
+## Recovery workflow
+If visual tests are flaky, stabilize fixtures and selectors before changing assertions.
+

package/.codex/skills/ui-ux-test-skill/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "UI UX Test Skill"
+  short_description: "Create UI and visual regression tests"
+  default_prompt: "Use $ui-ux-test-skill to create Playwright tests before UI changes."
+policy:
+  allow_implicit_invocation: true
+

package/.codex/skills/ui-ux-test-skill/checklists/checklist.md

@@ -0,0 +1,8 @@
+# UI Test Checklist
+
+- [ ] Load test.
+- [ ] Interaction test.
+- [ ] Validation test.
+- [ ] API sync test.
+- [ ] Visual regression test.
+

package/.codex/skills/ui-ux-test-skill/examples/example.md

@@ -0,0 +1,4 @@
+# Example
+
+Test dashboard load, filter interaction, validation message, API response sync, and desktop/mobile screenshots.
+

package/.codex/skills/ui-ux-test-skill/templates/playwright-test-template.md

@@ -0,0 +1,4 @@
+# Playwright Test Template
+
+Use `playwright/e2e`, `playwright/smoke`, `playwright/visual`, and `playwright/fixtures`.
+

package/.codex-plugin/plugin.json

@@ -1,9 +1,9 @@
 {
-  "name": "project-genesis-harness",
+  "name": "genesis-skill-set",
   "version": "0.1.0",
-  "description": "Codex project operating harness for planning, tracking, verification, docs sync, and reviews.",
+  "description": "Genesis harness skill system for Codex test-first, contract-first, memory-aware autonomous workflows.",
   "author": {
-    "name": "Project Genesis Harness"
+    "name": "Genesis Skill Set"
   },
   "license": "MIT",
   "keywords": [
@@ -11,23 +11,25 @@
     "skill",
     "planning",
     "verification",
-    "engineering"
+    "engineering",
+    "design",
+    "frontend"
   ],
   "skills": "./.codex/skills/",
   "interface": {
-    "displayName": "Project Genesis Harness",
-    "shortDescription": "Planning and verification harness for Codex",
-    "longDescription": "A Codex plugin that installs the project-genesis-harness skill for disciplined project initialization, feature planning, bug workflows, documentation synchronization, verification, audits, and completion reports.",
-    "developerName": "Project Genesis Harness",
+    "displayName": "Genesis Skill Set",
+    "shortDescription": "Test-first, contract-first Codex harness skills",
+    "longDescription": "A Codex plugin that installs the Genesis harness skill system: planning, architecture, codebase mapping, design specs, API contracts, UI tests, AI provider reliability, pipeline orchestration, research, docs, release workflows, repository memory, contracts, fixtures, Playwright templates, observability templates, and frontend design skills.",
+    "developerName": "Genesis Skill Set",
     "category": "Productivity",
     "capabilities": [
       "Write",
       "Review"
     ],
     "defaultPrompt": [
-      "Use $project-genesis-harness and run /init.",
-      "Use $project-genesis-harness to plan this feature.",
-      "Use $project-genesis-harness to audit this repo."
+      "Use $genesis-harness and run /init.",
+      "Use $pipeline-orchestration-skill to run the full test-first harness workflow.",
+      "Use $api-contract-skill to create endpoint contracts and tests before implementation."
     ],
     "brandColor": "#2563EB"
   }

package/README.md

@@ -1,181 +1,164 @@
-# Project Genesis Harness
-
-Project Genesis Harness is a Codex skill that turns Codex into a project operating harness: planning first, repository inspection, task tracking, test-first implementation, docs synchronization, architecture decisions, Mermaid diagrams, audits, and completion reports.
-
-## Install
-
-### From npm
-
-After the package is published to npm:
-
-```sh
-npm install -g codex-genesis-harness@latest
-```
-
-The package auto-installs the Codex skill into:
-
-```txt
-~/.agents/skills/project-genesis-harness
-~/.codex/skills/project-genesis-harness
-```
-
-You can also manage it manually:
-
-```sh
-genesis-harness install
-genesis-harness verify
-genesis-harness uninstall
-```
-
-Install only one target:
-
-```sh
-genesis-harness install --target agents
-genesis-harness install --target legacy
-genesis-harness install --target both
-```
-
-To skip auto-install during npm installation:
-
-```sh
-GENESIS_HARNESS_SKIP_POSTINSTALL=1 npm install -g codex-genesis-harness@latest
-```
-
-### From Git
-
-Clone or download this repository, then run:
-
-```sh
-./scripts/install.sh
-```
-
-By default, the installer copies the skill to:
-
-```txt
-~/.agents/skills/project-genesis-harness
-~/.codex/skills/project-genesis-harness
-```
-
-If you use a custom Codex home:
-
-```sh
-CODEX_HOME=/path/to/.codex ./scripts/install.sh
-```
-
-If you use a custom modern skills home:
-
-```sh
-GENESIS_HARNESS_HOME=/path/to/.agents ./scripts/install.sh
-```
-
-## Verify
-
-```sh
-./scripts/verify.sh
-```
-
-Verify an installed copy:
-
-```sh
-./scripts/verify.sh ~/.codex/skills/project-genesis-harness
-```
-
-## Uninstall
-
-```sh
-./scripts/uninstall.sh
-```
-
-## Use
-
-After installing, invoke the skill in Codex when working in a project:
-
-```txt
-Use $project-genesis-harness and run /init.
-```
-
-The skill supports:
-
-- `/init`
-- `/new-feature <description>`
-- `/fix-bug <description>`
-- `/plan <description>`
-- `/audit`
-- `/review`
-- `/status`
-
-## What Gets Installed
-
-```txt
-.codex/skills/project-genesis-harness/
-├── SKILL.md
-├── agents/openai.yaml
-├── resources/
-└── scripts/
-```
-
-The skill itself can initialize a target project with a `.planning/` knowledge base after the project brief is confirmed.
-
-## Plugin Metadata
-
-This repository includes:
-
-```txt
-.codex-plugin/plugin.json
-```
-
-The plugin manifest points Codex-compatible plugin tooling at the packaged skill under `.codex/skills/`.
-
-## Publish To npm
-
-The npm package name is:
-
-```txt
-codex-genesis-harness
-```
-
-Publish flow:
-
-```sh
-npm login
-npm run verify
-npm run eval
-npm run pack:check
-npm version patch
-npm publish --access public
-```
-
-The package is intentionally unscoped so it can be published by the token owner without requiring a pre-created npm organization or scope.
-
-## GitHub Actions npm Publish
-
-This repository includes `.github/workflows/publish-npm.yml`.
-
-On every push to `main`, the workflow:
-
-1. runs `npm run verify`
-2. runs `npm run eval`
-3. runs `npm run pack:check`
-4. derives a unique CI version like `0.1.0-ci.123.1`
-5. publishes `codex-genesis-harness` to npm with the `latest` tag
-
-Required GitHub secret:
-
-```txt
-NPM_TOKEN
-```
-
-Create it from npm with publish permission for `codex-genesis-harness`, then add it under:
-
-```txt
-GitHub repo -> Settings -> Secrets and variables -> Actions -> New repository secret
-```
-
-If GitHub Actions fails with `npm ERR! code E403` during `npm publish`, npm accepted the token format but rejected the publish authorization. Fix the npm-side credentials before re-running the workflow:
-
-1. Confirm the token belongs to an npm account that owns `codex-genesis-harness`, or can create the package if this is the first publish.
-2. Prefer an npm automation token with publish rights for CI. Granular tokens must include package write access.
-3. If the package name is already owned by another account or organization, either transfer/grant access on npm or rename/scope the package in `package.json`.
-4. Replace the GitHub `NPM_TOKEN` secret after rotating the token.
-
-The workflow validates `NPM_TOKEN` and package visibility before running the expensive verification and publish steps so credential problems fail with an actionable error.
+# Project Genesis Harness
+
+Project Genesis Harness packages the Genesis Codex harness skill system: test-first development, contract-first workflows, repository memory, codebase awareness, token-efficient operation, UI/API synchronization, AI pipeline reliability, and multi-session continuity.
+
+## Install
+
+### From npm
+
+Install the latest published package globally:
+
+```sh
+npm install -g codex-genesis-harness@latest
+```
+
+The package auto-installs all Genesis skills into:
+
+```txt
+~/.agents/skills/<skill-name>
+~/.codex/skills/<skill-name>
+```
+
+You can also manage them manually:
+
+```sh
+genesis-harness install
+genesis-harness verify
+genesis-harness uninstall
+```
+
+Install only one target:
+
+```sh
+genesis-harness install --target agents
+genesis-harness install --target legacy
+genesis-harness install --target both
+```
+
+To skip auto-install during npm installation:
+
+```sh
+GENESIS_HARNESS_SKIP_POSTINSTALL=1 npm install -g codex-genesis-harness@latest
+```
+
+### From Git
+
+Clone or download this repository, then run:
+
+```sh
+./scripts/install.sh
+```
+
+If you use custom homes:
+
+```sh
+CODEX_HOME=/path/to/.codex ./scripts/install.sh
+GENESIS_HARNESS_HOME=/path/to/.agents ./scripts/install.sh
+```
+
+## Verify
+
+```sh
+./scripts/verify.sh
+./scripts/run-evals.sh
+npm run pack:check
+```
+
+Verify an installed copy:
+
+```sh
+./scripts/verify.sh ~/.codex/skills
+```
+
+## Use
+
+After installing, invoke the skills in Codex:
+
+```txt
+Use $genesis-harness and run /init.
+Use $pipeline-orchestration-skill to run the full test-first harness workflow.
+Use $api-contract-skill to create endpoint contracts and tests before implementation.
+Use $genesis-new-design to design and build a premium frontend web experience.
+Use $genesis-upgrade-design to improve the existing UI without changing behavior.
+```
+
+`genesis-harness` supports:
+
+- `/init`
+- `/new-feature <description>`
+- `/fix-bug <description>`
+- `/plan <description>`
+- `/audit`
+- `/review`
+- `/status`
+
+## What Gets Installed
+
+```txt
+.codex/skills/
+  genesis-harness/
+  genesis-new-design/
+  genesis-upgrade-design/
+  architecture-skill/
+  planning-skill/
+  codebase-map-skill/
+  design-spec-skill/
+  api-contract-skill/
+  ui-ux-test-skill/
+  harness-engineering-skill/
+  ai-provider-skill/
+  pipeline-orchestration-skill/
+  research-skill/
+  docs-skill/
+  release-skill/
+.codebase/
+contracts/
+fixtures/
+tests/
+playwright/
+observability/
+```
+
+Each skill includes `SKILL.md`, `agents/openai.yaml`, `templates/`, `examples/`, and `checklists/`. The memory, contracts, fixtures, tests, Playwright, and observability folders provide reusable harness templates for downstream projects.
+
+## Package Metadata
+
+The npm package name is:
+
+```txt
+codex-genesis-harness
+```
+
+The plugin manifest at `.codex-plugin/plugin.json` points Codex-compatible plugin tooling at the packaged Genesis skill system under `.codex/skills/`.
+
+## Publish To npm
+
+Publish flow:
+
+```sh
+npm login
+npm run verify
+npm run eval
+npm run pack:check
+npm version patch
+npm publish --access public
+```
+
+The package is intentionally unscoped so it can be published by the token owner without requiring a pre-created npm organization or scope.
+
+## GitHub Actions npm Publish
+
+This repository includes `.github/workflows/publish-npm.yml`.
+
+Required GitHub secret:
+
+```txt
+NPM_TOKEN
+```
+
+If GitHub Actions fails with `npm ERR! code E403` during `npm publish`, npm accepted the token format but rejected the publish authorization. Fix the npm-side credentials before re-running the workflow:
+
+1. Confirm the token belongs to an npm account that owns `codex-genesis-harness`, or can create the package if this is the first publish.
+2. Prefer an npm automation token with publish rights for CI. Granular tokens must include package write access.
+3. If the package name is already owned by another account or organization, either transfer/grant access on npm or rename/scope the package in `package.json`.
+4. Replace the GitHub `NPM_TOKEN` secret after rotating the token.