Skip to content
Back to skills

Apple Hig Digit Entry Views

ASecurity

Use when creating, reviewing, or adapting tvOS fullscreen numeric sequence entry such as a PIN.

  • 7 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 26, 2026
ai-agentsgitsecurity

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add AyushRajSinghParihar/apple-human-interface-skills --skill apple-hig-digit-entry-views --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apple Hig Digit Entry Views?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Apple Hig Digit Entry Views
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ayushrajsinghparihar-apple-hig-digit-entry-views/badge)](https://www.skillsdirectory.com/skills/ayushrajsinghparihar-apple-hig-digit-entry-views)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: apple-hig-digit-entry-views
description: Use when creating, reviewing, or adapting tvOS fullscreen numeric sequence entry such as a PIN.
---

# Explain and protect numeric entry

Read [the digit-entry guide](../../references/digit-entry-views.md). This procedure is application advice for the tvOS-specific component, not a universal OTP-field specification.

Inspect sequence purpose/length, sensitivity, prompt, validation, platform/input, and create/review/adapt request. Distinguish a numeric sequence from a numeric quantity: leading zeroes and exact length may matter. Do not infer security from a screenshot showing obscured characters; inspect secure-entry configuration when available.

Use the fullscreen numeric-entry presentation for the intended TV task, with a clear title and prompt explaining why digits are needed. Mask sensitive sequences using secure fields. Specify completion, correction, cancellation, and an understandable rejected-entry path without exposing the secret. These lifecycle choices are application advice; the source does not define an authentication protocol or retry policy. For other platforms choose a supported secure-entry approach instead of claiming this component's availability.

Implement the entry/validation boundary or deliver prompt, field, sequence, and result-state specifications; review specific exposure or input-loss defects. Keep authorization and actual authentication outside a cosmetic redesign unless included in scope.

**Worked transformation:** Before: a TV parental PIN screen asks only `Number`, displays the full PIN, and converts `0042` into `42`. Decision: purpose, secrecy, and sequence identity are all lost. After: explain the parental approval task, mask secure entry, and preserve the exact four-digit sequence through validation.

Deliver the artifact and entry/correct/reject/cancel contract. Verify leading zeroes, correction, completion length, rejected input, and cancellation. Fail for sensitive exposure, altered sequence, unexplained purpose, or an exit that commits incomplete input. Native remote/keyboard and authentication behavior need separate execution evidence.

Load [virtual-keyboards](../apple-hig-virtual-keyboards/SKILL.md) for TV input variants or [privacy](../../../apple-hig-foundations/.topics/apple-hig-privacy/SKILL.md) for handling sensitive information.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.