菜单
Create or update Requests for Comment for this repository. Use when the user wants a new feature, subsystem, module, game mechanic, API change, or vendor contribution proposal drafted in `proposals/rfc/` before implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | rfc-creator |
| description | Create or update Requests for Comment for this repository. Use when the user wants a new feature, subsystem, module, game mechanic, API change, or vendor contribution proposal drafted in `proposals/rfc/` before implementation. |
Use this skill to draft repository-specific RFCs that follow proposals/rfc/README.md exactly. RFCs are for proposals before implementation, not for settled architectural decisions.
proposals/rfc/README.md and any relevant context from README.md, docs/project-overview.md, and docs/architecture.md.NNNN-short-title in lowercase kebab-case (e.g. 0001-minimal-poc).proposal/NNNN-short-title matching the RFC filename exactly before writing any files. Do not proceed without switching to this branch.proposals/rfc/NNNN-short-title.md on that branch.# RFC-NNNN: Title
**Status:** draft | under review | accepted | rejected
**Date:** YYYY-MM-DD
**Authors:** @handle
**Related:** links to issues, ADRs, or other RFCs
## Summary
## Motivation
## Design
## Open Questions
## Alternatives
## Summary to one clear paragraph.## Design when useful.## Open Questions to surface unresolved choices instead of hiding them.When creating a new RFC:
proposal/NNNN-short-title before writing files.proposals/rfc/.proposals/rfc/README.md./rfc-review before opening the proposal for comment.Structured SRE debugging methodology for aie-matrix production incidents. Use this skill whenever the user is investigating anything that is slow, broken, or behaving unexpectedly in production or staging — including slow deploys, failing health probes, high latency, unexpected restarts, memory pressure, or anything described as "something is wrong" or "why is X taking so long". Also use when writing a post-mortem or runbook entry. The skill enforces a disciplined observe-hypothesize-test loop rather than applying fixes based on intuition.
Gate check before opening a PR: clean build, all tests (unit + integration), spec coverage, doc impact, and a go/no-go verdict. Run after /speckit.implement and before opening a pull request.
Effect-ts coding standard for all server-side packages in aie-matrix (server/agent-host/ and server/*). Use when writing or reviewing services, route handlers, error types, logging, configuration, or background fibers in any of these packages.
Create or update the feature specification from a natural language feature description.
Validate gram notation snippets or files using the gram-lint CLI. Use whenever you need to check whether a gram expression or .map.gram file is syntactically valid — especially when designing format changes, reviewing example files, or verifying that proposed snippets are parseable by the WASM grammar.
Validates Gram notation files and inline snippets using the gram-lint CLI (parse errors, optional s-expression tree). Use when editing or generating .gram files, debugging Gram.parse failures, validating converter output, or when the user mentions gram-lint, Gram syntax, or linting gram documents.