deliverable-criteria_skill

This skill helps enforce Next.js 15 App Router deliverable criteria by guiding compilation, linting, testing, routing, data fetching, performance,
  • Shell

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill masanao-ohba/claude-manifests --skill deliverable-criteria

  • SKILL.md8.7 KB

Overview

This skill codifies quality gates and acceptance criteria for Next.js 15 App Router projects to ensure deployable, performant, accessible, and secure deliveries. It provides a structured pre-deployment checklist, functional verifications, performance targets, and operational requirements for production readiness. Use it to standardize sign-off across engineering, QA, security, and product teams.

How this skill works

The skill organizes checks into areas: compilation, linting, testing, functionality (routing, data fetching, interactivity), performance, accessibility, SEO, security, mobile, browser compatibility, error handling, monitoring, and deployment. Each area lists concrete criteria, verification steps, commands to run, and pass/fail acceptance rules. Teams follow the checklist, run the specified audits and tests, and mark items for final sign-off and release readiness.

When to use it

  • Before running a production build or creating a release candidate
  • During release readiness reviews and QA sign-off meetings
  • When onboarding a new Next.js app or migrating to App Router
  • For performance, accessibility, or security audits prior to launch
  • When documenting deployment and rollback procedures

Best practices

  • Automate checks in CI: build, type-check, lint, tests, and bundle analysis
  • Keep strict thresholds for Core Web Vitals and test on throttled networks
  • Enforce ESLint/Prettier rules with CI gating and justify any disabled rules
  • Run E2E tests for navigation, forms, and critical paths; require coverage minimums
  • Use secure storage for secrets, set security headers, and validate API inputs

Example use cases

  • Pre-release pipeline that fails CI on TypeScript, lint, or test errors
  • Sprint completion criteria where accessibility and performance audits are mandatory
  • Security review checklist for protected routes, JWT handling, and headers
  • Performance optimization task using bundle-analyzer and Lighthouse targets
  • Production readiness playbook including monitoring, health checks, and rollback steps

FAQ

Target Core Web Vitals: LCP < 2.5s, FID < 100ms, CLS < 0.1; Lighthouse > 90 and initial JS bundle < 200KB gzipped.

What fails a pre-deployment check immediately?

Any TypeScript compilation errors, build failures, ESLint errors, failing tests for critical paths, security vulnerabilities, or accessibility violations deemed critical.

How should caching and invalidation be verified?

Check response Cache-Control headers, validate stale-while-revalidate behavior, test cache invalidation after updates, and simulate scenarios in the Network tab and on staging.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational