solana-glossary: Command for Claude Code

.claude/commands/build-app.md

build-app is a command for Claude Code from solanabr/solana-glossary. It costs 13 tokens per session (2,006 once invoked), scanned C, a copy of build-app, MIT.

A command for building web applications with Next.js, React, Vite, Create React App, or other Node.js setups. It detects the project type and package manager before installing dependencies and continuing the build setup.

In plain words
What is it for?
Use it when starting or building a web client application. It helps prepare projects that use Next.js, React, Vite, Create React App, or Node.js.
Why use it?
It removes the need to identify the web framework and package manager manually. It provides a repeatable starting process for projects with different JavaScript setups.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

This is solanabr/solana-glossary's own configuration. It tells Claude Code how to work on solana-glossary itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything solana-glossary configures →

Reuse

Borrowing it

Nothing to install: this file belongs to solanabr/solana-glossary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/solanabr/solana-glossary/main/.claude/commands/build-app.md
Clone the repo
git clone --depth 1 https://github.com/solanabr/solana-glossary

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for build-app

README.md
[![agentmods](https://agentmods.dev/badge/commands/solanabr/solana-glossary/build-app/github.svg)](https://agentmods.dev/commands/solanabr/solana-glossary/build-app)
Your own site
<a href="https://agentmods.dev/commands/solanabr/solana-glossary/build-app"><img src="https://agentmods.dev/badge/commands/solanabr/solana-glossary/build-app/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for build-app

Your own site · 80×15
<a href="https://agentmods.dev/commands/solanabr/solana-glossary/build-app"><img src="https://agentmods.dev/badge/commands/solanabr/solana-glossary/build-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,006 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.02006
Opus 5 $0.00006 $0.01003
Sonnet 5 $0.00003 $0.00401
Haiku 4.5 $0.00001 $0.00201

Measured 9d ago against content hash 452b65de8443, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade C, and why

build-app scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf node_modules
Origin

This is a copy

91% identical to build-app — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/build-app.md · 334 lines

How it starts

The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are building a web client application. Follow these steps:

Step 1: Detect Framework

echo "🔍 Detecting web framework..."

# Check for Next.js
if grep -q "\"next\"" package.json 2>/dev/null; then
    echo "⚡ Next.js project detected"
    FRAMEWORK="nextjs"
# Check for Vite
elif [ -f "vite.config.ts" ] || [ -f "vite.config.js" ]; then
    echo "⚡ Vite project detected"
    FRAMEWORK="vite"
# Check for Create React App
elif grep -q "react-scripts" package.json 2>/dev/null; then
    echo "⚛️  Create React App detected"
    FRAMEWORK="cra"
# Generic React/Node
elif [ -f "package.json" ]; then
    echo "📦 Node.js project detected"
    FRAMEWORK="node"
else
    echo "❌ No package.json found"
    exit 1
fi

Step 2: Install Dependencies

echo "📦 Installing dependencies..."

# Check for lock files to determine package manager
if [ -f "pnpm-lock.yaml" ]; then
    PKG_MANAGER="pnpm"
elif [ -f "yarn.lock" ]; then
    PKG_MANAGER="yarn"
elif [ -f "bun.lockb" ]; then
    PKG_MANAGER="bun"
else
    PKG_MANAGER="npm"
fi

echo "Using package manager: $PKG_MANAGER"

# Install
$PKG_MANAGER install

Step 3: Environment Configuration

echo "🔧 Checking environment configuration..."

# Check for required env files
if [ -f ".env.example" ] && [ ! -f ".env.local" ]; then
    echo "⚠️  Missing .env.local - copying from .env.example"
    cp .env.example .env.local
    echo "📝 Please update .env.local with your values"
fi

# Verify Solana program ID is set
if grep -q "PROGRAM_ID\|NEXT_PUBLIC_PROGRAM_ID" .env.local 2>/dev/null; then
    echo "✅ Program ID configured"
else
    echo "⚠️  Warning: No PROGRAM_ID found in environment"
    echo "   Add: NEXT_PUBLIC_PROGRAM_ID=<your-program-id>"
fi

# Verify RPC endpoint
if grep -q "RPC_URL\|NEXT_PUBLIC_RPC" .env.local 2>/dev/null; then
    echo "✅ RPC endpoint configured"
else
    echo "ℹ️  Using default RPC endpoint"
fi

Read the full file on GitHub · 334 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 334 lines · 13 tokens per session scan C 452b65de8443

Subscribe to this mod's changes

build-app is a command published in the GitHub repository solanabr/solana-glossary (18 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 2,006 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 91% identical to build-app, differing in 2 lines, and is treated as a copy.

Related

Other commands, from other repositories

prototype-loop

Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.

Generous-Corp/pulp · 31 tokens

review-arch

Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.

smicolon/ai-kit · 35 tokens

a11y-audit-react

Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.

vanessamarely/ai-playbook-reposito · 0 tokens

next-upgrade

Structured workflow for upgrading Next.js applications across major versions. Use when migrating a Next.js project from one major version to another (e.g., 13 to 14, 14 to 15, 15 to 16). Covers codemod automation, breaking change detection, incremental migration paths, and post-upgrade validation.

oimiragieo/agent-studio · 66 tokens

mx-page-clone-from-template

GATED WRITE. Clone a Mendix page to a new name + optional entity rebinding via the mxcli MDL round-trip. Routes through the shadow-write engine (7 safety pillars). Pre-classifies the source as SIMPLE / COMPLEX / UNCLONEABLE; refuses UNCLONEABLE, requires --allow-lossy on COMPLEX. Auto-emits a /mx-handoff sheet for…

jordnlvr/MendixToolkit · 82 tokens

nextjs-cache

Get guidance on Next.js Cache Components setup.

horuz-ai/claude-plugins · 8 tokens