메뉴
Design an apptoken -- map high-level requirements to protocols, configuration steps, and implementation skills
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Apptoken ecosystem knowledge -- token standards (ERC-721C, ERC-1155C, ERC-20C), apptoken categories, cross-protocol integration patterns. Use this skill whenever the user asks about apptokens, Creator Token Standards, ERC-20C/ERC-721C/ERC-1155C, Limit Break tokens, cross-protocol integration, or how the apptoken ecosystem fits together.
Generate integration code for the LBAMM CLOBTransferHandler -- on-chain limit order book with maker deposits, FIFO order filling, and price-linked lists. Generates Foundry scripts for maker flows (deposit, open/close orders, withdraw) and taker flows (filling orders through AMM swaps). Use this skill whenever the user asks about LBAMM CLOB, on-chain order books, limit orders on LBAMM, maker/taker flows, CLOB deposits, or filling CLOB orders.
LBAMM transfer handler architecture -- how transfer handlers work during swap settlement, the ILimitBreakAMMTransferHandler interface, executor validation hooks, callback patterns, and custom handler development. Use this skill whenever the user asks about LBAMM transfer handlers, swap settlement, ammHandleTransfer, custom settlement logic, ITransferHandlerExecutorValidation, how swaps use transfer data, or writing a custom handler contract.
Generate DEX integration contracts that call LBAMM
Generate integration code for the LBAMM PermitTransferHandler -- gasless swap execution via EIP-712 signed permits with optional cosigner. Generates Foundry scripts, signing code, and transferData encoding for fill-or-kill and partial fill permit swaps.
Generate complete ILimitBreakAMMPoolHook Solidity implementations
SOC 직업 분류 기준
| name | apptoken-designer |
| description | Design an apptoken -- map high-level requirements to protocols, configuration steps, and implementation skills |
| user-invocable | true |
| argument-hint | [description of your token - what it does, who uses it, how it should behave] |
Take a high-level token idea and produce a concrete implementation plan: which protocols to use, what to configure, and which skills to invoke.
Parse the user's vision from $ARGUMENTS -- understand the token's purpose, target users, economic model, and behavioral constraints.
Clarify critical decisions early -- before building the plan, check if $ARGUMENTS leaves any of these ambiguous: reserve-backed (TokenMaster) vs unbacked, permissioned vs permissionless, target chain. If the token's core economic model is unclear, ask in a single message. If the vision is clear enough to produce a useful plan, proceed -- step 5 will flag remaining decisions for the user. Note: when the user asks for a TokenMaster token, the primary buy/sell mechanism is the TokenMaster Router -- don't ask about LBAMM/DEX trading unless the user specifically wants it.
Classify into apptoken pattern categories (a token can combine multiple):
| Category | Signals | Key Protocols |
|---|---|---|
| Client-Side | User acquisition, quests, 2FA, offerwalls | Trusted Forwarder (permissioned mode) |
| Trade | Trading fees, exclusive pairs, price ranges, fixed ratios, asset gating, lotteries | LBAMM token hooks, standard hook, Transfer Validator |
| Temporal | Vesting, expiries, time windows | LBAMM token hooks, standard hook |
| Spend-Only | Promotional tokens, game resources, utility tokens, no trading | Transfer Validator (restrictive policy) |
| Compliant | KYC, multi-jurisdiction | Transfer Validator, Trusted Forwarder |
| Backed | Price floor, reserve backing, monetized spends | TokenMaster pools (buy/sell via Router), optionally LBAMM for secondary DEX trading |
Map to a protocol stack -- determine which protocols are needed and in what order:
Produce an implementation plan with these sections:
a. Token Contract -- Which token standard to use, any custom overrides needed
b. Transfer Validator Setup -- Ruleset selection, list configuration, operator whitelisting
c. Protocol Configuration -- Per-protocol setup steps (LBAMM pools/hooks, TokenMaster deployment, Payment Processor settings)
d. Skill Sequence -- Ordered list of skills to invoke, with example arguments:
1. /transfer-validator-config [whitelist TokenMaster as operator]
2. /tokenmaster-deployer [Standard pool with USDC pairing, 5% creator fee]
3. /tokenmaster-integrator [buy/sell integration via Router]
e. Architecture Diagram -- ASCII diagram showing protocol interactions
Flag important decisions the user needs to make:
apptoken-general (ecosystem overview, token standards, pattern categories)| User Wants | Protocols Needed | Primary Skills |
|---|---|---|
| Simple tradeable token | ERC-20C, TV, LBAMM | /transfer-validator-config, /lbamm-standard-hook, /lbamm-pool |
| Token with price floor | ERC-20C, TV, TokenMaster | /tokenmaster-deployer, /transfer-validator-config |
| Backed token + DEX float | ERC-20C, TV, TokenMaster, LBAMM | Bootstrap via TM buys → disable TM buys → add LBAMM liquidity (TM sells stay as floor). /tokenmaster-deployer, /transfer-validator-config, /lbamm-standard-hook, /lbamm-pool |
| Game currency (no trading) | ERC-20C, TV | /transfer-validator-config (restrictive whitelist) |
| NFT collection with royalties | ERC-721C, TV, PP | /transfer-validator-config, /payment-processor-creator |
| NFT marketplace (buy/sell/trade) | ERC-721C, TV, PP | /transfer-validator-config, /payment-processor-creator, /payment-processor-exchange |
| Compliant token with KYC | ERC-20C, TV, Trusted Forwarder | /transfer-validator-config, custom forwarder setup |
| Token with custom swap logic | ERC-20C, TV, LBAMM + custom hook | /lbamm-token-hook, /lbamm-pool, /transfer-validator-config |
| Fixed-rate stablecoin swap | ERC-20C, TV, LBAMM (Fixed pool) | /lbamm-pool (Fixed type), /transfer-validator-config |
| Gasless swap execution | ERC-20C, TV, LBAMM + PermitC | /lbamm-permit-handler, /lbamm-pool, /transfer-validator-config |
| On-chain limit order book | ERC-20C, TV, LBAMM CLOB | /lbamm-clob, /lbamm-pool, /transfer-validator-config |
Transfer Validator is the foundation layer. Every other protocol (LBAMM, TokenMaster, Payment Processor) must be whitelisted as an operator in the Transfer Validator before it can move tokens. This gives creators a single kill switch over their entire token economy.
The Trusted Forwarder provides web2 app routing and optional permissioning (Client-Side and Compliant token categories). There is no dedicated skill for Trusted Forwarder deployment -- guide the user through manual setup using the Trusted Forwarder Factory at 0xFF0000B6c4352714cCe809000d0cd30A0E0c8DcE. See apptoken-general/references/ecosystem.md for details.