Add new explain-cards for Artificial Intelligence, BNB Chain, ERC Standards, ERC721, ERC1155, Solidity, and Upgradeable Smart Contracts. Introduce show-card for DeGov.AI and OpenZeppelin with comprehensive details on features, technology, and use cases. Ensure adherence to updated content structure and guidelines.

Author: boundless-forest

.cursor/rules/awesome-card.mdc

@@ -7,44 +7,42 @@ alwaysApply: false
 
 This rule defines the required content structure for an "awesome-card" in the Web3 Wiki, which curates a list of valuable resources related to a specific topic.
 
-## Content Structure
-
-```markdown
-#awesome-card
-
-## Introduction
-- **Topic Focus:** Clearly state the specific topic this list covers (e.g., Awesome [[Zero-Knowledge Proofs]], Awesome [[Solidity]] Resources).
-- **Purpose:** Explain *why* this curated list is useful (e.g., for developers learning X, for users exploring Y tools).
-- **Scope:** Briefly define what kind of resources are included and excluded.
-
-## Official Resources
-- **Primary Website:** [Project/Concept Name Official Website Link] - Link to the main landing page.
-- **Documentation:** [Link to Official Docs] - Describe what the documentation covers (e.g., API reference, getting started guide).
-- **Whitepaper/Specifications:** [Link to Paper/Spec] - Briefly mention the core topic of the paper.
-
-## Learning Materials
-- **Tutorials:** [Link to Tutorial] - Specify skill level (beginner, intermediate, advanced) and format (text, video).
-- **Courses:** [Link to Course] - Mention provider (e.g., Coursera, Udemy) and key learning outcomes.
-- **Books:** [Book Title] by [Author] ([Link to buy/info]) - Add publication year and target audience.
-- **Workshops/Guides:** [Link to Resource] - Describe the format and focus.
-
-## Development Tools
-- **SDKs/Libraries:** [Tool Name] ([Link to Repo/Docs]) - Specify language/platform and primary function.
-- **Frameworks:** [Framework Name] ([Link]) - Mention the problem it solves or its main use case.
-- **Testing Tools:** [Tool Name] ([Link]) - Describe the type of testing it facilitates.
-- **IDEs/Plugins:** [Tool Name] ([Link]) - Specify the IDE it integrates with.
-
-## Ecosystem & Community
-- **Key Projects/Implementations:** [[Project Card Name]] or [Project Name] ([Link]) - Link relevant `show-card`s or official project sites.
-- **Explorers:** [Explorer Name] ([Link]) - e.g., Etherscan, Solscan.
-- **Forums/Discussion:** [Link to Forum/Platform] - Mention primary focus (e.g., technical support, general discussion).
-- **Social Channels:** [Link to Discord/Twitter/etc.] - Specify the channel type.
-
-## Further Resources (Optional)
-- **Blogs/Articles:** [Link to Article/Blog] - Mention author/publication and key topic.
-- **Newsletters:** [Newsletter Name] ([Link to Subscribe]) - Describe frequency and content focus.
-- **Podcasts/Videos:** [Podcast/Channel Name] ([Link]) - Mention key hosts or topics covered.
-```
+## Key Content Considerations
+
+When creating or updating an `awesome-card`, ensure the following categories of resources are considered. The AI assistant should generate a logical content outline based on these key resource categories and the specific topic of the awesome list.
+
+**1. Introduction:**
+    - Topic Focus: Clearly state the specific topic (e.g., Awesome [[Zero-Knowledge Proofs]], Awesome [[Solidity]] Resources).
+    - Purpose: Why this curated list is useful.
+    - Scope: What kind of resources are included/excluded.
+
+**2. Official Resources:**
+    - Primary Website: Link to main landing page.
+    - Documentation: Link to official docs (describe coverage).
+    - Whitepaper/Specifications: Link to paper/spec (mention core topic).
+
+**3. Learning Materials:**
+    - Tutorials: Links with skill level and format.
+    - Courses: Links with provider and key learning outcomes.
+    - Books: Titles, authors, links (publication year, target audience).
+    - Workshops/Guides: Links with format and focus.
+
+**4. Development Tools (if applicable to the topic):**
+    - SDKs/Libraries: Names, links (language/platform, function).
+    - Frameworks: Names, links (problem solved/use case).
+    - Testing Tools: Names, links (type of testing).
+    - IDEs/Plugins: Names, links (IDE integration).
+
+**5. Ecosystem & Community:**
+    - Key Projects/Implementations: Links to `[[Project Card Name]]` or official sites.
+    - Explorers: Names, links (e.g., Etherscan, Solscan).
+    - Forums/Discussion: Links with primary focus.
+    - Social Channels: Links with channel type (Discord, Twitter, etc.).
+
+**6. Further Resources (Optional):**
+    - Blogs/Articles: Links with author/publication and key topic.
+    - Newsletters: Names, links (frequency, content focus).
+    - Podcasts/Videos: Names, links (key hosts/topics covered).
 
 ## General Guidelines Adherence
 

.cursor/rules/explain-card.mdc

@@ -7,38 +7,33 @@ alwaysApply: false
 
 This rule defines the required content structure for an "explain-card" in the Web3 Wiki.
 
-## Content Structure
-
-```markdown
-#explain-card
-
-## Introduction
-
-- **What it is:** Start with a clear, concise definition of the concept, at least 2 sentences. It would be longer if it's a complex concept.
-- **Analogy (Optional):** Use a simple analogy if it helps clarify the concept for beginners.
-- **Importance/Purpose:** Explain *why* this concept exists and why it's significant, especially within the Web3 context.
-- **Target Audience:** Briefly mention who this concept is most relevant to (e.g., developers, users, investors).
-
-## Core Concepts
-
-- **Key Components:** Break down the concept into its essential parts or elements. Explain each part clearly and deeply.
-- **Mechanism/How it Works:** Describe the process or workflow involved. Use diagrams or flowcharts if helpful (describe them in text).
-- **Technical Details:** Include relevant technical specifications, protocols, or algorithms. Explain technical details in a way that is easy to understand. 
-- **Variations/Types (If applicable):** Mention different types or implementations of the concept if they exist (e.g., different types of consensus mechanisms for "Proof of Stake").
-
-## Use Cases
-
-- **Specific Examples:** Provide concrete examples of how this concept is used in real-world Web3 projects or scenarios. Link to relevant `show-card`s if available (e.g., [[Uniswap]] as an example of a DEX).
-- **Benefits:** Detail the advantages or positive outcomes of using this concept.
-- **Limitations/Challenges:** Discuss the drawbacks, risks, or challenges associated with the concept.
-- **Comparison (Optional):** Briefly compare it to alternative concepts or traditional (Web 2.0) approaches if relevant.
-
-## Related Concepts (Optional)
-- **Prerequisites:** List any concepts the reader should understand before this one (e.g., [[Blockchain]] might be a prerequisite for [[Smart Contract]]).
-- **Building Blocks:** Link to concepts that are components of this one.
-- **Related Ideas:** Link to concepts that are similar, contrasting, or often discussed together.
-- **Further Reading:** Link to more advanced concepts that build upon this one.
-```
+## Key Content Considerations
+
+When creating or updating an `explain-card`, ensure the following aspects are covered. The AI assistant should generate a logical content outline based on these key elements and the specific nature of the concept being explained.
+
+**1. Introduction:**
+    - Clear and concise definition of the concept (at least 2 sentences, longer if complex).
+    - Analogy (optional, to clarify for beginners).
+    - Importance/Purpose: Why the concept exists and its significance in Web3.
+    - Target Audience (e.g., developers, users, investors).
+
+**2. Core Concepts & Mechanism:**
+    - Key Components: Essential parts or elements, explained clearly and deeply.
+    - Mechanism/How it Works: The process or workflow involved (diagrams can be described in text).
+    - Technical Details: Relevant specifications, protocols, or algorithms, explained accessibly.
+    - Variations/Types (if applicable): Different implementations or types of the concept.
+
+**3. Use Cases & Implications:**
+    - Specific Examples: Real-world Web3 project examples (link to `show-card`s if available).
+    - Benefits: Advantages or positive outcomes.
+    - Limitations/Challenges: Drawbacks, risks, or difficulties.
+    - Comparison (optional): To alternative concepts or Web 2.0 approaches.
+
+**4. Related Concepts (Optional but Recommended):**
+    - Prerequisites: Concepts to understand first.
+    - Building Blocks: Component concepts.
+    - Related Ideas: Similar, contrasting, or co-discussed concepts.
+    - Further Reading: Advanced concepts building upon this one.
 
 ## General Guidelines Adherence
 

.cursor/rules/show-card.mdc

@@ -7,47 +7,42 @@ alwaysApply: false
 
 This rule defines the required content structure for a "show-card" in the Web3 Wiki, used to showcase a particular project, tool, or service.
 
-## Content Structure
-
-```markdown
-#show-card
-
-## Overview
-- **What it is:** A concise summary of the project, tool, or service (1-2 sentences).
-- **Problem Solved:** Clearly articulate the problem this project addresses in the Web3 space.
-- **Value Proposition:** What is the unique benefit or advantage it offers?
-- **Official Website:** [Link to Official Website]
-- **Status:** (e.g., Live, Beta, In Development) - Mention key dates if available (e.g., launch date).
-
-## Key Features
-- List the main functionalities or capabilities. Use **bold** for the feature name.
-- **Feature 1:** Brief explanation of what it does and its benefit.
-- **Feature 2:** Brief explanation.
-- **Feature 3:** ... (Use paragraphs for more complex features if needed).
-
-## Technology
-- **Blockchain/Platform:** Specify the primary blockchain(s) it runs on or integrates with (e.g., [[Ethereum]], [[Solana]], Standalone).
-- **Architecture:** Briefly describe the high-level technical design or components.
-- **Core Mechanism:** Explain the key technical innovation or process if applicable (e.g., consensus method, scaling solution).
-- **Smart Contracts:** [Link to relevant contracts on explorer] (Optional) - Mention key audited contracts if applicable.
-
-## Ecosystem & Use Cases
-- **Target Audience:** Who are the primary users? (e.g., Developers, DeFi Traders, NFT Collectors).
-- **How it's Used:** Provide specific examples of how people interact with the project.
-- **Integrations:** Mention notable projects or platforms it integrates with.
-- **Tokenomics (If applicable):** Briefly describe the native token's utility, supply, and distribution model. Link to [[Token Name]] card if it exists.
-
-## Getting Started & Resources
-- **Accessing:** How does a user start using it? (e.g., Web app link, download link, API key signup).
-- **Documentation:** [Link to Official Documentation]
-- **Community:** [Link to Discord/Telegram/Forum]
-- **Support:** [Link to Support Channel/FAQ]
-- **Source Code:** [Link to GitHub/GitLab Repo] (If open source).
-
-## Related Concepts
-- Link to relevant `explain-card`s for underlying technologies or concepts (e.g., Built using [[Optimistic Rollups]], Implements [[Decentralized Identity]]).
-- Link to relevant `awesome-card`s (e.g., See [[Awesome DeFi Tools]]).
-```
+## Key Content Considerations
+
+When creating or updating a `show-card`, ensure the following aspects are covered. The AI assistant should generate a logical content outline based on these key elements and the specific nature of the project/tool/service being showcased.
+
+**1. Overview:**
+    - Concise summary of the project/tool/service (1-2 sentences).
+    - Problem Solved: The issue it addresses in Web3.
+    - Value Proposition: Its unique benefit or advantage.
+    - Official Website: Link to the official site.
+    - Status (e.g., Live, Beta, In Development, key dates).
+
+**2. Key Features:**
+    - Main functionalities or capabilities, with brief explanations of each and their benefits.
+
+**3. Technology:**
+    - Blockchain/Platform (e.g., [[Ethereum]], [[Solana]], Standalone).
+    - Architecture: High-level technical design/components.
+    - Core Mechanism: Key technical innovation or process.
+    - Smart Contracts: Links to relevant contracts (optional, mention audited contracts).
+
+**4. Ecosystem & Use Cases:**
+    - Target Audience (e.g., Developers, DeFi Traders, NFT Collectors).
+    - How it's Used: Specific examples of interaction.
+    - Integrations: Notable projects/platforms it integrates with.
+    - Tokenomics (if applicable): Native token's utility, supply, distribution (link to `[[Token Name]]` card).
+
+**5. Getting Started & Resources:**
+    - Accessing: How to start using it (e.g., web app, download, API signup).
+    - Documentation: Link to official documentation.
+    - Community: Link to Discord/Telegram/Forum.
+    - Support: Link to support channel/FAQ.
+    - Source Code: Link to GitHub/GitLab (if open source).
+
+**6. Related Concepts:**
+    - Links to relevant `explain-card`s (underlying technologies, e.g., Built using [[Optimistic Rollups]]).
+    - Links to relevant `awesome-card`s (e.g., See [[Awesome DeFi Tools]]).
 
 ## General Guidelines Adherence
 

.cursor/rules/wiki-guide.mdc

@@ -29,9 +29,9 @@ Each card must belong to one of the following three categories:
 - **Mandatory Category Tag:**
     - The very first line of every card file _must_ be the tag corresponding to its category (e.g., `#explain-card`, `#show-card`, `#awesome-card`), with **no preceding blank lines or content**. This is further detailed in the specific card type rule files.
 - **File Location:**
-    - All new card markdown files **MUST** be created **directly within the `cards` directory** (e.g., `cards/My New Card.md`).
+    - All new card markdown files **MUST** be created **directly within the `cards` directory** (e.g., `cards/My New Card.md`). **This is a strict requirement.**
     - No subdirectories within `cards` should be used for card storage unless explicitly specified in a future rule update.
-    - The AI assistant **MUST NOT** create card files in any other directory (e.g., the workspace root, `.cursor/rules/`, etc.). **Verify the creation path.**
+    - The AI assistant **MUST NOT** create card files in any other directory (e.g., the workspace root, `.cursor/rules/`, etc.). **Verify the creation path rigorously.**
 
 ## Card Content Rules
 
@@ -49,7 +49,12 @@ These guidelines apply to all cards and content within the wiki.
     -   Links **must** point to existing card files (case-sensitive filename, `.md` implied) located **directly within the `cards` directory**.
     -   **Verification is mandatory:** Before adding an internal link, confirm the target file exists (use `list_dir` or `file_search`).
     -   **No Broken Links:** Broken internal links are strictly forbidden.
-    -   **Handling Missing Targets:** If a potentially useful link target doesn't exist, either create the card first (following all rules) or omit the link.
+    -   **Handling Missing Targets:** If a potentially useful link target doesn't exist, the AI assistant **MUST**:
+        1.  Determine the most appropriate card category for the new concept (e.g., `#explain-card`, `#show-card`).
+        2.  Create the new card file (e.g., `cards/New Concept.md`) **directly within the `cards` directory**, adhering to all naming conventions (uppercase first letter, appropriate filename).
+        3.  Add the chosen category tag as the very first line of the new card file.
+        4.  Generate initial, relevant content for this new card based on its chosen category, the context of the link, and available knowledge. The goal is to create a useful stub, not just an empty file. Refer to the specific card type rules for content guidance.
+        5.  If creating a populated stub is not feasible or the concept is too broad/unknown, the link should be omitted. **Do not create empty or near-empty files.**
 -   **External Links (`[Text](mdc:URL)`):**
     -   Prioritize links to **official websites, documentation, or primary sources**, especially for projects, tools, and resources.
     -   Use **descriptive link text** (e.g., `[Official Ethereum Website]`) instead of generic terms like "here" or "link".
@@ -80,10 +85,10 @@ As an AI assistant, your role is to proactively maintain and improve the Web3 Wi
 4.  **Implement Changes:** Propose and apply specific, constructive changes to address identified issues, clearly stating the intent. Use web search and fetching tools to gather up-to-date information for content revisions.
 5.  **Link Management:**
     -   Actively create relevant internal links, ensuring they are valid by **verifying target file existence first**.
-    -   When a target is missing, follow the `Handling Missing Targets` rule (create card or omit link).
+    -   When a target is missing, follow the updated `Handling Missing Targets` rule (i.e., determine category, create the card file **in the `cards` directory with initial content**, or omit the link).
     -   Ensure external links adhere to the `Linking Standards`, using web search/fetch for verification.
 6.  **Card Creation:**
-    -   When creating new cards (e.g., to fulfill a missing link), ensure they are created **directly within the `cards` directory**.
-    -   Strictly adhere to all `Card Naming and Format` rules (uppercase first letter, category tag on the first line) and the specific content structure for the chosen card type.
+    -   When creating new cards (e.g., to fulfill a missing link as per `Handling Missing Targets`, or by direct user request), ensure they are created **directly and exclusively within the `cards` directory**. This path (`cards/FILENAME.md`) is non-negotiable.
+    -   Strictly adhere to all `Card Naming and Format` rules (uppercase first letter, descriptive name, category tag on the first line) and generate meaningful initial content according to the specific content considerations for the chosen card type.
 7.  **Exception - Main Page:** The card `Web3 Wiki.md` serves as the main page of the wiki. The AI assistant **MUST NOT** modify the content of this card. It is maintained manually.
 

cards/Artificial Intelligence.md

@@ -0,0 +1,3 @@
+#explain-card
+
+Artificial Intelligence (AI) refers to the simulation of human intelligence in machines that are programmed to think like humans and mimic their actions.

cards/BNB Chain.md

@@ -0,0 +1,3 @@
+#explain-card
+
+BNB Chain is a blockchain platform developed by Binance, known for its high performance and low transaction fees.