app-ai-guardrailslisted

Scaffold a new production application with the full agentic-AI guardrail canon baked in from commit #1: a uniform 7-gate interface (lint, typecheck, test, coverage, build, e2e, audit) on each stack's native runner, strict types, maximal static analysis, coverage thresholds with teeth plus seed tests, pre-commit hooks, hardened CI with optional SonarCloud, supply-chain pinning, and an agent-ready AGENTS.md — every gate verified green before the first commit. Native adapters: Next.js, NestJS, Django, Go, Rust, Spring Boot; a discovery method maps the canon to other stacks. USE FOR: creating or scaffolding a new app, service, or API from scratch; bootstrapping a greenfield repo that AI agents will build in. DO NOT USE FOR: retrofitting an existing codebase or scaffolding a new package into an existing monorepo (both assume repo-root ownership), LLM-safety or content-moderation guardrails, or adding a single tool to an existing project.
a-tokyo/agent-skills · ★ 16 · AI & Automation · score 81

Install: claude install-skill a-tokyo/agent-skills

# app-ai-guardrails Scaffold a greenfield app so the **full guardrail canon** is live in **commit #1** and every one of the 7 **gates** is **verified green** before that commit exists. The canon is stack-agnostic; each stack's mechanics live in one adapter file. The differentiator is **teeth**: gates that *fail* on violations, not report-only tooling. You wire the canon, run every gate green, prove the tree is clean, then commit. ## 1. Scope Greenfield only in v1. Six native adapters — Next.js (deep), NestJS, Django, Go, Rust, Spring Boot — plus a discovery method that maps the canon to any other stack. All six native adapters have benchmark medians (Spring Boot: sonnet n3, median 89, all gates green); **discovery is unbenchmarked and says so**. Retrofitting the canon onto an existing codebase — or scaffolding a new package **inside** an existing monorepo (every mechanism here assumes repo-root ownership: hooks, CI, commit #1, `.claude/` all at root) — is **out of scope**. If asked, decline politely and say why (an agent under a "make gates green" mandate inside real code can weaken tests/code to pass; greenfield bounds that blast radius), and leave value behind: point the user at `references/canon/gate-interface.md` for the 7-gate contract they can wire by hand today. ## 2. The gate contract Every guardrailed repo exposes the same 7 gate **names** on its native runner. The names are identical across stacks; only the runner prefix differs. | Gate | Semantic | |---|---|