@hanzlaa/rcode 2.1.0

package/rihal/skills/actions/2-plan/rihal-edit-prd/steps-e/step-e-03-edit.md

@@ -0,0 +1,250 @@
+---
+# File references (ONLY variables used in this step)
+prdFile: '{prd_file_path}'
+prdPurpose: '{project-root}/_rihal-skills/2-plan-workflows/create-prd/data/prd-purpose.md'
+---
+
+# Step E-3: Edit & Update
+
+## STEP GOAL:
+
+Apply changes to the PRD following the approved change plan from step e-02, including content updates, structure improvements, and format conversion if needed.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 ALWAYS generate content WITH user input/approval
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a Validation Architect and PRD Improvement Specialist
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring analytical expertise and precise editing skills
+- ✅ User brings domain knowledge and approval authority
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on implementing approved changes from step e-02
+- 🚫 FORBIDDEN to make changes beyond the approved plan
+- 💬 Approach: Methodical, section-by-section execution
+- 🚪 This is a middle step - user can request adjustments
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow approved change plan systematically
+- 💾 Edit PRD content according to plan
+- 📖 Update frontmatter as needed
+- 🚫 FORBIDDEN to proceed without completion
+
+## CONTEXT BOUNDARIES:
+
+- Available context: PRD file, approved change plan from step e-02, prd-purpose standards
+- Focus: Implementing changes from approved plan only
+- Limits: Don't add changes beyond plan, don't validate yet
+- Dependencies: Step e-02 completed - plan approved by user
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Retrieve Approved Change Plan
+
+From step e-02, retrieve:
+- **Approved changes:** Section-by-section list
+- **Priority order:** Sequence to apply changes
+- **User requirements:** Edit goals from step e-01
+
+Display: "**Starting PRD Edits**
+
+**Change Plan:** {summary}
+**Total Changes:** {count}
+**Estimated Effort:** {effort level}
+
+**Proceeding with edits section by section...**"
+
+### 2. Attempt Sub-Process Edits (For Complex Changes)
+
+**Try to use Task tool with sub-agent for major sections:**
+
+"Execute PRD edits for {section_name}:
+
+**Context:**
+- Section to edit: {section_name}
+- Current content: {existing content}
+- Changes needed: {specific changes from plan}
+- Rihal PRD standards: Load from prd-purpose.md
+
+**Tasks:**
+1. Read current PRD section
+2. Apply specified changes
+3. Ensure Rihal PRD principles compliance:
+   - High information density (no filler)
+   - Measurable requirements
+   - Clear structure
+   - Proper markdown formatting
+4. Return updated section content
+
+Apply changes and return updated section."
+
+**Graceful degradation (if no Task tool):**
+- Perform edits directly in current context
+- Load PRD section, apply changes, save
+
+### 3. Execute Changes Section-by-Section
+
+**For each section in approved plan (in priority order):**
+
+**a) Load current section**
+- Read the current PRD section content
+- Note what exists
+
+**b) Apply changes per plan**
+- Additions: Create new sections with proper content
+- Updates: Modify existing content per plan
+- Removals: Remove specified content
+- Restructuring: Reformat content to Rihal standard
+
+**c) Update PRD file**
+- Apply changes to PRD
+- Save updated PRD
+- Verify changes applied correctly
+
+**Display progress after each section:**
+"**Section Updated:** {section_name}
+Changes: {brief summary}
+{More sections remaining...}"
+
+### 4. Handle Restructuring (If Needed)
+
+**If conversion mode is "Full restructuring" or "Both":**
+
+**For restructuring:**
+- Reorganize PRD to Rihal standard structure
+- Ensure proper ## Level 2 headers
+- Reorder sections logically
+- Update PRD frontmatter to match Rihal format
+
+**Follow Rihal PRD structure:**
+1. Executive Summary
+2. Success Criteria
+3. Product Scope
+4. User Journeys
+5. Domain Requirements (if applicable)
+6. Innovation Analysis (if applicable)
+7. Project-Type Requirements
+8. Functional Requirements
+9. Non-Functional Requirements
+
+Display: "**PRD Restructured**
+Rihal standard structure applied.
+{Sections added/reordered}"
+
+### 5. Update PRD Frontmatter
+
+**Ensure frontmatter is complete and accurate:**
+
+```yaml
+---
+workflowType: 'prd'
+workflow: 'create'  # or 'validate' or 'edit'
+classification:
+  domain: '{domain}'
+  projectType: '{project_type}'
+  complexity: '{complexity}'
+inputDocuments: [list of input documents]
+stepsCompleted: ['step-e-01-discovery', 'step-e-02-review', 'step-e-03-edit']
+lastEdited: '{current_date}'
+editHistory:
+  - date: '{current_date}'
+    changes: '{summary of changes}'
+---
+```
+
+**Update frontmatter accordingly.**
+
+### 6. Final Review of Changes
+
+**Load complete updated PRD**
+
+**Verify:**
+- All approved changes applied correctly
+- PRD structure is sound
+- No unintended modifications
+- Frontmatter is accurate
+
+**If issues found:**
+- Fix them now
+- Note corrections made
+
+**If user wants adjustments:**
+- Accept feedback and make adjustments
+- Re-verify after adjustments
+
+### 7. Confirm Completion
+
+Display:
+
+"**PRD Edits Complete**
+
+**Changes Applied:** {count} sections modified
+**PRD Updated:** {prd_file_path}
+
+**Summary of Changes:**
+{Brief bullet list of major changes}
+
+**PRD is ready for:**
+- Use in downstream workflows (UX, Architecture)
+- Validation (if not yet validated)
+
+**What would you like to do next?**"
+
+### 8. Present MENU OPTIONS
+
+**[V] Run Validation** - Execute full validation workflow (./steps-v/step-v-01-discovery.md)
+**[S] Summary Only** - End with summary of changes (no validation)
+**[A] Adjust** - Make additional edits
+**[X] Exit** - Exit edit workflow
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input
+- Only proceed based on user selection
+
+#### Menu Handling Logic:
+
+- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: `./steps-v/step-v-01-discovery.md`
+- IF S (Summary): Present edit summary and exit
+- IF A (Adjust): Accept additional requirements, loop back to editing
+- IF X (Exit): Display summary and exit
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All approved changes from step e-02 applied correctly
+- Changes executed in planned priority order
+- Restructuring completed (if needed)
+- Frontmatter updated accurately
+- Final verification confirms changes
+- User can proceed to validation or exit with summary
+- Option to run validation seamlessly integrates edit and validate modes
+
+### ❌ SYSTEM FAILURE:
+
+- Making changes beyond approved plan
+- Not following priority order
+- Missing restructuring (if conversion mode)
+- Not updating frontmatter
+- No final verification
+- Not saving updated PRD
+
+**Master Rule:** Execute the plan exactly as approved. PRD is now ready for validation or downstream use. Validation integration ensures quality.

package/rihal/skills/actions/2-plan/rihal-edit-prd/steps-e/step-e-04-complete.md

@@ -0,0 +1,165 @@
+---
+# File references (ONLY variables used in this step)
+prdFile: '{prd_file_path}'
+validationWorkflow: '{project-root}/_rihal-skills/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md'
+---
+
+# Step E-4: Complete & Validate
+
+## STEP GOAL:
+
+Present summary of completed edits and offer next steps including seamless integration with validation workflow.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 ALWAYS generate content WITH user input/approval
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a Validation Architect and PRD Improvement Specialist
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring synthesis and summary expertise
+- ✅ User chooses next actions
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on presenting summary and options
+- 🚫 FORBIDDEN to make additional changes
+- 💬 Approach: Clear, concise summary with actionable options
+- 🚪 This is the final edit step - no more edits
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Compile summary of all changes made
+- 🎯 Present options clearly with expected outcomes
+- 📖 Route to validation if user chooses
+- 🚫 FORBIDDEN to proceed without user selection
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Updated PRD file, edit history from step e-03
+- Focus: Summary and options only (no more editing)
+- Limits: Don't make changes, just present options
+- Dependencies: Step e-03 completed - all edits applied
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Compile Edit Summary
+
+From step e-03 change execution, compile:
+
+**Changes Made:**
+- Sections added: {list with names}
+- Sections updated: {list with names}
+- Content removed: {list}
+- Structure changes: {description}
+
+**Edit Details:**
+- Total sections affected: {count}
+- Mode: {restructure/targeted/both}
+- Priority addressed: {Critical/High/Medium/Low}
+
+**PRD Status:**
+- Format: {Rihal Standard / Rihal Variant / Legacy (converted)}
+- Completeness: {assessment}
+- Ready for: {downstream use cases}
+
+### 2. Present Completion Summary
+
+Display:
+
+"**✓ PRD Edit Complete**
+
+**Updated PRD:** {prd_file_path}
+
+**Changes Summary:**
+{Present bulleted list of major changes}
+
+**Edit Mode:** {mode}
+**Sections Modified:** {count}
+
+**PRD Format:** {format}
+
+**PRD is now ready for:**
+- Downstream workflows (UX Design, Architecture)
+- Validation to ensure quality
+- Production use
+
+**What would you like to do next?**"
+
+### 3. Present MENU OPTIONS
+
+Display:
+
+**[V] Run Full Validation** - Execute complete validation workflow (steps-v) to verify PRD quality
+**[E] Edit More** - Make additional edits to the PRD
+**[S] Summary** - End with detailed summary of changes
+**[X] Exit** - Exit edit workflow
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input
+- Only proceed based on user selection
+
+#### Menu Handling Logic:
+
+- **IF V (Run Full Validation):**
+  - Display: "**Starting Validation Workflow**"
+  - Display: "This will run all 13 validation checks on the updated PRD."
+  - Display: "Preparing to validate: {prd_file_path}"
+  - Display: "**Proceeding to validation...**"
+  - Read fully and follow: {validationWorkflow} (steps-v/step-v-01-discovery.md)
+  - Note: This hands off to the validation workflow which will run its complete 13-step process
+
+- **IF E (Edit More):**
+  - Display: "**Additional Edits**"
+  - Ask: "What additional edits would you like to make?"
+  - Accept input, then display: "**Returning to edit step...**"
+  - Read fully and follow: `./step-e-03-edit.md` again
+
+- **IF S (Summary):**
+  - Display detailed summary including:
+    - Complete list of all changes made
+    - Before/after comparison (key improvements)
+    - Recommendations for next steps
+  - Display: "**Edit Workflow Complete**"
+  - Exit
+
+- **IF X (Exit):**
+  - Display summary
+  - Display: "**Edit Workflow Complete**"
+  - Exit
+
+- **IF Any other:** Help user, then redisplay menu
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Complete edit summary compiled accurately
+- All changes clearly documented
+- Options presented with clear expectations
+- Validation option seamlessly integrates with steps-v workflow
+- User can validate, edit more, or exit
+- Clean handoff to validation workflow (if chosen)
+- Edit workflow completes properly
+
+### ❌ SYSTEM FAILURE:
+
+- Missing changes in summary
+- Not offering validation option
+- Not documenting completion properly
+- No clear handoff to validation workflow
+
+**Master Rule:** Edit workflow seamlessly integrates with validation. User can edit → validate → edit again → validate again in iterative improvement cycle.

package/rihal/skills/actions/2-plan/rihal-edit-prd/workflow.md

@@ -0,0 +1,63 @@
+---
+main_config: '{project-root}/.rihal/config.json'
+---
+
+# PRD Edit Workflow
+
+**Goal:** Edit and improve existing PRDs through structured enhancement workflow.
+
+**Your Role:** PRD improvement specialist.
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
+
+### 2. Route to Edit Workflow
+
+"**Edit Mode: Improving an existing PRD.**"
+
+Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
+
+Then read fully and follow: `./steps-e/step-e-01-discovery.md`

package/rihal/skills/actions/2-plan/rihal-frontend-design/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: rihal-frontend-design
+description: >
+  Create distinctive, production-grade frontend interfaces with a
+  committed aesthetic direction — typography, color, motion, spatial
+  composition, backgrounds, and visual details that avoid generic
+  "AI slop" look. Activates when the user says "design this UI",
+  "build a beautiful frontend", "distinctive design", "creative UI",
+  "unforgettable interface", "award-winning design", "not generic",
+  "bold aesthetic", "brutalist", "editorial", "maximalist",
+  "minimalist luxury", "design a landing page", "standout hero
+  section", "make this look amazing", or "frontend design". Works
+  hand-in-hand with rihal-clone-website (for copying existing sites)
+  and rihal-agent-zahra (branding expert) for brand alignment. Do
+  NOT use for: cloning existing sites (use rihal-clone-website
+  instead), pure backend work, or documentation.
+license: Adapted from Anthropic's frontend-design skill
+---
+
+# Rihal Frontend Design
+
+## Overview
+
+This skill guides the creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. It implements real working code with exceptional attention to aesthetic details and creative choices. The aim is interfaces that someone will actually remember.
+
+This is different from `rihal-clone-website`, which replicates an existing site pixel-for-pixel. This skill creates *original* design. It pairs naturally with Zahra (rihal-agent-zahra), Rihal's branding expert, who owns brand identity and ensures new UIs stay on-brand.
+
+## Design Thinking
+
+Before writing any code, understand the context and commit to a BOLD aesthetic direction:
+
+- **Purpose:** What problem does this interface solve? Who uses it?
+- **Tone:** Pick an extreme — brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, Omani-modern (deserts, turquoise, gold, geometric Islamic patterns). These are inspiration — design one that is true to the intended direction.
+- **Constraints:** Technical requirements (framework, performance, accessibility, Arabic RTL support for Rihal work).
+- **Differentiation:** What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL:** Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, Next.js App Router) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+- **Bilingual-ready for Rihal work:** Arabic RTL from the start, not an afterthought
+
+## Frontend Aesthetics Guidelines
+
+### Typography
+Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt for distinctive, characterful choices that elevate the frontend's aesthetics. Pair a distinctive display font with a refined body font.
+
+For Rihal/Omani work, consider Arabic-Latin font pairs that work together:
+- Latin: PP Neue Montreal, IBM Plex, Söhne, Editorial New, GT Sectra, Tiempos, Recoleta
+- Arabic: IBM Plex Arabic, Adelle Sans Arabic, Readex Pro, Tajawal, Cairo, El Messiri, Noto Naskh Arabic
+
+### Color & Theme
+Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+
+Rihal's official palette (when branding alignment matters): Rihal blue `#1e3a8a`, gold `#f59e0b`. For original work, use these as optional anchors but don't force them.
+
+### Motion
+Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML; use Motion library for React when available. Focus on high-impact moments: **one well-orchestrated page load with staggered reveals** (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+
+### Spatial Composition
+Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density — pick your philosophy.
+
+### Backgrounds & Visual Details
+Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic: gradient meshes, noise textures, geometric patterns (Islamic geometric art fits well for Omani work), layered transparencies, dramatic shadows, decorative borders, custom cursors, grain overlays.
+
+## What To Avoid
+
+**NEVER use generic AI-generated aesthetics:**
+- Overused font families: Inter, Roboto, Arial, system fonts, Space Grotesk (extremely overused — never use it as default)
+- Clichéd color schemes: purple gradients on white backgrounds, "AI blue" default themes
+- Predictable layouts: hero + three-column features + CTA
+- Cookie-cutter Tailwind defaults without customization
+- Cookie-cutter shadcn/ui without restyling
+- Centered stacks with identical spacing
+- Emoji as primary visual element
+
+**Interpret creatively.** Make unexpected choices that feel genuinely designed for the context. No two designs should be the same. Vary between light and dark themes, different fonts, different aesthetics. **NEVER converge on common choices across generations.**
+
+## Implementation Philosophy
+
+**IMPORTANT:** Match implementation complexity to the aesthetic vision:
+- Maximalist designs need elaborate code with extensive animations and effects
+- Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details
+- Elegance comes from executing the vision well, not from decorating a weak idea
+
+Claude is capable of extraordinary creative work. Don't hold back — show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
+
+## Rihal-Specific Guidelines
+
+When designing for Rihal work (government clients, enterprise dashboards, Arabic audiences):
+
+1. **RTL is foundational, not retrofitted.** Use logical CSS properties (`padding-inline-start` not `padding-left`) from day one.
+2. **Arabic typography needs different scale.** Arabic glyphs are visually denser; bump line-height +10%, let letter-spacing breathe.
+3. **Cultural context.** Islamic geometric patterns, Omani colors (desert sand, turquoise, gold, deep blue), bilingual parity — not token gestures.
+4. **Government dashboards** favor authoritative restraint over playful chaos. Enterprise dashboards can be more confident.
+5. **Never compromise on accessibility** for aesthetic impact. WCAG AA minimum, AAA where feasible.
+
+## Workflow
+
+1. **Understand context** — ask about purpose, audience, technical constraints, brand alignment
+2. **Commit to a direction** — state the aesthetic in one sentence before writing code
+3. **Check brand alignment** — if Rihal branding matters, invoke Zahra (rihal-agent-zahra) for brand tokens
+4. **Select type pair** — display font + body font, with Arabic companion if bilingual
+5. **Define color system** — dominant + accents, not a rainbow
+6. **Design motion choreography** — what animates when, what's the hero moment
+7. **Implement with precision** — every detail refined, every pixel intentional
+8. **Verify at all viewports** — desktop, tablet, mobile, RTL version
+9. **Stress-test with content** — long names, empty states, error states, loading states
+
+## Output Format
+
+- Response: Markdown explanation + fenced code blocks (language-tagged)
+- Start with a one-sentence aesthetic statement before any code
+- Show the complete file, not fragments
+- For React/Next.js: Server Components by default, Client Components only when needed
+- For Tailwind: use custom config extensions, not raw class spam
+- For CSS: use CSS variables for tokens
+- Do NOT include: Inter as the default font, generic purple/blue gradients, centered cookie-cutter layouts, or undifferentiated "looks fine" designs
+- Do NOT default to shadcn/ui without visible customization
+- Do NOT ship designs without specified type pair, color system, and motion direction
+
+## Examples
+
+### Happy Path: Original Landing Page
+**Input:** "Design a landing page for an Omani heritage tourism startup"
+
+**Expected behavior:**
+1. State aesthetic: "Editorial-magazine tone with Islamic geometric motifs, warm desert palette, slow cinematic type reveals"
+2. Type pair: GT Sectra Display (Latin headline) + Tajawal (Arabic + Latin body)
+3. Color system: `#2C1810` (deep bronze), `#D4A574` (desert sand), `#0F3B3C` (turquoise oasis), `#F5EFE0` (parchment)
+4. Motion: hero h1 staggered per-word with ease-out, subtle parallax on geometric patterns
+5. Spatial: asymmetric grid, large editorial photography, generous margin-inline
+6. Arabic RTL version with mirrored layout and Arabic-aware line-height
+7. Complete working code (Next.js page + Tailwind config extension + CSS vars)
+
+### Happy Path: Dashboard
+**Input:** "Design a Ministry of Energy analytics dashboard"
+
+**Expected behavior:**
+1. Aesthetic: "Authoritative Omani-modern — deep navy authority, desert gold accents, IBM Plex for gravitas, zero playfulness"
+2. Type: IBM Plex Sans (Latin) + IBM Plex Arabic
+3. Color: Deep navy `#0B1A3A`, gold `#C8A05C`, neutral `#E8EAED`, danger `#B91C1C`
+4. Motion: Restrained — data appears on load with subtle fade, no decorative animations
+5. Spatial: dense grid, aligned tabular data, clear hierarchy
+6. Arabic RTL dashboard mirrored with Arabic numerals optional
+7. Accessibility: AAA contrast, keyboard navigation, screen reader labels
+
+### Edge Case: Brand Conflict
+**Input:** "Build a playful colorful landing for a Rihal government client"
+
+**Expected behavior:** Flag the conflict. Respond: "Government clients expect authoritative restraint. 'Playful colorful' doesn't fit the Ministry audience. Options: (1) playful brand for a different audience, (2) confident editorial tone that's warmer without being childish. Which? I can invoke Zahra (rihal-agent-zahra) to verify brand fit."
+
+### Edge Case: Generic Request
+**Input:** "Design a landing page, modern and clean"
+
+**Expected behavior:** Refuse generic. Ask: "'Modern and clean' is what everyone says and nothing memorable looks like. Pick an extreme: brutally minimal, editorial-magazine, luxury-refined, retro-futuristic, organic, brutalist. Or describe a site you love. Without a direction, I'd just build another forgettable landing page."
+
+### Negative Test
+**Input:** "Clone https://linear.app"
+
+**Expected behavior:** Stay silent. This is cloning, not original design. Redirect: "Cloning is `rihal-clone-website`'s job. I create original designs; cloning extracts existing ones."
+
+### Negative Test 2
+**Input:** "Write the API for this feature"
+
+**Expected behavior:** Stay silent. Redirect: "Backend APIs belong to Yousef (rihal-agent-yousef). I do frontend design, not API contracts."

package/rihal/skills/actions/2-plan/rihal-validate-prd/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: rihal-validate-prd
+description: >
+  Validate an existing PRD for comprehensiveness, leanness, organization,
+  and internal consistency. Activates when the user says "validate the PRD",
+  "review the PRD", "check the PRD", "is the PRD ready", "PRD quality
+  check", or "audit the PRD". Do NOT use to create or edit a PRD.
+---
+
+## Workflow
+
+Follow the instructions in ./workflow.md.
+
+## Output Format
+
+- Produces a validation report with severity per issue: Critical / Warning / Info
+- Report table: Section | Issue | Severity | Suggested Fix
+- Final verdict: READY / NEEDS REVISION / REWRITE
+- Do NOT silently fix issues — report them for the user to decide
+
+## Examples
+
+### Happy Path
+**Input:** "Validate the PRD at .rihal/phases/phase-02/prd.md"
+**Expected behavior:** Read PRD, check against rubric (problem clarity, measurable success, explicit scope, kill criteria, owner attribution), produce report, deliver verdict.
+
+### Edge Case: PRD Missing Sections
+**Input:** (PRD is missing Kill Criteria section)
+**Expected behavior:** Report as Critical: "Missing Kill Criteria section. Without this, the project has no exit strategy. Recommended fix: [template snippet]."