Production Grade
Principle-engineering posture for production-grade code: reads the repo first, plans before code, matches conventions, pulls latest docs over training recall, and ships the simplest correct change that holds the bar — proper algorithms and data structures, idempotent writes, schema+queries+indexes as one artefact, typed errors, tests in the same diff. Substrate-agnostic; defers to peer skills on their lanes. Use for non-trivial planning, design, implementation, review, or refactoring; RCA and debugging; performance and optimization work; changes touching a database schema, security, infrastruc
Install
npx skills add a-tokyo/aiworkspace --skill production-gradegit clone --depth 1 https://github.com/a-tokyo/aiworkspace.git /tmp/aiworkspace
mkdir -p ~/.claude/skills
cp -r /tmp/aiworkspace/.agents/skills/production-grade ~/.claude/skills/production-gradePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# production-grade
Principle-engineering posture as a skill. Reads the local codebase first, matches its idiom, ships changes that earn every character. Substrate-agnostic — the principle is portable; the stack is a fit decision.
## When to use
Load this skill for non-trivial engineering work in any language, framework, or substrate: planning ("plan of plans," "do it the right way") and implementation; changes touching a database schema, a security-impacting subsystem, infrastructure, or a public API surface; RCA, coordinated multi-subsystem drops, and rename campaigns; reviewing or refactoring; raising a vibe-coded codebase toward the principle bar; hardening inherited or generated code — dependency / CVE, security, and migration audits (R16); and minimalism passes — *"be lazy," "simplest / minimal solution," "YAGNI," "is this over-engineered," "what can we delete"* (R2, `references/11-minimalism-audit.md`).
Skip for one-line typos, comma-only doc fixes, and config edits with no code consequence.
## Meta-rules
Three meta-rules modulate every operating rule. Read them as the lens; read the R-rules as the directive set.
### M1 — Principle over substrate, concept over instanceDetails
- Skill name
production-grade- Repository
- a-tokyo/aiworkspace
- Path
.agents/skills/production-grade/SKILL.md- License
- Apache-2.0
- Repo updated
- 19 August 2026
FAQ
What does the Production Grade skill do?
Principle-engineering posture for production-grade code: reads the repo first, plans before code, matches conventions, pulls latest docs over training recall, and ships the simplest correct change that holds the bar — proper algorithms and data structures, idempotent writes, schema+queries+indexes as one artefact, typed errors, tests in the same diff. Substrate-agnostic; defers to peer skills on their lanes. Use for non-trivial planning, design, implementation, review, or refactoring; RCA and debugging; performance and optimization work; changes touching a database schema, security, infrastruc
How do I install the Production Grade skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add a-tokyo/aiworkspace --skill production-grade. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Production Grade popular?
It lives in a-tokyo/aiworkspace, which has 23 GitHub stars and 5 forks.
Related skills
Autoresearch
23a-tokyo/aiworkspace
Autonomous iterative experimentation loop for any programming task. Guides the user through defining goals, measurable metrics, and scope constraints, then runs an autonomous loop of code changes, testing, measuring, and keeping/discarding results. Inspired by Karpathy's autoresearch. USE FOR: autonomous improvement, iterative optimization, experiment loop, auto research, performance tuning, automated experimentation, hill climbing, try things automatically, optimize code, run experiments, autonomous coding loop. DO NOT USE FOR: one-shot tasks, simple bug fixes, code review, or tasks without a
Scaffold Skill
23a-tokyo/aiworkspace
Scaffold new AI agent skills with proper symlinking across all IDE tools (Cursor, Claude Code, Codex, etc.). Use when creating a new skill, adding a local skill, or when the user wants to write a custom skill -- either workspace-wide or for a specific project.
Tribunal
23a-tokyo/aiworkspace
Runs a doer -> verifier-panel -> consensus loop to verify a deliverable before it ships. An orchestrator freezes acceptance criteria before implementation, dispatches a doer, then convenes a context-walled panel of independent verifiers - including an adversary with an explicit must-oppose mandate - for evidence-anchored review adjudicated to a SHIP / SHIP_WITH_CAVEATS / ITERATE / BLOCK / ESCALATE verdict logged to a ledger. Use for multi-agent verification of any artifact - code slices, plans, documents, audits - whenever asked to verify a deliverable, vet a plan, run a consensus review or in
Repo to Skill
43NeuroAIHub/awesome_cognitive_and_neuroscience_skills
Convert a GitHub repository or local codebase into a well-structured Claude Code skill with progressive disclosure. Use this skill whenever the user provides a GitHub URL or local repo path and asks to turn it into a skill, create a skill from a repo, or convert a library/tool/framework into reusable skill documentation. Also trigger when users say things like 'make a skill from this repo', 'turn this codebase into a skill', or 'I want a skill for [library name]'.
Mne Python Guide
43NeuroAIHub/awesome_cognitive_and_neuroscience_skills
Domain-validated pipeline guidance for EEG/MEG data analysis using MNE-Python: data loading, preprocessing (filtering, ICA, re-referencing), epoching, ERP/ERF computation, time-frequency decomposition, source localization, decoding/MVPA, statistical testing, simulation, and visualization. Use this skill whenever the user works with EEG/MEG/sEEG/ECoG/NIRS/eye-tracking data in Python, mentions MNE, or needs neurophysiological analysis guidance.
Unity CLI Contract
40Nice-Wolf-Studio/unity-claude-skills
Use when a unity command fails with exit 2 or "unknown option"; when a subcommand's help prints the root help instead of its own; when the CLI hangs on a pager or a first-run prompt; when a flag documented in the skill does not exist on the installed binary; before parsing or scripting any unity output; when the unity-cli skill is not installed.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.