formio/ai / plugin/skills/formio-angular/formio-angular-resources
formio-angular-resources
VerifiedAngular-only sub-skill: adds, regenerates, or repairs one resource NgModule in an Angular workspace whose `AppModule` already wires `FormioAppConfig`. Reached from `formio-angular`, or by phrasing that names Angular: "add an Angular module for X", "regenerate the Angular `Participant` resource module", "in my Angular app, wire `X`'s children to `Y`". Not for: creating the Angular app or wiring `FormioAppConfig` (see `formio-angular`); extension requests that never name Angular (see `formio-application`); data modelling alone (see `formio-resource-planner`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 30.3 KB |
| references/app-integration.md | markdown | 19.6 KB |
| references/interview-guide.md | markdown | 10.2 KB |
| references/phase-a-plan-template.md | markdown | 12.8 KB |
| references/resource-module-patterns.md | markdown | 34.3 KB |
| references/worked-example.md | markdown | 9.3 KB |
references/worked-example.md
View on GitHub# Worked example — Task Manager
> **`FormioAppConfig` renames both URLs.** `appUrl` is the **Project URL** — the project this application reads and writes, and the one value anyone supplies. `apiUrl` is the **Base URL** — the deployment hosting it, which is normally derived from the Project URL rather than supplied. Take both from `project_get` (called with `cwd` set to the workspace root) when the Form.io MCP tools are callable by you, and otherwise ask the user for them — see [`project-urls.md`](../../../formio-mcp-setup/references/project-urls.md). Never compose, derive, or hand-type either one yourself.
End-to-end walk-through of `../SKILL.md`'s flow: the planner's input, the Phase A Scaffolding Plan emitted for approval, and representative Phase B files.
**Input** (`template.md` from the planner — Task Manager; accompanying `template.json` not shown inline):
```
- Project (type: resource)
Fields: name, description
- Task (type: resource)
Fields: title, description, project (select Project), assignee (select User), status, dueDate
- ProjectUser (type: resource, join)
Fields: project (select Project), user (select User)
Actions: Group Permissions (group=project, user=user)
- User resource: default `user`
- Login form: userLogin
- Registration: userRegister
```
**Phase A plan** (emitted for approval):
```
## Scaffolding Plan — Task Manager
### Target workspace
- Workspace: `/Users/me/code/task-manager` (existing; `FormioAppConfig` not yet wired — this plan wires it)
- FormioAppConfig.appUrl: https://taskmanager.form.io
- UI framework: Bootstrap 5
### Files to create / modify
src/app/
app-module.ts MODIFY
app-routing-module.ts MODIFY
config.ts NEW
home/home.{ts,html,scss} NEW (legacy naming: home/home.component.*)
auth/auth.module.ts NEW
project/project.module.ts NEW
project/resource.component.{ts,html,scss} NEW (tabs: View / Tasks / Members / Edit / Delete)
project/view/view.component.{ts,html,scss} NEW (header card: name + description; side card: task count + member count + "New Task" button)
project/tasks/project-tasks.module.ts NEW (1:N, parents: ['project'])
project/tasks/resource.component.{ts,html,scss} NEW (breadcrumb back to project + task tabs)
project/tasks/view/view.component.{ts,html,scss} NEW (status badge, due-date pill, assignee, description)
project/users/project-users.module.ts NEW (N:N via ProjectUser — admin-only)
project/users/index/project-users-index.component.{ts,html} NEW (grid — user column renders as link to that user)
task/task.module.ts NEW
task/resource.component.{ts,html,scss} NEW (tabs: View / Edit / Delete)
task/view/view.component.{ts,html,scss} NEW (same view layout as project/tasks — shared view template pattern)
### Module & route map
The `name` and `form` columns are deliberately both shown: `name` is the camelCase registry key, `form` is the form's `path` from `template.json`, and on multi-word resources they diverge. Copying a `name` into a `form` is the failure `resource-module-patterns.md` → "`name` vs. `form` — DO NOT conflate these two" exists to prevent.
| Path | Module | `name` | `form` (= template.json path) | Parents |
| ------------------------------ | ------------------------ | ------------- | ----------------------------- | ------------- |
| `/auth/login` | AuthModule | — | `user/login` | — |
| `/auth/register` | AuthModule | — | `user/register` | — |
| `/project` | ProjectModule | `project` | `project` | — |
| `/project/:id/tasks` | ProjectTasksModule | `task` | `task` | ['project'] |
| `/project/:id/users` | ProjectUsersModule | `projectUser` | `project-user` | ['project'] |
| `/task` | TaskModule | `task` | `task` | — |
The auth rows have no `name` — they are `FormioAuthConfig.login.form` / `.register.form`, not resource modules, and they take the path for the same reason (`userLogin` there 404s on sign-in). `projectUser` is the row that shows the divergence: camelCase key, kebab-case path.
### UI design sketch per resource (for review)
- **Project.view**: 2-col Bootstrap grid. Left card — `<h3>{{ service.resource?.data.name }}</h3>` header, description body. Right card — "Team & Work" header, with count badges for tasks and members and a prominent "New Task" button linking to `./tasks/new`.
- **Task.view**: Header shows status as a color-coded badge (`status === 'done'` → green, `'in-progress'` → yellow, `'open'` → gray). Subheader: due-date formatted with Angular date pipe and relative-time indicator. Body: full description. Footer: assignee line.
- **ProjectUsers.index** (admin grid): override the index template so the `user` column renders as a link to `/user/:id/view` when the user resource is browsable; otherwise render the user's `data.email` inline.
### N:N joins
- ProjectUser: mounted on Project only (User side omitted — admin operation on the join, not a normal user view). Index grid column `user` → link to that user's profile (or omitted if no User CRUD).
### Auth
- `/auth/login` → the form at path `user/login`, and `/auth/register` → `user/register`, mounted as children of the `/auth` route the parent AUTH phase adds (the planner names those forms `userLogin` / `userRegister`; the config takes their `path`, never the name); logout is `FormioAuthService.logout()` redirecting to `/auth/login`. The auth routes stay unguarded.
- `authGuard` (`src/app/auth/auth.guard.ts`) applied via `canActivate: [authGuard]` on the root `/project` and `/task` routes in `app-routing-module.ts` (anonymous has no access per `## Access Matrix`). The nested `/project/:id/tasks` and `/project/:id/users` routes inherit protection from the guarded parent. Per-group narrowing stays server-side — no role/group guard.
```
**After approval, Phase B** writes the full file set. The module file is only part of the story — every resource also gets `resource.component.{ts,html,scss}` and `view/view.component.{ts,html,scss}` with designed templates. Here's `project.module.ts` wiring in the custom overrides:
```typescript
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { RouterModule } from '@angular/router';
import { FormioModule } from '@formio/angular';
import {
FormioResource,
FormioResourceRoutes,
FormioResourceConfig,
FormioResourceService,
} from '@formio/angular/resource';
import { ResourceComponent } from './resource.component';
import { ViewComponent } from './view/view.component';
const projectRoutes = FormioResourceRoutes({
resource: ResourceComponent,
view: ViewComponent,
});
projectRoutes[2].children!.push({
path: 'tasks',
loadChildren: () => import('./tasks/project-tasks.module').then((m) => m.ProjectTasksModule),
});
projectRoutes[2].children!.push({
path: 'users',
loadChildren: () => import('./users/project-users.module').then((m) => m.ProjectUsersModule),
});
@NgModule({
imports: [CommonModule, FormioModule, FormioResource, RouterModule.forChild(projectRoutes)],
declarations: [ResourceComponent, ViewComponent],
providers: [
FormioResourceService,
{
provide: FormioResourceConfig,
useValue: {
name: 'project', // camelCase registry key (single-word, so no divergence)
form: 'project', // === template.json form.path — coincides with `name` here only because the resource is single-word
} satisfies FormioResourceConfig,
},
],
})
export class ProjectModule {}
```
And here's the designed `view/view.component.html` that makes this resource feel like a Project page, not a generic form render:
```html
<div class="row g-3">
<div class="col-md-8">
<div class="card h-100">
<div class="card-body">
<h3 class="card-title mb-2">{{ service.resource?.data?.name }}</h3>
@if (service.resource?.data?.description) {
<p class="card-text text-muted">
{{ service.resource?.data?.description }}
</p>
}
</div>
</div>
</div>
<div class="col-md-4">
<div class="card h-100">
<div class="card-header">Team & Work</div>
<div class="card-body d-flex flex-column gap-2">
<a [routerLink]="['../tasks']" class="btn btn-outline-primary">View Tasks</a>
<a [routerLink]="['../tasks/new']" class="btn btn-primary">+ New Task</a>
<a [routerLink]="['../users']" class="btn btn-outline-secondary">Manage Members</a>
</div>
</div>
</div>
</div>
```
See `resource-module-patterns.md` for the complete worked set (every override template, nested Task module, N:N ProjectUsersIndexComponent, AppModule wiring, and the "Designing the ViewComponent from the resource's fields" recipe).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |