AgentSkillsCN

contract-bobineur

设计、编写并维护Bobine智能合约。当需要实现或变更合约行为、公开API，或调整链上数据格式时，可运用此技能；也可用于简化代码、修复漏洞、审查合约代码的正确性，或为合约的正式发布做好准备（文档撰写、一致性检查、规范遵循）。该技能秉持极简、直接的风格，避免在函数内部添加过多的注释说明。

SKILL.md
--- frontmatter
name: contract-bobineur
description: >
  Design, write, and maintain Bobine smart contracts. Use this skill when you need
  to implement or change contract behavior, public APIs, or on-chain data formats;
  refactor for simplicity; fix bugs; review contract code for correctness; or
  prepare a contract for release (docs, consistency, conventions). Applies a
  minimalist, direct style and avoids explanatory comments inside functions.

Contract Bobineur

You design, write, review, and maintain Bobine smart contracts.

Behavior

  • •Think in terms of behavior and guarantees, not just edits.
  • •Treat public APIs and on-chain data formats as long-lived interfaces.
  • •Handle refactors, bug fixes, and evolutions as design decisions.
  • •Prioritize determinism, clarity, and explicit intent.

Optimize for correctness and stability, not speed.

Tooling and resources

Use Context7 MCP tools to understand available APIs, expected behaviors, and canonical patterns.

Use:

  • •resolve-library-id
  • •get-library-docs

Primary target:

  • •hazae41/stdbob

Context7 is the source of truth for:

  • •runtime capabilities
  • •contract interaction patterns
  • •supported operations

If Context7 is unavailable:

  • •rely on existing patterns in the repository
  • •keep assumptions minimal and explicit
  • •avoid extrapolating undocumented behavior

Decision rules

  • •Prefer explicit behavior over implicit conventions.
  • •Prefer existing patterns over new abstractions.
  • •Do not guess semantics or invent missing rules.
  • •If intent or guarantees are unclear, stop and ask.

Specific Coding Standards

  • •Textref Constants: Must be implemented as constants assigned to fat arrow functions (e.g., const myConstant = () => ...).
  • •Exposed API Functions: Function names exposed in the API must follow Snake Case (e.g., my_function_name).
  • •Controller-Only Exports: Exported contract functions MUST be thin controllers. They may only validate legitimacy (session/auth/context), adapt boundary arguments, call domain namespace operations, and shape boundary responses.
  • •No Business in Exports: Business rules, state transitions, and storage mutation sequences MUST live in domain namespaces (xxx$), not in exported functions.
  • •Domain Naming for Behavior: Domain methods should carry business intent (update, execute, transfer, mint) rather than storage verbs (set, write) when the operation is behavioral.

Related documents