ios-nfr

Evaluate iOS feature specs against non-functional requirement checklists.

3|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill ios-nfr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-nfr
Source: https://github.com/edfenton/claude-skills/tree/main/ios/ios-nfr
Command: npx skills add https://github.com/edfenton/claude-skills --skill ios-nfr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures iOS stories address non-functional requirements, aligning features with performance, reliability, security, accessibility, and maintainability standards.

Core Features & Use Cases

  • Checklist-based evaluation of iOS features against NFRs
  • Guidance for performance budgets, battery impact, offline behavior, accessibility, and observability
  • Use Case: when reviewing a feature spec, apply the NFR checklist to surface gaps and risks

Quick Start

Review an iOS feature spec and apply the NFR checklist to surface gaps.

Frequently Asked Questions about ios-nfr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check non-functional requirements for an iOS feature spec?

To check non-functional requirements for an iOS feature spec, apply a structured NFR checklist covering performance budgets, battery impact, offline behavior, accessibility, and observability to surface gaps and risks.

What are common iOS non-functional requirements I should verify during feature design?

Common iOS non-functional requirements to verify during feature design include performance budgets, battery impact, offline correctness, accessibility standards, security protocols, reliability, and maintainability metrics.

When do I need to evaluate accessibility and battery impact for iOS features?

You need to evaluate accessibility and battery impact for iOS features when reviewing feature specs, design docs, or implementation plans to ensure alignment with non-functional standards and prevent usability regressions.

Can I use a checklist to enforce performance budgets and offline correctness in iOS apps?

Yes, you can use a checklist-based evaluation to enforce performance budgets and offline correctness in iOS apps, applying structured frontmatter guidance to identify gaps during the feature review process.

What is the best way to surface security and reliability gaps in iOS feature plans?

The best way to surface security and reliability gaps in iOS feature plans is applying a non-functional requirements checklist to the spec, ensuring observability and maintainability standards are met before implementation.

Does reviewing iOS non-functional requirements help with maintainability and observability?

Reviewing iOS non-functional requirements directly improves maintainability and observability by systematically verifying feature specs against established standards, ensuring long-term code health and monitoring capabilities are addressed early.