Agent skill · ericnordelo
design-review
Review Canton design documents and architecture proposals against an incrementally maintained checklist covering clarity, Canton terminology, correctness, security, operability, upgradeability, and future compatibility. Use when evaluating a Canton proposal and producing actionable review comments.
What it needs
About 4k tokens when loaded.
What this skill does
Design Review Review the complete design against every checklist item. Report only material findings. For each finding, identify the affected passage, explain the problem and its impact, and suggest a precise correction. 1. Clarity and brevity. Make every sentence and paragraph express a clear point in direct language. Flag verbosity, convoluted phrasing, vague abstractions, and passages whose purpose is difficult to identify. 2. Purpose and relevance. Ensure every section contributes to the proposal's decision or design. Remove redundant material, low-value comparisons, and tangents such as competitive positioning when they do not affect the architecture. 3. Scope framing. State what will be delivered, what will not, and why. Do not frame simplicity or extensibility in a way that can be read as avoiding necessary work. 4. Information order. Introduce load-bearing decisions, constraints, trust assumptions, and limitations before sections that depend on them. Do not postpone information that the reader needs to understand earlier claims. 5. Definitions and acronyms. Define Canton-specific concepts, project-specific labels, acronyms, and referenced symbols before first use. Expand acronyms such as Smart Contract Upgrade (SCU), and explain unfamiliar choices or APIs rather than assuming recognition. 6. Official Canton terminology. Use the terminology from authoritative Canton documentation. In particular, distinguish Canton consensus from Daml/Daml-LF execution, and avoid invented or imprecise descriptions when an established term exists. 7. Concrete Canton concepts. Prefer precise definitions over abstract analogies. Describe a Canton contract as an instance of a template with state and business logic whose actions are authorized by parties. 8. Parties versus infrastructure. Keep parties, accounts, participant or validator nodes, synchronizers, signatories, observers, and controllers conceptually separate. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ericnordelo/design-review