A bitcoin, officially named UTXO, is represented by an address of a unique coin amount. A transaction is simply a record where a set of inputs bitcoin is destroyed and a new set of outputs bitcoin is created. This is why some people identify the coins by the transaction id and the coin's output position id. It is convenient to define the coin ticker based on its recordability among the alive chains by the financial principle that the same ticker has the same price: BTC for coins only recorded in BTC chain, ABC for coins only recorded in ABC chain, BSV for coins only recorded in BSV chain, BCH for coins recorded in ABC and BSV chains, B for coins recorded in all alive chains. Each block chain may have its preferred ATM. For keys management, it is advised to have different Hierarchical Deterministic key for coins of different ticker because no one wants to mix up coins of different price. Obviously, the price of B is the highest and the mining power moving from ABC chain to BSV chain will have zero impact on BCH price.
For all chains
ScriptTxComposer is the TXs composer following the above doctrine which creates the TXs for the user so that he can copy the TXs back to his personal wallet to sign and broadcast the TXs.
ATM for BTC chain
This is a public domain open source java script implement about BTC wallet. It is concept-simple and less user operation error possibility.
The "wallet" tab is in fact a deterministic way to generate a private key based on your input about the email and password which is not necessary to be a true email and password (you can arbitrarily to fake an email and the password); it is just easier for a user to memorize an email and password than to memorize the private key directly. However, if you keep your private key safe, say, on a paper and input that private key in usage such as sign or new a transaction, this "wallet" tab is not necessary.
Being java script, it means you can operate it directly in the browser. Further, if you insist a high security for your private keys, you can download the whole source code from github mentioned in its page and inspect the source code line by line and signing on a standalone offline browser with no any private key info leaking possibility. After signing, then turn online and broadcast the signed transaction into the bitcoin network.
You can also use this tool to verify correspondent address or public key for an encoded private key; see here. But as mentioned, any private key info shall not be transmitted on the internet so you shall do this task in a local copy version of the tool.
ATM for ABC and BSV chains
Almost the same as the ATM for BTC chain above. Thanks to replay benefit between ABC and BSV chains, no need for separate ATM for ABC and BSV chains to craft a transaction. However, its default broadcast channel will deny the transaction if the inputs of the transaction is not valid in ABC chain. Therefore, BSV users need to broadcast the transaction via other BSV-friendly nodes such as blockchair.com.
Sadly, there is no replay benefit between BTC chain and other chains so a user may need to sign the same transaction two times, one in this ATM and one in the BTC ATM above to have a transaction of ticker B. Ideally without bothering of tribalism of the authors of those wallets, it is possible for a programmer to design a wallet that is capable to craft the transactions in one stop and broadcast them afterward.