feat: cursor rulefiles from docs

.cursor/rules/blockchain-interactions.mdc

@@ -0,0 +1,100 @@
+---
+description: Guide on how to interact with blockchains and smart contracts from WAVS components using Rust.
+globs: **/*.rs
+alwaysApply: true
+---
+# Blockchain Interactions in WAVS Components
+
+This document outlines the necessary steps and configurations for interacting with Ethereum and other EVM-compatible blockchains from WAVS components. It includes dependency setup, chain configuration, and examples of querying an NFT balance.
+
+## Dependencies
+
+To interact with Ethereum blockchains, include the following dependencies in your `Cargo.toml`:
+
+```toml
+[dependencies]
+wit-bindgen-rt = { workspace = true, features = ["bitflags"] }
+wavs-wasi-utils = "=0.4.0-beta.2"
+wstd = "0.5.3"
+alloy-sol-macro = { version = "1.1.0", features = ["json"] }
+alloy-sol-types = "1.1.0"
+alloy-network = "0.15.10"
+alloy-provider = { version = "0.15.10", default-features = false, features = ["rpc-api"] }
+alloy-rpc-types = "0.15.10"
+alloy-contract = "0.15.10"
+anyhow = "1.0.98"
+serde = { version = "1.0.219", features = ["derive"] }
+serde_json = "1.0.140"
+```
+
+## Chain Configuration
+
+Define chain configurations in `wavs.toml` to specify RPC endpoints and chain IDs:
+
+```toml
+[default.chains.evm.local]
+chain_id = "31337"
+ws_endpoint = "ws://localhost:8545"
+http_endpoint = "http://localhost:8545"
+poll_interval_ms = 7000
+
+[default.chains.evm.evmereum]
+chain_id = "1"
+ws_endpoint = "wss://eth.drpc.org"
+http_endpoint = "https://eth.drpc.org"
+```
+
+## Accessing Configuration and Provider
+
+Use WAVS host bindings to access chain configurations and create a provider for Ethereum interactions:
+
+```rust
+use crate::bindings::host::get_evm_chain_config;
+use alloy_network::Ethereum;
+use alloy_provider::RootProvider;
+use wavs_wasi_utils::evm::new_evm_provider;
+
+let chain_config = get_evm_chain_config("local")?;
+let provider: RootProvider<Ethereum> = new_evm_provider::<Ethereum>(
+    chain_config.http_endpoint.unwrap()
+)?;
+```
+
+## Example: Querying NFT Balance
+
+To query an ERC721 NFT contract for a given owner address:
+
+```rust
+use crate::bindings::host::get_evm_chain_config;
+use alloy_network::Ethereum;
+use alloy_provider::RootProvider;
+use alloy_sol_types::sol;
+use wavs_wasi_utils::evm::{
+    alloy_primitives::{Address, U256},
+    new_evm_provider,
+};
+use wstd::runtime::block_on;
+
+sol! {
+    interface IERC721 {
+        function balanceOf(address owner) external view returns (uint256);
+    }
+}
+
+pub fn query_nft_ownership(address: Address, nft_contract: Address) -> Result<bool, String> {
+    block_on(async move {
+        let chain_config = get_evm_chain_config("local").unwrap();
+        let provider: RootProvider<Ethereum> = new_evm_provider::<Ethereum>(
+            chain_config.http_endpoint.unwrap()
+        );
+        let contract = IERC721::new(nft_contract, &provider);
+        let balance = contract.balanceOf(address).call().await?;
+
+        Ok(balance > U256::ZERO)
+    })
+}
+```
+
+For more detailed information and additional resources:
+- [wavs-wasi-utils documentation](https://docs.rs/wavs-wasi-utils/latest/wavs_wasi_utils/)
+- [Alloy documentation](https://docs.rs/alloy/latest/alloy/)

.cursor/rules/commands.mdc

@@ -0,0 +1,19 @@
+---
+description: CLI commands for WAVS development
+globs: **/Makefile
+alwaysApply: true
+---
+# Makefile Commands for WAVS Development
+
+This rule file provides the necessary command to access the help menu for WAVS development via the Makefile.
+
+To view all available commands for WAVS development, use the following command in your terminal:
+
+```bash
+make help
+```
+
+This command will display a list of all the commands available in the Makefile that are relevant to WAVS development. It's a quick way to get an overview of the tools and commands at your disposal for managing and developing the WAVS project.
+
+For more information:
+- No additional links provided.

.cursor/rules/component.mdc

@@ -0,0 +1,132 @@
+---
+description: Guide on creating and structuring components for WAVS service with examples in Rust.
+globs: **/*.rs
+alwaysApply: true
+---
+# Component Overview for WAVS Service
+
+Service components are crucial for the WAVS service, encapsulating the main business logic and interacting with the WAVS runtime through WebAssembly (WASM) bytecode. This guide covers the languages, structure, and examples for creating components.
+
+## Component Languages
+
+WAVS supports multiple programming languages for component development, compiled to WASM for execution. Examples primarily use Rust, with additional samples in Go and JavaScript.
+
+- [Go example](link)
+- [JavaScript example](link)
+
+## Component Structure
+
+Components generally follow a three-part structure:
+
+1. Decode incoming trigger data.
+2. Process the data with custom business logic.
+3. Encode and return the result for submission, if applicable.
+
+### Trigger Inputs
+
+Components can receive trigger data either from on-chain events or local testing. The handling of these inputs varies as shown in the `trigger.rs` example:
+
+```rust
+// In trigger.rs
+
+pub fn decode_trigger_event(trigger_data: TriggerData) -> Result<(u64, Vec<u8>, Destination)> {
+    match trigger_data {
+        TriggerData::EvmContractEvent(TriggerDataEvmContractEvent { log, .. }) => {
+            let event: solidity::NewTrigger = decode_event_log_data!(log)?;
+            let trigger_info = solidity::TriggerInfo::abi_decode(&event._triggerInfo)?;
+            Ok((trigger_info.triggerId, trigger_info.data.to_vec(), Destination::Ethereum))
+        },
+        TriggerData::Raw(data) => Ok((0, data.clone(), Destination::CliOutput)),
+        _ => Err(anyhow::anyhow!("Unsupported trigger data type")),
+    }
+}
+```
+
+### Component Logic
+
+Implement the `Guest` trait for your component, with `run` as the entry point for your logic:
+
+```rust
+// In lib.rs
+impl Guest for Component {
+    fn run(action: TriggerAction) -> Result<Option<WasmResponse>, String> {
+        let (trigger_id, req, dest) = decode_trigger_event(action.data)?;
+
+        let res = block_on(async move {
+            let resp_data = get_price_feed(id).await?;
+            serde_json::to_vec(&resp_data)
+        })?;
+
+        let output = match dest {
+            Destination::Ethereum => Some(encode_trigger_output(trigger_id, &res)),
+            Destination::CliOutput => Some(WasmResponse { 
+                payload: res.into(), 
+                ordering: None 
+            }),
+        };
+        Ok(output)
+    }
+}
+```
+
+#### Logging
+
+For development, use `println!()` for debugging. In production, use `host::log()` for structured logging with context.
+
+```rust
+// Development logging
+println!("Debug message: {:?}", data);
+
+// Production logging
+host::log(LogLevel::Info, "Production logging message");
+```
+
+### Component Output
+
+Encode the output data for submission back to Ethereum using the `encode_trigger_output` function:
+
+```rust
+pub fn encode_trigger_output(trigger_id: u64, output: impl AsRef<[u8]>) -> WasmResponse {
+    WasmResponse {
+        payload: solidity::DataWithId {
+            triggerId: trigger_id,
+            data: output.as_ref().to_vec().into(),
+        }
+        .abi_encode(),
+        ordering: None,
+    }
+}
+```
+
+## Component Definition
+
+Define components in the `service.json` file within the workflow object:
+
+```json
+{
+  "component": {
+    "source": {
+      "Digest": "65747b4b1a7fa98cab6abd9a81a6102068de77b1040b94de904112272b226f51"
+    },
+    "permissions": {
+      "allowed_http_hosts": "all",
+      "file_system": true
+    },
+    "fuel_limit": null,
+    "time_limit_seconds": 1800,
+    "config": {
+      "Variable_1": "0xb5d4D4a87Cb07f33b5FAd6736D8F1EE7D255d9E9",
+      "variable_2": "0x34045B4b0cdfADf87B840bCF544161168c8ab85A"
+    },
+    "env_keys": [
+      "WAVS_ENV_API_KEY"
+    ]
+  }
+}
+```
+
+For detailed information on component configuration and keys, refer to the [variables page](./variables).
+
+For more information:
+- [WAVS WASI Utils Crate Documentation](https://docs.rs/wavs-wasi-utils/latest/wavs_wasi_utils/macro.decode_event_log_data.html)
+- [Utilities and Crates Documentation](./utilities#sol-macro)

.cursor/rules/cursor-rules.mdc

@@ -0,0 +1,70 @@
+---
+description: 
+globs: 
+alwaysApply: false
+---
+---
+description: How to add or edit Cursor rules in our project
+globs: 
+alwaysApply: false
+---
+# Cursor Rules Location
+
+How to add new cursor rules to the project
+
+1. Always place rule files in PROJECT_ROOT/.cursor/rules/:
+    ```
+    .cursor/rules/
+    ├── your-rule-name.mdc
+    ├── another-rule.mdc
+    └── ...
+    ```
+
+2. Follow the naming convention:
+    - Use kebab-case for filenames
+    - Always use .mdc extension
+    - Make names descriptive of the rule's purpose
+
+3. Directory structure:
+    ```
+    PROJECT_ROOT/
+    ├── .cursor/
+    │   └── rules/
+    │       ├── your-rule-name.mdc
+    │       └── ...
+    └── ...
+    ```
+
+4. Never place rule files:
+    - In the project root
+    - In subdirectories outside .cursor/rules
+    - In any other location
+
+5. Cursor rules have the following structure:
+
+```
+---
+description: Short description of the rule's purpose
+globs: optional/path/pattern/**/*
+alwaysApply: false
+---
+# Rule Title
+
+Main content explaining the rule with markdown formatting.
+
+1. Step-by-step instructions
+2. Code examples
+3. Guidelines
+
+Example:
+```typescript
+// Good example
+function goodExample() {
+  // Implementation following guidelines
+}
+
+// Bad example
+function badExample() {
+  // Implementation not following guidelines
+}
+```