メニュー
Use when editing docs/specs/, CLAUDE.md orchestration, or agent rules — keep subsystem specs aligned with code, run drift checks, and follow the anchor-issue + design-first workflow (GitHub as integration surface).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when working with AI schema generation, agent execution, pipeline orchestration, vector storage, agent tools, or files in packages/ai-schema/, packages/ai-agent/, packages/ai-pipeline/, packages/ai-vector/, packages/ai-tools/, packages/ai-observability/
Use when working with JSON:API endpoints, resource serialization, query parsing, schema presentation, route building, or files in packages/api/, packages/routing/
Use when working with entity types, entity storage, entity queries, field definitions, field type plugins, config entities, config import/export, or files in packages/entity/, packages/entity-storage/, packages/field/, packages/config/. Covers EntityInterface, EntityBase, EntityType, EntityTypeManager, SqlEntityStorage, SqlEntityQuery, SqlSchemaHandler, EntityRepository, UnitOfWork, FieldDefinition, FieldTypeManager, FieldItemBase, ConfigFactory, ConfigManager. Also applies when touching User (packages/user/) or Node (packages/node/) entity subclasses.
Use when working with service providers, domain events, cache backends, database queries, migrations, package discovery, attribute scanning, or files in packages/foundation/, packages/cache/, packages/database-legacy/, packages/plugin/
Use when working with HTTP middleware, event middleware, job middleware, pipeline compilation, middleware discovery, or files in packages/foundation/src/Middleware/, packages/routing/, packages/user/src/Middleware/, packages/access/src/Middleware/, public/index.php
First fixture skill used by the client-transformer contract tests.
| name | waaseyaa-spec-maintenance |
| description | Use when editing docs/specs/, CLAUDE.md orchestration, or agent rules — keep subsystem specs aligned with code, run drift checks, and follow the anchor-issue + design-first workflow (GitHub as integration surface). |
docs/specs/**/*.md, root CLAUDE.md, skeleton CLAUDE.md, or .claude/rules/Subsystem specs live in docs/specs/. Load them with the Read tool or search with ripgrep from the repo root, for example:
docs/specs/entity-system.md — full file for the entity stackrg -n "YourSymbol" docs/specs/ — find mentions across specsThe orchestration table in CLAUDE.md maps file patterns to spec paths — prefer that table over guessing filenames.
After code changes that affect documented behaviour, update the relevant spec in the same PR when practical. Run:
bash tools/drift-detector.sh 5
Session hooks may run a shorter threshold; CI runs drift detection on pushes and PRs.
This repo uses the anchor-issue + design-first workflow for structured delivery (see docs/specs/workflow.md).
Precedence: Anchor issues are the primary ledger for multi-PR efforts (scope, work packages, descope decisions in the comment trail). GitHub is for PRs, CI, releases, security, and issues (including M11 filings); no enforced milestone taxonomy (docs/specs/workflow.md).