Cardano Dev Skills Dey Connect AI Agents to Current Documentation

Cardano Dev Skills dey give AI coding agents clear instructions and technical references wey dem fit use build transactions, write smart contracts, and understand Cardano standards. Di package dey tackle one kind wahala wey dey repeat for development: sometimes agents fit produce code wey look correct but e go depend on old libraries or network rules wey don change.

Giovanni Gargiulo, Senior Blockchain Architect for Cardano Foundation, show di tool during Developers Office Hours on September 18, where e carry one agent from explanation of CIP-68 reach example of Java implementation.

Aiken and Conway Errors for Cardano Code

Gargiulo start di project after e notice say to correct AI-generated code dey sometimes take pass time wey e for take implement di solution by himself. Wetin start as personal experiment later enter Cardano Foundation GitHub organization and dem open am for community contributions.

One problem wey dey repeat involve Aiken, di language wey people dey use develop smart contracts for Cardano. Di agent dey continue use patterns from standard library version 2.4 even when Gargiulo request documentation for version 3. Di code wey come out no gree compile.

Conway-era changes come create another kain failure point. When e dey work with stake address registration and certificates, di agent mix newer requirements with older way of constructing transaction. Di application code fit compile successfully but di transaction go fail when dem submit am to di network.

Software development kits, or SDKs, get similar problems. Dis libraries allow applications to construct transactions and interact with Cardano, but if dem rename fields or change function signatures, older examples fit no work again.

At first, Gargiulo dey download current documentation by hand and e go dey point di agent to am many times. If session restart or conversation context compress, e mean say dem need supply those instructions again. E also try documentation retrieval experiments wey require steady source maintenance, and na so e take lead to one package wey join references with reusable development workflows.

Maintained Sources and the CIP-68 Demonstration

Di version wey dem present during di session get 15 development skills and 55 documentation sources. On October 2, di project official website list 18 skills and 73 sources, covering SDKs, programming languages, infrastructure, CIPs, and ledger specifications.

One skill dey provide instructions for specific task, like how to build ADA transfer transaction, write validator, or optimize contract. Cardano Improvement Proposals, wey people sabi as CIPs, dey supply technical standards wey agents fit explain and apply through di sources wey follow dem.

Di package separate im source registry, task instructions, and downloaded references. Maintainers fit update documentation separate from di workflows wey dey tell agent how to use am.

Task descriptions still help di agent match ordinary requests to correct workflow. Developer fit ask for token transaction or contract review with natural language, make di agent select di relevant skill without special command.

Automated weekly process dey retrieve upstream changes and open GitHub pull request make human review before dem enter main branch. Users go then get di updated package. Claude Code users suppose enable automatic updates for im marketplace or update am by hand.

Di cardano-context skill dey add persistent project instruction wey tell Claude Code or Codex make dem treat existing Cardano knowledge as something wey fit don old and make dem consult di bundled references first. Di two agents dey use di same development skills and sources through their different installation routes.

For di demonstration, Gargiulo request explanation of CIP-68, di metadata standard for Cardano native assets. E separate reference NFT, wey im transaction output dey hold di metadata, from user token wey dey represent di asset for holder wallet. Na di issuer contract logic dey determine whether dem fit update di metadata.

Di agent come respond to request for corresponding transaction by selecting development instructions and showing available libraries. Gargiulo choose cardano-client-lib, one Java library, and e receive project configuration, dependencies, and implementation code. Di generated example specify Java 17.

Gargiulo no run di example during di session. So di demonstration focus on preparing di implementation, and end-to-end transaction testing still remain.

Feedback and Further Cardano Applications

Cardano Dev Skills get feedback mechanism to report incorrect documentation, missing instructions, or cases where agent no select correct skill. Bora, one project contributor, describe one time wey agent propose make dem file report at di end of session and e ask di user to review am before dem approve submission as GitHub issue.

Maintainers dey use those reports to check whether na source or workflow need correction. Gargiulo still separate documentation problems from requests wey no clear or wey get technical fault, because each one need different response.

Specialist contributions dey help expand coverage. Gargiulo mention addition of Go material by one contributor wey sabi di language and im Cardano tooling. Di project scope rules dey accept development integrations, specifications, SDKs, and infrastructure documentation but dem no dey include marketing material and end-product user manuals.

People fit inspect di package text directly, while im helper hooks need review because dem dey execute code. Gargiulo outline further sessions on prompt injection, trust boundaries, and times wey agents dey ignore documentation. E still describe plans for more work on modularity and compatibility with other agents for di second half of October.

Potential extensions wey dem discuss during di session include to assess governance proposals against di Cardano Constitution and one testnet experiment wey users go pay one agent in USDCx for smart contract review, possibly through Masumi. Dem present these ones as work in progress and proposed experiment respectively.

Hackathon onboarding provide one concrete application for di existing package. For one planned 36-hour event for Singapore, one participant describe say instead of to assemble long resource list for every team, dem go give developers Cardano Dev Skills with few starting prompts.

For that workflow, team fit begin with transaction, validator, or token standard inside im coding agent. Di relevant task instructions and technical references go dey available for di same environment, and any problem wey dem discover during implementation fit be reported through di package feedback process.