Skip to content
cccskills
FreePublished on GitHub

starknet-react-rules

Specific rules for Starknet React projects, focusing on blockchain integration.

The English summary is being prepared. Showing the original description.

See how to install

Files included (10)

  • SKILL.md3.7 KB
  • commands/starknet-react-rules.md120 B
  • hooks/post-execute.cjs318 B
  • hooks/pre-execute.cjs435 B
  • references/research-requirements.md370 B
  • rules/starknet-react-rules.md318 B
  • schemas/input.schema.json554 B
  • schemas/output.schema.json264 B
  • scripts/main.cjs1.1 KB
  • templates/implementation-template.md194 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Starknet React Rules Skill

<identity> You are a coding standards expert specializing in starknet react rules. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines:
  • Centralize blockchain connection management
  • Implement automatic reconnection and error handling
  • Use React hooks for transaction status management
  • Provide clear UI feedback for blockchain interactions
  • Implement comprehensive error handling for blockchain operations </instructions>
<examples> Example usage: ``` User: "Review this code for starknet react rules compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples>

Iron Laws

  1. NEVER interact with Starknet contracts without validating the connected wallet and chain ID
  2. ALWAYS handle transaction pending, confirmed, and rejected states explicitly
  3. NEVER hardcode contract addresses — always use environment variables or config files
  4. ALWAYS use TypeScript types generated from ABI for contract interactions
  5. NEVER skip error handling for wallet connection failures and transaction reverts

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Skipping chain ID validationWallet connected to wrong network silently corrupts transactionsAlways validate chainId matches expected Starknet network
Hardcoding contract addressesBreaking changes when deploying to different environmentsUse environment variables or config files for all contract addresses
Missing transaction state handlingUsers see blank UI during pending/rejected statesImplement loading, confirmed, and rejected state for all transactions
Direct ABI calls without TypeScript typesRuntime errors from wrong argument typesUse TypeScript types generated from ABI for all contract calls
Ignoring wallet connection errorsSilent failures create confusing UXAlways handle ConnectionError, UserRejectedRequestError, and RejectedRequestError

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Ensure accessibility in UI components including semantic HTML, ARIA attributes, keyboard navigation, and WCAG 2.2 AA compliance.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Use when you want to improve response quality through meta-cognitive reasoning. Applies 15+ reasoning methods to reconsider and refine initial outputs.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

N-round opposing-stance debates for trade-off analysis. Assigns pro/con roles to agents, runs structured debate rounds with quality scoring, and produces a moderator synthesis with confidence-rated recommendation. Generalizable to architecture, technology, security, and design decisions.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Force adversarial code review stance that eliminates confirmation bias — reviewer must find issues or re-analyze

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Creates specialized AI agents on-demand when no existing agent matches a request. Use when the Router cannot find a suitable agent for a task. Enables self-evolution by generating persistent agents.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

LLM-as-judge evaluation framework with 5-dimension rubric (accuracy, groundedness, coherence, completeness, helpfulness) for scoring AI-generated content quality with weighted composite scores and evidence citations

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

See all skills by oimiragieo

Report a problem with this skill