メニュー
Maintain repository memory and compressed codebase maps for token-efficient Codex operation. Use when files move, modules change, contracts change, tests change, or repository summaries need updating.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Define UI design specs, route contracts, visual states, accessibility expectations, and UI/API synchronization before frontend implementation. Use for new screens, redesigns, visual QA, or UI contract updates.
Automatically synchronize documentation with code changes across all project phases. Detects file changes, categorizes update types, auto-generates API docs, changelog entries, implementation handoffs, and validates cross-reference integrity. Use after any phase implementation.
Initialize and operate a project planning harness for Codex. Use this skill when the user types /init, asks to create a new project, add a feature, fix a bug, plan work, generate tests first, update docs, track phases, review changes, audit a repository, or manage architecture decisions.
Create premium frontend web designs and usable first-screen experiences for new websites, web apps, dashboards, tools, and landing pages. Use when Codex is asked to design or build a new frontend UI, create a fresh page or app experience, choose a visual direction for a new product surface, or turn a product brief into implementation-ready React, Next.js, Tailwind, CSS, or HTML.
Create decision-complete plans for Codex harness work, including tests, fixtures, contracts, memory updates, verification, and recovery. Use for new features, refactors, bug fixes, audits, or multi-phase autonomous work.
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.
| name | genesis-codebase-map |
| description | Maintain repository memory and compressed codebase maps for token-efficient Codex operation. Use when files move, modules change, contracts change, tests change, or repository summaries need updating. |
Keep .codebase/ accurate so future agents read summaries before source.
Use after meaningful code, contract, test, route, provider, pipeline, or architecture changes.
Do not use for changes that do not affect repository understanding.
Changed files, verification results, contracts touched, and current .codebase files.
Updated module index, current state, test matrix, dependency graph, and context summaries.
Run scripts/verify.sh after memory updates.
Update fixture index when fixtures change.
Reflect changed contracts in .codebase/API_CONTRACTS.md.
Update all impacted .codebase files.
Summaries must be short, link to source locations, and avoid duplicating full manuals.
Future agents can orient by reading CURRENT_STATE.md, MODULE_INDEX.md, and TEST_MATRIX.md.
Letting memory drift, overloading summaries with full docs, and forgetting test matrix changes.
If memory conflicts with code, trust verified code, update memory, and add a known problem entry.
