photonics-dhl/OpenScience

docs-sync

Use when project files or task status change, before handoff/compaction/deployment, or when stale docs, old memory, conflicting CURRENT claims, version drift, or bloated context could misroute the next session.

原文语言：多语言混合

api-contract

Use when designing, adding, or changing any backend API endpoint, event, or frontend-backend data schema. Do NOT use for internal function signatures that never cross a process boundary.

architecture-guard

Use before modifying code that touches module boundaries, AI/Provider SDK calls, or the monorepo layout. Do NOT use for pure content/documentation edits that don't change code structure.

database-migration

Use when writing, reviewing, or applying any database schema migration or deciding what belongs in the database vs object storage. Do NOT use for read-only queries or seed data scripts.

frontend-design

Use when building or modifying any UI page, component, or layout — especially workbench, public RO pages, or collaboration areas. Do NOT use for backend-only logic with no UI surface.

infra-runbook

Use when writing deployment/backup/restore runbooks, changing Docker/compose/network topology, or preparing a production operation. Do NOT use for local dev-only one-off commands.

repo-map

Use when entering the repo for the first time, running a read-only codebase audit (Phase 0), or needing a directory/dependency/service/data map. Do NOT use for editing code or refactoring — this skill is strictly read-only.

security-review

Use when reviewing code that touches auth, permissions, uploads, secrets, sandbox execution, logging, or before any public release. Do NOT use for purely cosmetic or docs-only changes.

test-gate

Use after any code change before claiming completion, and when preparing phase acceptance evidence. Do NOT use to design new test frameworks — this is a pass/fail gate, not a test-authoring guide.