Add an open-link button to skill cards and retire generic Soroban wording - #94
Conversation
The pill hands you the markdown URL but there was no way to just look at the file. Skill cards now carry an anchor to the same URL the pill copies. Ecosystem cards are left alone: their copy value is already the URL the card header links to, so a second chip would point at one destination twice.
The platform name is retired, and smart-contracts/SKILL.md already says so. This applies the same wording to the places that still described generic contracts, transactions, and tokens as Soroban ones. Proper nouns stay: soroban-sdk, SorobanArbitrary, the SEP-41/CAP-46 titles, project names like Scout Soroban, and the frontmatter descriptions that keep Soroban as a trigger word for people who still call it that. Also fixes the site README, which showed a category value that is no longer in FilterType.
|
There was a problem hiding this comment.
Pull request overview
Adds direct markdown links to first-party skill cards and modernizes generic Soroban terminology.
Changes:
- Adds an accessible new-tab link beside each first-party skill copy button.
- Replaces generic Soroban wording with Stellar smart contract terminology.
- Corrects the documented skill category example.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
skills/standards/SKILL.md |
Updates K2 terminology. |
skills/smart-contracts/development.md |
Modernizes transaction terminology. |
skills/dapp/SKILL.md |
Updates contract invocation wording. |
skills/cross-chain/SKILL.md |
Modernizes cross-chain contract terminology. |
skills/cross-chain/cctp.md |
Updates CCTP contract and transaction wording. |
skills/cross-chain/axelar.md |
Updates Axelar contract and token terminology. |
site/src/app/styles.scss |
Styles the copy-and-open control row. |
site/src/app/_components/SkillCard.tsx |
Adds the first-party markdown open-link button. |
site/README.md |
Corrects the FilterType category example. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🤖 Automated message from Kaan's Automated Triage Bot. Picked this up — assessing whether I can ship an airtight fix. |
|
🤖 Automated message from Kaan's Automated Triage Bot. Merged. The verification this PR deferred is now in: the preview workflow ran I also checked the two things worth checking by hand: the chip's |
🤖 Automated message from Kaan's Automated Triage Bot.
Refs #27 (deliberately not "Closes" — this picks off two items from James's list, the rest are editorial calls I'd rather leave to a human).
The first commit adds the open-link button he asked for: each skill card's copy pill now has an anchor beside it pointing at the same markdown URL,
target="_blank". Ecosystem cards don't get one, because their copy value is already the URL the card header links to and a second chip would send you to the same place twice. One caveat worth knowing before merge: GitHub Pages serves those files astext/markdown, so whether a browser renders the file inline or offers a download is up to the browser, and the site can't set response headers to influence that.The second commit is the "Soroban" pass. Generic prose about Soroban contracts, transactions, and tokens now says Stellar smart contracts, matching what
smart-contracts/SKILL.mdalready states about the retired platform name. Proper nouns stay put:soroban-sdk,SorobanArbitrary, the SEP-41 and CAP-46 titles, project names like Scout Soroban and Soroban Playground, and the frontmatter descriptions that keep "Soroban" as a trigger word for users who still call it that. Stellar's own docs still use the name in those senses, so a blanket rename would have made things less accurate, not more. The site README also documentedcategory: "Soroban", which isn't aFilterTypevalue any more and would failtscif anyone copied it.Note on verification: I could not run
pnpm lint,lint:ts, orbuildin my sandbox (no pnpm available), so I'm relying on the preview workflow to check them. Please don't merge until it's green, and the preview URL is the fastest way to eyeball the new chip.