メニュー
Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | frontend-patterns |
| description | Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only). |
| allowed-tools | Read, Grep |
Status: Not currently used. This repo is CLI + API server only -- no frontend.
When to activate: If a frontend is added, populate with framework-specific patterns.
Upstream reference: See docs/archive/harness-upstream/ for generic React/Next.js patterns from the SAW template.
Express API route implementation patterns with validation and error handling. Use when creating Express routes, implementing CRUD endpoints, adding server-side validation, handling webhooks, or implementing error handling. This project uses Express.js with direct pg queries -- no Next.js, no ORM.
Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only).
Database migration creation with mandatory RLS policies and ARCHitect approval workflow. Use when creating migrations, adding tables, or planning data migrations. Migrations are raw SQL files in `src/db/migrations/` with `XXX_description.sql` naming, registered in `index.ts`, auto-run on startup.
Pattern library discovery for pattern-first development. Use BEFORE implementing any new feature, creating components, writing API routes, or adding database operations. Ensures existing patterns are checked first.
Row Level Security patterns for database operations. Use when writing any database query, creating API routes that access data, implementing webhooks that write to the database, or working with user data. This project uses direct pg (node-postgres) queries with raw SQL -- no ORM.
Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, breaking down user stories, or translating business requirements to technical specs. Do NOT use for implementation work -- this is for planning and specification only.
