重新框架2实现者
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第一阶段——锁定决策
遍历`references/phase-1-decisions.md`并使用`references/decision-record.md`模板生成锁定决策记录。七个决策块(D1 目标语言、D2 基础、D3 范围、D4 始终需要的实现决策 - 实施者检查表第 2 部分的 F1–F6 / S1–S3 / Sub1–Sub2 / V1–V3 / T1–T3 / E1–E2、与检查表 1:1 的子编号、D5 模式机制、D6 集成故事、D7 功能标签集)详细说明;规范选项矩阵位于`spec/Implementor-Checklist.md`。
第 2 阶段——遍历规范语料库
锁定第一阶段后,逐个 EP 行走`references/phase-2-impl-order.md`。对于每个 EP,叶子都包含:首先要阅读的内容、要公开的合同、CLJS 参考如何实现它(作为一个示例,不是规范性的)、一致性装置检查的内容、常见的规范差距陷阱。依赖顺序是固定的:EP 001 配准→ 002 框架→ 006 反应基底→ 004 视图→ 009 仪器,然后针对`:core/*` 夹具进行第一次一致性检查。可选 EP(010 模式、008 测试、005 状态机、012 路由、011 SSR、013 流、014 HTTP、007 故事)遵循阶段 1 为它们声明的 `yes` 的顺序。
# re-frame2-implementor
This skill is **workflow + guidance** layered on the spec corpus at [`spec/`](../../spec/). The spec is the contract; the reference impl under `implementation/` is one worked example, not normative.
The job is to walk the engineer through two phases:
1. **Phase 1** — lock the load-bearing decisions (target language, substrate, scope, identity primitive, persistent data, concurrency, schema mechanism, hot-reload).
2. **Phase 2** — implement EPs in dependency order (001 → 002 → 006 → 004 → 009, then optional EPs per Phase 1 scope), validated by the conformance corpus.
## When NOT to use this skill
Full skill-disambiguation matrix lives at [`skills/README.md` §Skill routing — single source](../README.md#skill-routing--single-source). In brief: not for authoring on the CLJS reference, greenfield bootstrap, v1→v2 migration, live-app inspection, or pattern-rationale reading.
## Cardinal rules (one-liners; full text in [`references/cardinal-rules.md`](references/cardinal-rules.md))
1. **Spec is the contract.** When `implementation/` and [`spec/`](../../spec/) disagree, the spec wins.
2. **Phase 1 before Phase 2.** Lock decisions in writing before writing code.
3. **Dependency order.** EP 001 → 002 → 006 → 004 → 009 are the foundation; optional EPs sit downstream.
4. **Substrate-agnostic phrasing.** Write to "the identity primitive", "the render-tree", "the reactive container" — not to hiccup / Reagent / keywords.
5. **No core.async equivalents.** Async effects ride host primitives; cross-frame work is run-to-completion-drained.
6. **JVM-runnability for testing.** Pure transitions and pure sub computations must be callable from a non-substrate harness.
7. **Conformance corpus is the acceptance test.** Score is `passed / claimed-applicable`; a fixture you can't make pass without outside sources is a *spec gap*.
8. **Spec gap → draft a GitHub issue against `day8/re-frame2` and ask before filing.** Don't paper, don't invent, don't extrapolate from the reference — but don't auto-file either. Show the engineer the drafted title + body, restrict the body to public spec-quoted evidence (no private port source), and wait for explicit OK before running `gh issue create`. The skill runs in the engineer's port repo; spec gaps reach the framework maintainers via the upstream repo's GitHub issues — never via `bd` (re-frame2's internal tracker, never invoked from a published skill).
9. **Per-issue approval gate for any cross-repo side effect.** Before running `gh issue create` against a repo other than the one the engineer is working in, show the full draft (title, target repo, label set, body) and wait for explicit "yes" / "go" / "file it". Invoking the skill is consent to the workflow, not to each cross-repo write. See [`references/cardinal-rules.md` §9](references/cardinal-rules.md).
10. **Pin the spec corpus.** The kickoff prompt names a specific `day8/re-frame2` commit/tag; verify the checkout's HEAD and origin before reading the spec, and record the pinned hash in `DECISIONS.md` (preamble before D1). An unverified checkout is not the contract.
11. **Honour the reserved `:rf/*` scheme.** Framework-owned ids live under the single root namespace `:rf/*` (and its sub-namespaces); user code MUST NOT register under `:rf/*`. Reserved fx-ids and reserved app-db keys (`:rf/machines`, `:rf/route`, …) are part of the contract. A port that ignores the scheme fails conformance fixtures that assert `:rf.*` operation ids. Per [`spec/Conventions.md`](../../spec/Conventions.md); the "where does each surface live" map is [`spec/Ownership.md`](../../spec/Ownership.md).
## Phase 1 — lock the decisions
Walk [`references/phase-1-decisions.md`](references/phase-1-decisions.md) and produce a locked-decision record using the [`references/decision-record.md`](references/decision-record.md) template. The seven decision blocks (D1 target language, D2 substrate, D3 scope, D4 the always-required realisation decisions — Implementor-Checklist Part 2's F1–F6 / S1–S3 / Sub1–Sub2 / V1–V3 / T1–T3 / E1–E2, sub-numbered 1:1 with the checklist, D5 schema mechanism, D6 integration story, D7 capability tag set) are detailed there; the canonical option matrices live in [`spec/Implementor-Checklist.md`](../../spec/Implementor-Checklist.md).
Output of Phase 1: a single dated decision record committed to the port's own repo.
## Phase 2 — walk the spec corpus
With Phase 1 locked, walk [`references/phase-2-impl-order.md`](references/phase-2-impl-order.md) EP-by-EP. The leaf carries, for each EP: what to read first, the contract to expose, how the CLJS reference realised it (as **one** example, not normative), what the conformance fixtures check, common spec-gap traps.
Dependency order is fixed: **EP 001 Registration → 002 Frames → 006 Reactive substrate → 004 Views → 009 Instrumentation**, then a first conformance pass against the `:core/*` fixtures. Optional EPs (010 Schemas, 008 Testing, 005 State machines, 012 Routing, 011 SSR, 013 Flows, 014 HTTP, 007 Stories) follow in the order Phase 1 declared `yes` for them.
## Source discipline
Three tiers, in priority order:
1. **[`spec/`](../../spec/)** — the contract. Read in numeric order.
2. **[`spec/Implementor-Checklist.md`](../../spec/Implementor-Checklist.md)** — the decision-ordered companion.
3. **`implementation/`** — a worked example. Useful for "how did *someone* solve X?" Never useful as a contract claim.
If `implementation/` and `spec/` disagree, the spec wins.
## Conformance
The corpus at [`spec/conformance/`](../../spec/conformance/) is host-agnostic data. Harness shape, the EDN-handler-body DSL, capability tagging, scoring, and the spec-gap-vs-implementation-bug distinction are all in [`references/conformance.md`](references/conformance.md). The corpus is the acceptance test for [Goal 2 — AI-implementable from the spec alone](https://day8.github.io/re-frame2/spec/000-Vision/#ai-implementable-from-the-spec-alone).
## Kickoff and output
- [`references/kickoff-prompt.md`](references/kickoff-prompt.md) — paste-ready prompt for the engineer to drop into a fresh Claude session opened in the root of their port repo.
- [`references/output-format.md`](references/output-format.md) — the standard agent-output shape: implementation summary, capability tags claimed, conformance score, decisions made, spec gaps filed.
## Done — "v1-complete against `<capability tag set>`"
- [ ] Phase 1 decision record committed to the port's repo.
- [ ] All in-scope EPs have a working implementation.
- [ ] The port exposes [`spec/API.md`](../../spec/API.md), adapted to host idiom.
- [ ] Conformance score is `(claimed-applicable) / (claimed-applicable)`.
- [ ] Non-spec-gap failures fixed in the port; spec-gap failures filed as GitHub issues against `day8/re-frame2`.
- [ ] Port's README states claimed capability tags and conformance score.
## Reference files (all one level deep)
- [`references/cardinal-rules.md`](references/cardinal-rules.md) — the eleven rules in prose + anti-pattern corollaries.
- [`references/phase-1-decisions.md`](references/phase-1-decisions.md) — Phase 1 walkthrough, seven decision blocks.
- [`references/decision-record.md`](references/decision-record.md) — fill-in template for the locked-decision record.
- [`references/phase-2-impl-order.md`](references/phase-2-impl-order.md) — EP-by-EP implementation order.
- [`references/reference-impl-tour.md`](references/reference-impl-tour.md) — guided tour of the CLJS reference; what's substrate-specific vs pattern-required.
- [`references/conformance.md`](references/conformance.md) — corpus harness, DSL, capability tagging, scoring.
- [`references/kickoff-prompt.md`](references/kickoff-prompt.md) — fresh-session kickoff prompt.
- [`references/output-format.md`](references/output-format.md) — agent-output shape.
---
*Authoritative contract: [`spec/`](../../spec/). Decision companion: [`spec/Implementor-Checklist.md`](../../spec/Implementor-Checklist.md). Conformance: [`spec/conformance/`](../../spec/conformance/). CLJS reference (worked example): `implementation/`. Full skill-disambiguation matrix: [`skills/README.md` §Skill routing — single source](../README.md#skill-routing--single-source).*
---
> Source: [day8/re-frame2](https://github.com/day8/re-frame2) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
何时不使用此技能
基本规则(单行;全文见 [references/cardinal-rules.md](references/cardinal-rules.md))
第一阶段——锁定决策
第 2 阶段——遍历规范语料库
来源纪律
文件/命令 -> spec/ · implementation/ · skills/README.md · references/cardinal-rules.md · passed / claimed-applicable · day8/re-frame2 · gh issue create · DECISIONS.md
内容校验值 -> e53757b96118
当前原文的自动摘译,尚未人工审校。
何时不使用此技能
完整的技能消歧矩阵位于
skills/README.md§技能路由——单一来源。简而言之:不适用于 CLJS 参考、绿地引导、v1→v2 迁移、实时应用程序检查或模式原理阅读的创作。基本规则(单行;全文见 references/cardinal-rules.md)
规格就是合同。当
implementation/和spec/不同意时,规范获胜。第 1 阶段在第 2 阶段之前。在编写代码之前锁定书面决策。依赖顺序。 EP 001 → 002 → 006 → 004 → 009 为基础;可选的 EP 位于下游。与底层无关的措辞。写入“身份原语”、“渲染树”、“反应容器”——而不是打嗝/试剂/关键字。没有 core.async 等价物。异步效果乘坐主机原语;跨框架工作从运行到完成都是耗尽的。第 2 阶段——遍历规范语料库
在第一阶段锁定的情况下,逐个 EP 行走
references/phase-2-impl-order.md。对于每个 EP,叶子都包含:首先要阅读的内容、要公开的合同、CLJS 参考如何实现它(作为一个示例,不是规范性的)、一致性装置检查的内容、常见的规范差距陷阱。依赖顺序是固定的:EP 001 配准 → 002 框架 → 006 反应基底 → 004 视图 → 009 仪器,然后针对:core/*夹具进行第一次一致性检查。可选 EP(010 模式、008 测试、005 状态机、012 路由、011 SSR、013 流、014 HTTP、007 故事)遵循阶段 1 为它们声明的yes的顺序。来源纪律
三层,按优先顺序排列:
spec/——合同。按数字顺序阅读。spec/Implementor-Checklist.md— 决策命令同伴。implementation/——一个有效的例子。对于“某人如何解决 X?”很有用。作为合同索赔从来没有用。如果implementation/和spec/不一致,则该规范获胜。