build-with-claude

Name: build-with-claude
Author: sendaifun

162stars45forks

How to install build-with-claude?

sendaifun/solana-new/build-with-claude

$npx -y skills add sendaifun/solana-new --skill build-with-claude

Installs into the current project.

Summary

Guide a developer through building their Solana MVP step by step using Claude Code. Use when a user says "help me build this", "start the MVP", "guide me through implementation", "what should I build first", or "walk me through the code". Reads build-context.md from a prior scaff

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":"build-with-claude","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":"build-with-claude","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	# Build with Claude
50
51	## Overview
52
53	Guide the user through implementing their Solana MVP feature by feature. Break the work into small, testable increments. Use installed skills and MCPs to accelerate development. Keep the user shipping, not stuck.
54
55	## Workflow
56
57	1. Check for `.superstack/build-context.md`. If found, use the stack and architecture decisions. If not, ask what they've set up and what they want to build. Write `.superstack/build-context.md` with the context gathered so future skills can use it.
58	2. Read [references/skill-mcp-usage-guide.md](references/skill-mcp-usage-guide.md) to understand what tools are available BEFORE building.
59	3. Read [references/dev-environment-setup.md](references/dev-environment-setup.md) to ensure the dev environment is ready.
60	4. Read [references/solana-dev-patterns.md](references/solana-dev-patterns.md) for implementation patterns.
61	5. Break the MVP into 3-5 milestones, each shippable in 1-2 hours.
62	6. For each milestone:
63	a. Explain what we're building and why
64	b. Write the code (use installed skills for domain guidance)
65	c. Test it (devnet first, always)
66	d. Verify it works before moving on
67	7. When stuck, consult [references/error-recovery-guide.md](references/error-recovery-guide.md).
68	8. After MVP is complete, run through [references/testing-checklist.md](references/testing-checklist.md).
69
70	## Prior Context (Optional — never block on this)
71
72	If `.superstack/build-context.md` exists, use the stack and architecture decisions. If it doesn't exist, proceed immediately — ask the user what they've set up and what they want to build. Do NOT redirect to scaffold-project or any other command.
73
74	## Non-Negotiables
75
76	- Never block on missing context files. Always proceed by asking the user directly.
77	- Never write more than 1 milestone of code before testing. Ship small, verify often.
78	- Always test on devnet before suggesting mainnet.
79	- If the user is stuck for more than 2 attempts at the same problem, step back and try a different approach.
80	- Use the installed skills and MCPs — they exist to help. Don't reinvent what a skill already provides.
81	- Keep explanations short. The user is here to build, not read essays.
82	- Optionally update `.superstack/build-context.md` as milestones are completed.
83
84	## Phase Handoff
85
86	This skill is Phase 2 (Build) in the Idea → Build → Launch journey.
87
88	Reads: `.superstack/build-context.md` (from scaffold-project)
89	Writes/Updates: `.superstack/build-context.md` (creates if missing) with:
90	- `build_status.milestones`: array of completed milestones
91	- `build_status.mvp_complete`: boolean
92	- `build_status.tests_passing`: boolean
93	- `build

People who liked this also viewed

6 picks

Type

build-with-claude

162stars45forks

View on GitHub

How to install build-with-claude?

sendaifun/solana-new/build-with-claude

$npx -y skills add sendaifun/solana-new --skill build-with-claude

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":"build-with-claude","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":"build-with-claude","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	# Build with Claude
50
51	## Overview
52
53	Guide the user through implementing their Solana MVP feature by feature. Break the work into small, testable increments. Use installed skills and MCPs to accelerate development. Keep the user shipping, not stuck.
54
55	## Workflow
56
57	1. Check for `.superstack/build-context.md`. If found, use the stack and architecture decisions. If not, ask what they've set up and what they want to build. Write `.superstack/build-context.md` with the context gathered so future skills can use it.
58	2. Read [references/skill-mcp-usage-guide.md](references/skill-mcp-usage-guide.md) to understand what tools are available BEFORE building.
59	3. Read [references/dev-environment-setup.md](references/dev-environment-setup.md) to ensure the dev environment is ready.
60	4. Read [references/solana-dev-patterns.md](references/solana-dev-patterns.md) for implementation patterns.
61	5. Break the MVP into 3-5 milestones, each shippable in 1-2 hours.
62	6. For each milestone:
63	a. Explain what we're building and why
64	b. Write the code (use installed skills for domain guidance)
65	c. Test it (devnet first, always)
66	d. Verify it works before moving on
67	7. When stuck, consult [references/error-recovery-guide.md](references/error-recovery-guide.md).
68	8. After MVP is complete, run through [references/testing-checklist.md](references/testing-checklist.md).
69
70	## Prior Context (Optional — never block on this)
71
72	If `.superstack/build-context.md` exists, use the stack and architecture decisions. If it doesn't exist, proceed immediately — ask the user what they've set up and what they want to build. Do NOT redirect to scaffold-project or any other command.
73
74	## Non-Negotiables
75
76	- Never block on missing context files. Always proceed by asking the user directly.
77	- Never write more than 1 milestone of code before testing. Ship small, verify often.
78	- Always test on devnet before suggesting mainnet.
79	- If the user is stuck for more than 2 attempts at the same problem, step back and try a different approach.
80	- Use the installed skills and MCPs — they exist to help. Don't reinvent what a skill already provides.
81	- Keep explanations short. The user is here to build, not read essays.
82	- Optionally update `.superstack/build-context.md` as milestones are completed.
83
84	## Phase Handoff
85
86	This skill is Phase 2 (Build) in the Idea → Build → Launch journey.
87
88	Reads: `.superstack/build-context.md` (from scaffold-project)
89	Writes/Updates: `.superstack/build-context.md` (creates if missing) with:
90	- `build_status.milestones`: array of completed milestones
91	- `build_status.mvp_complete`: boolean
92	- `build_status.tests_passing`: boolean
93	- `build

People who liked this also viewed

6 picks

Type