fullstack-template: Instructions file for Claude Code

CLAUDE.md

fullstack-template CLAUDE.md is an instructions file for Claude Code from GRACENOBLE/fullstack-template. It costs 2,671 tokens per session, scanned A, original, MIT.

A repository guide for a full-stack application using Next.js and React in the web interface, Go in the backend, PostgreSQL for data, and Kotlin for Android. It records the commands and workflows for running, testing, and building each part.

In plain words
What is it for?
It is for developing and testing web, backend, database, and Android features in one repository.
Why use it?
It gives a coding agent the project's technology choices and required commands before it changes code.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions AGENTS.md.

This is GRACENOBLE/fullstack-template's own configuration. It tells Claude Code how to work on fullstack-template 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 fullstack-template configures →

Reuse

Borrowing it

Nothing to install: this file belongs to GRACENOBLE/fullstack-template. 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/GRACENOBLE/fullstack-template/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/GRACENOBLE/fullstack-template

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 fullstack-template CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gracenoble/fullstack-template/claude-md/github.svg)](https://agentmods.dev/instructions/gracenoble/fullstack-template/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/gracenoble/fullstack-template/claude-md"><img src="https://agentmods.dev/badge/instructions/gracenoble/fullstack-template/claude-md/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 fullstack-template CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gracenoble/fullstack-template/claude-md"><img src="https://agentmods.dev/badge/instructions/gracenoble/fullstack-template/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,671 This file is loaded in full into every session.
When invoked 2,671 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.02671 $0.02671
Opus 5.5 $0.01068 $0.01068
Sonnet 5.5 $0.00534 $0.00534
Haiku 4.5 $0.00267 $0.00267

Measured 1mo ago against content hash 722205104be4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fullstack-template CLAUDE.md scanned grade A with 0 findings 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 1mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

CLAUDE.md · 204 lines

How it starts

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

Project Guide

Stack

Layer Tech
Frontend Next.js 16, React 19, TypeScript 5, Tailwind CSS 4
Backend Go 1.25, Gin, database/sql + pgx v5 stdlib
Database PostgreSQL 16 via Docker Compose
Mobile Android, Kotlin 2.2, Jetpack Compose BOM 2026.02, Material3
Dev tools pnpm, Air (Go hot reload), Testcontainers, Gradle 9.4

Run commands

cd backend && make docker-run   # start Postgres
cd backend && make watch        # backend dev with hot reload (Air) → :8080
cd web && pnpm dev              # web dev → :3000

cd backend && make test         # all tests
cd backend && make itest        # integration tests only (requires Docker)
cd web && pnpm lint && pnpm build
cd web && pnpm test             # Vitest unit + component tests
cd web && pnpm test:watch       # watch mode during TDD

cd mobile && ./gradlew assembleDebug          # build Android APK
cd mobile && ./gradlew lint && ./gradlew test # mobile quality gate
cd mobile && ./gradlew connectedAndroidTest   # instrumented tests (emulator/device required)

Migration commands (run from backend/)

make migrate-create name=<slug>   # create a new timestamped SQL migration file
make migrate-status               # show applied vs. pending migrations
make migrate-up                   # apply all pending migrations
make migrate-up-one               # apply the next pending migration only
make migrate-down                 # roll back the last applied migration
make migrate-reset                # roll back everything to version 0
make migrate-version              # print current schema version

Feature development workflow — always follow this

  1. Check docs first — delegate to docs agent: find relevant topic docs, verify they match the current code
  2. Fix stale docs — if docs diverge from code, update docs before implementing
  3. Migrate — if the feature needs new or changed tables: make migrate-create name=<slug>, write the SQL, make migrate-up
  4. Write tests first (TDD) — write failing tests that describe the intended behaviour before writing any implementation code
  5. Implement — delegate to backend or web agent, passing the relevant doc content as context; implementation is complete when all tests pass
  6. Env vars — if any new env vars were added to loadConfig(), add them to backend/.env.example with a safe placeholder value and a comment explaining the format
  7. Update docs — delegate to docs agent: update last_verified, add new topics if introduced
  8. Quality gate — run /project:check before declaring done

Read the full file on GitHub · 204 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. 1mo ago First seen · 204 lines · 2,671 tokens per session scan A 722205104be4

Subscribe to this mod's changes

fullstack-template CLAUDE.md is an instructions file published in the GitHub repository GRACENOBLE/fullstack-template (6 stars, last pushed 1mo ago), licensed MIT. It adds 2,671 tokens to every session, about $0.0107 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other instructions, from other repositories