القائمة
Map Hara Vital's Codex commands, including start-session/end-session, audits, bug hunts, feature starts, PR prep, and test scaffolding, so they trigger automatically from chat requests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build accessible React components with WCAG 2.1 Level AA compliance for Hara Vital. Use when creating interactive elements, forms, modals, bottom sheets, or any user-facing components. Triggers on "accessibility", "a11y", "ARIA", "keyboard", "focus", "screen reader", "WCAG".
Helps write conventional commit messages following Hara Vital standards. Triggers on "commit", "ready to commit", "push".
Hara Vital Supabase patterns — service-role client, RLS policies, attribution tokens, event tracking, and PQL billing flow. Triggers on "supabase", "database", "query", "API route", "service role", "RLS", "attribution", "token", "event", "PQL", "billing".
Hara Vital design system knowledge — tokens, liquid-glass patterns, animation easings, and UI conventions. Triggers on "style", "design", "component", "card", "button", "animation", "glass", "token", "color", "shadow", "UI".
Structured workflow for complex tasks requiring deliberate planning, step-by-step execution with pros/cons analysis, and built-in testing. Use when tasks involve multiple interdependent steps, code modifications, file operations, or any work where incremental validation prevents cascading errors. Particularly valuable for debugging, refactoring, system integration, or building complex features. Includes explicit triggers for consistent application across conversations and Codex CLI.
Enforce checking existing code before creating new implementations (USE → IMPROVE → ADD). Triggers on "create component", "add feature", "build", "new component", "new hook".
| name | tooling-registry |
| description | Map Hara Vital's Codex commands, including start-session/end-session, audits, bug hunts, feature starts, PR prep, and test scaffolding, so they trigger automatically from chat requests. |
Use this skill whenever a request matches any of the command phrases below or when a plan is required. It links natural-language triggers to the scripts/command docs we added under .codex/ so Codex can respond like Claude.
Session workflows are part of the primary trigger surface. If the user asks to start or end a session, run those workflows before falling back to a generic repo bootstrap.
| Trigger phrases | Action |
|---|---|
/start-session, "start session", "run start-session" | Follow .codex/commands/start-session/COMMAND.md: read the active plan (default .claude/plans/main.md), run node scripts/codex/git-session-summary.mjs "2 days ago", then brief context + next steps + blockers. |
/end-session, "end session", "run end-session" | Follow .codex/commands/end-session/COMMAND.md: run node scripts/codex/git-session-summary.mjs "today 00:00", append the new ### Session — YYYY-MM-DD block to the active plan, and report carryover items. |
/audit, "run audit on ", "complexity report" | Run node scripts/codex/audit.mjs <path>; include Markdown report from .codex/commands/audit/COMMAND.md. |
/bug-hunt, "find bugs in " | Follow .codex/commands/bug-hunt/COMMAND.md checklist, covering React/TS/Supabase patterns. |
/feature-start, "kick off feature", "plan feature" | Run through .codex/commands/feature-start/COMMAND.md (analysis, reuse check, checklist). |
/pr-prep, "prepare PR" | Execute node scripts/codex/pr-prep.mjs (build/lint/test + scans) and finish the manual checklist. |
/test-create, "add tests for " | Use .codex/commands/test-create/COMMAND.md templates for components/hooks/utils/API routes. |
When a trigger is detected, explicitly mention which command is running and summarize the results/output.
step-by-step-execution. Always save plans under docs/plans/ with descriptive filenames (e.g., docs/plans/feature-name.md).## Execution Plan
**Goal:** ...
**Steps:**
1. ...
- Action: ...
- Test: ...
update_plan in Codex CLI) so context stays current.