القائمة
Tech health check: documentation, security, architecture, data analysis. Use when user requests project audit, tech debt review, or health check.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Consolidated view of the add-pro ecosystem - commands, skills, relationships and dependencies. Loaded by /add as source of truth.
Source of truth for ADD doc rules, depth floors, IDs, refs, validation gate. Load before any doc write.
Use when running agent-judged QA validation (read-PNG by default; the playwright plugin adds live driving) — the Level C judge rubric, severity taxonomy, dual-judge (@ux-agent review ∥ @qa-agent) method, report schema/template, and the config.json/screens.json formats. Consumed by /add.qa and both judges.
Use when a state-materializing command starts or is asked to upgrade — reads the setup receipt, compares the recorded contract against the shipped one, executes the declared upgrade deltas sequentially, and rewrites the receipt even on a verified-current no-op. Consumed by /add.qa-setup STEP 1.5 and STEP 11.
Internal skill for developing ADD framework artefacts (commands, skills, agents, scripts). Use when add-framework--plan analyzes viability of new framework features, when add-framework--build implements framework artefacts, or when creating/modifying commands, skills, or agents. Always use this skill before proposing or implementing changes to the framework itself.
Use when building, styling, or theming UI components, pages, layouts, dashboards, charts, tables, or forms for SaaS products.
| name | add-health-check |
| description | Tech health check: documentation, security, architecture, data analysis. Use when user requests project audit, tech debt review, or health check. |
Suite of skills for complete technical analysis of the project. Always consult CLAUDE.md for general project standards.
/tech-health-check
├── PHASE 1 - DISCOVERY (parallel)
│ ├── context-discovery → architecture, multi-tenancy, modules
│ ├── documentation-analyzer → CLAUDE.md, patterns
│ └── infrastructure-check → MCP, env vars, deps
│
├── PHASE 2 - ANALYSIS (parallel, depends on Phase 1)
│ ├── security-analyzer → RLS, secrets, boundaries
│ ├── architecture-analyzer → clean arch, imports, CQRS
│ └── data-analyzer → migrations, indexes, N+1
│
└── PHASE 3 - CONSOLIDATION
└── HEALTH-REPORT.md → scorecard + roadmap
| Pillar | Level | Reason |
|---|---|---|
| Documentation | 🔴 Critical | impacts AI dev quality |
| Security | 🔴 Critical | data leaks, privacy |
| Architecture | 🟠 High | accumulating tech debt |
| Data | 🟡 Medium | performance, consistency |
| Infrastructure | 🔵 Info | prerequisite for analysis |
Phase 1: context-discovery → context-discovery.md; documentation-analyzer → documentation-report.md; infrastructure-check → infrastructure-report.md.
Phase 2: security-analyzer (deps: context, infrastructure) → security-report.md; architecture-analyzer (deps: context) → architecture-report.md; data-analyzer (deps: context, infrastructure) → data-report.md.
/tech-health-check
Process:
docs/health-checks/YYYY-MM-DD/ with current dateOutput files: context-discovery.md, documentation-report.md, infrastructure-report.md, security-report.md, architecture-report.md, data-report.md, HEALTH-REPORT.md.
Reports written for entrepreneurs who may not be technical — accessible style, prioritized critical → desirable. Language follows owner.md (default English); technical terms stay in EN; glossary included in HEALTH-REPORT.md.