specforge

SpecForge MCP Server & Claude Code Plugin

Make LLMs write better code, not just code that works.

Purpose: Give AI assistants authoritative language specs, generation checklists, and linter rules—replacing training data from Stack Overflow and random GitHub repos with actual best practices.

Quick Start

New here? See QUICKSTART.md for 5-minute setup.

Claude Code Plugin: See PLUGIN.md for plugin installation and usage.

Install as Claude Code Plugin

/plugin install github:krisarmstrong/specforge-mcp

Then use slash commands like:

• /checklist python - Get pre-coding checklist
• /spec typescript stdlib - Get TypeScript stdlib docs
• /lint-rule python ruff E501 - Explain a linter rule
• /search-specs async error handling - Search all specs

WebUI

npm run webui:install  # First time
npm run dev:webui      # Start at http://localhost:3847

LLM Integration: See System Prompt Template to configure LLMs to use SpecForge automatically.

Key Feature: Generation Checklists

Every supported language now has a generation-checklist.md with 10-20 critical rules to follow BEFORE writing code:

specs/python/generation-checklist.md     # Type hints, pathlib, context managers...
specs/typescript/generation-checklist.md # const/let, ===, Promise handling...
specs/go/generation-checklist.md         # Error handling, defer, context...
specs/rust/generation-checklist.md       # Ownership, ?, no unwrap...
... (35 languages total)

The Difference:

Without SpecForge	With SpecForge
Code that "works"	Code that follows best practices
Silent bugs	Caught by linter-aware patterns
Security vulnerabilities	Security anti-patterns avoided
Inconsistent style	Idiomatic code

MCP Tools

Tool	Purpose
get_checklist(language)	Call FIRST - Critical rules before writing code
get_spec(language, category, topic)	Full language specification
get_linter_rule(language, linter, rule)	Specific linter rule explanation
search_specs(query)	Search across all specs
list_available(language, category)	List available topics

Supported Languages

Language	Spec	Stdlib	Linters	Formatters	Patterns
Assembly (x86-64, ARM, RISC-V, WASM)	✅	✅ (ABI refs)	-	-	✅
BASIC	✅	✅	-	-	✅
Bash	✅	✅	shellcheck	shfmt	✅
Batch	✅	✅	-	-	✅
Go	✅	✅	golangci-lint	gofmt, goimports, gofumpt, golines	✅
C#	✅	✅ (namespace pages)	.NET analyzers, StyleCop	dotnet format	✅
JavaScript	✅	✅ (Node + Web APIs)	Biome	Biome	✅
TypeScript	✅	✅	Biome	Biome	✅
C	✅	✅	clang-tidy, cppcheck	clang-format	✅
C++	✅	✅	clang-tidy, cppcheck	clang-format	✅
CSS	✅	✅	Biome	Biome	✅
HTML	✅	✅	html-validate, htmlhint	Biome	✅
Git	✅	✅	gitlint, commitlint	commitlint/commitizen	✅
Java	✅	✅ (package pages)	Error Prone, SpotBugs, Checkstyle, PMD	google-java-format	✅
Kotlin	✅	✅ (package pages)	detekt, ktlint	ktlint, ktfmt	✅
Lua	✅	✅	luacheck	stylua	✅
PowerShell	✅	✅	PSScriptAnalyzer	-	✅
Python	✅	✅ (module pages)	Ruff, mypy	Ruff	✅
Rust	✅	✅ (module pages)	clippy	rustfmt	✅
SQL	✅	✅ (Postgres/MySQL/SQLite/SQL Server)	sqlfluff	sqlfluff	✅
Swift	✅	✅ (module pages)	SwiftLint	swift-format	✅
PHP	✅	✅	PHPStan, Psalm	PHP-CS-Fixer	✅
Ruby	✅	✅	RuboCop	RuboCop	✅
Dart	✅	✅	Dart linter	dart format	✅
R	✅	✅	lintr	styler	✅
Julia	✅	✅	JET, StaticLint	JuliaFormatter	✅
Scala	✅	✅	Scalafix, WartRemover	Scalafmt	✅
Elixir	✅	✅	Credo	mix format	✅
Clojure	✅	✅	clj-kondo, eastwood	zprint	✅
Haskell	✅	✅	HLint	fourmolu, ormolu	✅
Zig	✅	✅	-	zig fmt	✅
OCaml	✅	✅	odoc	ocamlformat	✅
Markdown	✅	-	markdownlint	Prettier, markdownfmt	✅
YAML	✅	-	yamllint	Prettier, yamlfix	✅
Dockerfile	✅	-	hadolint	-	✅

Notes on specs:

• Some ecosystems do not publish a single open spec; we use the most authoritative public references available.
• C++ uses cppreference, as ISO C++ specs are copyrighted.
• TypeScript uses the official Handbook (the formal spec is archived).
• SQL uses vendor references (PostgreSQL/MySQL/SQLite/SQL Server).
• Assembly uses vendor/architecture references plus ABI docs in stdlib.

BASIC Ecosystem Notes