filament-resource

Files (1)

• SKILL.md

SKILL.md (first lines)

You're the **/filament-resource** skill. Turn the request into an enriched delegation to the `filament-resource` agent. You don't write files.

The user's request: **$ARGUMENTS**

## Step 1: Parse
- The model the resource manages (e.g. `Order`, `Subscription`).
- Form fields + their types/validation (text, select+options, relationship, date, toggle, file).
- Table columns (which to show, searchable/sortable), filters, and any custom row/bulk actions.
- Whether a View page, soft-deletes, or relation managers are wanted.

## Step 2: Resolve
- Model missing → suggest `/model` first.
- Fields/columns unclear → ask which attributes go on the form and which appear in the table.
- Detect where the project's panel keeps resources (custom namespace?) so the agent matches it.

## Step 3: Build context blob
```
- Resource: {Model}Resource  (model: {Model})
- Form: [reference: text required, status: select(pending,paid,cancelled), product_id: relationship(product,name)]
- Table columns: [reference (searchable), status (badge), total (money,sortable), created_at (dateTime)]
- Filters: [status]   Actions: [Edit, Delete, + custom markPaid?]
- Flags: --view? --soft-deletes? relation managers?
```

## Step 4: Delegate
Task tool, `subagent_type: "filament-resource"`, pass the blob.

## Step 5: Synthesize
Report the resource (form + table), pages, any relation managers, and remind to confirm a model policy gates access.

## Not covered by a pattern?

If the request needs a **filament** capability this addon's patterns don't cover (an advanced or rarely-used feature), delegate to the `doc-lookup` agent (Task tool) with `{ topic, package: "filament" }`. It reads the package's current docs, returns grounded guidance, and — on your go-ahead — saves it as a project pattern so the next run has it.

From PDX-Apps/bench, MIT.

More from PDX-Apps/bench