القائمة
Validates web frontend code (TypeScript, ESLint, unit tests) in the frontend/ directory
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | validate-frontend |
| description | Validates web frontend code (TypeScript, ESLint, unit tests) in the frontend/ directory |
| user-invocable | true |
CLAUDE: When this skill is invoked with /validate-frontend, run these commands in sequence:
cd frontend && bun run type-check && bun run lint && bun run test -- --run
Validates the web frontend codebase (Vite + React + TypeScript) for type safety, lint compliance, and test correctness.
/validate-frontend
cd frontend && bun run type-check
.ts and .tsx filestsconfig.json configurationcd frontend && bun run lint
cd frontend && bun run test -- --run
cd frontend && bun run type-check && bun run lint && bun run test -- --run
cd frontend && bun run test:e2e
cd frontend && bun run test:integration
cd frontend && bun run test:coverage
cd frontend && bun run test:ui
frontend-design - Design system complianceaccessibility-check - WCAG compliance auditdesign-review - Visual consistency reviewUse when designing prompts for LLMs, optimizing model performance, building evaluation frameworks, or implementing advanced prompting techniques like chain-of-thought, few-shot learning, or structured outputs.
How to deploy Dravr infrastructure and apply Cloud Run config changes. Use when editing infra/ terraform, when a merged code change is live but a Cloud Run setting (cpu, memory, min/max instances, env var, scaling) hasn't taken effect, or when asked to plan/apply infra. Explains the two-pipeline model (app binary auto-deploys on push; terraform infra config is a separate manual apply) plus the cpu/cpu_idle guardrails.
Enforces zero-tolerance code quality policy using Clippy with strict lints, all warnings treated as errors
Write well-formatted notes to the dravr-vault Obsidian knowledge base. Use this skill whenever creating or updating an ADR, runbook, plan, API doc, guide, session output, or any structured document that should land in the vault — even when the user doesn't say "Obsidian" explicitly. Delegates to obsidian:obsidian-cli to write to the live vault and applies Dravr frontmatter and formatting standards.
Bootstrap Pierre server with database, admin user, coaches, and test users for development and testing
Validates coach markdown files for required frontmatter fields, sections, and naming conventions