メニュー
Scaffold a complete new feature page for the Grants Applicant Portal — creates component files, registers a lazy route, and optionally creates a core service.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Diagnose and fix a bug in the Grants Applicant Portal — takes a bug report or stack trace, locates the root cause, implements a targeted fix, and verifies with tests.
End-to-end ticket implementation for the Grants Applicant Portal — parses ticket details, architects a solution across frontend and/or backend, implements using specialist sub-agents in parallel, runs tests, and produces a PR-ready summary.
New developer orientation for the Grants Applicant Portal — tours the codebase, explains key architecture patterns, answers "how do I..." questions, and produces a personalised cheat sheet.
Refactor a component, service, or domain area in the Grants Applicant Portal — understands existing code, plans changes, implements via specialist sub-agents, and verifies nothing broke.
Full PR review for the Grants Applicant Portal — runs security, architecture/conventions, and test coverage reviews in parallel and produces a structured report ready to paste into GitHub.
Scaffold a complete FastEndpoints endpoint for the Grants Applicant Portal backend — creates the endpoint class, request, response, and validator files, then registers it within the domain folder.
| name | new-feature |
| description | Scaffold a complete new feature page for the Grants Applicant Portal — creates component files, registers a lazy route, and optionally creates a core service. |
Scaffold a complete new feature for the Grants Applicant Portal frontend.
Feature name (kebab-case): $ARGUMENTS
If $ARGUMENTS is empty, ask the user for the feature name before doing anything else.
Read existing features for patterns — read one existing feature component (e.g. src/app/features/workspace/workspace-selector.component.ts) so you match the exact coding style, decorator usage, and import patterns already in this project.
Create the feature folder and files under src/app/features/<name>/:
<name>.component.ts — standalone Angular component with selector: 'app-<name>'. Do not import CommonModule or RouterModule — use Angular 20's built-in control flow (@if, @for, @switch) in templates and import individual directives (RouterLink, RouterOutlet) only if the template needs them.<name>.component.html — minimal template with a wrapping <div> and a heading<name>.component.scss — empty placeholder<name>.component.spec.ts — basic TestBed spec that checks the component creates successfullyRegister the route in src/app/app.routes.ts — add a lazy-loaded route using loadComponent pointing at the new component. Choose a sensible URL path from the feature name. Place it in the correct position relative to existing routes (authenticated routes go after the auth guard is applied).
Check if a data service is needed — if the feature name implies data fetching (e.g. involves applicants, workspaces, payments), ask the user whether to also create a core/services/<name>.service.ts. If yes, create it following the pattern in step 1 (read an existing service first).
Report what was created — list every file created/modified with its path, and show the route entry that was added.
standalone: true)loadComponent (lazy), never eager import in routes*.module.ts) — this project does not use NgModules for featuresCommonModule or RouterModule — use Angular 20 control flow syntax and individual directive imports