Review Angular numeric inputs and min/max validation after Angular 12 when <input type="number"> behavior can affect form validity and submit flows.
Scanned 10/2/2026
npx -y skills add janpereira-dev/ngAutoPilot --skill angular--forms--angular-number-input-min-max-validation-v12 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Forms Angular Number Input Min Max Validation V12?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/janpereira-dev-angular-forms-angular-number-input-min-max-validat)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
id: angular.forms.angular-number-input-min-max-validation-v12
name: Angular Number Input Min Max Validation v12
description: >
Review Angular numeric inputs and min/max validation after Angular 12 when <input type="number"> behavior can affect form validity and submit flows.
stack:
- Angular
- TypeScript
category: forms
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
- number input min max
- form validity
compatibility:
angular:
min: "12"
---
# Angular Number Input Min Max Validation v12
## Purpose
Review numeric input validation after Angular 12.
## When to Use
- The app uses numeric inputs with min/max.
## When Not to Use
- The app has no numeric input validation risk.
## Required Inputs
- numeric forms
- validation flows
## Procedure
1. Find min/max numeric inputs.
2. Validate submit behavior.
## Do
- Keep validation explicit.
## Do Not
- Do not remove domain rules to avoid validation changes.
## Review Checklist
- [ ] Numeric input behavior is validated.
## Expected Output
1. Number input summary.
## Exit Criteria
- Numeric validation risk is explicit.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!