Production Readiness
Guide users through preparing a web app or API for production, verifying its deployment and observing real use. Create an offline HTML checklist with separate stage ratings, environment-specific evidence and blockers, and implement agreed local fixes.
Install
/plugin marketplace add superhero-tech/superhero-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add superhero-tech/superhero-skills --skill production-readinessgit clone --depth 1 https://github.com/superhero-tech/superhero-skills.git /tmp/superhero-skills
mkdir -p ~/.claude/skills
cp -r /tmp/superhero-skills/plugins/product-discovery/skills/engineering/production-readiness ~/.claude/skills/production-readinessPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Production readiness Help the user prepare an application for release, step by step. The durable result is one Polish, offline `docs/production-readiness.html` with embedded state, evidence and history. Default to the user's language in conversation; use Polish in the report unless requested otherwise. Do not describe its output as a security certification. Requires local repository access and Python 3.9 or later. The HTML works offline, including its embedded Geist Sans font; JavaScript only enables filters. ## Guide two practical runs The normal journey is: run on dev to find and fix problems before deploying; after deployment, run again with the production URL to verify the remaining requirements. Explain it in those words. Real-use observation is a later follow-up, not a third dashboard competing for attention. ## Separate environments from release stages - Environments are concrete local/dev, preview, staging or production instances. Preview/staging is optional; do not require an extra hosted environment for every small application. An isolated restore or migration trial still needs a suitable safe place. - Assess three stages separately: `preparation` before deployment, `deployment` verification of the target deployment (which can happen before admitting users), and `observation` of real use after release. A production instance can exist without serving users yet. Never average these stage ratings or call local success production verification.
Details
- Skill name
production-readiness- Repository
- superhero-tech/superhero-skills
- Path
plugins/product-discovery/skills/engineering/production-readiness/SKILL.md- License
- MIT
- Repo updated
- 13 November 2026
FAQ
What does the Production Readiness skill do?
Guide users through preparing a web app or API for production, verifying its deployment and observing real use. Create an offline HTML checklist with separate stage ratings, environment-specific evidence and blockers, and implement agreed local fixes.
How do I install the Production Readiness skill?
Claude Code plugin: /plugin marketplace add superhero-tech/superhero-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Production Readiness popular?
It lives in superhero-tech/superhero-skills, which has 298 GitHub stars and 25 forks.
Related skills
Ab Test Design
298superhero-tech/superhero-skills
Design an A/B test and decide whether available traffic can detect a useful effect. Use when planning a randomized product comparison, checking sample size or test duration, or creating an interactive A/B test card.
Affinity Mapping
298superhero-tech/superhero-skills
Synthesize interview transcripts into evidenced themes and user needs, then render an interactive HTML evidence map. Use when synthesizing interviews, affinity mapping, or preparing opportunities for discovery.
Build Figma Library
298superhero-tech/superhero-skills
Build or extend a Figma token and component library from product documentation, code, or an existing UI. Prepare it for another agent by checking component properties, composition examples, and handoff, including publishing when reuse spans files. Use for reconstructing design systems and making libraries reusable; screen-only design and documentation of existing components have separate workflows.
AWS Account Management
299hoodini/ai-agents-skills
Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.
Docker Build Isolation
339Lanqiao-Luca/ai-java-workflow
显式选择Docker构建后端,核白名单输入、容器限制、候选身份与资源停止,不继承私人Docker状态。
AWS Cost Optimization
206ahmedasmar/devops-claude-skills
AWS cost optimization and FinOps workflows. Use this skill whenever the user mentions AWS costs, cloud spending, FinOps, Reserved Instances, Savings Plans, or cost reduction. Triggers include finding unused resources, analyzing the AWS bill, rightsizing EC2 or RDS instances, evaluating Spot instances, detecting cost anomalies, migrating to Graviton or newer instance generations, implementing tagging for cost allocation, setting up AWS Budgets, conducting monthly cost reviews, comparing RI vs Savings Plans, and optimizing storage, network, or database costs.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.