القائمة
CellScript action, transition, resource, shared, receipt, capability, flow, and fail-closed basics.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Parser, type, lowering, runtime, and production-gate diagnostics with migration hints and safe next actions.
Generated builders, action-aware scans, deployment plans, live registry verification, and evidence boundaries.
CKB Cell Model, lock/type roles, Source views, WitnessArgs, CellDeps, capacity, since, and replacement semantics for CellScript work.
CompileMetadata, ProofPlan, builder assumptions, constraints, ABI, audit bundles, receipts, and artifact verification.
CellScript package layout, Cell.toml, build/check/fmt/test, canonical 0.21 command groups, registry/package verification, and legacy alias migration.
| name | cellscript-language-basics |
| description | CellScript action, transition, resource, shared, receipt, capability, flow, and fail-closed basics. |
| references | ["docs/wiki/Tutorial-02-Language-Basics.md","docs/wiki/Tutorial-03-Resources-and-Cell-Effects.md","docs/wiki/Tutorial-09-Action-Model-and-Canonical-Syntax.md","examples/token.cell"] |
| commands | ["cellc check","cellc explain"] |
Use this skill when writing or reviewing CellScript source. Prefer the action model already documented in the repository: visible actions, explicit transitions, resource/shared/receipt declarations, and verification blocks.
Do not introduce actor-style terminology or hidden state transitions. If a surface is reserved, deferred, metadata-only, runtime-required, or fail-closed, say so directly and point to current compiler evidence.
Validation defaults:
cellc check --message-format=json for source feedback;cellc explain <CODE> for diagnostic recovery;