Generates a modular-monolith mapping from a confirmed concept model only when the user explicitly invokes $concept-implementation. / 仅在用户显式调用 $concept-implementation 时做模块单体映射。
SkillScore92Maintained
Automatic
◆Coding pack
Last verified 10/10/2026
What it changes
Passed 22 of 24 test cases with the skill, and 15 of 24 without it.
Without skill63%
With skill92%
Checks it passed that the model alone missed
States that query methods produce no action completions.
Declines to generate implementation code without a confirmed concept model.
Identifies the conflicting grace period duration as a PRD transcription error.
and 10 more in the full report
7 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+29 pp
Tokens
+25%
Agent turns
0%
Response time
-14%
Model gemini-3.6-flashMeasured 10/10/2026v322 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
$concept-implementation When a multi-step booking sync rule encounters a failure halfway through, does a compensation action need to restore the exact prior state of completed concepts?
What was checked, without and with the skill
Checked
Without skill
With skill
Clarifies that compensation actions do not need to restore exact prior state.
Passed
Passed
States that completed concept actions remain completed despite later workflow failures.
Missed
Passed
case-16 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md77 lines7 files
Concept Implementation
Map a confirmed concept model to verifiable, composable implementation. Run only on explicit
$concept-implementation invocation; deliver a plan or code as requested. Continue confirmed
portions and route model gaps affecting implementation back to concept-design.
Concepts
Concept module: partitions actions and their state relations by purpose, not by entity. The same
identity can participate in several concepts. Use type parameters/opaque IDs for external identities;
concepts never reference, call, or query each other. Encapsulate storage while exposing abstract
state and actions to composition.
Synchronization rule: a named causal rule outside concepts, expressing identifiable application
policy that can be located, verified, and evolved independently. One entry can trigger several rules;
one rule can serve several entries. Grouping preserves rule boundaries without requiring a file or
package per rule.
Actions and queries: actions are observable occurrences in the contract and may read or update
state. Queries only return binding sets and produce no action completions. A request can occur as
a Requesting/Web action without the requested action following.
Constraints
Contracts and legibility: composition produces only behavior permitted by each concept contract.
Keep concept/action/parameter meanings aligned across specifications, code, and logs; map renames.
Actions enforce preconditions, invariants, effects, and result cases. A false precondition does not
automatically imply an error output; specify rejection results. Where queries cannot replace atomic
checks at the write.
Rule execution: use WYSIWID completion → binding → invocation semantics. When conjunctively
matches named inputs/outputs; omitted fields are wildcards and empty patterns do not imply success.
Where queries, filters, or computes zero/many binding sets; zero fires nothing, each set invokes then.
Then uses constants or bound values; its calls have no implicit order. Subsequent outputs require
new completion matches. State changes alone do not automatically trigger rules.
Correlation and boundaries: WYSIWID matches completions within one runtime flow and propagates
that correlation. Batch actions also require object bindings; documentation groups are not runtime
identities. Cross-concept policy belongs in syncs, public actions/queries respect confirmed permissions,
and composition owns no business state but may retain execution records. Repository convention:
connect rules through concept actions rather than hiding causality in direct sync-to-sync calls.
Failure and recovery: handle no-match, rejection, and faults according to entry contracts; required
responses must not be missing, crossed, or duplicated. Match errors and negative results by their
respective cases. Define response, retry, compensation, or intentional ignoring and state consequences.