Skip to content
Back to skills

Nova Resource Patterns

ASecurity

Consistent Nova resources—fields, actions, metrics, lenses, filters, authorization—and how to evolve resources alongside schema changes

  • 147 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
databasestesting

Security analysis

A100/100

Scanned June 6, 2026

npx -y skills add jpcaparas/superpowers-laravel --skill nova-resource-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nova Resource Patterns?

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

Security grade badge for Nova Resource Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jpcaparas-nova-resource-patterns/badge)](https://www.skillsdirectory.com/skills/jpcaparas-nova-resource-patterns)

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: laravel:nova:resource-patterns
description: Consistent Nova resources—fields, actions, metrics, lenses, filters, authorization—and how to evolve resources alongside schema changes
---

# Nova Resource Patterns

Build consistent Nova resources that mirror domain models and evolve safely.

## Fields

- Keep fields ordered: identifiers → primary attributes → relations → meta
- Use `->sortable()`/`->filterable()` where it delivers value
- Hide sensitive fields (e.g., tokens) from index/detail unless necessary
- Prefer `BelongsTo`/`HasMany`/`Morph*` relations with searchable constraints

## Authorization

- Use Nova policies mirroring model policies for `viewAny`, `view`, `create`, `update`, `delete`
- Avoid leaking existence via unauthorized search; scope queries

## Actions

- Keep actions idempotent or provide safeguards
- Provide confirmation messages and clear result feedback

## Filters & Lenses

- Filters: simple, commonly used constraints (status, owner, date range)
- Lenses: opinionated, task‑centric views (e.g., stale items)

## Metrics

- Value/Trend/Partition metrics for essentials; cache appropriately
- Use explicit time ranges; label units clearly

## Resource Organization

- Group resources by domain (navigation grouping)
- Keep display titles meaningful; use `title()` consistently

## Testing

- Prefer feature tests that exercise policy + query scope + resource logic
- For actions, test success and failure states with realistic seed data

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.