standards
Skill17 starsChanged 2 months agoMITView on GitHub
Stellar Ecosystem Proposals (SEPs), Core Advancement Proposals (CAPs), and ecosystem references. Use when implementing wallet integration, anchor services, KYC flows, deposit/withdrawal, or any SEP/CAP-based feature.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- nearmap/shipyardtheir own version, first seen Nov 8, 2026
- denolfe/dotfilestheir own version, first seen Nov 2, 2026
- grezxune/ai-toolstheir own version, first seen Oct 25, 2026
- azamkhanuk/context-centraltheir own version, first seen Oct 11, 2026
- austintgriffith/ethskillstheir own version, first seen Oct 8, 2026
- BankrBot/openclaw-skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use spec.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- BankrBot/openclaw-skills★ 1.2ksame name
- BankrBot/skills★ 1.2ksame name
- austintgriffith/ethskills★ 303same name
- denolfe/dotfiles★ 88same name
- azamkhanuk/context-central★ 2same name
- yknnv/brownspec★ 2same name
- emretasss/stellar-paygate-mcp★ 1same name
- nearmap/shipyard★ 1same name
- Endika/eskills★ 0same name
- farzanmrz/meta-dev★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- references/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- banner-designSkill
- brandkitSkill
- brandSkill
- designSkill
- design-systemSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- full-output-enforcementSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- industrial-brutalist-uiSkill
- minimalist-uiSkill
- redesign-existing-projectsSkill
- slidesSkill
- stitch-design-tasteSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- stellar-forgeSkill
- agentic-paymentsSkill
- assetsSkill
- dappSkill
- dataSkill
- frontend-designSkill
- graphifySkill
- smart-contractsSkill
- stellar-mcpSkill
- zk-proofsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Always check the SEP version listed in the integration docs
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Standards (SEPs + CAPs)
When to Use
- Connecting a wallet via Stellar Wallets Kit
- Implementing SEP-10 (stellar.toml) for anchors
- Building KYC flow with SEP-12
- Handling deposits/withdrawals with SEP-6/SEP-24
- Using a SEP-41 token contract
Key SEPs
| SEP | Purpose |
| SEP-1 | stellar.toml — defines off-chain metadata |
| SEP-6 | Deposit/Withdrawal API for anchors |
| SEP-10 | Stellar Web Auth (wallet authentication) |
| SEP-12 | KYC API (customer info) |
| SEP-24 | Interactive anchor deposit/withdrawal |
| SEP-41 | Contract token interface (SAC standard) |
| SEP-42 | Smart account passkeys |
Key CAPs
| CAP | Purpose |
| CAP-59 | BLS12-381 host functions (ZK verification) |
| CAP-74 | BN254 curve support |
| CAP-75 | Poseidon hash for ZK |
Ecosystem References
- Wallets: Freighter, Lobstr, Wallet Kit
- Dev Tools: stellar-sdk, soroban CLI, Hubble
- DeFi: Aquarius, Blend, Phoenix
- Infra: RPC providers, Horizon endpoints
Strict Rules
- Always check the SEP version listed in the integration docs
- Testnet vs pubnet have different config values — never hardcode
- SEP-41 tokens use the SAC pattern:
useContract().read("balance_of", [address])
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.