launch-token

Name: launch-token
Author: sendaifun

162stars45forks

How to install launch-token?

sendaifun/solana-new/launch-token

$npx -y skills add sendaifun/solana-new --skill launch-token

Installs into the current project.

Summary

Guide a developer through launching a token on Solana. Use when a user says "launch a token", "create a token", "pump.fun", "bonding curve", "token launch", "create a memecoin", or "SPL token". Reads build-context.md from a prior scaffold phase if available.

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"launch-token","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"launch-token","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Launch Token
50
51	## Overview
52
53	Walk the user through every step of launching a token on Solana — from choosing the right token standard (SPL vs Token-2022) and launch mechanism (Pump.fun bonding curve, Raydium pool, direct mint) to setting up metadata, configuring tokenomics, and going live. Covers both meme-style launches and serious project token design.
54
55	## Workflow
56
57	1. Check for `.superstack/build-context.md`. If found, use stack decisions. If not, ask: what kind of token (meme, utility, governance)? What launch mechanism (Pump.fun, Meteora DBC, custom bonding curve, direct LP)? Write `.superstack/build-context.md` with the context gathered so future skills can use it.
58	2. Read [references/token-launch-patterns.md](references/token-launch-patterns.md) to select the right launch path.
59	3. Read [references/tokenomics-checklist.md](references/tokenomics-checklist.md) to validate supply design and distribution.
60	4. Guide the user through implementation:
61	a. Create the mint (SPL Token or Token-2022 with extensions)
62	b. Set metadata (on-chain via Metaplex or Token-2022 metadata extension)
63	c. Configure launch mechanism (Pump.fun, Meteora DBC, direct LP, or custom bonding curve)
64	d. Test the full flow on devnet
65	e. Execute mainnet launch
66	5. Verify the token appears on explorers and DEX aggregators.
67
68	## Non-Negotiables
69
70	- Always test the full token creation and launch flow on devnet before mainnet.
71	- Never skip metadata — tokens without metadata are invisible to wallets and explorers.
72	- Warn about irrevocable actions: revoking mint authority, freeze authority, or update authority is permanent.
73	- If using Pump.fun, explain the bonding-curve mechanics, that migration to PumpSwap happens when the curve completes, and that current creator-fee / reward-sharing settings should be treated as a one-time configuration decision. Avoid hardcoding market-cap or liquidity thresholds unless you are citing current Pump docs.
74	- If using Meteora DBC, explain that it is a configurable multi-segment bonding curve that graduates into DAMM v1 or DAMM v2 after its migration threshold is reached.
75	- Validate tokenomics before launch — flag unreasonable supply, missing vesting, or rug-pull patterns.
76	- Use `rug-check-mcp` or `aethercore-token-rugcheck` to verify the token doesn't trigger safety warnings.
77
78	## Phase Handoff
79
80	This skill is Phase 2 (Build) in the Idea → Build → Launch journey.
81
82	Reads: `.superstack/build-context.md`
83	Writes/Updates: `.superstack/build-context.md` (creates if missing) with:
84	- `token.mint_address`: string (devnet and mainnet)
85	- `token.standard`: "spl-token" \| "token-2022"
86	- `token.launch_mechanism`: "pumpfun" \| "meteora-dbc" \| "raydium" \| "custom" \|

People who liked this also viewed

6 picks

Type

launch-token

162stars45forks

View on GitHub

How to install launch-token?

sendaifun/solana-new/launch-token

$npx -y skills add sendaifun/solana-new --skill launch-token

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"launch-token","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"launch-token","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Launch Token
50
51	## Overview
52
53	Walk the user through every step of launching a token on Solana — from choosing the right token standard (SPL vs Token-2022) and launch mechanism (Pump.fun bonding curve, Raydium pool, direct mint) to setting up metadata, configuring tokenomics, and going live. Covers both meme-style launches and serious project token design.
54
55	## Workflow
56
57	1. Check for `.superstack/build-context.md`. If found, use stack decisions. If not, ask: what kind of token (meme, utility, governance)? What launch mechanism (Pump.fun, Meteora DBC, custom bonding curve, direct LP)? Write `.superstack/build-context.md` with the context gathered so future skills can use it.
58	2. Read [references/token-launch-patterns.md](references/token-launch-patterns.md) to select the right launch path.
59	3. Read [references/tokenomics-checklist.md](references/tokenomics-checklist.md) to validate supply design and distribution.
60	4. Guide the user through implementation:
61	a. Create the mint (SPL Token or Token-2022 with extensions)
62	b. Set metadata (on-chain via Metaplex or Token-2022 metadata extension)
63	c. Configure launch mechanism (Pump.fun, Meteora DBC, direct LP, or custom bonding curve)
64	d. Test the full flow on devnet
65	e. Execute mainnet launch
66	5. Verify the token appears on explorers and DEX aggregators.
67
68	## Non-Negotiables
69
70	- Always test the full token creation and launch flow on devnet before mainnet.
71	- Never skip metadata — tokens without metadata are invisible to wallets and explorers.
72	- Warn about irrevocable actions: revoking mint authority, freeze authority, or update authority is permanent.
73	- If using Pump.fun, explain the bonding-curve mechanics, that migration to PumpSwap happens when the curve completes, and that current creator-fee / reward-sharing settings should be treated as a one-time configuration decision. Avoid hardcoding market-cap or liquidity thresholds unless you are citing current Pump docs.
74	- If using Meteora DBC, explain that it is a configurable multi-segment bonding curve that graduates into DAMM v1 or DAMM v2 after its migration threshold is reached.
75	- Validate tokenomics before launch — flag unreasonable supply, missing vesting, or rug-pull patterns.
76	- Use `rug-check-mcp` or `aethercore-token-rugcheck` to verify the token doesn't trigger safety warnings.
77
78	## Phase Handoff
79
80	This skill is Phase 2 (Build) in the Idea → Build → Launch journey.
81
82	Reads: `.superstack/build-context.md`
83	Writes/Updates: `.superstack/build-context.md` (creates if missing) with:
84	- `token.mint_address`: string (devnet and mainnet)
85	- `token.standard`: "spl-token" \| "token-2022"
86	- `token.launch_mechanism`: "pumpfun" \| "meteora-dbc" \| "raydium" \| "custom" \|

People who liked this also viewed

6 picks

Type