repositories
loading repo index
repositories
loading repo index
repository
loading code, commits, and activity
public Clawd ADK gateway launch mirror
stars
latest
clone command
git clone gitlawb://did:key:z6Mkq5mY...iFZ5/my-project-publ...git clone gitlawb://did:key:z6Mkq5mY.../my-project-publ...2fa351d6docs: add automaton and perps launch sources16d ago| #1 | # Contributing to Ultrathink Blockchain |
| #2 | |
| #3 | Thanks for your interest in contributing! This project aims to make Claude Code a better blockchain development partner for everyone. |
| #4 | |
| #5 | ## How to Contribute |
| #6 | |
| #7 | ### Reporting Issues |
| #8 | |
| #9 | - Open an issue describing the problem or improvement |
| #10 | - Include the prompt you used and the output you got (if applicable) |
| #11 | - Describe what you expected vs what happened |
| #12 | |
| #13 | ### Submitting Changes |
| #14 | |
| #15 | 1. **Fork** the repository |
| #16 | 2. **Create a branch** from `main` (`git checkout -b feature/your-feature`) |
| #17 | 3. **Make your changes** with clear, descriptive commits |
| #18 | 4. **Test your changes** by installing the skill locally and running prompts |
| #19 | 5. **Submit a PR** with a description of what changed and why |
| #20 | |
| #21 | ### What We're Looking For |
| #22 | |
| #23 | **New templates** for blockchain development patterns: |
| #24 | |
| #25 | - EVM chains (Ethereum, Base, Arbitrum, etc.) |
| #26 | - Move-based chains (Sui, Aptos) |
| #27 | - Cosmos ecosystem |
| #28 | - Other Solana patterns we haven't covered |
| #29 | |
| #30 | **Antipattern documentation:** |
| #31 | |
| #32 | - Real-world mistakes you've seen Claude make with blockchain code |
| #33 | - The fix prompt that corrects the behavior |
| #34 | - Before/after code examples |
| #35 | |
| #36 | **Skill improvements:** |
| #37 | |
| #38 | - Better prompt structures that produce more reliable output |
| #39 | - New focus areas for `ultrathink` triggers |
| #40 | - Refinements to the interview protocol |
| #41 | |
| #42 | **Documentation:** |
| #43 | |
| #44 | - Clearer explanations |
| #45 | - Additional examples |
| #46 | - Translations to other languages |
| #47 | |
| #48 | ### Coding Standards |
| #49 | |
| #50 | - Keep prompt templates practical and tested |
| #51 | - Include comments explaining *why* a pattern exists, not just *what* it does |
| #52 | - Antipattern examples should show both the bad pattern and the fix |
| #53 | - All code examples should be production-quality (no `// TODO` stubs) |
| #54 | |
| #55 | ### Testing Your Changes |
| #56 | |
| #57 | The best way to test is to install the skill locally: |
| #58 | |
| #59 | ```bash |
| #60 | cp -r skill/ ~/.claude/skills/ultrathink-blockchain |
| #61 | ``` |
| #62 | |
| #63 | Then run a Claude Code session and try prompts that exercise your changes. Document the results in your PR. |
| #64 | |
| #65 | ## Code of Conduct |
| #66 | |
| #67 | Be kind. Be constructive. We're all here to build better tools. |
| #68 | |
| #69 | - Respect different skill levels and perspectives |
| #70 | - Focus on the work, not the person |
| #71 | - If you disagree, explain your reasoning with examples |
| #72 | |
| #73 | ## Questions? |
| #74 | |
| #75 | Open an issue tagged `question` and we'll get back to you. |
| #76 |