القائمة
Use when completing any task (final validation step), running audits, preparing for deployment, or when ESLint/TypeScript/build errors occur.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when creating or modifying any UI element visible to the user, reviewing HTML markup, adding interactive elements, or when Lighthouse Accessibility drops below 90.
Use when creating or modifying .astro/.tsx files, configuring astro.config.mjs, working with Content Collections, or when TypeScript or build errors occur.
Use when creating or editing pages, blog posts, or content files, adding meta tags, or when Lighthouse SEO drops below 90.
Use when writing or reviewing any CSS class, changing colors, modifying globals.css, or when hardcoded colors or inline styles are detected.
Use when creating or modifying any visible UI element, adjusting spacing or typography, reviewing visual consistency, or when Lighthouse Performance drops below 90.
Use when starting work on an AstroDeck project, needing to understand the project structure, or looking up available components, sections, and layouts.
| name | qa |
| description | Use when completing any task (final validation step), running audits, preparing for deployment, or when ESLint/TypeScript/build errors occur. |
This skill references the following globals — read them BEFORE starting work:
system/globals/responsiveness.md— Breakpoints, test order, anti-patterns
Testing, Validation, Code Quality, Launch Readiness
| Metric | Target | Measurement |
|---|---|---|
| Lighthouse Best Practices | >90 | Lighthouse JSON → categories.best-practices.score * 100 |
| ESLint Errors | 0 | npm run lint -- --format json |
| ESLint Warnings | 0 | npm run lint -- --format json |
| Formatting Issues | 0 | npm run format:check |
| HTML Validation Errors | 0 | npx html-validate dist/ |
# Full QA pipeline
npm run check:kpis # All static convention checks (single source of truth)
npm run lint # ESLint errors/warnings
npm run format:check # Prettier formatting
npx tsc --noEmit # TypeScript errors
npm run build # Astro build (0 errors, 0 warnings)
# or javascript:void(0))public/favicon.svg)public/og-image.png, 1200x630px)astro.config.mjsclient:load directives| Category | Minimum | Ideal |
|---|---|---|
| Performance | 90 | 95+ |
| Accessibility | 90 | 95+ |
| Best Practices | 90 | 95+ |
| SEO | 90 | 95+ |
These rules always apply — even under time pressure, even for "just a small update":
npm run build. "I only changed text" — content changes can also break the build (missing frontmatter fields, broken links).// eslint-disable-next-line is allowed, but only with an explanation of why the rule doesn't apply here.lint → format → tsc → build) takes under 30 seconds.Read LEARNINGS.md in this directory to avoid known anti-patterns.