القائمة
Use when starting a new project — discovers founder profile and product blueprint, writes docs/owner.md + docs/product.md
التثبيت باستخدام 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-product-discovery |
| description | Use when starting a new project — discovers founder profile and product blueprint, writes docs/owner.md + docs/product.md |
Runs a quick founder + product discovery in 5–10 minutes, creating a communication profile and a development blueprint.
Principle: Speed over completeness. Infer based on market patterns. Simplify for MVP. Don't overload.
docs/owner.md or docs/product.md does not existdocs/owner.md + docs/product.md already populated/add.brainstorm or /add.new instead)/add.hotfix)Output: docs/owner.md. Goal: identify technical level + communication preferences.
Workflow:
docs/owner.md — if exists, ask whether to update or skipdocs/owner.md and commit: docs: create founder profile...Technical Level Inference:
Q1 = a AND Q3 ∈ {a, b} → leigo (non-technical)Q1 = b AND Q3 ∈ {a, b} → basicQ1 = c AND Q3 ∈ {a, b} → intermediateQ1 = d OR Q3 = c → technicalCommunication Style Inference:
Q2 = a → simplifiedQ2 = b → balancedQ2 = c → technicalOutput: docs/product.md. Goal: understand the product idea and create an MVP blueprint.
Workflow:
docs/product.md — if exists, ask whether to update or restart| Response depth | Action |
|---|---|
| Shallow (<20 words) | Ask 3 follow-up questions |
| Medium (20–100 words) | Proceed with targeted questions |
| Rich (100+ words) | Proceed to inference |
{{skill:add-doc-schemas/SKILL.md}} before writingdocs/product.md and commit: docs: create product blueprint for MVP.../add.brainstorm or /add.new for the first roadmap itemInference based on: market patterns (how 80% of similar products work), MVP mentality (minimum to validate), user context (what they emphasized), common sense (first-time user expectations).
| Vertical | Pattern |
|---|---|
| scheduling | 2 users (admin+client), calendar integration |
| ecommerce | 2 users (admin+client), payments mandatory |
| saas-b2b | multi-tenant, 3 users (owner, admin, member) |
| marketplace | 3 users (admin, seller, buyer), payments |
| internal-management | 1–2 users (admin, team?), no integration |
| courses | 2–3 users (admin, instructor?, student), payments |
| delivery | 3 users (admin, courier, client), geolocation |
Hybrid (human-readable + token-efficient). Load {{skill:add-doc-schemas/SKILL.md}} before writing.
| File | Sections |
|---|---|
owner.md | identification, technical level, communication preferences, project context |
product.md | what it is, for whom, problem solved, MVP features, cut features, user types, integrations, roadmap phases |
User: "I want an app to schedule appointments for a hair salon"