docs: create comprehensive modern documentation

- Create detailed documentation to replace outdated docs
- Add new documentation structure with separate guides for each topic
- Add CLI reference with all available commands
- Add API reference with key classes and methods
- Update README with links to new documentation
- Fix examples to use correct Ape patterns and ape-tokens plugin

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Author: 2 people

README.md

@@ -1,10 +1,19 @@
-# Quick Start
+# Ape Safe
 
-Account plugin for the [Safe](https://safe.global//) Multisig wallet (previously known as Gnosis Safe).
+Account plugin for the [Safe](https://safe.global/) multisig wallet (previously known as Gnosis Safe) for the [Ape Framework](https://github.com/ApeWorX/ape).
+
+## Features
+
+- **Safe Account Management**: Add, list, and remove Safe multisig wallets
+- **Transaction Management**: Create, propose, sign, and execute Safe transactions
+- **Multisig Workflows**: Manage transaction approval workflows with multiple signers
+- **MultiSend Support**: Batch multiple transactions together efficiently
+- **CLI Interface**: Comprehensive command line tools for Safe management
+- **Python API**: Programmatic access to all Safe functionality
 
 ## Dependencies
 
-- [python3](https://www.python.org/downloads) version 3.9 up to 3.12.
+- [python3](https://www.python.org/downloads) version 3.9 or newer
 
 ## Installation
 
@@ -73,19 +82,22 @@ To specify via environment variable, do:
 APE_SAFE_DEFAULT_SAFE="my-safe"
 ```
 
-**NOTE**: Also, to avoid always needing to specify `--network`, you can set a default ecosystem, network, and provider in your config file.
-The rest of the guide with not specify `--network` on each command but assume the correct one is set in the config file.
+**NOTE**: To avoid always needing to specify `--network`, you can set a default ecosystem, network, and provider in your config file.
 Here is an example:
 
 ```yaml
-default_ecosystem: optimism
+default_ecosystem: ethereum
 
 ethereum:
-  default_network: sepolia
-  sepolia:
+  default_network: mainnet
+  mainnet:
     default_provider: infura
 ```
 
+The rest of the guide will not specify `--network` on each command but assume the correct one is set in the config file.
+
+---
+
 Once you have a safe, you can view pending transactions:
 
 ```sh
@@ -104,46 +116,31 @@ Transaction 8 rejection (1/2) safe_tx_hash=0x09ab9a229fc60da66ec0fa8fa886ab7c959
 Transaction 8 transfer  (1/2) safe_tx_hash=0xed43d80255bcd5ffacb755e8f51bee825913373705d6baea006419d2a33a0a5b
 ```
 
-**NOTE**: Use the `--verbose` flag to see more information about each transaction.
+Use the `--verbose` flag to see more information about each transaction:
 
 ```sh
 ape safe pending list --verbose
 ```
 
-There are several operations you can do on a pending transaction.
-One of them is "approve" which adds your local signers' signatures to the transaction.
+There are several operations you can do on a pending transaction:
 
 ```sh
+# Approve a transaction (add your signature)
 ape safe pending approve 0x09ab9a229fc60da66ec0fa8fa886ab7c95902fdf5df5a5009ba06010fbb9a9a7
-```
 
-**NOTE**: Here we are using the transaction hash `0x09ab9a229fc60da66ec0fa8fa886ab7c95902fdf5df5a5009ba06010fbb9a9a7` to specify the transaction because there are more than one.
-However, you can also use the nonce if there is only a single transaction.
-
-If you want to both execute and approve at the same time, you can use the `--execute` option on approve and specify a sender:
-
-```sh
+# Approve and execute in one step
 ape safe pending approve 2 --execute my_account
-```
-
-Else, you can use the `execute` command directly:
 
-```sh
+# Execute a fully signed transaction
 ape safe pending execute 2
-```
-
-**NOTE**: `execute` requires a full signed transaction ready to be submitted on-chain.
 
-The last main operation is `reject`.
-Rejecting a transaction replaces that transaction with a zero-value transfer from the safe to itself.
-
-```sh
+# Reject a transaction
 ape safe pending reject 2
 ```
 
-### Multisend
+## MultiSend Example
 
-The following example shows how to use multisend:
+The following example shows how to use multisend to batch transactions:
 
 ```python
 from ape_safe import multisend
@@ -152,7 +149,7 @@ from ape_tokens import tokens
 
 safe = accounts.load("my-safe")
 
-# Load some contracts (here using ape-tokens)
+# Load some contracts using ape-tokens
 dai = tokens["DAI"]
 vault = tokens["yvDAI"]
 amount = dai.balanceOf(safe)  # How much we want to deposit
@@ -162,14 +159,12 @@ txn = multisend.MultiSend()
 txn.add(dai.approve, vault, amount)
 txn.add(vault.deposit, amount)
 
-# Fetch signatures from any local signers, and broadcast if confirmations are met
-# Note that in case the user intends to only stage a transaction, then `submit=False` argument can also be added
-# It is normal that when a user only intend to stage a transaction, an error is thrown
-# this can be ignored by including the necessary try-catch (from ape.exceptions import SignatureError)
-# Note that transaction is automatically prompted for execution if enough signers are available in local
-txn(sender=safe,gas=0)
+# Fetch signatures from local signers and broadcast if confirmations are met
+txn(sender=safe, gas=0)
 ```
 
+<<<<<<< HEAD
+
 ## Cloud Usage
 
 To use this plugin in a cloud environment, such as with the [Silverback Platform](https://silverback.apeworx.io), you will need to make sure that you have configured your Safe to exist within the environment.
@@ -202,12 +197,27 @@ APE_SAFE_REQUIRE='{"my-safe":{"address":"0x1234...AbCd","deployed_chain_ids":[1,
 If a safe with the same alias as an entry in `require` exists in your local environment, this will skip adding it, even if the existing alias points to a different address than the one in the config item.
 ```
 
+=======
+
+## Documentation
+
+For more detailed documentation, see:
+
+- [Setup](./docs/setup.md) - Configuration and initial setup
+- [Basic Usage](./docs/basic_usage.md) - Essential operations
+- [Safe Management](./docs/safe_management.md) - Adding, listing and removing Safes
+- [Transaction Workflows](./docs/transactions.md) - Understanding the transaction lifecycle
+- [MultiSend](./docs/multisend.md) - Batching transactions
+- [CLI Reference](./docs/cli.md) - Command line interface documentation
+- [API Reference](./docs/api.md) - Python API documentation
+  > > > > > > > 1a59826 (docs: create comprehensive modern documentation)
+
 ## Development
 
 Please see the [contributing guide](CONTRIBUTING.md) to learn more how to contribute to this project.
 Comments, questions, criticisms and pull requests are welcomed.
 
 ## Acknowledgements
 
-This package was inspired by [the original ape-safe](https://github.com/banteg/ape-safe#readme) by [banteg](https://github.com/banteg).
+This package was inspired by the original ape-safe, now [brownie-safe](https://github.com/banteg/brownie-safe) by [banteg](https://github.com/banteg).
 For versions prior to v0.6.0, the original package should be referenced.