Popravek besedila: učinkoviti komunikaciji -> vzpostavljanju učinkovite komunikacije

- Changed intro to focus on schools and kindergartens ordering workshops
- Reordered links: učenci priseljenci, starši učencev, starši otrok v vrtcih, zaposleni
- Updated link descriptions to be more specific about target groups

.gemini/commands/speckit.analyze.toml

@@ -0,0 +1,188 @@
+description = "Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation."
+
+prompt = """
+---
+description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Goal
+
+Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit.tasks` has successfully produced a complete `tasks.md`.
+
+## Operating Constraints
+
+**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
+
+**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit.analyze`.
+
+## Execution Steps
+
+### 1. Initialize Analysis Context
+
+Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
+
+- SPEC = FEATURE_DIR/spec.md
+- PLAN = FEATURE_DIR/plan.md
+- TASKS = FEATURE_DIR/tasks.md
+
+Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command).
+For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+
+### 2. Load Artifacts (Progressive Disclosure)
+
+Load only the minimal necessary context from each artifact:
+
+**From spec.md:**
+
+- Overview/Context
+- Functional Requirements
+- Non-Functional Requirements
+- User Stories
+- Edge Cases (if present)
+
+**From plan.md:**
+
+- Architecture/stack choices
+- Data Model references
+- Phases
+- Technical constraints
+
+**From tasks.md:**
+
+- Task IDs
+- Descriptions
+- Phase grouping
+- Parallel markers [P]
+- Referenced file paths
+
+**From constitution:**
+
+- Load `.specify/memory/constitution.md` for principle validation
+
+### 3. Build Semantic Models
+
+Create internal representations (do not include raw artifacts in output):
+
+- **Requirements inventory**: Each functional + non-functional requirement with a stable key (derive slug based on imperative phrase; e.g., "User can upload file" → `user-can-upload-file`)
+- **User story/action inventory**: Discrete user actions with acceptance criteria
+- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword / explicit reference patterns like IDs or key phrases)
+- **Constitution rule set**: Extract principle names and MUST/SHOULD normative statements
+
+### 4. Detection Passes (Token-Efficient Analysis)
+
+Focus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary.
+
+#### A. Duplication Detection
+
+- Identify near-duplicate requirements
+- Mark lower-quality phrasing for consolidation
+
+#### B. Ambiguity Detection
+
+- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria
+- Flag unresolved placeholders (TODO, TKTK, ???, `<placeholder>`, etc.)
+
+#### C. Underspecification
+
+- Requirements with verbs but missing object or measurable outcome
+- User stories missing acceptance criteria alignment
+- Tasks referencing files or components not defined in spec/plan
+
+#### D. Constitution Alignment
+
+- Any requirement or plan element conflicting with a MUST principle
+- Missing mandated sections or quality gates from constitution
+
+#### E. Coverage Gaps
+
+- Requirements with zero associated tasks
+- Tasks with no mapped requirement/story
+- Non-functional requirements not reflected in tasks (e.g., performance, security)
+
+#### F. Inconsistency
+
+- Terminology drift (same concept named differently across files)
+- Data entities referenced in plan but absent in spec (or vice versa)
+- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note)
+- Conflicting requirements (e.g., one requires Next.js while other specifies Vue)
+
+### 5. Severity Assignment
+
+Use this heuristic to prioritize findings:
+
+- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality
+- **HIGH**: Duplicate or conflicting requirement, ambiguous security/performance attribute, untestable acceptance criterion
+- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case
+- **LOW**: Style/wording improvements, minor redundancy not affecting execution order
+
+### 6. Produce Compact Analysis Report
+
+Output a Markdown report (no file writes) with the following structure:
+
+## Specification Analysis Report
+
+| ID | Category | Severity | Location(s) | Summary | Recommendation |
+|----|----------|----------|-------------|---------|----------------|
+| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version |
+
+(Add one row per finding; generate stable IDs prefixed by category initial.)
+
+**Coverage Summary Table:**
+
+| Requirement Key | Has Task? | Task IDs | Notes |
+|-----------------|-----------|----------|-------|
+
+**Constitution Alignment Issues:** (if any)
+
+**Unmapped Tasks:** (if any)
+
+**Metrics:**
+
+- Total Requirements
+- Total Tasks
+- Coverage % (requirements with >=1 task)
+- Ambiguity Count
+- Duplication Count
+- Critical Issues Count
+
+### 7. Provide Next Actions
+
+At end of report, output a concise Next Actions block:
+
+- If CRITICAL issues exist: Recommend resolving before `/speckit.implement`
+- If only LOW/MEDIUM: User may proceed, but provide improvement suggestions
+- Provide explicit command suggestions: e.g., "Run /speckit.specify with refinement", "Run /speckit.plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'"
+
+### 8. Offer Remediation
+
+Ask the user: "Would you like me to suggest concrete remediation edits for the top N issues?" (Do NOT apply them automatically.)
+
+## Operating Principles
+
+### Context Efficiency
+
+- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation
+- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis
+- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow
+- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts
+
+### Analysis Guidelines
+
+- **NEVER modify files** (this is read-only analysis)
+- **NEVER hallucinate missing sections** (if absent, report them accurately)
+- **Prioritize constitution violations** (these are always CRITICAL)
+- **Use examples over exhaustive rules** (cite specific instances, not generic patterns)
+- **Report zero issues gracefully** (emit success report with coverage statistics)
+
+## Context
+
+{{args}}
+"""

.gemini/commands/speckit.checklist.toml

@@ -0,0 +1,298 @@
+description = "Generate a custom checklist for the current feature based on user requirements."
+
+prompt = """
+---
+description: Generate a custom checklist for the current feature based on user requirements.
+---
+
+## Checklist Purpose: "Unit Tests for English"
+
+**CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain.
+
+**NOT for verification/testing**:
+
+- ❌ NOT "Verify the button clicks correctly"
+- ❌ NOT "Test error handling works"
+- ❌ NOT "Confirm the API returns 200"
+- ❌ NOT checking if code/implementation matches the spec
+
+**FOR requirements quality validation**:
+
+- ✅ "Are visual hierarchy requirements defined for all card types?" (completeness)
+- ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity)
+- ✅ "Are hover state requirements consistent across all interactive elements?" (consistency)
+- ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage)
+- ✅ "Does the spec define what happens when logo image fails to load?" (edge cases)
+
+**Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works.
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Execution Steps
+
+1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS list.
+   - All file paths must be absolute.
+   - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+
+2. **Clarify intent (dynamic)**: Derive up to THREE initial contextual clarifying questions (no pre-baked catalog). They MUST:
+   - Be generated from the user's phrasing + extracted signals from spec/plan/tasks
+   - Only ask about information that materially changes checklist content
+   - Be skipped individually if already unambiguous in `$ARGUMENTS`
+   - Prefer precision over breadth
+
+   Generation algorithm:
+   1. Extract signals: feature domain keywords (e.g., auth, latency, UX, API), risk indicators ("critical", "must", "compliance"), stakeholder hints ("QA", "review", "security team"), and explicit deliverables ("a11y", "rollback", "contracts").
+   2. Cluster signals into candidate focus areas (max 4) ranked by relevance.
+   3. Identify probable audience & timing (author, reviewer, QA, release) if not explicit.
+   4. Detect missing dimensions: scope breadth, depth/rigor, risk emphasis, exclusion boundaries, measurable acceptance criteria.
+   5. Formulate questions chosen from these archetypes:
+      - Scope refinement (e.g., "Should this include integration touchpoints with X and Y or stay limited to local module correctness?")
+      - Risk prioritization (e.g., "Which of these potential risk areas should receive mandatory gating checks?")
+      - Depth calibration (e.g., "Is this a lightweight pre-commit sanity list or a formal release gate?")
+      - Audience framing (e.g., "Will this be used by the author only or peers during PR review?")
+      - Boundary exclusion (e.g., "Should we explicitly exclude performance tuning items this round?")
+      - Scenario class gap (e.g., "No recovery flows detected—are rollback / partial failure paths in scope?")
+
+   Question formatting rules:
+   - If presenting options, generate a compact table with columns: Option | Candidate | Why It Matters
+   - Limit to A–E options maximum; omit table if a free-form answer is clearer
+   - Never ask the user to restate what they already said
+   - Avoid speculative categories (no hallucination). If uncertain, ask explicitly: "Confirm whether X belongs in scope."
+
+   Defaults when interaction impossible:
+   - Depth: Standard
+   - Audience: Reviewer (PR) if code-related; Author otherwise
+   - Focus: Top 2 relevance clusters
+
+   Output the questions (label Q1/Q2/Q3). After answers: if ≥2 scenario classes (Alternate / Exception / Recovery / Non-Functional domain) remain unclear, you MAY ask up to TWO more targeted follow‑ups (Q4/Q5) with a one-line justification each (e.g., "Unresolved recovery path risk"). Do not exceed five total questions. Skip escalation if user explicitly declines more.
+
+3. **Understand user request**: Combine `$ARGUMENTS` + clarifying answers:
+   - Derive checklist theme (e.g., security, review, deploy, ux)
+   - Consolidate explicit must-have items mentioned by user
+   - Map focus selections to category scaffolding
+   - Infer any missing context from spec/plan/tasks (do NOT hallucinate)
+
+4. **Load feature context**: Read from FEATURE_DIR:
+   - spec.md: Feature requirements and scope
+   - plan.md (if exists): Technical details, dependencies
+   - tasks.md (if exists): Implementation tasks
+
+   **Context Loading Strategy**:
+   - Load only necessary portions relevant to active focus areas (avoid full-file dumping)
+   - Prefer summarizing long sections into concise scenario/requirement bullets
+   - Use progressive disclosure: add follow-on retrieval only if gaps detected
+   - If source docs are large, generate interim summary items instead of embedding raw text
+
+5. **Generate checklist** - Create "Unit Tests for Requirements":
+   - Create `FEATURE_DIR/checklists/` directory if it doesn't exist
+   - Generate unique checklist filename:
+     - Use short, descriptive name based on domain (e.g., `ux.md`, `api.md`, `security.md`)
+     - Format: `[domain].md`
+     - If file exists, append to existing file
+   - Number items sequentially starting from CHK001
+   - Each `/speckit.checklist` run creates a NEW file (never overwrites existing checklists)
+
+   **CORE PRINCIPLE - Test the Requirements, Not the Implementation**:
+   Every checklist item MUST evaluate the REQUIREMENTS THEMSELVES for:
+   - **Completeness**: Are all necessary requirements present?
+   - **Clarity**: Are requirements unambiguous and specific?
+   - **Consistency**: Do requirements align with each other?
+   - **Measurability**: Can requirements be objectively verified?
+   - **Coverage**: Are all scenarios/edge cases addressed?
+
+   **Category Structure** - Group items by requirement quality dimensions:
+   - **Requirement Completeness** (Are all necessary requirements documented?)
+   - **Requirement Clarity** (Are requirements specific and unambiguous?)
+   - **Requirement Consistency** (Do requirements align without conflicts?)
+   - **Acceptance Criteria Quality** (Are success criteria measurable?)
+   - **Scenario Coverage** (Are all flows/cases addressed?)
+   - **Edge Case Coverage** (Are boundary conditions defined?)
+   - **Non-Functional Requirements** (Performance, Security, Accessibility, etc. - are they specified?)
+   - **Dependencies & Assumptions** (Are they documented and validated?)
+   - **Ambiguities & Conflicts** (What needs clarification?)
+
+   **HOW TO WRITE CHECKLIST ITEMS - "Unit Tests for English"**:
+
+   ❌ **WRONG** (Testing implementation):
+   - "Verify landing page displays 3 episode cards"
+   - "Test hover states work on desktop"
+   - "Confirm logo click navigates home"
+
+   ✅ **CORRECT** (Testing requirements quality):
+   - "Are the exact number and layout of featured episodes specified?" [Completeness]
+   - "Is 'prominent display' quantified with specific sizing/positioning?" [Clarity]
+   - "Are hover state requirements consistent across all interactive elements?" [Consistency]
+   - "Are keyboard navigation requirements defined for all interactive UI?" [Coverage]
+   - "Is the fallback behavior specified when logo image fails to load?" [Edge Cases]
+   - "Are loading states defined for asynchronous episode data?" [Completeness]
+   - "Does the spec define visual hierarchy for competing UI elements?" [Clarity]
+
+   **ITEM STRUCTURE**:
+   Each item should follow this pattern:
+   - Question format asking about requirement quality
+   - Focus on what's WRITTEN (or not written) in the spec/plan
+   - Include quality dimension in brackets [Completeness/Clarity/Consistency/etc.]
+   - Reference spec section `[Spec §X.Y]` when checking existing requirements
+   - Use `[Gap]` marker when checking for missing requirements
+
+   **EXAMPLES BY QUALITY DIMENSION**:
+
+   Completeness:
+   - "Are error handling requirements defined for all API failure modes? [Gap]"
+   - "Are accessibility requirements specified for all interactive elements? [Completeness]"
+   - "Are mobile breakpoint requirements defined for responsive layouts? [Gap]"
+
+   Clarity:
+   - "Is 'fast loading' quantified with specific timing thresholds? [Clarity, Spec §NFR-2]"
+   - "Are 'related episodes' selection criteria explicitly defined? [Clarity, Spec §FR-5]"
+   - "Is 'prominent' defined with measurable visual properties? [Ambiguity, Spec §FR-4]"
+
+   Consistency:
+   - "Do navigation requirements align across all pages? [Consistency, Spec §FR-10]"
+   - "Are card component requirements consistent between landing and detail pages? [Consistency]"
+
+   Coverage:
+   - "Are requirements defined for zero-state scenarios (no episodes)? [Coverage, Edge Case]"
+   - "Are concurrent user interaction scenarios addressed? [Coverage, Gap]"
+   - "Are requirements specified for partial data loading failures? [Coverage, Exception Flow]"
+
+   Measurability:
+   - "Are visual hierarchy requirements measurable/testable? [Acceptance Criteria, Spec §FR-1]"
+   - "Can 'balanced visual weight' be objectively verified? [Measurability, Spec §FR-2]"
+
+   **Scenario Classification & Coverage** (Requirements Quality Focus):
+   - Check if requirements exist for: Primary, Alternate, Exception/Error, Recovery, Non-Functional scenarios
+   - For each scenario class, ask: "Are [scenario type] requirements complete, clear, and consistent?"
+   - If scenario class missing: "Are [scenario type] requirements intentionally excluded or missing? [Gap]"
+   - Include resilience/rollback when state mutation occurs: "Are rollback requirements defined for migration failures? [Gap]"
+
+   **Traceability Requirements**:
+   - MINIMUM: ≥80% of items MUST include at least one traceability reference
+   - Each item should reference: spec section `[Spec §X.Y]`, or use markers: `[Gap]`, `[Ambiguity]`, `[Conflict]`, `[Assumption]`
+   - If no ID system exists: "Is a requirement & acceptance criteria ID scheme established? [Traceability]"
+
+   **Surface & Resolve Issues** (Requirements Quality Problems):
+   Ask questions about the requirements themselves:
+   - Ambiguities: "Is the term 'fast' quantified with specific metrics? [Ambiguity, Spec §NFR-1]"
+   - Conflicts: "Do navigation requirements conflict between §FR-10 and §FR-10a? [Conflict]"
+   - Assumptions: "Is the assumption of 'always available podcast API' validated? [Assumption]"
+   - Dependencies: "Are external podcast API requirements documented? [Dependency, Gap]"
+   - Missing definitions: "Is 'visual hierarchy' defined with measurable criteria? [Gap]"
+
+   **Content Consolidation**:
+   - Soft cap: If raw candidate items > 40, prioritize by risk/impact
+   - Merge near-duplicates checking the same requirement aspect
+   - If >5 low-impact edge cases, create one item: "Are edge cases X, Y, Z addressed in requirements? [Coverage]"
+
+   **🚫 ABSOLUTELY PROHIBITED** - These make it an implementation test, not a requirements test:
+   - ❌ Any item starting with "Verify", "Test", "Confirm", "Check" + implementation behavior
+   - ❌ References to code execution, user actions, system behavior
+   - ❌ "Displays correctly", "works properly", "functions as expected"
+   - ❌ "Click", "navigate", "render", "load", "execute"
+   - ❌ Test cases, test plans, QA procedures
+   - ❌ Implementation details (frameworks, APIs, algorithms)
+
+   **✅ REQUIRED PATTERNS** - These test requirements quality:
+   - ✅ "Are [requirement type] defined/specified/documented for [scenario]?"
+   - ✅ "Is [vague term] quantified/clarified with specific criteria?"
+   - ✅ "Are requirements consistent between [section A] and [section B]?"
+   - ✅ "Can [requirement] be objectively measured/verified?"
+   - ✅ "Are [edge cases/scenarios] addressed in requirements?"
+   - ✅ "Does the spec define [missing aspect]?"
+
+6. **Structure Reference**: Generate the checklist following the canonical template in `.specify/templates/checklist-template.md` for title, meta section, category headings, and ID formatting. If template is unavailable, use: H1 title, purpose/created meta lines, `##` category sections containing `- [ ] CHK### <requirement item>` lines with globally incrementing IDs starting at CHK001.
+
+7. **Report**: Output full path to created checklist, item count, and remind user that each run creates a new file. Summarize:
+   - Focus areas selected
+   - Depth level
+   - Actor/timing
+   - Any explicit user-specified must-have items incorporated
+
+**Important**: Each `/speckit.checklist` command invocation creates a checklist file using short, descriptive names unless file already exists. This allows:
+
+- Multiple checklists of different types (e.g., `ux.md`, `test.md`, `security.md`)
+- Simple, memorable filenames that indicate checklist purpose
+- Easy identification and navigation in the `checklists/` folder
+
+To avoid clutter, use descriptive types and clean up obsolete checklists when done.
+
+## Example Checklist Types & Sample Items
+
+**UX Requirements Quality:** `ux.md`
+
+Sample items (testing the requirements, NOT the implementation):
+
+- "Are visual hierarchy requirements defined with measurable criteria? [Clarity, Spec §FR-1]"
+- "Is the number and positioning of UI elements explicitly specified? [Completeness, Spec §FR-1]"
+- "Are interaction state requirements (hover, focus, active) consistently defined? [Consistency]"
+- "Are accessibility requirements specified for all interactive elements? [Coverage, Gap]"
+- "Is fallback behavior defined when images fail to load? [Edge Case, Gap]"
+- "Can 'prominent display' be objectively measured? [Measurability, Spec §FR-4]"
+
+**API Requirements Quality:** `api.md`
+
+Sample items:
+
+- "Are error response formats specified for all failure scenarios? [Completeness]"
+- "Are rate limiting requirements quantified with specific thresholds? [Clarity]"
+- "Are authentication requirements consistent across all endpoints? [Consistency]"
+- "Are retry/timeout requirements defined for external dependencies? [Coverage, Gap]"
+- "Is versioning strategy documented in requirements? [Gap]"
+
+**Performance Requirements Quality:** `performance.md`
+
+Sample items:
+
+- "Are performance requirements quantified with specific metrics? [Clarity]"
+- "Are performance targets defined for all critical user journeys? [Coverage]"
+- "Are performance requirements under different load conditions specified? [Completeness]"
+- "Can performance requirements be objectively measured? [Measurability]"
+- "Are degradation requirements defined for high-load scenarios? [Edge Case, Gap]"
+
+**Security Requirements Quality:** `security.md`
+
+Sample items:
+
+- "Are authentication requirements specified for all protected resources? [Coverage]"
+- "Are data protection requirements defined for sensitive information? [Completeness]"
+- "Is the threat model documented and requirements aligned to it? [Traceability]"
+- "Are security requirements consistent with compliance obligations? [Consistency]"
+- "Are security failure/breach response requirements defined? [Gap, Exception Flow]"
+
+## Anti-Examples: What NOT To Do
+
+**❌ WRONG - These test implementation, not requirements:**
+
+```markdown
+- [ ] CHK001 - Verify landing page displays 3 episode cards [Spec §FR-001]
+- [ ] CHK002 - Test hover states work correctly on desktop [Spec §FR-003]
+- [ ] CHK003 - Confirm logo click navigates to home page [Spec §FR-010]
+- [ ] CHK004 - Check that related episodes section shows 3-5 items [Spec §FR-005]
+```
+
+**✅ CORRECT - These test requirements quality:**
+
+```markdown
+- [ ] CHK001 - Are the number and layout of featured episodes explicitly specified? [Completeness, Spec §FR-001]
+- [ ] CHK002 - Are hover state requirements consistently defined for all interactive elements? [Consistency, Spec §FR-003]
+- [ ] CHK003 - Are navigation requirements clear for all clickable brand elements? [Clarity, Spec §FR-010]
+- [ ] CHK004 - Is the selection criteria for related episodes documented? [Gap, Spec §FR-005]
+- [ ] CHK005 - Are loading state requirements defined for asynchronous episode data? [Gap]
+- [ ] CHK006 - Can "visual hierarchy" requirements be objectively measured? [Measurability, Spec §FR-001]
+```
+
+**Key Differences:**
+
+- Wrong: Tests if the system works correctly
+- Correct: Tests if the requirements are written correctly
+- Wrong: Verification of behavior
+- Correct: Validation of requirement quality
+- Wrong: "Does it do X?"
+- Correct: "Is X clearly specified?"
+"""

.gemini/commands/speckit.clarify.toml

@@ -0,0 +1,185 @@
+description = "Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec."
+
+prompt = """
+---
+description: Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
+handoffs: 
+  - label: Build Technical Plan
+    agent: speckit.plan
+    prompt: Create a plan for the spec. I am building with...
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.
+
+Note: This clarification workflow is expected to run (and be completed) BEFORE invoking `/speckit.plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.
+
+Execution steps:
+
+1. Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` from repo root **once** (combined `--json --paths-only` mode / `-Json -PathsOnly`). Parse minimal JSON payload fields:
+   - `FEATURE_DIR`
+   - `FEATURE_SPEC`
+   - (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)
+   - If JSON parsing fails, abort and instruct user to re-run `/speckit.specify` or verify feature branch environment.
+   - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+
+2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce an internal coverage map used for prioritization (do not output raw map unless no questions will be asked).
+
+   Functional Scope & Behavior:
+   - Core user goals & success criteria
+   - Explicit out-of-scope declarations
+   - User roles / personas differentiation
+
+   Domain & Data Model:
+   - Entities, attributes, relationships
+   - Identity & uniqueness rules
+   - Lifecycle/state transitions
+   - Data volume / scale assumptions
+
+   Interaction & UX Flow:
+   - Critical user journeys / sequences
+   - Error/empty/loading states
+   - Accessibility or localization notes
+
+   Non-Functional Quality Attributes:
+   - Performance (latency, throughput targets)
+   - Scalability (horizontal/vertical, limits)
+   - Reliability & availability (uptime, recovery expectations)
+   - Observability (logging, metrics, tracing signals)
+   - Security & privacy (authN/Z, data protection, threat assumptions)
+   - Compliance / regulatory constraints (if any)
+
+   Integration & External Dependencies:
+   - External services/APIs and failure modes
+   - Data import/export formats
+   - Protocol/versioning assumptions
+
+   Edge Cases & Failure Handling:
+   - Negative scenarios
+   - Rate limiting / throttling
+   - Conflict resolution (e.g., concurrent edits)
+
+   Constraints & Tradeoffs:
+   - Technical constraints (language, storage, hosting)
+   - Explicit tradeoffs or rejected alternatives
+
+   Terminology & Consistency:
+   - Canonical glossary terms
+   - Avoided synonyms / deprecated terms
+
+   Completion Signals:
+   - Acceptance criteria testability
+   - Measurable Definition of Done style indicators
+
+   Misc / Placeholders:
+   - TODO markers / unresolved decisions
+   - Ambiguous adjectives ("robust", "intuitive") lacking quantification
+
+   For each category with Partial or Missing status, add a candidate question opportunity unless:
+   - Clarification would not materially change implementation or validation strategy
+   - Information is better deferred to planning phase (note internally)
+
+3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints:
+    - Maximum of 10 total questions across the whole session.
+    - Each question must be answerable with EITHER:
+       - A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR
+       - A one-word / short‑phrase answer (explicitly constrain: "Answer in <=5 words").
+    - Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation.
+    - Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved.
+    - Exclude questions already answered, trivial stylistic preferences, or plan-level execution details (unless blocking correctness).
+    - Favor clarifications that reduce downstream rework risk or prevent misaligned acceptance tests.
+    - If more than 5 categories remain unresolved, select the top 5 by (Impact * Uncertainty) heuristic.
+
+4. Sequential questioning loop (interactive):
+    - Present EXACTLY ONE question at a time.
+    - For multiple‑choice questions:
+       - **Analyze all options** and determine the **most suitable option** based on:
+          - Best practices for the project type
+          - Common patterns in similar implementations
+          - Risk reduction (security, performance, maintainability)
+          - Alignment with any explicit project goals or constraints visible in the spec
+       - Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice).
+       - Format as: `**Recommended:** Option [X] - <reasoning>`
+       - Then render all options as a Markdown table:
+
+       | Option | Description |
+       |--------|-------------|
+       | A | <Option A description> |
+       | B | <Option B description> |
+       | C | <Option C description> (add D/E as needed up to 5) |
+       | Short | Provide a different short answer (<=5 words) (Include only if free-form alternative is appropriate) |
+
+       - After the table, add: `You can reply with the option letter (e.g., "A"), accept the recommendation by saying "yes" or "recommended", or provide your own short answer.`
+    - For short‑answer style (no meaningful discrete options):
+       - Provide your **suggested answer** based on best practices and context.
+       - Format as: `**Suggested:** <your proposed answer> - <brief reasoning>`
+       - Then output: `Format: Short answer (<=5 words). You can accept the suggestion by saying "yes" or "suggested", or provide your own answer.`
+    - After the user answers:
+       - If the user replies with "yes", "recommended", or "suggested", use your previously stated recommendation/suggestion as the answer.
+       - Otherwise, validate the answer maps to one option or fits the <=5 word constraint.
+       - If ambiguous, ask for a quick disambiguation (count still belongs to same question; do not advance).
+       - Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.
+    - Stop asking further questions when:
+       - All critical ambiguities resolved early (remaining queued items become unnecessary), OR
+       - User signals completion ("done", "good", "no more"), OR
+       - You reach 5 asked questions.
+    - Never reveal future queued questions in advance.
+    - If no valid questions exist at start, immediately report no critical ambiguities.
+
+5. Integration after EACH accepted answer (incremental update approach):
+    - Maintain in-memory representation of the spec (loaded once at start) plus the raw file contents.
+    - For the first integrated answer in this session:
+       - Ensure a `## Clarifications` section exists (create it just after the highest-level contextual/overview section per the spec template if missing).
+       - Under it, create (if not present) a `### Session YYYY-MM-DD` subheading for today.
+    - Append a bullet line immediately after acceptance: `- Q: <question> → A: <final answer>`.
+    - Then immediately apply the clarification to the most appropriate section(s):
+       - Functional ambiguity → Update or add a bullet in Functional Requirements.
+       - User interaction / actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.
+       - Data shape / entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.
+       - Non-functional constraint → Add/modify measurable criteria in Non-Functional / Quality Attributes section (convert vague adjective to metric or explicit target).
+       - Edge case / negative flow → Add a new bullet under Edge Cases / Error Handling (or create such subsection if template provides placeholder for it).
+       - Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as "X")` once.
+    - If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.
+    - Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).
+    - Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.
+    - Keep each inserted clarification minimal and testable (avoid narrative drift).
+
+6. Validation (performed after EACH write plus final pass):
+   - Clarifications session contains exactly one bullet per accepted answer (no duplicates).
+   - Total asked (accepted) questions ≤ 5.
+   - Updated sections contain no lingering vague placeholders the new answer was meant to resolve.
+   - No contradictory earlier statement remains (scan for now-invalid alternative choices removed).
+   - Markdown structure valid; only allowed new headings: `## Clarifications`, `### Session YYYY-MM-DD`.
+   - Terminology consistency: same canonical term used across all updated sections.
+
+7. Write the updated spec back to `FEATURE_SPEC`.
+
+8. Report completion (after questioning loop ends or early termination):
+   - Number of questions asked & answered.
+   - Path to updated spec.
+   - Sections touched (list names).
+   - Coverage summary table listing each taxonomy category with Status: Resolved (was Partial/Missing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial/Missing but low impact).
+   - If any Outstanding or Deferred remain, recommend whether to proceed to `/speckit.plan` or run `/speckit.clarify` again later post-plan.
+   - Suggested next command.
+
+Behavior rules:
+
+- If no meaningful ambiguities found (or all potential questions would be low-impact), respond: "No critical ambiguities detected worth formal clarification." and suggest proceeding.
+- If spec file missing, instruct user to run `/speckit.specify` first (do not create a new spec here).
+- Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).
+- Avoid speculative tech stack questions unless the absence blocks functional clarity.
+- Respect user early termination signals ("stop", "done", "proceed").
+- If no questions asked due to full coverage, output a compact coverage summary (all categories Clear) then suggest advancing.
+- If quota reached with unresolved high-impact categories remaining, explicitly flag them under Deferred with rationale.
+
+Context for prioritization: {{args}}
+"""

.gemini/commands/speckit.constitution.toml

@@ -0,0 +1,86 @@
+description = "Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync."
+
+prompt = """
+---
+description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
+handoffs: 
+  - label: Build Specification
+    agent: speckit.specify
+    prompt: Implement the feature specification based on the updated constitution. I want to build...
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+You are updating the project constitution at `.specify/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
+
+Follow this execution flow:
+
+1. Load the existing constitution template at `.specify/memory/constitution.md`.
+   - Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
+   **IMPORTANT**: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
+
+2. Collect/derive values for placeholders:
+   - If user input (conversation) supplies a value, use it.
+   - Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
+   - For governance dates: `RATIFICATION_DATE` is the original adoption date (if unknown ask or mark TODO), `LAST_AMENDED_DATE` is today if changes are made, otherwise keep previous.
+   - `CONSTITUTION_VERSION` must increment according to semantic versioning rules:
+     - MAJOR: Backward incompatible governance/principle removals or redefinitions.
+     - MINOR: New principle/section added or materially expanded guidance.
+     - PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
+   - If version bump type ambiguous, propose reasoning before finalizing.
+
+3. Draft the updated constitution content:
+   - Replace every placeholder with concrete text (no bracketed tokens left except intentionally retained template slots that the project has chosen not to define yet—explicitly justify any left).
+   - Preserve heading hierarchy and comments can be removed once replaced unless they still add clarifying guidance.
+   - Ensure each Principle section: succinct name line, paragraph (or bullet list) capturing non‑negotiable rules, explicit rationale if not obvious.
+   - Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
+
+4. Consistency propagation checklist (convert prior checklist into active validations):
+   - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
+   - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
+   - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
+   - Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
+   - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
+
+5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
+   - Version change: old → new
+   - List of modified principles (old title → new title if renamed)
+   - Added sections
+   - Removed sections
+   - Templates requiring updates (✅ updated / ⚠ pending) with file paths
+   - Follow-up TODOs if any placeholders intentionally deferred.
+
+6. Validation before final output:
+   - No remaining unexplained bracket tokens.
+   - Version line matches report.
+   - Dates ISO format YYYY-MM-DD.
+   - Principles are declarative, testable, and free of vague language ("should" → replace with MUST/SHOULD rationale where appropriate).
+
+7. Write the completed constitution back to `.specify/memory/constitution.md` (overwrite).
+
+8. Output a final summary to the user with:
+   - New version and bump rationale.
+   - Any files flagged for manual follow-up.
+   - Suggested commit message (e.g., `docs: amend constitution to vX.Y.Z (principle additions + governance update)`).
+
+Formatting & Style Requirements:
+
+- Use Markdown headings exactly as in the template (do not demote/promote levels).
+- Wrap long rationale lines to keep readability (<100 chars ideally) but do not hard enforce with awkward breaks.
+- Keep a single blank line between sections.
+- Avoid trailing whitespace.
+
+If the user supplies partial updates (e.g., only one principle revision), still perform validation and version decision steps.
+
+If critical info missing (e.g., ratification date truly unknown), insert `TODO(<FIELD_NAME>): explanation` and include in the Sync Impact Report under deferred items.
+
+Do not create a new template; always operate on the existing `.specify/memory/constitution.md` file.
+"""

.gemini/commands/speckit.implement.toml

@@ -0,0 +1,139 @@
+description = "Execute the implementation plan by processing and executing all tasks defined in tasks.md"
+
+prompt = """
+---
+description: Execute the implementation plan by processing and executing all tasks defined in tasks.md
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+
+2. **Check checklists status** (if FEATURE_DIR/checklists/ exists):
+   - Scan all checklist files in the checklists/ directory
+   - For each checklist, count:
+     - Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`
+     - Completed items: Lines matching `- [X]` or `- [x]`
+     - Incomplete items: Lines matching `- [ ]`
+   - Create a status table:
+
+     ```text
+     | Checklist | Total | Completed | Incomplete | Status |
+     |-----------|-------|-----------|------------|--------|
+     | ux.md     | 12    | 12        | 0          | ✓ PASS |
+     | test.md   | 8     | 5         | 3          | ✗ FAIL |
+     | security.md | 6   | 6         | 0          | ✓ PASS |
+     ```
+
+   - Calculate overall status:
+     - **PASS**: All checklists have 0 incomplete items
+     - **FAIL**: One or more checklists have incomplete items
+
+   - **If any checklist is incomplete**:
+     - Display the table with incomplete item counts
+     - **STOP** and ask: "Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes/no)"
+     - Wait for user response before continuing
+     - If user says "no" or "wait" or "stop", halt execution
+     - If user says "yes" or "proceed" or "continue", proceed to step 3
+
+   - **If all checklists are complete**:
+     - Display the table showing all checklists passed
+     - Automatically proceed to step 3
+
+3. Load and analyze the implementation context:
+   - **REQUIRED**: Read tasks.md for the complete task list and execution plan
+   - **REQUIRED**: Read plan.md for tech stack, architecture, and file structure
+   - **IF EXISTS**: Read data-model.md for entities and relationships
+   - **IF EXISTS**: Read contracts/ for API specifications and test requirements
+   - **IF EXISTS**: Read research.md for technical decisions and constraints
+   - **IF EXISTS**: Read quickstart.md for integration scenarios
+
+4. **Project Setup Verification**:
+   - **REQUIRED**: Create/verify ignore files based on actual project setup:
+
+   **Detection & Creation Logic**:
+   - Check if the following command succeeds to determine if the repository is a git repo (create/verify .gitignore if so):
+
+     ```sh
+     git rev-parse --git-dir 2>/dev/null
+     ```
+
+   - Check if Dockerfile* exists or Docker in plan.md → create/verify .dockerignore
+   - Check if .eslintrc* exists → create/verify .eslintignore
+   - Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns
+   - Check if .prettierrc* exists → create/verify .prettierignore
+   - Check if .npmrc or package.json exists → create/verify .npmignore (if publishing)
+   - Check if terraform files (*.tf) exist → create/verify .terraformignore
+   - Check if .helmignore needed (helm charts present) → create/verify .helmignore
+
+   **If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only
+   **If ignore file missing**: Create with full pattern set for detected technology
+
+   **Common Patterns by Technology** (from plan.md tech stack):
+   - **Node.js/JavaScript/TypeScript**: `node_modules/`, `dist/`, `build/`, `*.log`, `.env*`
+   - **Python**: `__pycache__/`, `*.pyc`, `.venv/`, `venv/`, `dist/`, `*.egg-info/`
+   - **Java**: `target/`, `*.class`, `*.jar`, `.gradle/`, `build/`
+   - **C#/.NET**: `bin/`, `obj/`, `*.user`, `*.suo`, `packages/`
+   - **Go**: `*.exe`, `*.test`, `vendor/`, `*.out`
+   - **Ruby**: `.bundle/`, `log/`, `tmp/`, `*.gem`, `vendor/bundle/`
+   - **PHP**: `vendor/`, `*.log`, `*.cache`, `*.env`
+   - **Rust**: `target/`, `debug/`, `release/`, `*.rs.bk`, `*.rlib`, `*.prof*`, `.idea/`, `*.log`, `.env*`
+   - **Kotlin**: `build/`, `out/`, `.gradle/`, `.idea/`, `*.class`, `*.jar`, `*.iml`, `*.log`, `.env*`
+   - **C++**: `build/`, `bin/`, `obj/`, `out/`, `*.o`, `*.so`, `*.a`, `*.exe`, `*.dll`, `.idea/`, `*.log`, `.env*`
+   - **C**: `build/`, `bin/`, `obj/`, `out/`, `*.o`, `*.a`, `*.so`, `*.exe`, `Makefile`, `config.log`, `.idea/`, `*.log`, `.env*`
+   - **Swift**: `.build/`, `DerivedData/`, `*.swiftpm/`, `Packages/`
+   - **R**: `.Rproj.user/`, `.Rhistory`, `.RData`, `.Ruserdata`, `*.Rproj`, `packrat/`, `renv/`
+   - **Universal**: `.DS_Store`, `Thumbs.db`, `*.tmp`, `*.swp`, `.vscode/`, `.idea/`
+
+   **Tool-Specific Patterns**:
+   - **Docker**: `node_modules/`, `.git/`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage/`
+   - **ESLint**: `node_modules/`, `dist/`, `build/`, `coverage/`, `*.min.js`
+   - **Prettier**: `node_modules/`, `dist/`, `build/`, `coverage/`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`
+   - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`
+   - **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt`
+
+5. Parse tasks.md structure and extract:
+   - **Task phases**: Setup, Tests, Core, Integration, Polish
+   - **Task dependencies**: Sequential vs parallel execution rules
+   - **Task details**: ID, description, file paths, parallel markers [P]
+   - **Execution flow**: Order and dependency requirements
+
+6. Execute implementation following the task plan:
+   - **Phase-by-phase execution**: Complete each phase before moving to the next
+   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together  
+   - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
+   - **File-based coordination**: Tasks affecting the same files must run sequentially
+   - **Validation checkpoints**: Verify each phase completion before proceeding
+
+7. Implementation execution rules:
+   - **Setup first**: Initialize project structure, dependencies, configuration
+   - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios
+   - **Core development**: Implement models, services, CLI commands, endpoints
+   - **Integration work**: Database connections, middleware, logging, external services
+   - **Polish and validation**: Unit tests, performance optimization, documentation
+
+8. Progress tracking and error handling:
+   - Report progress after each completed task
+   - Halt execution if any non-parallel task fails
+   - For parallel tasks [P], continue with successful tasks, report failed ones
+   - Provide clear error messages with context for debugging
+   - Suggest next steps if implementation cannot proceed
+   - **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file.
+
+9. Completion validation:
+   - Verify all required tasks are completed
+   - Check that implemented features match the original specification
+   - Validate that tests pass and coverage meets requirements
+   - Confirm the implementation follows the technical plan
+   - Report final status with summary of completed work
+
+Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `/speckit.tasks` first to regenerate the task list.
+"""

.gemini/commands/speckit.plan.toml

@@ -0,0 +1,93 @@
+description = "Execute the implementation planning workflow using the plan template to generate design artifacts."
+
+prompt = """
+---
+description: Execute the implementation planning workflow using the plan template to generate design artifacts.
+handoffs: 
+  - label: Create Tasks
+    agent: speckit.tasks
+    prompt: Break the plan into tasks
+    send: true
+  - label: Create Checklist
+    agent: speckit.checklist
+    prompt: Create a checklist for the following domain...
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+1. **Setup**: Run `.specify/scripts/bash/setup-plan.sh --json` from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+
+2. **Load context**: Read FEATURE_SPEC and `.specify/memory/constitution.md`. Load IMPL_PLAN template (already copied).
+
+3. **Execute plan workflow**: Follow the structure in IMPL_PLAN template to:
+   - Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
+   - Fill Constitution Check section from constitution
+   - Evaluate gates (ERROR if violations unjustified)
+   - Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
+   - Phase 1: Generate data-model.md, contracts/, quickstart.md
+   - Phase 1: Update agent context by running the agent script
+   - Re-evaluate Constitution Check post-design
+
+4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
+
+## Phases
+
+### Phase 0: Outline & Research
+
+1. **Extract unknowns from Technical Context** above:
+   - For each NEEDS CLARIFICATION → research task
+   - For each dependency → best practices task
+   - For each integration → patterns task
+
+2. **Generate and dispatch research agents**:
+
+   ```text
+   For each unknown in Technical Context:
+     Task: "Research {unknown} for {feature context}"
+   For each technology choice:
+     Task: "Find best practices for {tech} in {domain}"
+   ```
+
+3. **Consolidate findings** in `research.md` using format:
+   - Decision: [what was chosen]
+   - Rationale: [why chosen]
+   - Alternatives considered: [what else evaluated]
+
+**Output**: research.md with all NEEDS CLARIFICATION resolved
+
+### Phase 1: Design & Contracts
+
+**Prerequisites:** `research.md` complete
+
+1. **Extract entities from feature spec** → `data-model.md`:
+   - Entity name, fields, relationships
+   - Validation rules from requirements
+   - State transitions if applicable
+
+2. **Generate API contracts** from functional requirements:
+   - For each user action → endpoint
+   - Use standard REST/GraphQL patterns
+   - Output OpenAPI/GraphQL schema to `/contracts/`
+
+3. **Agent context update**:
+   - Run `.specify/scripts/bash/update-agent-context.sh gemini`
+   - These scripts detect which AI agent is in use
+   - Update the appropriate agent-specific context file
+   - Add only new technology from current plan
+   - Preserve manual additions between markers
+
+**Output**: data-model.md, /contracts/*, quickstart.md, agent-specific file
+
+## Key rules
+
+- Use absolute paths
+- ERROR on gate failures or unresolved clarifications
+"""

.gemini/commands/speckit.specify.toml

@@ -0,0 +1,261 @@
+description = "Create or update the feature specification from a natural language feature description."
+
+prompt = """
+---
+description: Create or update the feature specification from a natural language feature description.
+handoffs: 
+  - label: Build Technical Plan
+    agent: speckit.plan
+    prompt: Create a plan for the spec. I am building with...
+  - label: Clarify Spec Requirements
+    agent: speckit.clarify
+    prompt: Clarify specification requirements
+    send: true
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+The text the user typed after `/speckit.specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{{args}}` appears literally below. Do not ask the user to repeat it unless they provided an empty command.
+
+Given that feature description, do this:
+
+1. **Generate a concise short name** (2-4 words) for the branch:
+   - Analyze the feature description and extract the most meaningful keywords
+   - Create a 2-4 word short name that captures the essence of the feature
+   - Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
+   - Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
+   - Keep it concise but descriptive enough to understand the feature at a glance
+   - Examples:
+     - "I want to add user authentication" → "user-auth"
+     - "Implement OAuth2 integration for the API" → "oauth2-api-integration"
+     - "Create a dashboard for analytics" → "analytics-dashboard"
+     - "Fix payment processing timeout bug" → "fix-payment-timeout"
+
+2. **Check for existing branches before creating new one**:
+   
+   a. First, fetch all remote branches to ensure we have the latest information:
+      ```bash
+      git fetch --all --prune
+      ```
+   
+   b. Find the highest feature number across all sources for the short-name:
+      - Remote branches: `git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$'`
+      - Local branches: `git branch | grep -E '^[* ]*[0-9]+-<short-name>$'`
+      - Specs directories: Check for directories matching `specs/[0-9]+-<short-name>`
+   
+   c. Determine the next available number:
+      - Extract all numbers from all three sources
+      - Find the highest number N
+      - Use N+1 for the new branch number
+   
+   d. Run the script `.specify/scripts/bash/create-new-feature.sh --json "{{args}}"` with the calculated number and short-name:
+      - Pass `--number N+1` and `--short-name "your-short-name"` along with the feature description
+      - Bash example: `.specify/scripts/bash/create-new-feature.sh --json "{{args}}" --json --number 5 --short-name "user-auth" "Add user authentication"`
+      - PowerShell example: `.specify/scripts/bash/create-new-feature.sh --json "{{args}}" -Json -Number 5 -ShortName "user-auth" "Add user authentication"`
+   
+   **IMPORTANT**:
+   - Check all three sources (remote branches, local branches, specs directories) to find the highest number
+   - Only match branches/directories with the exact short-name pattern
+   - If no existing branches/directories found with this short-name, start with number 1
+   - You must only ever run this script once per feature
+   - The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
+   - The JSON output will contain BRANCH_NAME and SPEC_FILE paths
+   - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot")
+
+3. Load `.specify/templates/spec-template.md` to understand required sections.
+
+4. Follow this execution flow:
+
+    1. Parse user description from Input
+       If empty: ERROR "No feature description provided"
+    2. Extract key concepts from description
+       Identify: actors, actions, data, constraints
+    3. For unclear aspects:
+       - Make informed guesses based on context and industry standards
+       - Only mark with [NEEDS CLARIFICATION: specific question] if:
+         - The choice significantly impacts feature scope or user experience
+         - Multiple reasonable interpretations exist with different implications
+         - No reasonable default exists
+       - **LIMIT: Maximum 3 [NEEDS CLARIFICATION] markers total**
+       - Prioritize clarifications by impact: scope > security/privacy > user experience > technical details
+    4. Fill User Scenarios & Testing section
+       If no clear user flow: ERROR "Cannot determine user scenarios"
+    5. Generate Functional Requirements
+       Each requirement must be testable
+       Use reasonable defaults for unspecified details (document assumptions in Assumptions section)
+    6. Define Success Criteria
+       Create measurable, technology-agnostic outcomes
+       Include both quantitative metrics (time, performance, volume) and qualitative measures (user satisfaction, task completion)
+       Each criterion must be verifiable without implementation details
+    7. Identify Key Entities (if data involved)
+    8. Return: SUCCESS (spec ready for planning)
+
+5. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.
+
+6. **Specification Quality Validation**: After writing the initial spec, validate it against quality criteria:
+
+   a. **Create Spec Quality Checklist**: Generate a checklist file at `FEATURE_DIR/checklists/requirements.md` using the checklist template structure with these validation items:
+
+      ```markdown
+      # Specification Quality Checklist: [FEATURE NAME]
+      
+      **Purpose**: Validate specification completeness and quality before proceeding to planning
+      **Created**: [DATE]
+      **Feature**: [Link to spec.md]
+      
+      ## Content Quality
+      
+      - [ ] No implementation details (languages, frameworks, APIs)
+      - [ ] Focused on user value and business needs
+      - [ ] Written for non-technical stakeholders
+      - [ ] All mandatory sections completed
+      
+      ## Requirement Completeness
+      
+      - [ ] No [NEEDS CLARIFICATION] markers remain
+      - [ ] Requirements are testable and unambiguous
+      - [ ] Success criteria are measurable
+      - [ ] Success criteria are technology-agnostic (no implementation details)
+      - [ ] All acceptance scenarios are defined
+      - [ ] Edge cases are identified
+      - [ ] Scope is clearly bounded
+      - [ ] Dependencies and assumptions identified
+      
+      ## Feature Readiness
+      
+      - [ ] All functional requirements have clear acceptance criteria
+      - [ ] User scenarios cover primary flows
+      - [ ] Feature meets measurable outcomes defined in Success Criteria
+      - [ ] No implementation details leak into specification
+      
+      ## Notes
+      
+      - Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`
+      ```
+
+   b. **Run Validation Check**: Review the spec against each checklist item:
+      - For each item, determine if it passes or fails
+      - Document specific issues found (quote relevant spec sections)
+
+   c. **Handle Validation Results**:
+
+      - **If all items pass**: Mark checklist complete and proceed to step 6
+
+      - **If items fail (excluding [NEEDS CLARIFICATION])**:
+        1. List the failing items and specific issues
+        2. Update the spec to address each issue
+        3. Re-run validation until all items pass (max 3 iterations)
+        4. If still failing after 3 iterations, document remaining issues in checklist notes and warn user
+
+      - **If [NEEDS CLARIFICATION] markers remain**:
+        1. Extract all [NEEDS CLARIFICATION: ...] markers from the spec
+        2. **LIMIT CHECK**: If more than 3 markers exist, keep only the 3 most critical (by scope/security/UX impact) and make informed guesses for the rest
+        3. For each clarification needed (max 3), present options to user in this format:
+
+           ```markdown
+           ## Question [N]: [Topic]
+           
+           **Context**: [Quote relevant spec section]
+           
+           **What we need to know**: [Specific question from NEEDS CLARIFICATION marker]
+           
+           **Suggested Answers**:
+           
+           | Option | Answer | Implications |
+           |--------|--------|--------------|
+           | A      | [First suggested answer] | [What this means for the feature] |
+           | B      | [Second suggested answer] | [What this means for the feature] |
+           | C      | [Third suggested answer] | [What this means for the feature] |
+           | Custom | Provide your own answer | [Explain how to provide custom input] |
+           
+           **Your choice**: _[Wait for user response]_
+           ```
+
+        4. **CRITICAL - Table Formatting**: Ensure markdown tables are properly formatted:
+           - Use consistent spacing with pipes aligned
+           - Each cell should have spaces around content: `| Content |` not `|Content|`
+           - Header separator must have at least 3 dashes: `|--------|`
+           - Test that the table renders correctly in markdown preview
+        5. Number questions sequentially (Q1, Q2, Q3 - max 3 total)
+        6. Present all questions together before waiting for responses
+        7. Wait for user to respond with their choices for all questions (e.g., "Q1: A, Q2: Custom - [details], Q3: B")
+        8. Update the spec by replacing each [NEEDS CLARIFICATION] marker with the user's selected or provided answer
+        9. Re-run validation after all clarifications are resolved
+
+   d. **Update Checklist**: After each validation iteration, update the checklist file with current pass/fail status
+
+7. Report completion with branch name, spec file path, checklist results, and readiness for the next phase (`/speckit.clarify` or `/speckit.plan`).
+
+**NOTE:** The script creates and checks out the new branch and initializes the spec file before writing.
+
+## General Guidelines
+
+## Quick Guidelines
+
+- Focus on **WHAT** users need and **WHY**.
+- Avoid HOW to implement (no tech stack, APIs, code structure).
+- Written for business stakeholders, not developers.
+- DO NOT create any checklists that are embedded in the spec. That will be a separate command.
+
+### Section Requirements
+
+- **Mandatory sections**: Must be completed for every feature
+- **Optional sections**: Include only when relevant to the feature
+- When a section doesn't apply, remove it entirely (don't leave as "N/A")
+
+### For AI Generation
+
+When creating this spec from a user prompt:
+
+1. **Make informed guesses**: Use context, industry standards, and common patterns to fill gaps
+2. **Document assumptions**: Record reasonable defaults in the Assumptions section
+3. **Limit clarifications**: Maximum 3 [NEEDS CLARIFICATION] markers - use only for critical decisions that:
+   - Significantly impact feature scope or user experience
+   - Have multiple reasonable interpretations with different implications
+   - Lack any reasonable default
+4. **Prioritize clarifications**: scope > security/privacy > user experience > technical details
+5. **Think like a tester**: Every vague requirement should fail the "testable and unambiguous" checklist item
+6. **Common areas needing clarification** (only if no reasonable default exists):
+   - Feature scope and boundaries (include/exclude specific use cases)
+   - User types and permissions (if multiple conflicting interpretations possible)
+   - Security/compliance requirements (when legally/financially significant)
+
+**Examples of reasonable defaults** (don't ask about these):
+
+- Data retention: Industry-standard practices for the domain
+- Performance targets: Standard web/mobile app expectations unless specified
+- Error handling: User-friendly messages with appropriate fallbacks
+- Authentication method: Standard session-based or OAuth2 for web apps
+- Integration patterns: RESTful APIs unless specified otherwise
+
+### Success Criteria Guidelines
+
+Success criteria must be:
+
+1. **Measurable**: Include specific metrics (time, percentage, count, rate)
+2. **Technology-agnostic**: No mention of frameworks, languages, databases, or tools
+3. **User-focused**: Describe outcomes from user/business perspective, not system internals
+4. **Verifiable**: Can be tested/validated without knowing implementation details
+
+**Good examples**:
+
+- "Users can complete checkout in under 3 minutes"
+- "System supports 10,000 concurrent users"
+- "95% of searches return results in under 1 second"
+- "Task completion rate improves by 40%"
+
+**Bad examples** (implementation-focused):
+
+- "API response time is under 200ms" (too technical, use "Users see results instantly")
+- "Database can handle 1000 TPS" (implementation detail, use user-facing metric)
+- "React components render efficiently" (framework-specific)
+- "Redis cache hit rate above 80%" (technology-specific)
+"""

.gemini/commands/speckit.tasks.toml

@@ -0,0 +1,141 @@
+description = "Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts."
+
+prompt = """
+---
+description: Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
+handoffs: 
+  - label: Analyze For Consistency
+    agent: speckit.analyze
+    prompt: Run a project analysis for consistency
+    send: true
+  - label: Implement Project
+    agent: speckit.implement
+    prompt: Start the implementation in phases
+    send: true
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+
+2. **Load design documents**: Read from FEATURE_DIR:
+   - **Required**: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
+   - **Optional**: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
+   - Note: Not all projects have all documents. Generate tasks based on what's available.
+
+3. **Execute task generation workflow**:
+   - Load plan.md and extract tech stack, libraries, project structure
+   - Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
+   - If data-model.md exists: Extract entities and map to user stories
+   - If contracts/ exists: Map endpoints to user stories
+   - If research.md exists: Extract decisions for setup tasks
+   - Generate tasks organized by user story (see Task Generation Rules below)
+   - Generate dependency graph showing user story completion order
+   - Create parallel execution examples per user story
+   - Validate task completeness (each user story has all needed tasks, independently testable)
+
+4. **Generate tasks.md**: Use `.specify.specify/templates/tasks-template.md` as structure, fill with:
+   - Correct feature name from plan.md
+   - Phase 1: Setup tasks (project initialization)
+   - Phase 2: Foundational tasks (blocking prerequisites for all user stories)
+   - Phase 3+: One phase per user story (in priority order from spec.md)
+   - Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
+   - Final Phase: Polish & cross-cutting concerns
+   - All tasks must follow the strict checklist format (see Task Generation Rules below)
+   - Clear file paths for each task
+   - Dependencies section showing story completion order
+   - Parallel execution examples per story
+   - Implementation strategy section (MVP first, incremental delivery)
+
+5. **Report**: Output path to generated tasks.md and summary:
+   - Total task count
+   - Task count per user story
+   - Parallel opportunities identified
+   - Independent test criteria for each story
+   - Suggested MVP scope (typically just User Story 1)
+   - Format validation: Confirm ALL tasks follow the checklist format (checkbox, ID, labels, file paths)
+
+Context for task generation: {{args}}
+
+The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.
+
+## Task Generation Rules
+
+**CRITICAL**: Tasks MUST be organized by user story to enable independent implementation and testing.
+
+**Tests are OPTIONAL**: Only generate test tasks if explicitly requested in the feature specification or if user requests TDD approach.
+
+### Checklist Format (REQUIRED)
+
+Every task MUST strictly follow this format:
+
+```text
+- [ ] [TaskID] [P?] [Story?] Description with file path
+```
+
+**Format Components**:
+
+1. **Checkbox**: ALWAYS start with `- [ ]` (markdown checkbox)
+2. **Task ID**: Sequential number (T001, T002, T003...) in execution order
+3. **[P] marker**: Include ONLY if task is parallelizable (different files, no dependencies on incomplete tasks)
+4. **[Story] label**: REQUIRED for user story phase tasks only
+   - Format: [US1], [US2], [US3], etc. (maps to user stories from spec.md)
+   - Setup phase: NO story label
+   - Foundational phase: NO story label  
+   - User Story phases: MUST have story label
+   - Polish phase: NO story label
+5. **Description**: Clear action with exact file path
+
+**Examples**:
+
+- ✅ CORRECT: `- [ ] T001 Create project structure per implementation plan`
+- ✅ CORRECT: `- [ ] T005 [P] Implement authentication middleware in src/middleware/auth.py`
+- ✅ CORRECT: `- [ ] T012 [P] [US1] Create User model in src/models/user.py`
+- ✅ CORRECT: `- [ ] T014 [US1] Implement UserService in src/services/user_service.py`
+- ❌ WRONG: `- [ ] Create User model` (missing ID and Story label)
+- ❌ WRONG: `T001 [US1] Create model` (missing checkbox)
+- ❌ WRONG: `- [ ] [US1] Create User model` (missing Task ID)
+- ❌ WRONG: `- [ ] T001 [US1] Create model` (missing file path)
+
+### Task Organization
+
+1. **From User Stories (spec.md)** - PRIMARY ORGANIZATION:
+   - Each user story (P1, P2, P3...) gets its own phase
+   - Map all related components to their story:
+     - Models needed for that story
+     - Services needed for that story
+     - Endpoints/UI needed for that story
+     - If tests requested: Tests specific to that story
+   - Mark story dependencies (most stories should be independent)
+
+2. **From Contracts**:
+   - Map each contract/endpoint → to the user story it serves
+   - If tests requested: Each contract → contract test task [P] before implementation in that story's phase
+
+3. **From Data Model**:
+   - Map each entity to the user story(ies) that need it
+   - If entity serves multiple stories: Put in earliest story or Setup phase
+   - Relationships → service layer tasks in appropriate story phase
+
+4. **From Setup/Infrastructure**:
+   - Shared infrastructure → Setup phase (Phase 1)
+   - Foundational/blocking tasks → Foundational phase (Phase 2)
+   - Story-specific setup → within that story's phase
+
+### Phase Structure
+
+- **Phase 1**: Setup (project initialization)
+- **Phase 2**: Foundational (blocking prerequisites - MUST complete before user stories)
+- **Phase 3+**: User Stories in priority order (P1, P2, P3...)
+  - Within each story: Tests (if requested) → Models → Services → Endpoints → Integration
+  - Each phase should be a complete, independently testable increment
+- **Final Phase**: Polish & Cross-Cutting Concerns
+"""

.gemini/commands/speckit.taskstoissues.toml

@@ -0,0 +1,32 @@
+description = "Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts."
+
+prompt = """
+---
+description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
+tools: ['github/github-mcp-server/issue_write']
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Outline
+
+1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
+1. From the executed script, extract the path to **tasks**.
+1. Get the Git remote by running:
+
+```bash
+git config --get remote.origin.url
+```
+
+**ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL**
+
+1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
+
+**UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL**
+"""

.gitignore

@@ -0,0 +1 @@
+.venv/

.specify/memory/constitution.md

@@ -0,0 +1,50 @@
+# [PROJECT_NAME] Constitution
+<!-- Example: Spec Constitution, TaskFlow Constitution, etc. -->
+
+## Core Principles
+
+### [PRINCIPLE_1_NAME]
+<!-- Example: I. Library-First -->
+[PRINCIPLE_1_DESCRIPTION]
+<!-- Example: Every feature starts as a standalone library; Libraries must be self-contained, independently testable, documented; Clear purpose required - no organizational-only libraries -->
+
+### [PRINCIPLE_2_NAME]
+<!-- Example: II. CLI Interface -->
+[PRINCIPLE_2_DESCRIPTION]
+<!-- Example: Every library exposes functionality via CLI; Text in/out protocol: stdin/args → stdout, errors → stderr; Support JSON + human-readable formats -->
+
+### [PRINCIPLE_3_NAME]
+<!-- Example: III. Test-First (NON-NEGOTIABLE) -->
+[PRINCIPLE_3_DESCRIPTION]
+<!-- Example: TDD mandatory: Tests written → User approved → Tests fail → Then implement; Red-Green-Refactor cycle strictly enforced -->
+
+### [PRINCIPLE_4_NAME]
+<!-- Example: IV. Integration Testing -->
+[PRINCIPLE_4_DESCRIPTION]
+<!-- Example: Focus areas requiring integration tests: New library contract tests, Contract changes, Inter-service communication, Shared schemas -->
+
+### [PRINCIPLE_5_NAME]
+<!-- Example: V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity -->
+[PRINCIPLE_5_DESCRIPTION]
+<!-- Example: Text I/O ensures debuggability; Structured logging required; Or: MAJOR.MINOR.BUILD format; Or: Start simple, YAGNI principles -->
+
+## [SECTION_2_NAME]
+<!-- Example: Additional Constraints, Security Requirements, Performance Standards, etc. -->
+
+[SECTION_2_CONTENT]
+<!-- Example: Technology stack requirements, compliance standards, deployment policies, etc. -->
+
+## [SECTION_3_NAME]
+<!-- Example: Development Workflow, Review Process, Quality Gates, etc. -->
+
+[SECTION_3_CONTENT]
+<!-- Example: Code review requirements, testing gates, deployment approval process, etc. -->
+
+## Governance
+<!-- Example: Constitution supersedes all other practices; Amendments require documentation, approval, migration plan -->
+
+[GOVERNANCE_RULES]
+<!-- Example: All PRs/reviews must verify compliance; Complexity must be justified; Use [GUIDANCE_FILE] for runtime development guidance -->
+
+**Version**: [CONSTITUTION_VERSION] | **Ratified**: [RATIFICATION_DATE] | **Last Amended**: [LAST_AMENDED_DATE]
+<!-- Example: Version: 2.1.1 | Ratified: 2025-06-13 | Last Amended: 2025-07-16 -->

.specify/scripts/bash/check-prerequisites.sh

@@ -0,0 +1,166 @@
+#!/usr/bin/env bash
+
+# Consolidated prerequisite checking script
+#
+# This script provides unified prerequisite checking for Spec-Driven Development workflow.
+# It replaces the functionality previously spread across multiple scripts.
+#
+# Usage: ./check-prerequisites.sh [OPTIONS]
+#
+# OPTIONS:
+#   --json              Output in JSON format
+#   --require-tasks     Require tasks.md to exist (for implementation phase)
+#   --include-tasks     Include tasks.md in AVAILABLE_DOCS list
+#   --paths-only        Only output path variables (no validation)
+#   --help, -h          Show help message
+#
+# OUTPUTS:
+#   JSON mode: {"FEATURE_DIR":"...", "AVAILABLE_DOCS":["..."]}
+#   Text mode: FEATURE_DIR:... \n AVAILABLE_DOCS: \n ✓/✗ file.md
+#   Paths only: REPO_ROOT: ... \n BRANCH: ... \n FEATURE_DIR: ... etc.
+
+set -e
+
+# Parse command line arguments
+JSON_MODE=false
+REQUIRE_TASKS=false
+INCLUDE_TASKS=false
+PATHS_ONLY=false
+
+for arg in "$@"; do
+    case "$arg" in
+        --json)
+            JSON_MODE=true
+            ;;
+        --require-tasks)
+            REQUIRE_TASKS=true
+            ;;
+        --include-tasks)
+            INCLUDE_TASKS=true
+            ;;
+        --paths-only)
+            PATHS_ONLY=true
+            ;;
+        --help|-h)
+            cat << 'EOF'
+Usage: check-prerequisites.sh [OPTIONS]
+
+Consolidated prerequisite checking for Spec-Driven Development workflow.
+
+OPTIONS:
+  --json              Output in JSON format
+  --require-tasks     Require tasks.md to exist (for implementation phase)
+  --include-tasks     Include tasks.md in AVAILABLE_DOCS list
+  --paths-only        Only output path variables (no prerequisite validation)
+  --help, -h          Show this help message
+
+EXAMPLES:
+  # Check task prerequisites (plan.md required)
+  ./check-prerequisites.sh --json
+  
+  # Check implementation prerequisites (plan.md + tasks.md required)
+  ./check-prerequisites.sh --json --require-tasks --include-tasks
+  
+  # Get feature paths only (no validation)
+  ./check-prerequisites.sh --paths-only
+  
+EOF
+            exit 0
+            ;;
+        *)
+            echo "ERROR: Unknown option '$arg'. Use --help for usage information." >&2
+            exit 1
+            ;;
+    esac
+done
+
+# Source common functions
+SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "$SCRIPT_DIR/common.sh"
+
+# Get feature paths and validate branch
+eval $(get_feature_paths)
+check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
+
+# If paths-only mode, output paths and exit (support JSON + paths-only combined)
+if $PATHS_ONLY; then
+    if $JSON_MODE; then
+        # Minimal JSON paths payload (no validation performed)
+        printf '{"REPO_ROOT":"%s","BRANCH":"%s","FEATURE_DIR":"%s","FEATURE_SPEC":"%s","IMPL_PLAN":"%s","TASKS":"%s"}\n' \
+            "$REPO_ROOT" "$CURRENT_BRANCH" "$FEATURE_DIR" "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS"
+    else
+        echo "REPO_ROOT: $REPO_ROOT"
+        echo "BRANCH: $CURRENT_BRANCH"
+        echo "FEATURE_DIR: $FEATURE_DIR"
+        echo "FEATURE_SPEC: $FEATURE_SPEC"
+        echo "IMPL_PLAN: $IMPL_PLAN"
+        echo "TASKS: $TASKS"
+    fi
+    exit 0
+fi
+
+# Validate required directories and files
+if [[ ! -d "$FEATURE_DIR" ]]; then
+    echo "ERROR: Feature directory not found: $FEATURE_DIR" >&2
+    echo "Run /speckit.specify first to create the feature structure." >&2
+    exit 1
+fi
+
+if [[ ! -f "$IMPL_PLAN" ]]; then
+    echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
+    echo "Run /speckit.plan first to create the implementation plan." >&2
+    exit 1
+fi
+
+# Check for tasks.md if required
+if $REQUIRE_TASKS && [[ ! -f "$TASKS" ]]; then
+    echo "ERROR: tasks.md not found in $FEATURE_DIR" >&2
+    echo "Run /speckit.tasks first to create the task list." >&2
+    exit 1
+fi
+
+# Build list of available documents
+docs=()
+
+# Always check these optional docs
+[[ -f "$RESEARCH" ]] && docs+=("research.md")
+[[ -f "$DATA_MODEL" ]] && docs+=("data-model.md")
+
+# Check contracts directory (only if it exists and has files)
+if [[ -d "$CONTRACTS_DIR" ]] && [[ -n "$(ls -A "$CONTRACTS_DIR" 2>/dev/null)" ]]; then
+    docs+=("contracts/")
+fi
+
+[[ -f "$QUICKSTART" ]] && docs+=("quickstart.md")
+
+# Include tasks.md if requested and it exists
+if $INCLUDE_TASKS && [[ -f "$TASKS" ]]; then
+    docs+=("tasks.md")
+fi
+
+# Output results
+if $JSON_MODE; then
+    # Build JSON array of documents
+    if [[ ${#docs[@]} -eq 0 ]]; then
+        json_docs="[]"
+    else
+        json_docs=$(printf '"%s",' "${docs[@]}")
+        json_docs="[${json_docs%,}]"
+    fi
+    
+    printf '{"FEATURE_DIR":"%s","AVAILABLE_DOCS":%s}\n' "$FEATURE_DIR" "$json_docs"
+else
+    # Text output
+    echo "FEATURE_DIR:$FEATURE_DIR"
+    echo "AVAILABLE_DOCS:"
+    
+    # Show status of each potential document
+    check_file "$RESEARCH" "research.md"
+    check_file "$DATA_MODEL" "data-model.md"
+    check_dir "$CONTRACTS_DIR" "contracts/"
+    check_file "$QUICKSTART" "quickstart.md"
+    
+    if $INCLUDE_TASKS; then
+        check_file "$TASKS" "tasks.md"
+    fi
+fi

.specify/scripts/bash/common.sh

@@ -0,0 +1,156 @@
+#!/usr/bin/env bash
+# Common functions and variables for all scripts
+
+# Get repository root, with fallback for non-git repositories
+get_repo_root() {
+    if git rev-parse --show-toplevel >/dev/null 2>&1; then
+        git rev-parse --show-toplevel
+    else
+        # Fall back to script location for non-git repos
+        local script_dir="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+        (cd "$script_dir/../../.." && pwd)
+    fi
+}
+
+# Get current branch, with fallback for non-git repositories
+get_current_branch() {
+    # First check if SPECIFY_FEATURE environment variable is set
+    if [[ -n "${SPECIFY_FEATURE:-}" ]]; then
+        echo "$SPECIFY_FEATURE"
+        return
+    fi
+
+    # Then check git if available
+    if git rev-parse --abbrev-ref HEAD >/dev/null 2>&1; then
+        git rev-parse --abbrev-ref HEAD
+        return
+    fi
+
+    # For non-git repos, try to find the latest feature directory
+    local repo_root=$(get_repo_root)
+    local specs_dir="$repo_root/specs"
+
+    if [[ -d "$specs_dir" ]]; then
+        local latest_feature=""
+        local highest=0
+
+        for dir in "$specs_dir"/*; do
+            if [[ -d "$dir" ]]; then
+                local dirname=$(basename "$dir")
+                if [[ "$dirname" =~ ^([0-9]{3})- ]]; then
+                    local number=${BASH_REMATCH[1]}
+                    number=$((10#$number))
+                    if [[ "$number" -gt "$highest" ]]; then
+                        highest=$number
+                        latest_feature=$dirname
+                    fi
+                fi
+            fi
+        done
+
+        if [[ -n "$latest_feature" ]]; then
+            echo "$latest_feature"
+            return
+        fi
+    fi
+
+    echo "main"  # Final fallback
+}
+
+# Check if we have git available
+has_git() {
+    git rev-parse --show-toplevel >/dev/null 2>&1
+}
+
+check_feature_branch() {
+    local branch="$1"
+    local has_git_repo="$2"
+
+    # For non-git repos, we can't enforce branch naming but still provide output
+    if [[ "$has_git_repo" != "true" ]]; then
+        echo "[specify] Warning: Git repository not detected; skipped branch validation" >&2
+        return 0
+    fi
+
+    if [[ ! "$branch" =~ ^[0-9]{3}- ]]; then
+        echo "ERROR: Not on a feature branch. Current branch: $branch" >&2
+        echo "Feature branches should be named like: 001-feature-name" >&2
+        return 1
+    fi
+
+    return 0
+}
+
+get_feature_dir() { echo "$1/specs/$2"; }
+
+# Find feature directory by numeric prefix instead of exact branch match
+# This allows multiple branches to work on the same spec (e.g., 004-fix-bug, 004-add-feature)
+find_feature_dir_by_prefix() {
+    local repo_root="$1"
+    local branch_name="$2"
+    local specs_dir="$repo_root/specs"
+
+    # Extract numeric prefix from branch (e.g., "004" from "004-whatever")
+    if [[ ! "$branch_name" =~ ^([0-9]{3})- ]]; then
+        # If branch doesn't have numeric prefix, fall back to exact match
+        echo "$specs_dir/$branch_name"
+        return
+    fi
+
+    local prefix="${BASH_REMATCH[1]}"
+
+    # Search for directories in specs/ that start with this prefix
+    local matches=()
+    if [[ -d "$specs_dir" ]]; then
+        for dir in "$specs_dir"/"$prefix"-*; do
+            if [[ -d "$dir" ]]; then
+                matches+=("$(basename "$dir")")
+            fi
+        done
+    fi
+
+    # Handle results
+    if [[ ${#matches[@]} -eq 0 ]]; then
+        # No match found - return the branch name path (will fail later with clear error)
+        echo "$specs_dir/$branch_name"
+    elif [[ ${#matches[@]} -eq 1 ]]; then
+        # Exactly one match - perfect!
+        echo "$specs_dir/${matches[0]}"
+    else
+        # Multiple matches - this shouldn't happen with proper naming convention
+        echo "ERROR: Multiple spec directories found with prefix '$prefix': ${matches[*]}" >&2
+        echo "Please ensure only one spec directory exists per numeric prefix." >&2
+        echo "$specs_dir/$branch_name"  # Return something to avoid breaking the script
+    fi
+}
+
+get_feature_paths() {
+    local repo_root=$(get_repo_root)
+    local current_branch=$(get_current_branch)
+    local has_git_repo="false"
+
+    if has_git; then
+        has_git_repo="true"
+    fi
+
+    # Use prefix-based lookup to support multiple branches per spec
+    local feature_dir=$(find_feature_dir_by_prefix "$repo_root" "$current_branch")
+
+    cat <<EOF
+REPO_ROOT='$repo_root'
+CURRENT_BRANCH='$current_branch'
+HAS_GIT='$has_git_repo'
+FEATURE_DIR='$feature_dir'
+FEATURE_SPEC='$feature_dir/spec.md'
+IMPL_PLAN='$feature_dir/plan.md'
+TASKS='$feature_dir/tasks.md'
+RESEARCH='$feature_dir/research.md'
+DATA_MODEL='$feature_dir/data-model.md'
+QUICKSTART='$feature_dir/quickstart.md'
+CONTRACTS_DIR='$feature_dir/contracts'
+EOF
+}
+
+check_file() { [[ -f "$1" ]] && echo "  ✓ $2" || echo "  ✗ $2"; }
+check_dir() { [[ -d "$1" && -n $(ls -A "$1" 2>/dev/null) ]] && echo "  ✓ $2" || echo "  ✗ $2"; }
+

.specify/scripts/bash/create-new-feature.sh

@@ -0,0 +1,330 @@
+#!/usr/bin/env bash
+
+set -e
+
+JSON_MODE=false
+SHORT_NAME=""
+BRANCH_NUMBER=""
+ARGS=()
+i=1
+while [ $i -le $# ]; do
+    arg="${!i}"
+    case "$arg" in
+        --json) 
+            JSON_MODE=true 
+            ;;
+        --short-name)
+            if [ $((i + 1)) -gt $# ]; then
+                echo 'Error: --short-name requires a value' >&2
+                exit 1
+            fi
+            i=$((i + 1))
+            next_arg="${!i}"
+            # Check if the next argument is another option (starts with --)
+            if [[ "$next_arg" == --* ]]; then
+                echo 'Error: --short-name requires a value' >&2
+                exit 1
+            fi
+            SHORT_NAME="$next_arg"
+            ;;
+        --number)
+            if [ $((i + 1)) -gt $# ]; then
+                echo 'Error: --number requires a value' >&2
+                exit 1
+            fi
+            i=$((i + 1))
+            next_arg="${!i}"
+            if [[ "$next_arg" == --* ]]; then
+                echo 'Error: --number requires a value' >&2
+                exit 1
+            fi
+            BRANCH_NUMBER="$next_arg"
+            ;;
+        --file)
+            if [ $((i + 1)) -gt $# ]; then
+                echo 'Error: --file requires a value' >&2
+                exit 1
+            fi
+            i=$((i + 1))
+            next_arg="${!i}"
+            if [[ "$next_arg" == --* ]]; then
+                echo 'Error: --file requires a value' >&2
+                exit 1
+            fi
+            FEATURE_FILE="$next_arg"
+            ;;
+        --help|-h) 
+            echo "Usage: $0 [--json] [--short-name <name>] [--number N] [--file <path>] <feature_description>"
+            echo ""
+            echo "Options:"
+            echo "  --json              Output in JSON format"
+            echo "  --short-name <name> Provide a custom short name (2-4 words) for the branch"
+            echo "  --number N          Specify branch number manually (overrides auto-detection)"
+            echo "  --file <path>       Read feature description from a file"
+            echo "  --help, -h          Show this help message"
+            echo ""
+            echo "Examples:"
+            echo "  $0 'Add user authentication system' --short-name 'user-auth'"
+            echo "  $0 'Implement OAuth2 integration for API' --number 5"
+            echo "  $0 --file my_feature.md --short-name 'new-feature'"
+            exit 0
+            ;;
+        *) 
+            ARGS+=("$arg") 
+            ;;
+    esac
+    i=$((i + 1))
+done
+
+FEATURE_DESCRIPTION=""
+if [ -n "$FEATURE_FILE" ]; then
+    if [ ! -f "$FEATURE_FILE" ]; then
+        echo "Error: Feature file not found: $FEATURE_FILE" >&2
+        exit 1
+    fi
+    FEATURE_DESCRIPTION=$(cat "$FEATURE_FILE")
+elif [ ${#ARGS[@]} -gt 0 ]; then
+    FEATURE_DESCRIPTION="${ARGS[*]}"
+fi
+
+if [ -z "$FEATURE_DESCRIPTION" ]; then
+    echo "Usage: $0 [--json] [--short-name <name>] [--number N] [--file <path>] <feature_description>" >&2
+    exit 1
+fi
+
+# Function to find the repository root by searching for existing project markers
+find_repo_root() {
+    local dir="$1"
+    while [ "$dir" != "/" ]; do
+        if [ -d "$dir/.git" ] || [ -d "$dir/.specify" ]; then
+            echo "$dir"
+            return 0
+        fi
+        dir="$(dirname "$dir")"
+    done
+    return 1
+}
+
+# Function to get highest number from specs directory
+get_highest_from_specs() {
+    local specs_dir="$1"
+    local highest=0
+    
+    if [ -d "$specs_dir" ]; then
+        for dir in "$specs_dir"/*; do
+            [ -d "$dir" ] || continue
+            dirname=$(basename "$dir")
+            number=$(echo "$dirname" | grep -o '^[0-9]\+' || echo "0")
+            number=$((10#$number))
+            if [ "$number" -gt "$highest" ]; then
+                highest=$number
+            fi
+        done
+    fi
+    
+    echo "$highest"
+}
+
+# Function to get highest number from git branches
+get_highest_from_branches() {
+    local highest=0
+    
+    # Get all branches (local and remote)
+    branches=$(git branch -a 2>/dev/null || echo "")
+    
+    if [ -n "$branches" ]; then
+        while IFS= read -r branch; do
+            # Clean branch name: remove leading markers and remote prefixes
+            clean_branch=$(echo "$branch" | sed 's/^[* ]*//; s|^remotes/[^/]*/||')
+            
+            # Extract feature number if branch matches pattern ###-*
+            if echo "$clean_branch" | grep -q '^[0-9]\{3\}-'; then
+                number=$(echo "$clean_branch" | grep -o '^[0-9]\{3\}' || echo "0")
+                number=$((10#$number))
+                if [ "$number" -gt "$highest" ]; then
+                    highest=$number
+                fi
+            fi
+        done <<< "$branches"
+    fi
+    
+    echo "$highest"
+}
+
+# Function to check existing branches (local and remote) and return next available number
+check_existing_branches() {
+    local short_name="$1"
+    local specs_dir="$2"
+    
+    # Fetch all remotes to get latest branch info (suppress errors if no remotes)
+    git fetch --all --prune 2>/dev/null || true
+    
+    # Find all branches matching the pattern using git ls-remote (more reliable)
+    local remote_branches=$(git ls-remote --heads origin 2>/dev/null | grep -E "refs/heads/[0-9]+-${short_name}$" | sed 's/.*\/\([0-9]*\)-.*/\1/' | sort -n)
+    
+    # Also check local branches
+    local local_branches=$(git branch 2>/dev/null | grep -E "^[* ]*[0-9]+-${short_name}$" | sed 's/^[* ]*//' | sed 's/-.*//' | sort -n)
+    
+    # Check specs directory as well
+    local spec_dirs=""
+    if [ -d "$specs_dir" ]; then
+        spec_dirs=$(find "$specs_dir" -maxdepth 1 -type d -name "[0-9]*-${short_name}" 2>/dev/null | xargs -n1 basename 2>/dev/null | sed 's/-.*//' | sort -n)
+    fi
+    
+    # Combine all sources and get the highest number
+    local max_num=0
+    for num in $remote_branches $local_branches $spec_dirs; do
+        if [ "$num" -gt "$max_num" ]; then
+            max_num=$num
+        fi
+    done
+    
+    # Return next number
+    echo $((max_num + 1))
+}
+
+# Function to clean and format a branch name
+clean_branch_name() {
+    local name="$1"
+    echo "$name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-//' | sed 's/-$//'
+}
+
+# Resolve repository root. Prefer git information when available, but fall back
+# to searching for repository markers so the workflow still functions in repositories that
+# were initialised with --no-git.
+SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+if git rev-parse --show-toplevel >/dev/null 2>&1; then
+    REPO_ROOT=$(git rev-parse --show-toplevel)
+    HAS_GIT=true
+else
+    REPO_ROOT="$(find_repo_root "$SCRIPT_DIR")"
+    if [ -z "$REPO_ROOT" ]; then
+        echo "Error: Could not determine repository root. Please run this script from within the repository." >&2
+        exit 1
+    fi
+    HAS_GIT=false
+fi
+
+cd "$REPO_ROOT"
+
+SPECS_DIR="$REPO_ROOT/specs"
+mkdir -p "$SPECS_DIR"
+
+# Function to generate branch name with stop word filtering and length filtering
+generate_branch_name() {
+    local description="$1"
+    
+    # Common stop words to filter out
+    local stop_words="^(i|a|an|the|to|for|of|in|on|at|by|with|from|is|are|was|were|be|been|being|have|has|had|do|does|did|will|would|should|could|can|may|might|must|shall|this|that|these|those|my|your|our|their|want|need|add|get|set)$"
+    
+    # Convert to lowercase and split into words
+    local clean_name=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/ /g')
+    
+    # Filter words: remove stop words and words shorter than 3 chars (unless they're uppercase acronyms in original)
+    local meaningful_words=()
+    for word in $clean_name; do
+        # Skip empty words
+        [ -z "$word" ] && continue
+        
+        # Keep words that are NOT stop words AND (length >= 3 OR are potential acronyms)
+        if ! echo "$word" | grep -qiE "$stop_words"; then
+            if [ ${#word} -ge 3 ]; then
+                meaningful_words+=("$word")
+            elif echo "$description" | grep -q "\b${word^^}\b"; then
+                # Keep short words if they appear as uppercase in original (likely acronyms)
+                meaningful_words+=("$word")
+            fi
+        fi
+    done
+    
+    # If we have meaningful words, use first 3-4 of them
+    if [ ${#meaningful_words[@]} -gt 0 ]; then
+        local max_words=3
+        if [ ${#meaningful_words[@]} -eq 4 ]; then max_words=4; fi
+        
+        local result=""
+        local count=0
+        for word in "${meaningful_words[@]}"; do
+            if [ $count -ge $max_words ]; then break; fi
+            if [ -n "$result" ]; then result="$result-"; fi
+            result="$result$word"
+            count=$((count + 1))
+        done
+        echo "$result"
+    else
+        # Fallback to original logic if no meaningful words found
+        local cleaned=$(clean_branch_name "$description")
+        echo "$cleaned" | tr '-' '\n' | grep -v '^$' | head -3 | tr '\n' '-' | sed 's/-$//'
+    fi
+}
+
+# Generate branch name
+if [ -n "$SHORT_NAME" ]; then
+    # Use provided short name, just clean it up
+    BRANCH_SUFFIX=$(clean_branch_name "$SHORT_NAME")
+else
+    # Generate from description with smart filtering
+    BRANCH_SUFFIX=$(generate_branch_name "$FEATURE_DESCRIPTION")
+fi
+
+# Determine branch number
+if [ -z "$BRANCH_NUMBER" ]; then
+    if [ "$HAS_GIT" = true ]; then
+        # Check existing branches on remotes
+        BRANCH_NUMBER=$(check_existing_branches "$BRANCH_SUFFIX" "$SPECS_DIR")
+    else
+        # Fall back to local directory check
+        HIGHEST=$(get_highest_from_specs "$SPECS_DIR")
+        BRANCH_NUMBER=$((HIGHEST + 1))
+    fi
+fi
+
+FEATURE_NUM=$(printf "%03d" "$BRANCH_NUMBER")
+BRANCH_NAME="${FEATURE_NUM}-${BRANCH_SUFFIX}"
+
+# GitHub enforces a 244-byte limit on branch names
+# Validate and truncate if necessary
+MAX_BRANCH_LENGTH=244
+if [ ${#BRANCH_NAME} -gt $MAX_BRANCH_LENGTH ]; then
+    # Calculate how much we need to trim from suffix
+    # Account for: feature number (3) + hyphen (1) = 4 chars
+    MAX_SUFFIX_LENGTH=$((MAX_BRANCH_LENGTH - 4))
+    
+    # Truncate suffix at word boundary if possible
+    TRUNCATED_SUFFIX=$(echo "$BRANCH_SUFFIX" | cut -c1-$MAX_SUFFIX_LENGTH)
+    # Remove trailing hyphen if truncation created one
+    TRUNCATED_SUFFIX=$(echo "$TRUNCATED_SUFFIX" | sed 's/-$//')
+    
+    ORIGINAL_BRANCH_NAME="$BRANCH_NAME"
+    BRANCH_NAME="${FEATURE_NUM}-${TRUNCATED_SUFFIX}"
+    
+    >&2 echo "[specify] Warning: Branch name exceeded GitHub's 244-byte limit"
+    >&2 echo "[specify] Original: $ORIGINAL_BRANCH_NAME (${#ORIGINAL_BRANCH_NAME} bytes)"
+    >&2 echo "[specify] Truncated to: $BRANCH_NAME (${#BRANCH_NAME} bytes)"
+fi
+
+if [ "$HAS_GIT" = true ]; then
+    git checkout -b "$BRANCH_NAME"
+else
+    >&2 echo "[specify] Warning: Git repository not detected; skipped branch creation for $BRANCH_NAME"
+fi
+
+FEATURE_DIR="$SPECS_DIR/$BRANCH_NAME"
+mkdir -p "$FEATURE_DIR"
+
+TEMPLATE="$REPO_ROOT/.specify/templates/spec-template.md"
+SPEC_FILE="$FEATURE_DIR/spec.md"
+if [ -f "$TEMPLATE" ]; then cp "$TEMPLATE" "$SPEC_FILE"; else touch "$SPEC_FILE"; fi
+
+# Set the SPECIFY_FEATURE environment variable for the current session
+export SPECIFY_FEATURE="$BRANCH_NAME"
+
+if $JSON_MODE; then
+    printf '{"BRANCH_NAME":"%s","SPEC_FILE":"%s","FEATURE_NUM":"%s"}\n' "$BRANCH_NAME" "$SPEC_FILE" "$FEATURE_NUM"
+else
+    echo "BRANCH_NAME: $BRANCH_NAME"
+    echo "SPEC_FILE: $SPEC_FILE"
+    echo "FEATURE_NUM: $FEATURE_NUM"
+    echo "SPECIFY_FEATURE environment variable set to: $BRANCH_NAME"
+fi

.specify/scripts/bash/setup-plan.sh

@@ -0,0 +1,61 @@
+#!/usr/bin/env bash
+
+set -e
+
+# Parse command line arguments
+JSON_MODE=false
+ARGS=()
+
+for arg in "$@"; do
+    case "$arg" in
+        --json) 
+            JSON_MODE=true 
+            ;;
+        --help|-h) 
+            echo "Usage: $0 [--json]"
+            echo "  --json    Output results in JSON format"
+            echo "  --help    Show this help message"
+            exit 0 
+            ;;
+        *) 
+            ARGS+=("$arg") 
+            ;;
+    esac
+done
+
+# Get script directory and load common functions
+SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "$SCRIPT_DIR/common.sh"
+
+# Get all paths and variables from common functions
+eval $(get_feature_paths)
+
+# Check if we're on a proper feature branch (only for git repos)
+check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
+
+# Ensure the feature directory exists
+mkdir -p "$FEATURE_DIR"
+
+# Copy plan template if it exists
+TEMPLATE="$REPO_ROOT/.specify/templates/plan-template.md"
+if [[ -f "$TEMPLATE" ]]; then
+    cp "$TEMPLATE" "$IMPL_PLAN"
+    echo "Copied plan template to $IMPL_PLAN"
+else
+    echo "Warning: Plan template not found at $TEMPLATE"
+    # Create a basic plan file if template doesn't exist
+    touch "$IMPL_PLAN"
+fi
+
+# Output results
+if $JSON_MODE; then
+    printf '{"FEATURE_SPEC":"%s","IMPL_PLAN":"%s","SPECS_DIR":"%s","BRANCH":"%s","HAS_GIT":"%s"}\n' \
+        "$FEATURE_SPEC" "$IMPL_PLAN" "$FEATURE_DIR" "$CURRENT_BRANCH" "$HAS_GIT"
+else
+    echo "FEATURE_SPEC: $FEATURE_SPEC"
+    echo "IMPL_PLAN: $IMPL_PLAN" 
+    echo "SPECS_DIR: $FEATURE_DIR"
+    echo "BRANCH: $CURRENT_BRANCH"
+    echo "HAS_GIT: $HAS_GIT"
+fi
+

.specify/scripts/bash/update-agent-context.sh

@@ -0,0 +1,781 @@
+#!/usr/bin/env bash
+
+# Update agent context files with information from plan.md
+#
+# This script maintains AI agent context files by parsing feature specifications 
+# and updating agent-specific configuration files with project information.
+#
+# MAIN FUNCTIONS:
+# 1. Environment Validation
+#    - Verifies git repository structure and branch information
+#    - Checks for required plan.md files and templates
+#    - Validates file permissions and accessibility
+#
+# 2. Plan Data Extraction
+#    - Parses plan.md files to extract project metadata
+#    - Identifies language/version, frameworks, databases, and project types
+#    - Handles missing or incomplete specification data gracefully
+#
+# 3. Agent File Management
+#    - Creates new agent context files from templates when needed
+#    - Updates existing agent files with new project information
+#    - Preserves manual additions and custom configurations
+#    - Supports multiple AI agent formats and directory structures
+#
+# 4. Content Generation
+#    - Generates language-specific build/test commands
+#    - Creates appropriate project directory structures
+#    - Updates technology stacks and recent changes sections
+#    - Maintains consistent formatting and timestamps
+#
+# 5. Multi-Agent Support
+#    - Handles agent-specific file paths and naming conventions
+#    - Supports: Claude, Gemini, Copilot, Cursor, Qwen, opencode, Codex, Windsurf, Kilo Code, Auggie CLI, Roo Code, CodeBuddy CLI, Amp, SHAI, or Amazon Q Developer CLI
+#    - Can update single agents or all existing agent files
+#    - Creates default Claude file if no agent files exist
+#
+# Usage: ./update-agent-context.sh [agent_type]
+# Agent types: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|shai|q
+# Leave empty to update all existing agent files
+
+set -e
+
+# Enable strict error handling
+set -u
+set -o pipefail
+
+#==============================================================================
+# Configuration and Global Variables
+#==============================================================================
+
+# Get script directory and load common functions
+SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "$SCRIPT_DIR/common.sh"
+
+# Get all paths and variables from common functions
+eval $(get_feature_paths)
+
+NEW_PLAN="$IMPL_PLAN"  # Alias for compatibility with existing code
+AGENT_TYPE="${1:-}"
+
+# Agent-specific file paths  
+CLAUDE_FILE="$REPO_ROOT/CLAUDE.md"
+GEMINI_FILE="$REPO_ROOT/GEMINI.md"
+COPILOT_FILE="$REPO_ROOT/.github/agents/copilot-instructions.md"
+CURSOR_FILE="$REPO_ROOT/.cursor/rules/specify-rules.mdc"
+QWEN_FILE="$REPO_ROOT/QWEN.md"
+AGENTS_FILE="$REPO_ROOT/AGENTS.md"
+WINDSURF_FILE="$REPO_ROOT/.windsurf/rules/specify-rules.md"
+KILOCODE_FILE="$REPO_ROOT/.kilocode/rules/specify-rules.md"
+AUGGIE_FILE="$REPO_ROOT/.augment/rules/specify-rules.md"
+ROO_FILE="$REPO_ROOT/.roo/rules/specify-rules.md"
+CODEBUDDY_FILE="$REPO_ROOT/CODEBUDDY.md"
+AMP_FILE="$REPO_ROOT/AGENTS.md"
+SHAI_FILE="$REPO_ROOT/SHAI.md"
+Q_FILE="$REPO_ROOT/AGENTS.md"
+
+# Template file
+TEMPLATE_FILE="$REPO_ROOT/.specify/templates/agent-file-template.md"
+
+# Global variables for parsed plan data
+NEW_LANG=""
+NEW_FRAMEWORK=""
+NEW_DB=""
+NEW_PROJECT_TYPE=""
+
+#==============================================================================
+# Utility Functions
+#==============================================================================
+
+log_info() {
+    echo "INFO: $1"
+}
+
+log_success() {
+    echo "✓ $1"
+}
+
+log_error() {
+    echo "ERROR: $1" >&2
+}
+
+log_warning() {
+    echo "WARNING: $1" >&2
+}
+
+# Cleanup function for temporary files
+cleanup() {
+    local exit_code=$?
+    rm -f /tmp/agent_update_*_$$
+    rm -f /tmp/manual_additions_$$
+    exit $exit_code
+}
+
+# Set up cleanup trap
+trap cleanup EXIT INT TERM
+
+#==============================================================================
+# Validation Functions
+#==============================================================================
+
+validate_environment() {
+    # Check if we have a current branch/feature (git or non-git)
+    if [[ -z "$CURRENT_BRANCH" ]]; then
+        log_error "Unable to determine current feature"
+        if [[ "$HAS_GIT" == "true" ]]; then
+            log_info "Make sure you're on a feature branch"
+        else
+            log_info "Set SPECIFY_FEATURE environment variable or create a feature first"
+        fi
+        exit 1
+    fi
+    
+    # Check if plan.md exists
+    if [[ ! -f "$NEW_PLAN" ]]; then
+        log_error "No plan.md found at $NEW_PLAN"
+        log_info "Make sure you're working on a feature with a corresponding spec directory"
+        if [[ "$HAS_GIT" != "true" ]]; then
+            log_info "Use: export SPECIFY_FEATURE=your-feature-name or create a new feature first"
+        fi
+        exit 1
+    fi
+    
+    # Check if template exists (needed for new files)
+    if [[ ! -f "$TEMPLATE_FILE" ]]; then
+        log_warning "Template file not found at $TEMPLATE_FILE"
+        log_warning "Creating new agent files will fail"
+    fi
+}
+
+#==============================================================================
+# Plan Parsing Functions
+#==============================================================================
+
+extract_plan_field() {
+    local field_pattern="$1"
+    local plan_file="$2"
+    
+    grep "^\*\*${field_pattern}\*\*: " "$plan_file" 2>/dev/null | \
+        head -1 | \
+        sed "s|^\*\*${field_pattern}\*\*: ||" | \
+        sed 's/^[ \t]*//;s/[ \t]*$//' | \
+        grep -v "NEEDS CLARIFICATION" | \
+        grep -v "^N/A$" || echo ""
+}
+
+parse_plan_data() {
+    local plan_file="$1"
+    
+    if [[ ! -f "$plan_file" ]]; then
+        log_error "Plan file not found: $plan_file"
+        return 1
+    fi
+    
+    if [[ ! -r "$plan_file" ]]; then
+        log_error "Plan file is not readable: $plan_file"
+        return 1
+    fi
+    
+    log_info "Parsing plan data from $plan_file"
+    
+    NEW_LANG=$(extract_plan_field "Language/Version" "$plan_file")
+    NEW_FRAMEWORK=$(extract_plan_field "Primary Dependencies" "$plan_file")
+    NEW_DB=$(extract_plan_field "Storage" "$plan_file")
+    NEW_PROJECT_TYPE=$(extract_plan_field "Project Type" "$plan_file")
+    
+    # Log what we found
+    if [[ -n "$NEW_LANG" ]]; then
+        log_info "Found language: $NEW_LANG"
+    else
+        log_warning "No language information found in plan"
+    fi
+    
+    if [[ -n "$NEW_FRAMEWORK" ]]; then
+        log_info "Found framework: $NEW_FRAMEWORK"
+    fi
+    
+    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
+        log_info "Found database: $NEW_DB"
+    fi
+    
+    if [[ -n "$NEW_PROJECT_TYPE" ]]; then
+        log_info "Found project type: $NEW_PROJECT_TYPE"
+    fi
+}
+
+format_technology_stack() {
+    local lang="$1"
+    local framework="$2"
+    local parts=()
+    
+    # Add non-empty parts
+    [[ -n "$lang" && "$lang" != "NEEDS CLARIFICATION" ]] && parts+=("$lang")
+    [[ -n "$framework" && "$framework" != "NEEDS CLARIFICATION" && "$framework" != "N/A" ]] && parts+=("$framework")
+    
+    # Join with proper formatting
+    if [[ ${#parts[@]} -eq 0 ]]; then
+        echo ""
+    elif [[ ${#parts[@]} -eq 1 ]]; then
+        echo "${parts[0]}"
+    else
+        # Join multiple parts with " + "
+        local result="${parts[0]}"
+        for ((i=1; i<${#parts[@]}; i++)); do
+            result="$result + ${parts[i]}"
+        done
+        echo "$result"
+    fi
+}
+
+#==============================================================================
+# Template and Content Generation Functions
+#==============================================================================
+
+get_project_structure() {
+    local project_type="$1"
+    
+    if [[ "$project_type" == *"web"* ]]; then
+        echo "backend/\\nfrontend/\\ntests/"
+    else
+        echo "src/\\ntests/"
+    fi
+}
+
+get_commands_for_language() {
+    local lang="$1"
+    
+    case "$lang" in
+        *"Python"*)
+            echo "cd src && pytest && ruff check ."
+            ;;
+        *"Rust"*)
+            echo "cargo test && cargo clippy"
+            ;;
+        *"JavaScript"*|*"TypeScript"*)
+            echo "npm test \\&\\& npm run lint"
+            ;;
+        *)
+            echo "# Add commands for $lang"
+            ;;
+    esac
+}
+
+get_language_conventions() {
+    local lang="$1"
+    echo "$lang: Follow standard conventions"
+}
+
+create_new_agent_file() {
+    local target_file="$1"
+    local temp_file="$2"
+    local project_name="$3"
+    local current_date="$4"
+    
+    if [[ ! -f "$TEMPLATE_FILE" ]]; then
+        log_error "Template not found at $TEMPLATE_FILE"
+        return 1
+    fi
+    
+    if [[ ! -r "$TEMPLATE_FILE" ]]; then
+        log_error "Template file is not readable: $TEMPLATE_FILE"
+        return 1
+    fi
+    
+    log_info "Creating new agent context file from template..."
+    
+    if ! cp "$TEMPLATE_FILE" "$temp_file"; then
+        log_error "Failed to copy template file"
+        return 1
+    fi
+    
+    # Replace template placeholders
+    local project_structure
+    project_structure=$(get_project_structure "$NEW_PROJECT_TYPE")
+    
+    local commands
+    commands=$(get_commands_for_language "$NEW_LANG")
+    
+    local language_conventions
+    language_conventions=$(get_language_conventions "$NEW_LANG")
+    
+    # Perform substitutions with error checking using safer approach
+    # Escape special characters for sed by using a different delimiter or escaping
+    local escaped_lang=$(printf '%s\n' "$NEW_LANG" | sed 's/[\[\.*^$()+{}|]/\\&/g')
+    local escaped_framework=$(printf '%s\n' "$NEW_FRAMEWORK" | sed 's/[\[\.*^$()+{}|]/\\&/g')
+    local escaped_branch=$(printf '%s\n' "$CURRENT_BRANCH" | sed 's/[\[\.*^$()+{}|]/\\&/g')
+    
+    # Build technology stack and recent change strings conditionally
+    local tech_stack
+    if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
+        tech_stack="- $escaped_lang + $escaped_framework ($escaped_branch)"
+    elif [[ -n "$escaped_lang" ]]; then
+        tech_stack="- $escaped_lang ($escaped_branch)"
+    elif [[ -n "$escaped_framework" ]]; then
+        tech_stack="- $escaped_framework ($escaped_branch)"
+    else
+        tech_stack="- ($escaped_branch)"
+    fi
+
+    local recent_change
+    if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
+        recent_change="- $escaped_branch: Added $escaped_lang + $escaped_framework"
+    elif [[ -n "$escaped_lang" ]]; then
+        recent_change="- $escaped_branch: Added $escaped_lang"
+    elif [[ -n "$escaped_framework" ]]; then
+        recent_change="- $escaped_branch: Added $escaped_framework"
+    else
+        recent_change="- $escaped_branch: Added"
+    fi
+
+    local substitutions=(
+        "s|\[PROJECT NAME\]|$project_name|"
+        "s|\[DATE\]|$current_date|"
+        "s|\[EXTRACTED FROM ALL PLAN.MD FILES\]|$tech_stack|"
+        "s|\[ACTUAL STRUCTURE FROM PLANS\]|$project_structure|g"
+        "s|\[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES\]|$commands|"
+        "s|\[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE\]|$language_conventions|"
+        "s|\[LAST 3 FEATURES AND WHAT THEY ADDED\]|$recent_change|"
+    )
+    
+    for substitution in "${substitutions[@]}"; do
+        if ! sed -i.bak -e "$substitution" "$temp_file"; then
+            log_error "Failed to perform substitution: $substitution"
+            rm -f "$temp_file" "$temp_file.bak"
+            return 1
+        fi
+    done
+    
+    # Convert \n sequences to actual newlines
+    newline=$(printf '\n')
+    sed -i.bak2 "s/\\\\n/${newline}/g" "$temp_file"
+    
+    # Clean up backup files
+    rm -f "$temp_file.bak" "$temp_file.bak2"
+    
+    return 0
+}
+
+
+
+
+update_existing_agent_file() {
+    local target_file="$1"
+    local current_date="$2"
+    
+    log_info "Updating existing agent context file..."
+    
+    # Use a single temporary file for atomic update
+    local temp_file
+    temp_file=$(mktemp) || {
+        log_error "Failed to create temporary file"
+        return 1
+    }
+    
+    # Process the file in one pass
+    local tech_stack=$(format_technology_stack "$NEW_LANG" "$NEW_FRAMEWORK")
+    local new_tech_entries=()
+    local new_change_entry=""
+    
+    # Prepare new technology entries
+    if [[ -n "$tech_stack" ]] && ! grep -q "$tech_stack" "$target_file"; then
+        new_tech_entries+=("- $tech_stack ($CURRENT_BRANCH)")
+    fi
+    
+    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]] && ! grep -q "$NEW_DB" "$target_file"; then
+        new_tech_entries+=("- $NEW_DB ($CURRENT_BRANCH)")
+    fi
+    
+    # Prepare new change entry
+    if [[ -n "$tech_stack" ]]; then
+        new_change_entry="- $CURRENT_BRANCH: Added $tech_stack"
+    elif [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]]; then
+        new_change_entry="- $CURRENT_BRANCH: Added $NEW_DB"
+    fi
+    
+    # Check if sections exist in the file
+    local has_active_technologies=0
+    local has_recent_changes=0
+    
+    if grep -q "^## Active Technologies" "$target_file" 2>/dev/null; then
+        has_active_technologies=1
+    fi
+    
+    if grep -q "^## Recent Changes" "$target_file" 2>/dev/null; then
+        has_recent_changes=1
+    fi
+    
+    # Process file line by line
+    local in_tech_section=false
+    local in_changes_section=false
+    local tech_entries_added=false
+    local changes_entries_added=false
+    local existing_changes_count=0
+    local file_ended=false
+    
+    while IFS= read -r line || [[ -n "$line" ]]; do
+        # Handle Active Technologies section
+        if [[ "$line" == "## Active Technologies" ]]; then
+            echo "$line" >> "$temp_file"
+            in_tech_section=true
+            continue
+        elif [[ $in_tech_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
+            # Add new tech entries before closing the section
+            if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
+                printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
+                tech_entries_added=true
+            fi
+            echo "$line" >> "$temp_file"
+            in_tech_section=false
+            continue
+        elif [[ $in_tech_section == true ]] && [[ -z "$line" ]]; then
+            # Add new tech entries before empty line in tech section
+            if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
+                printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
+                tech_entries_added=true
+            fi
+            echo "$line" >> "$temp_file"
+            continue
+        fi
+        
+        # Handle Recent Changes section
+        if [[ "$line" == "## Recent Changes" ]]; then
+            echo "$line" >> "$temp_file"
+            # Add new change entry right after the heading
+            if [[ -n "$new_change_entry" ]]; then
+                echo "$new_change_entry" >> "$temp_file"
+            fi
+            in_changes_section=true
+            changes_entries_added=true
+            continue
+        elif [[ $in_changes_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
+            echo "$line" >> "$temp_file"
+            in_changes_section=false
+            continue
+        elif [[ $in_changes_section == true ]] && [[ "$line" == "- "* ]]; then
+            # Keep only first 2 existing changes
+            if [[ $existing_changes_count -lt 2 ]]; then
+                echo "$line" >> "$temp_file"
+                ((existing_changes_count++))
+            fi
+            continue
+        fi
+        
+        # Update timestamp
+        if [[ "$line" =~ \*\*Last\ updated\*\*:.*[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9] ]]; then
+            echo "$line" | sed "s/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]/$current_date/" >> "$temp_file"
+        else
+            echo "$line" >> "$temp_file"
+        fi
+    done < "$target_file"
+    
+    # Post-loop check: if we're still in the Active Technologies section and haven't added new entries
+    if [[ $in_tech_section == true ]] && [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
+        printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
+        tech_entries_added=true
+    fi
+    
+    # If sections don't exist, add them at the end of the file
+    if [[ $has_active_technologies -eq 0 ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
+        echo "" >> "$temp_file"
+        echo "## Active Technologies" >> "$temp_file"
+        printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
+        tech_entries_added=true
+    fi
+    
+    if [[ $has_recent_changes -eq 0 ]] && [[ -n "$new_change_entry" ]]; then
+        echo "" >> "$temp_file"
+        echo "## Recent Changes" >> "$temp_file"
+        echo "$new_change_entry" >> "$temp_file"
+        changes_entries_added=true
+    fi
+    
+    # Move temp file to target atomically
+    if ! mv "$temp_file" "$target_file"; then
+        log_error "Failed to update target file"
+        rm -f "$temp_file"
+        return 1
+    fi
+    
+    return 0
+}
+#==============================================================================
+# Main Agent File Update Function
+#==============================================================================
+
+update_agent_file() {
+    local target_file="$1"
+    local agent_name="$2"
+    
+    if [[ -z "$target_file" ]] || [[ -z "$agent_name" ]]; then
+        log_error "update_agent_file requires target_file and agent_name parameters"
+        return 1
+    fi
+    
+    log_info "Updating $agent_name context file: $target_file"
+    
+    local project_name
+    project_name=$(basename "$REPO_ROOT")
+    local current_date
+    current_date=$(date +%Y-%m-%d)
+    
+    # Create directory if it doesn't exist
+    local target_dir
+    target_dir=$(dirname "$target_file")
+    if [[ ! -d "$target_dir" ]]; then
+        if ! mkdir -p "$target_dir"; then
+            log_error "Failed to create directory: $target_dir"
+            return 1
+        fi
+    fi
+    
+    if [[ ! -f "$target_file" ]]; then
+        # Create new file from template
+        local temp_file
+        temp_file=$(mktemp) || {
+            log_error "Failed to create temporary file"
+            return 1
+        }
+        
+        if create_new_agent_file "$target_file" "$temp_file" "$project_name" "$current_date"; then
+            if mv "$temp_file" "$target_file"; then
+                log_success "Created new $agent_name context file"
+            else
+                log_error "Failed to move temporary file to $target_file"
+                rm -f "$temp_file"
+                return 1
+            fi
+        else
+            log_error "Failed to create new agent file"
+            rm -f "$temp_file"
+            return 1
+        fi
+    else
+        # Update existing file
+        if [[ ! -r "$target_file" ]]; then
+            log_error "Cannot read existing file: $target_file"
+            return 1
+        fi
+        
+        if [[ ! -w "$target_file" ]]; then
+            log_error "Cannot write to existing file: $target_file"
+            return 1
+        fi
+        
+        if update_existing_agent_file "$target_file" "$current_date"; then
+            log_success "Updated existing $agent_name context file"
+        else
+            log_error "Failed to update existing agent file"
+            return 1
+        fi
+    fi
+    
+    return 0
+}
+
+#==============================================================================
+# Agent Selection and Processing
+#==============================================================================
+
+update_specific_agent() {
+    local agent_type="$1"
+    
+    case "$agent_type" in
+        claude)
+            update_agent_file "$CLAUDE_FILE" "Claude Code"
+            ;;
+        gemini)
+            update_agent_file "$GEMINI_FILE" "Gemini CLI"
+            ;;
+        copilot)
+            update_agent_file "$COPILOT_FILE" "GitHub Copilot"
+            ;;
+        cursor-agent)
+            update_agent_file "$CURSOR_FILE" "Cursor IDE"
+            ;;
+        qwen)
+            update_agent_file "$QWEN_FILE" "Qwen Code"
+            ;;
+        opencode)
+            update_agent_file "$AGENTS_FILE" "opencode"
+            ;;
+        codex)
+            update_agent_file "$AGENTS_FILE" "Codex CLI"
+            ;;
+        windsurf)
+            update_agent_file "$WINDSURF_FILE" "Windsurf"
+            ;;
+        kilocode)
+            update_agent_file "$KILOCODE_FILE" "Kilo Code"
+            ;;
+        auggie)
+            update_agent_file "$AUGGIE_FILE" "Auggie CLI"
+            ;;
+        roo)
+            update_agent_file "$ROO_FILE" "Roo Code"
+            ;;
+        codebuddy)
+            update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
+            ;;
+        amp)
+            update_agent_file "$AMP_FILE" "Amp"
+            ;;
+        shai)
+            update_agent_file "$SHAI_FILE" "SHAI"
+            ;;
+        q)
+            update_agent_file "$Q_FILE" "Amazon Q Developer CLI"
+            ;;
+        *)
+            log_error "Unknown agent type '$agent_type'"
+            log_error "Expected: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|amp|shai|q"
+            exit 1
+            ;;
+    esac
+}
+
+update_all_existing_agents() {
+    local found_agent=false
+    
+    # Check each possible agent file and update if it exists
+    if [[ -f "$CLAUDE_FILE" ]]; then
+        update_agent_file "$CLAUDE_FILE" "Claude Code"
+        found_agent=true
+    fi
+    
+    if [[ -f "$GEMINI_FILE" ]]; then
+        update_agent_file "$GEMINI_FILE" "Gemini CLI"
+        found_agent=true
+    fi
+    
+    if [[ -f "$COPILOT_FILE" ]]; then
+        update_agent_file "$COPILOT_FILE" "GitHub Copilot"
+        found_agent=true
+    fi
+    
+    if [[ -f "$CURSOR_FILE" ]]; then
+        update_agent_file "$CURSOR_FILE" "Cursor IDE"
+        found_agent=true
+    fi
+    
+    if [[ -f "$QWEN_FILE" ]]; then
+        update_agent_file "$QWEN_FILE" "Qwen Code"
+        found_agent=true
+    fi
+    
+    if [[ -f "$AGENTS_FILE" ]]; then
+        update_agent_file "$AGENTS_FILE" "Codex/opencode"
+        found_agent=true
+    fi
+    
+    if [[ -f "$WINDSURF_FILE" ]]; then
+        update_agent_file "$WINDSURF_FILE" "Windsurf"
+        found_agent=true
+    fi
+    
+    if [[ -f "$KILOCODE_FILE" ]]; then
+        update_agent_file "$KILOCODE_FILE" "Kilo Code"
+        found_agent=true
+    fi
+
+    if [[ -f "$AUGGIE_FILE" ]]; then
+        update_agent_file "$AUGGIE_FILE" "Auggie CLI"
+        found_agent=true
+    fi
+    
+    if [[ -f "$ROO_FILE" ]]; then
+        update_agent_file "$ROO_FILE" "Roo Code"
+        found_agent=true
+    fi
+
+    if [[ -f "$CODEBUDDY_FILE" ]]; then
+        update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
+        found_agent=true
+    fi
+
+    if [[ -f "$SHAI_FILE" ]]; then
+        update_agent_file "$SHAI_FILE" "SHAI"
+        found_agent=true
+    fi
+
+    if [[ -f "$Q_FILE" ]]; then
+        update_agent_file "$Q_FILE" "Amazon Q Developer CLI"
+        found_agent=true
+    fi
+    
+    # If no agent files exist, create a default Claude file
+    if [[ "$found_agent" == false ]]; then
+        log_info "No existing agent files found, creating default Claude file..."
+        update_agent_file "$CLAUDE_FILE" "Claude Code"
+    fi
+}
+print_summary() {
+    echo
+    log_info "Summary of changes:"
+    
+    if [[ -n "$NEW_LANG" ]]; then
+        echo "  - Added language: $NEW_LANG"
+    fi
+    
+    if [[ -n "$NEW_FRAMEWORK" ]]; then
+        echo "  - Added framework: $NEW_FRAMEWORK"
+    fi
+    
+    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
+        echo "  - Added database: $NEW_DB"
+    fi
+    
+    echo
+
+    log_info "Usage: $0 [claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|codebuddy|shai|q]"
+}
+
+#==============================================================================
+# Main Execution
+#==============================================================================
+
+main() {
+    # Validate environment before proceeding
+    validate_environment
+    
+    log_info "=== Updating agent context files for feature $CURRENT_BRANCH ==="
+    
+    # Parse the plan file to extract project information
+    if ! parse_plan_data "$NEW_PLAN"; then
+        log_error "Failed to parse plan data"
+        exit 1
+    fi
+    
+    # Process based on agent type argument
+    local success=true
+    
+    if [[ -z "$AGENT_TYPE" ]]; then
+        # No specific agent provided - update all existing agent files
+        log_info "No agent specified, updating all existing agent files..."
+        if ! update_all_existing_agents; then
+            success=false
+        fi
+    else
+        # Specific agent provided - update only that agent
+        log_info "Updating specific agent: $AGENT_TYPE"
+        if ! update_specific_agent "$AGENT_TYPE"; then
+            success=false
+        fi
+    fi
+    
+    # Print summary
+    print_summary
+    
+    if [[ "$success" == true ]]; then
+        log_success "Agent context update completed successfully"
+        exit 0
+    else
+        log_error "Agent context update completed with errors"
+        exit 1
+    fi
+}
+
+# Execute main function if script is run directly
+if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
+    main "$@"
+fi
+

.specify/templates/agent-file-template.md

@@ -0,0 +1,28 @@
+# [PROJECT NAME] Development Guidelines
+
+Auto-generated from all feature plans. Last updated: [DATE]
+
+## Active Technologies
+
+[EXTRACTED FROM ALL PLAN.MD FILES]
+
+## Project Structure
+
+```text
+[ACTUAL STRUCTURE FROM PLANS]
+```
+
+## Commands
+
+[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]
+
+## Code Style
+
+[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]
+
+## Recent Changes
+
+[LAST 3 FEATURES AND WHAT THEY ADDED]
+
+<!-- MANUAL ADDITIONS START -->
+<!-- MANUAL ADDITIONS END -->

.specify/templates/checklist-template.md

@@ -0,0 +1,40 @@
+# [CHECKLIST TYPE] Checklist: [FEATURE NAME]
+
+**Purpose**: [Brief description of what this checklist covers]
+**Created**: [DATE]
+**Feature**: [Link to spec.md or relevant documentation]
+
+**Note**: This checklist is generated by the `/speckit.checklist` command based on feature context and requirements.
+
+<!-- 
+  ============================================================================
+  IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
+  
+  The /speckit.checklist command MUST replace these with actual items based on:
+  - User's specific checklist request
+  - Feature requirements from spec.md
+  - Technical context from plan.md
+  - Implementation details from tasks.md
+  
+  DO NOT keep these sample items in the generated checklist file.
+  ============================================================================
+-->
+
+## [Category 1]
+
+- [ ] CHK001 First checklist item with clear action
+- [ ] CHK002 Second checklist item
+- [ ] CHK003 Third checklist item
+
+## [Category 2]
+
+- [ ] CHK004 Another category item
+- [ ] CHK005 Item with specific criteria
+- [ ] CHK006 Final item in this category
+
+## Notes
+
+- Check items off as completed: `[x]`
+- Add comments or findings inline
+- Link to relevant resources or documentation
+- Items are numbered sequentially for easy reference

.specify/templates/plan-template.md

@@ -0,0 +1,104 @@
+# Implementation Plan: [FEATURE]
+
+**Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
+**Input**: Feature specification from `/specs/[###-feature-name]/spec.md`
+
+**Note**: This template is filled in by the `/speckit.plan` command. See `.specify/templates/commands/plan.md` for the execution workflow.
+
+## Summary
+
+[Extract from feature spec: primary requirement + technical approach from research]
+
+## Technical Context
+
+<!--
+  ACTION REQUIRED: Replace the content in this section with the technical details
+  for the project. The structure here is presented in advisory capacity to guide
+  the iteration process.
+-->
+
+**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]  
+**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]  
+**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]  
+**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]  
+**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
+**Project Type**: [single/web/mobile - determines source structure]  
+**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]  
+**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]  
+**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]
+
+## Constitution Check
+
+*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
+
+[Gates determined based on constitution file]
+
+## Project Structure
+
+### Documentation (this feature)
+
+```text
+specs/[###-feature]/
+├── plan.md              # This file (/speckit.plan command output)
+├── research.md          # Phase 0 output (/speckit.plan command)
+├── data-model.md        # Phase 1 output (/speckit.plan command)
+├── quickstart.md        # Phase 1 output (/speckit.plan command)
+├── contracts/           # Phase 1 output (/speckit.plan command)
+└── tasks.md             # Phase 2 output (/speckit.tasks command - NOT created by /speckit.plan)
+```
+
+### Source Code (repository root)
+<!--
+  ACTION REQUIRED: Replace the placeholder tree below with the concrete layout
+  for this feature. Delete unused options and expand the chosen structure with
+  real paths (e.g., apps/admin, packages/something). The delivered plan must
+  not include Option labels.
+-->
+
+```text
+# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
+src/
+├── models/
+├── services/
+├── cli/
+└── lib/
+
+tests/
+├── contract/
+├── integration/
+└── unit/
+
+# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
+backend/
+├── src/
+│   ├── models/
+│   ├── services/
+│   └── api/
+└── tests/
+
+frontend/
+├── src/
+│   ├── components/
+│   ├── pages/
+│   └── services/
+└── tests/
+
+# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
+api/
+└── [same as backend above]
+
+ios/ or android/
+└── [platform-specific structure: feature modules, UI flows, platform tests]
+```
+
+**Structure Decision**: [Document the selected structure and reference the real
+directories captured above]
+
+## Complexity Tracking
+
+> **Fill ONLY if Constitution Check has violations that must be justified**
+
+| Violation | Why Needed | Simpler Alternative Rejected Because |
+|-----------|------------|-------------------------------------|
+| [e.g., 4th project] | [current need] | [why 3 projects insufficient] |
+| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient] |

.specify/templates/spec-template.md

@@ -0,0 +1,115 @@
+# Feature Specification: [FEATURE NAME]
+
+**Feature Branch**: `[###-feature-name]`  
+**Created**: [DATE]  
+**Status**: Draft  
+**Input**: User description: "$ARGUMENTS"
+
+## User Scenarios & Testing *(mandatory)*
+
+<!--
+  IMPORTANT: User stories should be PRIORITIZED as user journeys ordered by importance.
+  Each user story/journey must be INDEPENDENTLY TESTABLE - meaning if you implement just ONE of them,
+  you should still have a viable MVP (Minimum Viable Product) that delivers value.
+  
+  Assign priorities (P1, P2, P3, etc.) to each story, where P1 is the most critical.
+  Think of each story as a standalone slice of functionality that can be:
+  - Developed independently
+  - Tested independently
+  - Deployed independently
+  - Demonstrated to users independently
+-->
+
+### User Story 1 - [Brief Title] (Priority: P1)
+
+[Describe this user journey in plain language]
+
+**Why this priority**: [Explain the value and why it has this priority level]
+
+**Independent Test**: [Describe how this can be tested independently - e.g., "Can be fully tested by [specific action] and delivers [specific value]"]
+
+**Acceptance Scenarios**:
+
+1. **Given** [initial state], **When** [action], **Then** [expected outcome]
+2. **Given** [initial state], **When** [action], **Then** [expected outcome]
+
+---
+
+### User Story 2 - [Brief Title] (Priority: P2)
+
+[Describe this user journey in plain language]
+
+**Why this priority**: [Explain the value and why it has this priority level]
+
+**Independent Test**: [Describe how this can be tested independently]
+
+**Acceptance Scenarios**:
+
+1. **Given** [initial state], **When** [action], **Then** [expected outcome]
+
+---
+
+### User Story 3 - [Brief Title] (Priority: P3)
+
+[Describe this user journey in plain language]
+
+**Why this priority**: [Explain the value and why it has this priority level]
+
+**Independent Test**: [Describe how this can be tested independently]
+
+**Acceptance Scenarios**:
+
+1. **Given** [initial state], **When** [action], **Then** [expected outcome]
+
+---
+
+[Add more user stories as needed, each with an assigned priority]
+
+### Edge Cases
+
+<!--
+  ACTION REQUIRED: The content in this section represents placeholders.
+  Fill them out with the right edge cases.
+-->
+
+- What happens when [boundary condition]?
+- How does system handle [error scenario]?
+
+## Requirements *(mandatory)*
+
+<!--
+  ACTION REQUIRED: The content in this section represents placeholders.
+  Fill them out with the right functional requirements.
+-->
+
+### Functional Requirements
+
+- **FR-001**: System MUST [specific capability, e.g., "allow users to create accounts"]
+- **FR-002**: System MUST [specific capability, e.g., "validate email addresses"]  
+- **FR-003**: Users MUST be able to [key interaction, e.g., "reset their password"]
+- **FR-004**: System MUST [data requirement, e.g., "persist user preferences"]
+- **FR-005**: System MUST [behavior, e.g., "log all security events"]
+
+*Example of marking unclear requirements:*
+
+- **FR-006**: System MUST authenticate users via [NEEDS CLARIFICATION: auth method not specified - email/password, SSO, OAuth?]
+- **FR-007**: System MUST retain user data for [NEEDS CLARIFICATION: retention period not specified]
+
+### Key Entities *(include if feature involves data)*
+
+- **[Entity 1]**: [What it represents, key attributes without implementation]
+- **[Entity 2]**: [What it represents, relationships to other entities]
+
+## Success Criteria *(mandatory)*
+
+<!--
+  ACTION REQUIRED: Define measurable success criteria.
+  These must be technology-agnostic and measurable.
+-->
+
+### Measurable Outcomes
+
+- **SC-001**: [Measurable metric, e.g., "Users can complete account creation in under 2 minutes"]
+- **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users without degradation"]
+- **SC-003**: [User satisfaction metric, e.g., "90% of users successfully complete primary task on first attempt"]
+- **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]

.specify/templates/tasks-template.md

@@ -0,0 +1,251 @@
+---
+
+description: "Task list template for feature implementation"
+---
+
+# Tasks: [FEATURE NAME]
+
+**Input**: Design documents from `/specs/[###-feature-name]/`
+**Prerequisites**: plan.md (required), spec.md (required for user stories), research.md, data-model.md, contracts/
+
+**Tests**: The examples below include test tasks. Tests are OPTIONAL - only include them if explicitly requested in the feature specification.
+
+**Organization**: Tasks are grouped by user story to enable independent implementation and testing of each story.
+
+## Format: `[ID] [P?] [Story] Description`
+
+- **[P]**: Can run in parallel (different files, no dependencies)
+- **[Story]**: Which user story this task belongs to (e.g., US1, US2, US3)
+- Include exact file paths in descriptions
+
+## Path Conventions
+
+- **Single project**: `src/`, `tests/` at repository root
+- **Web app**: `backend/src/`, `frontend/src/`
+- **Mobile**: `api/src/`, `ios/src/` or `android/src/`
+- Paths shown below assume single project - adjust based on plan.md structure
+
+<!-- 
+  ============================================================================
+  IMPORTANT: The tasks below are SAMPLE TASKS for illustration purposes only.
+  
+  The /speckit.tasks command MUST replace these with actual tasks based on:
+  - User stories from spec.md (with their priorities P1, P2, P3...)
+  - Feature requirements from plan.md
+  - Entities from data-model.md
+  - Endpoints from contracts/
+  
+  Tasks MUST be organized by user story so each story can be:
+  - Implemented independently
+  - Tested independently
+  - Delivered as an MVP increment
+  
+  DO NOT keep these sample tasks in the generated tasks.md file.
+  ============================================================================
+-->
+
+## Phase 1: Setup (Shared Infrastructure)
+
+**Purpose**: Project initialization and basic structure
+
+- [ ] T001 Create project structure per implementation plan
+- [ ] T002 Initialize [language] project with [framework] dependencies
+- [ ] T003 [P] Configure linting and formatting tools
+
+---
+
+## Phase 2: Foundational (Blocking Prerequisites)
+
+**Purpose**: Core infrastructure that MUST be complete before ANY user story can be implemented
+
+**⚠️ CRITICAL**: No user story work can begin until this phase is complete
+
+Examples of foundational tasks (adjust based on your project):
+
+- [ ] T004 Setup database schema and migrations framework
+- [ ] T005 [P] Implement authentication/authorization framework
+- [ ] T006 [P] Setup API routing and middleware structure
+- [ ] T007 Create base models/entities that all stories depend on
+- [ ] T008 Configure error handling and logging infrastructure
+- [ ] T009 Setup environment configuration management
+
+**Checkpoint**: Foundation ready - user story implementation can now begin in parallel
+
+---
+
+## Phase 3: User Story 1 - [Title] (Priority: P1) 🎯 MVP
+
+**Goal**: [Brief description of what this story delivers]
+
+**Independent Test**: [How to verify this story works on its own]
+
+### Tests for User Story 1 (OPTIONAL - only if tests requested) ⚠️
+
+> **NOTE: Write these tests FIRST, ensure they FAIL before implementation**
+
+- [ ] T010 [P] [US1] Contract test for [endpoint] in tests/contract/test_[name].py
+- [ ] T011 [P] [US1] Integration test for [user journey] in tests/integration/test_[name].py
+
+### Implementation for User Story 1
+
+- [ ] T012 [P] [US1] Create [Entity1] model in src/models/[entity1].py
+- [ ] T013 [P] [US1] Create [Entity2] model in src/models/[entity2].py
+- [ ] T014 [US1] Implement [Service] in src/services/[service].py (depends on T012, T013)
+- [ ] T015 [US1] Implement [endpoint/feature] in src/[location]/[file].py
+- [ ] T016 [US1] Add validation and error handling
+- [ ] T017 [US1] Add logging for user story 1 operations
+
+**Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
+
+---
+
+## Phase 4: User Story 2 - [Title] (Priority: P2)
+
+**Goal**: [Brief description of what this story delivers]
+
+**Independent Test**: [How to verify this story works on its own]
+
+### Tests for User Story 2 (OPTIONAL - only if tests requested) ⚠️
+
+- [ ] T018 [P] [US2] Contract test for [endpoint] in tests/contract/test_[name].py
+- [ ] T019 [P] [US2] Integration test for [user journey] in tests/integration/test_[name].py
+
+### Implementation for User Story 2
+
+- [ ] T020 [P] [US2] Create [Entity] model in src/models/[entity].py
+- [ ] T021 [US2] Implement [Service] in src/services/[service].py
+- [ ] T022 [US2] Implement [endpoint/feature] in src/[location]/[file].py
+- [ ] T023 [US2] Integrate with User Story 1 components (if needed)
+
+**Checkpoint**: At this point, User Stories 1 AND 2 should both work independently
+
+---
+
+## Phase 5: User Story 3 - [Title] (Priority: P3)
+
+**Goal**: [Brief description of what this story delivers]
+
+**Independent Test**: [How to verify this story works on its own]
+
+### Tests for User Story 3 (OPTIONAL - only if tests requested) ⚠️
+
+- [ ] T024 [P] [US3] Contract test for [endpoint] in tests/contract/test_[name].py
+- [ ] T025 [P] [US3] Integration test for [user journey] in tests/integration/test_[name].py
+
+### Implementation for User Story 3
+
+- [ ] T026 [P] [US3] Create [Entity] model in src/models/[entity].py
+- [ ] T027 [US3] Implement [Service] in src/services/[service].py
+- [ ] T028 [US3] Implement [endpoint/feature] in src/[location]/[file].py
+
+**Checkpoint**: All user stories should now be independently functional
+
+---
+
+[Add more user story phases as needed, following the same pattern]
+
+---
+
+## Phase N: Polish & Cross-Cutting Concerns
+
+**Purpose**: Improvements that affect multiple user stories
+
+- [ ] TXXX [P] Documentation updates in docs/
+- [ ] TXXX Code cleanup and refactoring
+- [ ] TXXX Performance optimization across all stories
+- [ ] TXXX [P] Additional unit tests (if requested) in tests/unit/
+- [ ] TXXX Security hardening
+- [ ] TXXX Run quickstart.md validation
+
+---
+
+## Dependencies & Execution Order
+
+### Phase Dependencies
+
+- **Setup (Phase 1)**: No dependencies - can start immediately
+- **Foundational (Phase 2)**: Depends on Setup completion - BLOCKS all user stories
+- **User Stories (Phase 3+)**: All depend on Foundational phase completion
+  - User stories can then proceed in parallel (if staffed)
+  - Or sequentially in priority order (P1 → P2 → P3)
+- **Polish (Final Phase)**: Depends on all desired user stories being complete
+
+### User Story Dependencies
+
+- **User Story 1 (P1)**: Can start after Foundational (Phase 2) - No dependencies on other stories
+- **User Story 2 (P2)**: Can start after Foundational (Phase 2) - May integrate with US1 but should be independently testable
+- **User Story 3 (P3)**: Can start after Foundational (Phase 2) - May integrate with US1/US2 but should be independently testable
+
+### Within Each User Story
+
+- Tests (if included) MUST be written and FAIL before implementation
+- Models before services
+- Services before endpoints
+- Core implementation before integration
+- Story complete before moving to next priority
+
+### Parallel Opportunities
+
+- All Setup tasks marked [P] can run in parallel
+- All Foundational tasks marked [P] can run in parallel (within Phase 2)
+- Once Foundational phase completes, all user stories can start in parallel (if team capacity allows)
+- All tests for a user story marked [P] can run in parallel
+- Models within a story marked [P] can run in parallel
+- Different user stories can be worked on in parallel by different team members
+
+---
+
+## Parallel Example: User Story 1
+
+```bash
+# Launch all tests for User Story 1 together (if tests requested):
+Task: "Contract test for [endpoint] in tests/contract/test_[name].py"
+Task: "Integration test for [user journey] in tests/integration/test_[name].py"
+
+# Launch all models for User Story 1 together:
+Task: "Create [Entity1] model in src/models/[entity1].py"
+Task: "Create [Entity2] model in src/models/[entity2].py"
+```
+
+---
+
+## Implementation Strategy
+
+### MVP First (User Story 1 Only)
+
+1. Complete Phase 1: Setup
+2. Complete Phase 2: Foundational (CRITICAL - blocks all stories)
+3. Complete Phase 3: User Story 1
+4. **STOP and VALIDATE**: Test User Story 1 independently
+5. Deploy/demo if ready
+
+### Incremental Delivery
+
+1. Complete Setup + Foundational → Foundation ready
+2. Add User Story 1 → Test independently → Deploy/Demo (MVP!)
+3. Add User Story 2 → Test independently → Deploy/Demo
+4. Add User Story 3 → Test independently → Deploy/Demo
+5. Each story adds value without breaking previous stories
+
+### Parallel Team Strategy
+
+With multiple developers:
+
+1. Team completes Setup + Foundational together
+2. Once Foundational is done:
+   - Developer A: User Story 1
+   - Developer B: User Story 2
+   - Developer C: User Story 3
+3. Stories complete and integrate independently
+
+---
+
+## Notes
+
+- [P] tasks = different files, no dependencies
+- [Story] label maps task to specific user story for traceability
+- Each user story should be independently completable and testable
+- Verify tests fail before implementing
+- Commit after each task or logical group
+- Stop at any checkpoint to validate story independently
+- Avoid: vague tasks, same file conflicts, cross-story dependencies that break independence

.vscode/settings.json

@@ -0,0 +1,2 @@
+{
+}

GEMINI.md

@@ -0,0 +1,29 @@
+# prosberry_produkcija Development Guidelines
+
+Auto-generated from all feature plans. Last updated: 2025-11-17
+
+## Active Technologies
+
+- Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`). + `jq` (for `posodobi_blog.sh`). (001-add-blog)
+
+## Project Structure
+
+```text
+src/
+tests/
+```
+
+## Commands
+
+npm test && npm run lint
+
+## Code Style
+
+Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`).: Follow standard conventions
+
+## Recent Changes
+
+- 001-add-blog: Added Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`). + `jq` (for `posodobi_blog.sh`).
+
+<!-- MANUAL ADDITIONS START -->
+<!-- MANUAL ADDITIONS END -->

README.md

@@ -0,0 +1,115 @@
+## 1. Opis Projekta
+
+**Prosberry.si** je profesionalna spletna stran za podjetje **PROSBERRY, Amra Kurešepi Zulji s.p.** Stran služi kot digitalna vizitka in informacijska točka za storitve, ki jih podjetje ponuja. Glavni cilj projekta je predstaviti strokovnost in osebni pristop Amre Kurešepi Zulji na področju jezikovnega izobraževanja in medkulturnega posredovanja.
+
+Spletna stran je zasnovana kot statična stran (HTML, CSS, JavaScript), kar zagotavlja hitro nalaganje in enostavno vzdrževanje. Za funkcionalnost kontaktnega obrazca se uporablja PHP. Projekt vključuje tudi nabor skript za avtomatizacijo (Python in Shell), ki poenostavljajo procese, kot so optimizacija slik in posodabljanje ponavljajočih se elementov (glava, noga).
+
+### Glavne funkcionalnosti in vsebine:
+- **Predstavitev storitev:** Podroben opis jezikovnih tečajev (angleščina, albanščina, slovenščina), medkulturnega posredovanja in specializiranih delavnic.
+- **Osebna predstavitev:** Stran "Kdo sem" z osebno zgodbo in kvalifikacijami izvajalke.
+- **Cenik in reference:** Pregled cen storitev in mnenja zadovoljnih strank.
+- **Kontaktni obrazec:** Enostaven način za pošiljanje povpraševanj.
+- **Pogosta vprašanja (FAQ):** Odgovori na najpogostejša vprašanja za lažje informiranje obiskovalcev.
+- **Odziven dizajn:** Stran je prilagojena za optimalen prikaz na različnih napravah (mobilni telefoni, tablice, namizni računalniki).
+
+## 2. Struktura Projekta (Zemljevid)
+
+```
+.
+├── assets
+│   ├── favicon
+│   │   └── site.webmanifest
+│   ├── images/
+│   └── pdf/
+├── cene-in-reference
+│   └── index.html
+├── cene-in-sodelovanja
+│   └── index.html
+├── css
+│   ├── animations.css
+│   └── style.css
+├── delavnice
+│   └── index.html
+├── js
+│   └── main.js
+├── kdo-sem
+│   └── index.html
+├── kontakt
+│   ├── index.html
+│   └── process_form.php
+│── politika-zasebnosti
+│   └── index.html
+├── pogosta-vprasanja
+│   └── index.html
+├── ponudba
+│   └── index.html
+├── skupaj-za-vkljucevanje
+│   ├── delavnica-od-tujca-do-sosolca
+│   │   └── index.html
+│   ├── delavnica-sola-in-starsi
+│   │   └── index.html
+│   ├── delavnica-vrtec-novi-zacetki
+│   │   └── index.html
+│   ├── delavnica-zakaj-znati-slovensko
+│   │   └── index.html
+│   └── medkulturno-posredovanje
+│       └── index.html
+├── error_log
+├── footer-template.html
+├── header-template.html
+├── generate_responsive_images.py
+├── index.html
+├── minify_js.py
+├── optimize_images.py
+├── robots.txt
+├── sitemap.xml
+├── update-footer.sh
+└── update-menus.sh
+```
+
+## 3. Opis Datotek in Map
+
+### 📁 Korenske datoteke in mape
+
+- **`index.html`**: Glavna vstopna stran (domača stran), ki pozdravi obiskovalca in na kratko predstavi ključne storitve ter ga usmeri na podstrani.
+- **`kdo-sem/index.html`**: Stran "Kdo sem", ki vsebuje podrobnejšo osebno predstavitev Amre Kurešepi Zulji, njeno zgodbo in strokovno ozadje.
+- **`ponudba/index.html`**: Stran, ki podrobno predstavlja ponudbo jezikovnih tečajev in medkulturnega posredovanja.
+- **`cene-in-reference/index.html`**: Stran s cenikom za posamezne storitve in referencami (mnenji) strank.
+- **`cene-in-sodelovanja/index.html`**: Alternativna ali starejša stran za cene, ki uporabnika preusmeri na kontaktno stran za več informacij.
+- **`kontakt/index.html`**: Stran s kontaktnimi podatki in obrazcem za pošiljanje sporočil.
+- **`pogosta-vprasanja/index.html`**: Stran z zbranimi pogostimi vprašanji in odgovori (FAQ).
+- **`politika-zasebnosti/index.html`**: Pravna stran, ki opisuje politiko varovanja osebnih podatkov v skladu z GDPR.
+- **`delavnice/index.html`**: Pregledna stran, ki deluje kot kazalo za vse razpoložljive delavnice in vodi do njihovih podstrani.
+- **`skupaj-za-vkljucevanje/`**: Mapa, ki združuje vsebine, povezane s programom "Skupaj za vključevanje". Vsebuje podstrani za medkulturno posredovanje in posamezne delavnice.
+
+### 📁 `assets/`
+Mapa za vse statične vire, kot so slike, ikone in dokumenti.
+- **`favicon/site.webmanifest`**: Manifest datoteka, ki brskalnikom omogoča, da spletno stran prikažejo z lastnostmi spletne aplikacije (npr. ikona na domačem zaslonu).
+- **`images/`**: Mapa, kjer so shranjene vse slike, uporabljene na spletni strani.
+- **`pdf/`**: Mapa za PDF dokumente, ki ponujajo podrobnejše opise delavnic.
+
+### 📁 `css/`
+Mapa za stilsko oblikovanje spletne strani.
+- **`style.css`**: Glavna in obsežna CSS datoteka, ki vsebuje vse stile za celotno spletno stran, vključno z odzivnostjo in oblikovanjem posameznih sekcij.
+- **`animations.css`**: Ločena CSS datoteka, namenjena izključno animacijam.
+
+### 📁 `js/`
+Mapa za JavaScript kodo, ki skrbi za interaktivnost.
+- **`main.js`**: Osrednja JavaScript datoteka, ki upravlja:
+  - Delovanje navigacije (mobilni meni, večnivojski dropdown meniji).
+  - Interaktivne elemente, kot so "harmonika" (accordion) na straneh s pogostimi vprašanji.
+  - Inicializacijo knjižnice AOS (Animate On Scroll) za animacije ob drsenju.
+  - Logiko za pošiljanje podatkov iz kontaktnega obrazca.
+
+### ⚙️ Backend in konfiguracija
+- **`kontakt/process_form.php`**: PHP skripta, ki na strežniški strani obdela podatke, poslane preko kontaktnega obrazca, in jih pošlje na e-poštni naslov.
+- **`robots.txt`**: Datoteka, ki spletnim iskalnikom (npr. Google) daje navodila, katere dele spletne strani naj indeksirajo in katerih ne.
+- **`sitemap.xml`**: Zemljevid spletnega mesta v XML formatu, ki iskalnikom pomaga pri lažjem in učinkovitejšem odkrivanju vseh podstrani.
+- **`error_log`**: Samodejno generirana datoteka s strani strežnika, ki beleži morebitne PHP napake.
+
+### 🛠️ Orodja za avtomatizacijo in vzdrževanje
+- **`header-template.html`** in **`footer-template.html`**: Predlogi za glavo in nogo spletne strani. Uporabljata se za centralno upravljanje teh elementov, da jih ni treba ročno urejati na vsaki strani posebej.
+- **`update-menus.sh`** in **`update-footer.sh`**: Shell skripti, ki avtomatizirata posodabljanje glave in noge. Skripta prebere vsebino iz predloge in jo vstavi v vse `.html` datoteke v projektu.
+- **`optimize_images.py`**: Python skripta za optimizacijo slik. Slike pretvori v sodoben in učinkovit `.webp` format, jih po potrebi pomanjša in originale shrani v varnostno kopijo.
+- **`generate_responsive_images.py`**: Python skripta, ki iz originalnih slik ustvari več manjših različic za odziven prikaz na različnih velikostih zaslonov.
+- **`minify_js.py`**: Preprosta Python skripta, ki iz datoteke `main.js` odstrani komentarje in odvečne presledke ter tako zmanjša njeno velikost za hitrejše nalaganje.

assets/favicon/favicon.svg

@@ -0,0 +1,12 @@
+<svg xmlns="http://www.w3.org/2000/svg" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" width="2362" height="2362"><svg width="2362" height="2362" viewBox="0 0 2362 2362" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+    <g id="SvgjsG1013">
+        <path id="SvgjsPath1012" fill="#354142" fill-rule="evenodd" stroke="none" d="M 937.795349 1195.49646 C 966.264954 1138.223022 984.921387 1106.972534 997.62146 1089.100708 C 1010.321472 1071.228516 1034.061401 1039.541016 1050.376953 1018.683716 C 1066.692627 997.826416 1087.135498 966.947021 1095.805664 950.062622 C 1104.475708 933.178345 1117.601318 901.772339 1124.973633 880.271606 C 1138.37793 841.179565 1138.37793 841.179565 1127.140259 820.095703 C 1120.959717 808.499634 1111.712402 787.898071 1106.590576 774.314453 C 1101.468872 760.730713 1094.128784 737.427734 1090.279541 722.529785 C 1086.237793 706.887573 1082.321289 675.795654 1081.01001 648.943848 C 1079.568115 619.415649 1080.373779 589.951904 1083.217896 568.214233 C 1085.68103 549.387207 1091.63916 520.741821 1096.45813 504.558105 C 1101.277344 488.374268 1111.807617 461.318359 1119.859009 444.43396 C 1127.910522 427.549683 1141.736938 403.011475 1150.584595 389.904785 C 1159.432007 376.79834 1175.701416 356.095581 1186.738892 343.898804 C 1197.776123 331.702271 1220.65564 311.329346 1237.582153 298.625732 C 1254.508545 285.922119 1281.612183 268.919189 1297.812256 260.841309 C 1314.012329 252.763428 1339.693848 242.026367 1354.882568 236.981445 C 1370.071167 231.936523 1399.325317 225.135254 1419.891968 221.867188 C 1446.872559 217.580566 1468.851685 216.513672 1498.81958 218.036621 C 1521.663208 219.197266 1552.542603 222.701172 1567.440674 225.82251 C 1582.338623 228.944092 1605.091797 234.944092 1618.00354 239.156006 C 1630.915161 243.367676 1653.668335 252.935303 1668.566406 260.417725 C 1683.464355 267.899902 1707.030396 282.07666 1720.935059 291.921875 C 1734.839722 301.766846 1759.247559 323.45105 1775.174316 340.108765 C 1791.101074 356.766602 1811.88208 382.079712 1821.354004 396.360229 C 1830.82605 410.640869 1844.986816 436.005615 1852.822266 452.726196 C 1860.657959 469.446655 1871.295288 498.393555 1876.460815 517.052246 C 1883.811035 543.602417 1886.2854 562.47998 1887.84375 603.892334 C 1889.341309 643.69519 1888.383545 665.395874 1883.979004 691.466064 C 1880.758667 710.528076 1874.724854 736.285889 1870.570679 748.705566 C 1866.416626 761.125366 1856.626831 784.109863 1848.815796 799.782471 C 1841.004883 815.455078 1827.173096 838.705566 1818.078613 851.450562 C 1808.984009 864.195313 1790.641724 885.502319 1777.317871 898.799316 C 1763.994019 912.096191 1740.851685 931.41394 1725.890625 941.727783 C 1710.929688 952.041504 1687.364136 966.16333 1673.522827 973.109985 C 1659.681396 980.056396 1636.245239 989.802368 1621.442261 994.7677 C 1606.639282 999.733032 1580.380737 1006.572266 1563.089844 1009.966064 C 1545.452881 1013.427612 1512.950684 1016.299194 1489.051392 1016.50708 C 1465.621216 1016.71106 1433.449097 1014.67395 1417.557861 1011.980225 C 1401.666504 1009.286499 1375.237305 1003.193359 1358.82605 998.440186 C 1342.414673 993.686646 1319.085205 985.081299 1306.983032 979.317017 C 1284.978882 968.836426 1284.978882 968.836426 1257.365845 975.547607 C 1242.178711 979.23877 1216.751099 986.509399 1200.859863 991.704712 C 1184.968506 996.89978 1160.946655 1007.635254 1147.477783 1015.561401 C 1134.008911 1023.487427 1112.369263 1039.906738 1099.389526 1052.048584 C 1086.40979 1064.19043 1065.580322 1087.728271 1053.101807 1104.354858 C 1040.623291 1120.981567 1022.966125 1148.732056 1013.863403 1166.022461 C 1004.760925 1183.312866 993.19989 1209.743042 988.172424 1224.756226 C 983.144714 1239.769409 977.736084 1263.335327 976.153137 1277.124878 C 974.570129 1290.914551 974.236633 1311.948364 975.411987 1323.866699 C 976.587585 1335.785156 981.295227 1358.098022 985.873718 1373.450928 L 994.198059 1401.365234 L 1002.113708 1378.712402 C 1006.467346 1366.253296 1015.245117 1346.27356 1021.619934 1334.312988 C 1027.994995 1322.352417 1041.2677 1302.609131 1051.11499 1290.439087 C 1060.962158 1278.269043 1080.805664 1259.033081 1095.211548 1247.692505 C 1109.61731 1236.352051 1131.249268 1222.567261 1143.282593 1217.059814 C 1155.315796 1211.552246 1175.053345 1204.482788 1187.143555 1201.349976 C 1200.475586 1197.895264 1224.262939 1195.653809 1247.59375 1195.653809 C 1283.620483 1195.653809 1286.624023 1196.216309 1294.926514 1204.518677 C 1302.441895 1212.034058 1303.791382 1216.809814 1303.791382 1235.889771 C 1303.791382 1248.268066 1301.162231 1269.063721 1297.94873 1282.102173 C 1294.735352 1295.140747 1286.647095 1317.738281 1279.974976 1332.31897 C 1273.302734 1346.899658 1260.590576 1368.99353 1251.725952 1381.416504 C 1242.861084 1393.839355 1226.164429 1412.660645 1214.622314 1423.241455 C 1203.080078 1433.822266 1181.786255 1450.235596 1167.30249 1459.715454 C 1152.818726 1469.195313 1128.440186 1481.769775 1113.128052 1487.658569 C 1097.815796 1493.547363 1075.089966 1500.359863 1062.626221 1502.797241 C 1042.041626 1506.822754 1040.179565 1507.928955 1042.308838 1514.867798 C 1043.5979 1519.069092 1052.493164 1538.764893 1062.076172 1558.63623 C 1071.659302 1578.507446 1089.584473 1609.919312 1101Line truncated
+        <path id="SvgjsPath1011" fill="#ccb2e6" fill-rule="evenodd" stroke="none" d="M 435.193481 1054.51123 C 401.827332 1054.344849 380.105713 1052.277222 360.121826 1047.365601 C 344.655548 1043.564331 319.464478 1035.236328 304.141479 1028.859009 C 288.818604 1022.481689 266.530151 1011.767334 254.611801 1005.049316 C 242.693466 998.331177 224.563217 986.524658 214.322388 978.812622 C 204.081558 971.100586 185.046753 954.134766 172.022919 941.110962 C 158.998962 928.087036 141.115158 907.30188 132.281052 894.921875 C 123.446945 882.54187 109.75177 859.410767 101.847244 843.519531 C 93.942719 827.628174 83.263115 801.235107 78.114708 784.867676 C 72.966301 768.500488 66.860207 740.87146 64.545509 723.469971 C 62.10561 705.127563 61.166771 672.858154 62.311386 646.685425 C 63.684155 615.297974 67.090675 590.778809 73.489616 566.227905 C 78.551613 546.80603 89.87886 515.926636 98.661278 497.606812 C 107.443687 479.286987 122.753784 452.921265 132.683685 439.016479 C 142.613693 425.111816 163.470856 401.043945 179.033127 385.532593 C 194.595291 370.02124 218.259384 350.062866 231.620163 341.180786 C 244.98082 332.298584 271.469482 317.661743 290.484009 308.654541 C 309.498444 299.647217 339.272705 288.726074 356.648956 284.385254 C 383.113678 277.77417 398.502136 276.49292 451.445831 276.49292 C 510.079102 276.49292 517.130432 277.223877 548.959961 286.600098 C 567.83075 292.158936 594.647095 301.81958 608.55188 308.068115 C 622.456726 314.31665 645.209961 326.650269 659.114746 335.476318 C 673.019592 344.302124 697.19873 363.895874 712.846191 379.0177 C 728.493652 394.139404 749.910095 417.88855 760.43811 431.793213 C 770.966187 445.697998 786.248047 470.076538 794.397827 485.967773 C 802.547668 501.859009 813.184082 527.862671 818.034363 543.753906 C 822.884521 559.645142 828.750427 584.023682 831.069763 597.928345 C 833.745667 613.972046 834.613281 646.304565 833.444214 686.413452 C 831.837097 741.549072 830.350708 753.747314 821.799622 781.972656 C 816.408447 799.768555 807.455811 824.344604 801.905151 836.586548 C 796.354309 848.828491 785.055481 870.218994 776.796509 884.12085 C 761.780029 909.397217 761.780029 909.397217 772.263367 937.856079 C 778.029175 953.508545 788.669556 980.892578 795.908813 998.709595 C 803.147949 1016.526733 808.648193 1032.259033 808.131348 1033.67041 C 807.614563 1035.081787 796.081604 1031.483521 782.502502 1025.674194 C 768.923401 1019.864868 742.919678 1010.067871 724.71637 1003.902832 C 706.513062 997.737671 685.931091 991.893066 678.97876 990.914673 C 668.706604 989.468872 658.940735 992.93457 626.860596 1009.410034 C 605.14801 1020.560913 574.268494 1033.645752 558.239563 1038.487427 C 542.210632 1043.328979 518.531982 1048.967773 505.620331 1051.017944 C 492.70871 1053.068115 461.016632 1054.640137 435.193481 1054.51123 Z"></path>
+        <path id="SvgjsPath1010" fill="#fcb39f" fill-rule="evenodd" stroke="none" d="M 1473.538086 956.873657 C 1454.66748 956.674927 1431.91394 954.988037 1422.97522 953.124878 C 1414.036621 951.261719 1395.41626 946.411255 1381.597168 942.345825 C 1367.77771 938.280396 1345.024414 929.178467 1331.034302 922.119263 C 1317.043823 915.060059 1299.096313 908.552002 1291.150635 907.657104 C 1281.871094 906.611694 1264.432373 909.56604 1242.393555 915.916992 C 1223.522949 921.355103 1199.458984 928.768677 1188.918091 932.391724 C 1169.753052 938.979004 1169.753052 938.979004 1172.243774 930.977295 C 1173.613892 926.576294 1181.130981 905.097778 1188.948242 883.247437 C 1196.80603 861.285156 1202.473389 839.481689 1201.622314 834.490356 C 1200.775635 829.524414 1190.924683 806.690918 1179.731567 783.74939 C 1168.538452 760.807861 1155.711304 727.844482 1151.226929 710.497681 C 1144.478027 684.390015 1143.073608 669.355835 1143.073608 623.209839 C 1143.073608 577.415894 1144.499023 561.948242 1151.056396 536.582153 C 1155.446777 519.598511 1165.399292 492.130249 1173.172729 475.541992 C 1180.946411 458.953735 1194.010376 435.509644 1202.203979 423.443726 C 1210.397705 411.378174 1227.760742 390.847168 1240.78833 377.819336 C 1253.816162 364.791748 1274.347168 347.428589 1286.412842 339.234985 C 1298.478638 331.041382 1321.545532 318.157349 1337.672729 310.60376 C 1353.799805 303.050293 1379.184204 293.393311 1394.082153 289.143555 C 1412.119019 283.998779 1436.520874 280.724365 1467.11438 279.343262 C 1502.767822 277.733887 1520.160889 278.672363 1544.764526 283.533447 C 1562.202393 286.97876 1591.096802 295.426514 1608.974365 302.306152 C 1626.852051 309.185791 1653.107544 322.057739 1667.320435 330.910034 C 1681.533081 339.762573 1701.639771 354.62793 1712.001831 363.944214 C 1722.363892 373.260742 1740.332642 392.157837 1751.932007 405.938232 C 1763.531494 419.718384 1779.719482 443.866577 1787.905273 459.600708 C 1796.091187 475.334839 1806.815796 499.734863 1811.737793 513.822754 C 1816.659912 527.910889 1822.448364 551.785278 1824.601074 566.877075 C 1826.753662 581.968994 1827.734131 617.070068 1826.779907 644.879639 C 1825.225586 690.172119 1823.880249 698.548706 1813.872192 725.241089 C 1807.727051 741.630371 1795.679199 768.446655 1787.098633 784.83313 C 1774.774536 808.369141 1763.533325 822.601196 1733.575806 852.59729 C 1707.401611 878.805054 1686.501099 895.973877 1666.109375 908.018066 C 1649.860107 917.615601 1622.231201 930.414063 1604.711548 936.459229 C 1587.192139 942.504272 1558.230957 949.651611 1540.353394 952.342529 C 1522.475708 955.033325 1492.408813 957.072388 1473.538086 956.873657 Z"></path>
+        <path id="SvgjsPath1009" fill="#9fc3a6" fill-rule="evenodd" stroke="none" d="M 1344.13916 1863.805908 C 1342.661133 1863.805908 1335.375244 1854.578735 1327.948364 1843.301147 C 1320.521362 1832.023438 1311.065063 1811.669434 1306.934326 1798.069824 C 1300.632935 1777.323486 1299.670044 1766.526367 1300.952759 1730.992554 C 1302.011597 1701.661499 1304.427124 1684.027466 1308.810059 1673.632446 C 1312.290771 1665.377319 1317.478271 1655.625854 1320.338013 1651.962646 C 1325.268677 1645.64624 1326.146973 1645.984863 1337.335693 1658.516968 C 1343.824585 1665.785156 1352.93042 1679.33374 1357.570679 1688.625 C 1362.21106 1697.91626 1368.241943 1713.910278 1370.9729 1724.167236 C 1373.703979 1734.424194 1375.957642 1754.304199 1375.981323 1768.345093 C 1376.004639 1782.385986 1373.447388 1802.701416 1370.297974 1813.490479 C 1367.14856 1824.279541 1360.579102 1840.014404 1355.699097 1848.456543 C 1350.819092 1856.898682 1345.617188 1863.805908 1344.13916 1863.805908 Z M 1054.144653 1447.541016 C 1040.975586 1449.307373 1040.975586 1449.307373 1044.440796 1430.24292 C 1046.346558 1419.757202 1051.184204 1402.41626 1055.190918 1391.707275 C 1059.197754 1380.998047 1070.474609 1360.2771 1080.25061 1345.660767 C 1090.026733 1331.044312 1106.819336 1311.048218 1117.567383 1301.225098 C 1128.31543 1291.401978 1150.640625 1276.724854 1167.178589 1268.609009 C 1183.716919 1260.493286 1207.620605 1252.024414 1220.297852 1249.789429 C 1236.01416 1247.018677 1244.523193 1246.901611 1247.043213 1249.421509 C 1249.56311 1251.941528 1248.197021 1260.924805 1242.749146 1277.657227 C 1238.354736 1291.154053 1228.302002 1313.127563 1220.409424 1326.487061 C 1212.517212 1339.84668 1197.014893 1360.546509 1185.960449 1372.486694 C 1174.906006 1384.42688 1155.045776 1401.314941 1141.826904 1410.015869 C 1128.607788 1418.716553 1106.434692 1430.321655 1092.553101 1435.804932 C 1078.671509 1441.28833 1061.387817 1446.56958 1054.144653 1447.541016 Z"></path>
+        <path id="SvgjsPath1008" fill="#cae5c2" fill-rule="evenodd" stroke="none" d="M 1465.438477 1406.214844 C 1562.683838 1368.329102 1594.423218 1353.86377 1598.709351 1349.627441 C 1602.995483 1345.391113 1611.776367 1328.922974 1618.222412 1313.03186 C 1624.668335 1297.140625 1636.071167 1273.574829 1643.561768 1260.663208 C 1651.05249 1247.751587 1666.891968 1225.810913 1678.760254 1211.906128 C 1690.628784 1198.001343 1710.661621 1178.342163 1723.277832 1168.219116 C 1735.894043 1158.096069 1755.967896 1144.189331 1767.88623 1137.315186 C 1779.804565 1130.44104 1800.404663 1120.495239 1813.664185 1115.213379 C 1826.92334 1109.931519 1853.995239 1102.303955 1873.823242 1098.263184 C 1896.523438 1093.637207 1923.70874 1090.93396 1947.229492 1090.963745 C 1969.401245 1090.991943 1997.827881 1093.744751 2017.167236 1097.736206 C 2035.087891 1101.435059 2062.717041 1109.626953 2078.564941 1115.94043 C 2094.413086 1122.254028 2117.943848 1133.712891 2130.855469 1141.404785 C 2143.76709 1149.096558 2163.679932 1163.355713 2175.106445 1173.091919 C 2186.532959 1182.828125 2204.974365 1201.232544 2216.087646 1213.990723 C 2227.200684 1226.749023 2243.399658 1249.257935 2252.084961 1264.01062 C 2260.770508 1278.763306 2272.654785 1304.03894 2278.494873 1320.178711 C 2284.335205 1336.318604 2291.829834 1363.253906 2295.149902 1380.034912 C 2298.469971 1396.815918 2301.450439 1425.985596 2301.772949 1444.856445 C 2302.095459 1463.727295 2300.265381 1492.506348 2297.706055 1508.809814 C 2295.146973 1525.113281 2289.292236 1549.491943 2284.696045 1562.984253 C 2280.099609 1576.476807 2269.786621 1600.517822 2261.778564 1616.409058 C 2253.77002 1632.300293 2239.96167 1655.053589 2231.093018 1666.971924 C 2222.224365 1678.890259 2203.762695 1699.345581 2190.067139 1712.428223 C 2176.371338 1725.510742 2156.227295 1742.105225 2145.302002 1749.30481 C 2134.376709 1756.504272 2111.271973 1769.012451 2093.958008 1777.100586 C 2076.644287 1785.188721 2049.828125 1795.158691 2034.366211 1799.255859 C 2014.05603 1804.637939 1991.720215 1807.082275 1953.885376 1808.063477 C 1917.532959 1809.006226 1893.784668 1807.829102 1876.235229 1804.214844 C 1862.330566 1801.351196 1841.202393 1795.500244 1829.284058 1791.212646 C 1817.365723 1786.924927 1797.862793 1778.528809 1785.944458 1772.554199 C 1774.026123 1766.579834 1755.231689 1755.557617 1744.179199 1748.060791 C 1733.126465 1740.563721 1715.372559 1726.994385 1704.725952 1717.906494 C 1694.079224 1708.818604 1676.610474 1689.741699 1665.906982 1675.513428 C 1655.203247 1661.285156 1640.628418 1638.103027 1633.518433 1623.997314 C 1626.408691 1609.891846 1616.817139 1587.267822 1612.204224 1573.72168 C 1607.591187 1560.175781 1601.032349 1532.003418 1597.628906 1511.116455 C 1591.905273 1475.988403 1590.586914 1472.488647 1580.050659 1464.452148 C 1573.785889 1459.673828 1545.435303 1444.615479 1517.049194 1430.989502 L 1465.438477 1406.214844 Z"></path>
+        <path id="SvgjsPath1007" fill="#b0d6ed" fill-rule="evenodd" stroke="none" d="M 428.065002 2058.47168 C 410.135254 2058.271973 384.90152 2055.815674 371.989899 2053.012939 C 359.078278 2050.210205 337.950287 2044.456543 325.038666 2040.227173 C 312.127014 2035.997681 290.186432 2026.891113 276.281616 2019.990356 C 262.376801 2013.089478 242.873993 2001.759766 232.942001 1994.813232 C 223.01001 1987.866699 203.772507 1971.394409 190.191956 1958.208008 C 176.611526 1945.021729 158.457458 1925.179932 149.849747 1914.115356 C 141.24202 1903.050781 128.543549 1883.547974 121.630989 1870.775757 C 114.71843 1858.00354 104.900955 1835.276245 99.814377 1820.270508 C 94.727806 1805.264893 88.064445 1778.641846 85.006767 1761.108398 C 81.949203 1743.574951 79.454079 1715.221436 79.462128 1698.100708 C 79.470062 1680.979736 81.944138 1651.757324 84.95993 1633.161499 C 87.97583 1614.565796 95.864487 1584.918457 102.490257 1567.27832 C 109.116142 1549.638184 122.488159 1521.96875 132.205887 1505.790527 C 141.923615 1489.612183 161.100052 1464.306396 174.820251 1449.555542 C 188.540451 1434.804688 209.141907 1415.52124 220.601303 1406.703613 C 232.060593 1397.885742 253.523407 1384.151611 268.296417 1376.183105 C 283.069305 1368.214722 306.98291 1357.672607 321.437622 1352.756104 C 335.892426 1347.839844 360.673004 1341.360107 376.505768 1338.356689 C 392.338501 1335.353149 419.527283 1332.895874 436.925232 1332.895874 C 454.32309 1332.895874 482.178894 1335.28125 498.826935 1338.196899 C 515.474854 1341.112549 541.00415 1347.559082 555.558716 1352.522949 C 570.113281 1357.486816 590.755615 1366.278564 601.430603 1372.060303 C 612.10553 1377.842285 631.204407 1389.968994 643.872559 1399.008789 C 656.540649 1408.048584 678.967041 1428.266602 693.708984 1443.937744 C 709.81543 1461.059448 726.998779 1484.281494 736.764893 1502.124756 C 745.703735 1518.456421 757.340454 1538.894409 762.624329 1547.542725 C 771.33197 1561.794556 777.756531 1566.043945 831.245361 1592.931396 C 863.703125 1609.247192 894.023071 1624.968384 898.622925 1627.867676 C 906.759644 1632.996094 905.998718 1633.63269 870.564209 1651.333984 C 846.801697 1663.20459 827.454834 1675.988892 814.903076 1688.114502 C 795.664246 1706.699951 795.664246 1706.699951 791.316467 1746.427856 C 788.493652 1772.221436 782.807678 1798.390137 775.105225 1821.036865 C 768.580261 1840.221436 756.083984 1868.663086 747.335693 1884.240479 C 735.673279 1905.006836 720.79834 1923.162109 691.580566 1952.291016 C 663.996582 1979.791016 642.598877 1997.443359 622.060486 2009.642578 C 605.741577 2019.335693 576.523315 2032.669189 557.131226 2039.272461 C 537.739075 2045.875977 508.1008 2052.97876 491.268585 2055.056396 C 474.436279 2057.134277 445.994659 2058.670898 428.065002 2058.47168 Z"></path>
+    </g>
+</svg><style>@media (prefers-color-scheme: light) { :root { filter: none; } }
+@media (prefers-color-scheme: dark) { :root { filter: none; } }
+</style></svg>

assets/favicon/site.webmanifest

@@ -0,0 +1,21 @@
+{
+  "name": "MyWebSite",
+  "short_name": "MySite",
+  "icons": [
+    {
+      "src": "/web-app-manifest-192x192.png",
+      "sizes": "192x192",
+      "type": "image/png",
+      "purpose": "maskable"
+    },
+    {
+      "src": "/web-app-manifest-512x512.png",
+      "sizes": "512x512",
+      "type": "image/png",
+      "purpose": "maskable"
+    }
+  ],
+  "theme_color": "#ffffff",
+  "background_color": "#ffffff",
+  "display": "standalone"
+}

blog/article-template.html

@@ -0,0 +1,112 @@
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>__ARTICLE_TITLE__ - Prosberry</title>
+    <meta name="description" content="__ARTICLE_SUMMARY__">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
+    <link rel="stylesheet" href="/css/style.css?v=1763500835">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+    __HEADER_CONTENT__
+    <main>
+        <section class="article-hero">
+            <div class="article-hero-text">
+                <p class="article-date">__ARTICLE_DATE__</p>
+                <h1>__ARTICLE_TITLE__</h1>
+                <p class="article-summary">__ARTICLE_SUMMARY__</p>
+            </div>
+            <div class="article-hero-image" style="background-image: url('__ARTICLE_IMAGE__');"></div>
+        </section>
+        <section class="article-content-section">
+            <div class="article-grid" data-aos="fade-up">
+                <article class="article-card">
+                    <div class="article-card-body">
+                        __ARTICLE_CONTENT__
+                    </div>
+                </article>
+                <aside class="article-sidebar">
+                    <div class="sidebar-card">
+                        <h3>Povezave</h3>
+                        <a href="/blog/">Vsi članki</a>
+                        <a href="/skupaj-za-vkljucevanje/">Skupaj za vključevanje</a>
+                        <a href="/kontakt/">Kontakt</a>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Podpora</h3>
+                        <p>Potrebujete pomoč pri razumevanju kulturne dinamike v razredu?</p>
+                        <a class="cta-button" href="/kontakt/">Pišite nam</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+<section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        <section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+    </main>
+    __FOOTER_CONTENT__
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>

blog/clanki-source/2025-11-17-medkulturnost-prostor-za-rast.html

@@ -0,0 +1,374 @@
+<!-- {
+  "title": "Medkulturnost: prostor za rast v razredih in skupinah vrtca",
+  "date": "2025-11-17",
+  "image": "/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/1.png",
+  "summary": "Kako ustvariti varen prostor za učno povezovanje v razredih in skupinah vrtca, kjer so otroci iz različnih kulturnih okolij."
+} -->
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Medkulturnost: prostor za rast v razredih in skupinah vrtca | Prosberry</title>
+    <meta name="description"
+        content="Kako ustvariti varen prostor za učno povezovanje v razredih in skupinah vrtca, kjer so otroci iz različnih kulturnih okolij.">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
+    <link rel="stylesheet" href="/css/style.css">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+<header class="main-header">
+    <nav class="nav-container">
+        <div class="logo">
+            <a href="/">
+                <picture>
+                    <source
+                        srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
+                        sizes="(max-width: 768px) 100px, 180px" type="image/webp">
+                    <img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
+                        fetchpriority="high">
+                </picture>
+            </a>
+        </div>
+        <div class="nav-links">
+            <a href="/" >Začetna</a>
+            
+            <!-- 1. Poučevanje jezikov (prej Ponudba) -->
+            <a href="/ponudba/" >Učenje jezikov</a>
+            
+            <!-- 2. Medkulturno povezovanje (prej Skupaj za vključevanje) -->
+            <!-- Opomba: Povezava vodi na medkulturno posredovanje s podmenijem -->
+            <div class="dropdown">
+                <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropbtn" >Medkulturno povezovanje</a>
+                <div class="dropdown-content">
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropdown-main-link">Pregled strani</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Načini posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Vrste posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#sodelujem">S kom sodelujem</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek sodelovanja in cena</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#zakaj">Zakaj izbrati Prosberry</a>
+                </div>
+            </div>
+            
+            <!-- 3. Delavnice za vključevanje (Nova glavna kategorija s podmenijem) -->
+            <div class="dropdown">
+                <a href="/delavnice/" class="dropbtn" >Delavnice za vključevanje</a>
+                <div class="dropdown-content">
+                    <a href="/delavnice/" class="dropdown-main-link">Pregled delavnic</a>
+                    <div class="dropdown-submenu">
+                        <a href="#">Šola</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Vrtec</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Zaposleni</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
+                        </div>
+                    </div>
+                </div>
+            </div>
+            
+            <a href="/kdo-sem/" >Kdo sem</a>
+            <a href="/cene-in-reference/" >Cene in reference</a>
+            <a href="/pogosta-vprasanja/" >Vprašanja</a>
+            <a href="/blog/" class="active">Blog</a>
+            <a href="/kontakt/" >Kontakt</a>
+        </div>
+        <div class="mobile-menu-btn">
+            <span></span>
+            <span></span>
+            <span></span>
+        </div>
+    </nav>
+</header>
+    <main>
+        <section class="contact-hero blog-hero">
+            <div class="contact-hero-content" data-aos="fade-up">
+                <span class="contact-hero-kicker">17. november 2025</span>
+                <h1>Medkulturnost: prostor za rast v razredih in skupinah vrtca</h1>
+
+            </div>
+            <div class="contact-hero-shape shape-a"></div>
+            <div class="contact-hero-shape shape-b"></div>
+            <div class="contact-hero-shape shape-c"></div>
+            <div class="contact-hero-shape shape-d"></div>
+        </section>
+
+        <section class="blog-content">
+            <div class="blog-layout-wrapper">
+                <div class="blog-main-column">
+                    <article class="blog-article-content" data-aos="fade-up">
+
+
+                        <div class="article-body-text">
+                            <div class="article-inline-image float-left">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/1.png"
+                                    alt="Medkulturnost prostor za rast" loading="lazy">
+                            </div>
+
+                            <p>V mnogih slovenskih šolah in vrtcih so danes v razredih in
+                                skupinah tudi otroci iz različnih kulturnih okolij. Takšna raznolikost prinaša svoje
+                                izzive, a hkrati ogromno priložnosti za rast, empatijo in nove poglede. Ta stik med
+                                različnimi kulturami – to, čemur pravimo medkulturnost – pomeni, da se učimo razumeti,
+                                spoštovati in ceniti različne običaje, jezike in načine izražanja, hkrati pa ohranjamo
+                                svojo identiteto. V praksi to pomeni ustvariti prijazno in spodbudno vzdušje, kjer se
+                                vsak otrok počuti varno in vključeno.</p>
+
+                            <h2>Kaj pomenijo medkulturne razlike v razredu in vrtcu?</h2>
+
+                            <div class="article-inline-image float-right">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/2.png"
+                                    alt="Medkulturne razlike" loading="lazy">
+                            </div>
+
+                            <p>Medkulturne razlike se ne kažejo le v jeziku, praznovanjih ali videzu otrok, temveč
+                                predvsem v načinu razmišljanja, izražanja in vedenja – v stvareh, ki so pogosto
+                                nevidne,
+                                dokler nanje ne opozorimo. Vsak otrok prihaja iz okolja, kjer so bile določene
+                                vrednote
+                                in navade učene, cenjene in razumljene nekoliko drugače. To vpliva na to, kako se
+                                vključuje v razred ali skupino, sodeluje in doživlja šolo ali vrtec kot varen
+                                prostor za
+                                napredovanje in razvoj.</p>
+                            <p><strong>Pomembno:</strong> To niso pravila, temveč opazovanja. Otroci iz iste države
+                                se
+                                lahko med seboj zelo razlikujejo – vsak prinese svojo zgodbo, družinske vrednote in
+                                izkušnje. Te razlike so priložnost za razumevanje in odprtost, ne razlog za sodbo
+                                ali
+                                primerjavo.</p>
+
+                            <h2>Kako se otroci izražajo: besede, tišina in pogledi</h2>
+
+                            <div class="article-inline-image float-left">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/3.png"
+                                    alt="Kako se otroci izražajo" loading="lazy">
+                            </div>
+
+                            <p>V razredu ali skupini se otroci ne izražajo samo z besedami – govorica telesa, očesni
+                                stik in tišina prav tako povedo veliko o tem, kako se počutijo, razumejo učne vsebine in
+                                sodelujejo z drugimi. Razumevanje teh razlik je ključ do uspešne medkulturne
+                                komunikacije, saj različni načini izražanja pogosto izhajajo iz kulturnega ozadja otrok.
+                            </p>
+
+                            <ul>
+                                <li><strong>Komunikacija in odnos do avtoritete:</strong> Nekateri otroci so
+                                    neposredni
+                                    in povedo stvari naravnost, drugi pa uporabljajo bolj taktičen ali previden
+                                    način
+                                    izražanja, da ohranijo harmonijo. Enako velja za odnos do učiteljev – v
+                                    nekaterih
+                                    kulturah je avtoriteta formalna in nedotakljiva, drugje pa bolj partnerska in
+                                    pogajalska. Če tega ne prepoznamo, lahko napačno razumemo otrokove motive ali
+                                    namene.</li>
+                                <li><strong>Tišina in aktivno sodelovanje:</strong> Nekateri otroci bodo takoj
+                                    delili
+                                    svoje mnenje, drugi pa raje poslušajo in premislijo, preden spregovorijo. Ti
+                                    trenutki tišine niso znak nezainteresiranosti, temveč drugačen način učenja in
+                                    participacije, ki ga je pomembno razumeti v kontekstu njihove kulturne izkušnje.
+                                </li>
+                                <li><strong>Očesni stik in neverbalna komunikacija:</strong> Neposreden očesni stik
+                                    je v
+                                    nekaterih kulturah znak pozornosti in iskrenosti, v drugih pa lahko pomeni
+                                    predrznost ali nespoštovanje. Geste, mimika in fizična bližina se prav tako
+                                    razlikujejo – nasmeh je lahko znak prijaznosti ali način, kako otrok skrije
+                                    neprijetna čustva. Če ne poznamo kulturnega ozadja, lahko napačno
+                                    interpretiramo,
+                                    zakaj se otrok vede na določen način.</li>
+                            </ul>
+                            <div class="article-inline-image float-right">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/4.png"
+                                    alt="Nasvet" loading="lazy">
+                            </div>
+                            <p>➡️ <strong>Nasvet:</strong> Ne sklepajte avtomatično, da otrok ne želi sodelovati ali
+                                ni
+                                pozoren. Opazujte, poslušajte in prilagajajte interpretacijo kulturnemu kontekstu.
+                                Uporabite igre, delo v parih ali manjše skupine, da omogočite postopno vključevanje
+                                in
+                                udobno interakcijo.</p>
+
+                            <h2>Primeri iz prakse</h2>
+                            <ol>
+                                <li><strong>Učenka iz Ukrajine ne sodeluje pri ustnih odgovorih</strong> Učitelj
+                                    lahko
+                                    pomisli, da se noče vključiti, a v resnici še ni samozavestna v slovenščini ali
+                                    se
+                                    boji neposrednega nastopa v tujem jeziku.</li>
+                                <p>➡️ <strong>Nasvet:</strong> Ponudite možnost pisnega odgovarjanja ali dela v
+                                    paru.
+                                    Spodbujajte postopno vključevanje brez pritiska.</p>
+                                <li><strong>Starši otrok iz Albanije se ne udeležijo roditeljskega sestanka</strong>
+                                    Ni
+                                    nujno, da jih ne zanima – morda se zaradi omejenega znanja jezika počutijo
+                                    nelagodno
+                                    pri javnem izražanju svojih mnenj.</li>
+                                <p>➡️ <strong>Nasvet:</strong> Povabilo pošljite v preprostem jeziku in ponudite
+                                    možnost
+                                    prvega individualnega srečanja, da zgradite zaupanje.</p>
+                                <li><strong>Otrok iz Sirije se izogiba očesnemu stiku</strong> V nekaterih kulturah
+                                    je
+                                    neposreden očesni stik lahko razumljen kot predrznost ali nespoštovanje, zato se
+                                    ga
+                                    otrok izogiba.</li>
+                                <p>➡️ <strong>Nasvet:</strong> Pristopite z razumevanjem in uporabite igre ali
+                                    naloge,
+                                    ki omogočajo sodelovanje brez pritiska na neposreden očesni stik.</p>
+                            </ol>
+
+                            <h2>5 praktičnih nasvetov</h2>
+
+                            <div class="article-inline-image float-right">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/5.png"
+                                    alt="Praktični nasveti" loading="lazy">
+                            </div>
+
+                            <ol>
+                                <li><strong>Vprašajte, ne predvidevajte.</strong> Vsaka družina ima svojo zgodbo –
+                                    pristopite z radovednostjo, ne s sodbo.</li>
+                                <li><strong>Učite o raznolikosti.</strong> Pogovorite se o različnih jezikih,
+                                    praznikih
+                                    in običajih – otroci bodo to doživeli kot bogastvo, ne kot razliko.</li>
+                                <li><strong>Ustvarite varno okolje.</strong> Naj učenci vedo, da je v redu, če
+                                    delajo
+                                    napake v jeziku. Vzdušje sprejemanja spodbuja učenje.</li>
+                                <li><strong>Sodelujte s starši.</strong> Tudi kratka sporočila o napredku otroka
+                                    gradijo
+                                    zaupanje.</li>
+                                <li><strong>Povežite se s strokovnjaki.</strong> Delavnice medkulturnega
+                                    posredovanja
+                                    ali svetovanja lahko učiteljem in staršem pomagajo bolje razumeti kulturne
+                                    razlike v
+                                    praksi.</li>
+                            </ol>
+
+                            <h2>Zaključek</h2>
+                            <div class="article-inline-image float-left">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/6.png"
+                                    alt="Zaključek" loading="lazy">
+                            </div>
+                            <p>Medkulturnost v razredu ni ovira, ampak priložnost, da skupaj ustvarimo okolje, kjer
+                                se
+                                vsak otrok počuti slišan, spoštovan in sprejet. Z nekaj razumevanja, potrpežljivosti
+                                in
+                                medsebojnega sodelovanja lahko razred postane resnično bogata skupnost. Delite svoje
+                                izkušnje in vprašanja v kontaktnem obrazcu – skupaj lahko gradimo močnejše in bolj
+                                vključujoče šolske in vrtčevske skupnosti.</p>
+                        </div>
+                    </article>
+                </div>
+
+                <aside class="blog-sidebar">
+                    <div class="sidebar-card">
+                        <h3>Povezane teme</h3>
+                        <div class="sidebar-links">
+                            <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
+                                priseljenci</a>
+                            <a href="/blog/">Vsi članki</a>
+                        </div>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Potrebujete pomoč?</h3>
+                        <p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
+                        <a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+<section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        
+    </main>
+
+
+
+
+
+
+<section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+
+<footer>
+    <div class="footer-content">
+        <div class="footer-logo">
+            <h3>PROSBERRY</h3>
+        </div>
+        <div class="footer-links">
+            <p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
+        </div>
+        <div class="footer-contact">
+            <p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
+            <p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
+        </div>
+    </div>
+</footer>
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>

blog/clanki-source/2025-11-17-sample-article.html

@@ -0,0 +1,214 @@
+<!-- {
+  "title": "Sample Article Title",
+  "date": "2025-11-17",
+  "image": "/assets/images/blog/sample-image.webp",
+  "summary": "This is a sample summary for the article. It should be one or two sentences long."
+} -->
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Sample Article Title - Prosberry</title>
+    <meta name="description"
+        content="This is a sample summary for the article. It should be one or two sentences long.">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
+    <link rel="stylesheet" href="/css/style.css?v=1763500835">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+<header class="main-header">
+    <nav class="nav-container">
+        <div class="logo">
+            <a href="/">
+                <picture>
+                    <source
+                        srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
+                        sizes="(max-width: 768px) 100px, 180px" type="image/webp">
+                    <img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
+                        fetchpriority="high">
+                </picture>
+            </a>
+        </div>
+        <div class="nav-links">
+            <a href="/" >Začetna</a>
+            
+            <!-- 1. Poučevanje jezikov (prej Ponudba) -->
+            <a href="/ponudba/" >Učenje jezikov</a>
+            
+            <!-- 2. Medkulturno povezovanje (prej Skupaj za vključevanje) -->
+            <!-- Opomba: Povezava vodi na medkulturno posredovanje s podmenijem -->
+            <div class="dropdown">
+                <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropbtn" >Medkulturno povezovanje</a>
+                <div class="dropdown-content">
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropdown-main-link">Pregled strani</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Načini posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Vrste posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#sodelujem">S kom sodelujem</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek sodelovanja in cena</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#zakaj">Zakaj izbrati Prosberry</a>
+                </div>
+            </div>
+            
+            <!-- 3. Delavnice za vključevanje (Nova glavna kategorija s podmenijem) -->
+            <div class="dropdown">
+                <a href="/delavnice/" class="dropbtn" >Delavnice za vključevanje</a>
+                <div class="dropdown-content">
+                    <a href="/delavnice/" class="dropdown-main-link">Pregled delavnic</a>
+                    <div class="dropdown-submenu">
+                        <a href="#">Šola</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Vrtec</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Zaposleni</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
+                        </div>
+                    </div>
+                </div>
+            </div>
+            
+            <a href="/kdo-sem/" >Kdo sem</a>
+            <a href="/cene-in-reference/" >Cene in reference</a>
+            <a href="/pogosta-vprasanja/" >Vprašanja</a>
+            <a href="/blog/" class="active">Blog</a>
+            <a href="/kontakt/" >Kontakt</a>
+        </div>
+        <div class="mobile-menu-btn">
+            <span></span>
+            <span></span>
+            <span></span>
+        </div>
+    </nav>
+</header>
+    <main>
+        <section class="article-hero">
+            <div class="article-hero-text">
+                <p class="article-date">17. november 2025</p>
+                <h1>Sample Article Title</h1>
+                <p class="article-summary">This is a sample summary for the article. It should be one or two sentences
+                    long.</p>
+            </div>
+            <div class="article-hero-image" style="background-image: url('/assets/images/blog/sample-image.webp');">
+            </div>
+        </section>
+        <section class="article-content-section">
+            <div class="article-grid" data-aos="fade-up">
+                <article class="article-card">
+                    <div class="article-card-body">
+
+                    </div>
+                </article>
+                <aside class="article-sidebar">
+                    <div class="sidebar-card">
+                        <h3>Povezave</h3>
+                        <a href="/blog/">Vsi članki</a>
+                        <a href="/skupaj-za-vkljucevanje/">Skupaj za vključevanje</a>
+                        <a href="/kontakt/">Kontakt</a>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Podpora</h3>
+                        <p>Potrebujete pomoč pri razumevanju kulturne dinamike v razredu?</p>
+                        <a class="cta-button" href="/kontakt/">Pišite nam</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+<section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        
+    </main>
+
+
+
+
+
+
+<section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+
+<footer>
+    <div class="footer-content">
+        <div class="footer-logo">
+            <h3>PROSBERRY</h3>
+        </div>
+        <div class="footer-links">
+            <p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
+        </div>
+        <div class="footer-contact">
+            <p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
+            <p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
+        </div>
+    </div>
+</footer>
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>

blog/clanki-source/2025-11-18-dojemanje-casa-tocnosti-discipline.html

@@ -0,0 +1,215 @@
+<!-- {
+  "title": "Dojemanje časa, točnosti in discipline – od juga proti severu Evrope",
+  "date": "2025-11-18",
+  "image": "/assets/images/blog/time-discipline.webp",
+  "summary": "Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično sporočajo z zamudo ali redom."
+} -->
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope - Prosberry</title>
+    <meta name="description"
+        content="Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično sporočajo z zamudo ali redom.">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
+    <link rel="stylesheet" href="/css/style.css?v=1763500835">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+<header class="main-header">
+    <nav class="nav-container">
+        <div class="logo">
+            <a href="/">
+                <picture>
+                    <source
+                        srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
+                        sizes="(max-width: 768px) 100px, 180px" type="image/webp">
+                    <img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
+                        fetchpriority="high">
+                </picture>
+            </a>
+        </div>
+        <div class="nav-links">
+            <a href="/" >Začetna</a>
+            
+            <!-- 1. Poučevanje jezikov (prej Ponudba) -->
+            <a href="/ponudba/" >Učenje jezikov</a>
+            
+            <!-- 2. Medkulturno povezovanje (prej Skupaj za vključevanje) -->
+            <!-- Opomba: Povezava vodi na medkulturno posredovanje s podmenijem -->
+            <div class="dropdown">
+                <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropbtn" >Medkulturno povezovanje</a>
+                <div class="dropdown-content">
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropdown-main-link">Pregled strani</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Načini posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Vrste posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#sodelujem">S kom sodelujem</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek sodelovanja in cena</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#zakaj">Zakaj izbrati Prosberry</a>
+                </div>
+            </div>
+            
+            <!-- 3. Delavnice za vključevanje (Nova glavna kategorija s podmenijem) -->
+            <div class="dropdown">
+                <a href="/delavnice/" class="dropbtn" >Delavnice za vključevanje</a>
+                <div class="dropdown-content">
+                    <a href="/delavnice/" class="dropdown-main-link">Pregled delavnic</a>
+                    <div class="dropdown-submenu">
+                        <a href="#">Šola</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Vrtec</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Zaposleni</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
+                        </div>
+                    </div>
+                </div>
+            </div>
+            
+            <a href="/kdo-sem/" >Kdo sem</a>
+            <a href="/cene-in-reference/" >Cene in reference</a>
+            <a href="/pogosta-vprasanja/" >Vprašanja</a>
+            <a href="/blog/" class="active">Blog</a>
+            <a href="/kontakt/" >Kontakt</a>
+        </div>
+        <div class="mobile-menu-btn">
+            <span></span>
+            <span></span>
+            <span></span>
+        </div>
+    </nav>
+</header>
+    <main>
+        <section class="article-hero">
+            <div class="article-hero-text">
+                <p class="article-date">18. november 2025</p>
+                <h1>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</h1>
+                <p class="article-summary">Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do
+                    natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično
+                    sporočajo z zamudo ali redom.</p>
+            </div>
+            <div class="article-hero-image" style="background-image: url('/assets/images/blog/time-discipline.webp');">
+            </div>
+        </section>
+        <section class="article-content-section">
+            <div class="article-grid" data-aos="fade-up">
+                <article class="article-card">
+                    <div class="article-card-body">
+
+                    </div>
+                </article>
+                <aside class="article-sidebar">
+                    <div class="sidebar-card">
+                        <h3>Povezave</h3>
+                        <a href="/blog/">Vsi članki</a>
+                        <a href="/skupaj-za-vkljucevanje/">Skupaj za vključevanje</a>
+                        <a href="/kontakt/">Kontakt</a>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Podpora</h3>
+                        <p>Potrebujete pomoč pri razumevanju kulturne dinamike v razredu?</p>
+                        <a class="cta-button" href="/kontakt/">Pišite nam</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+<section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        
+    </main>
+
+
+
+
+
+
+<section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+
+<footer>
+    <div class="footer-content">
+        <div class="footer-logo">
+            <h3>PROSBERRY</h3>
+        </div>
+        <div class="footer-links">
+            <p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
+        </div>
+        <div class="footer-contact">
+            <p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
+            <p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
+        </div>
+    </div>
+</footer>
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>

blog/clanki/2025-11-15-prihaja-kmalu.html

@@ -0,0 +1,244 @@
+<!-- {
+  "title": "Prihaja kmalu",
+  "date": "2025-11-15",
+  "image": "/assets/images/blog/2025-11-15-prihaja-kmalu/header.png",
+  "summary": "Prihajajo novi članki o medkulturnih temah; vmes si lahko preberete že objavljeno vsebino."
+} -->
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Prihaja kmalu | Prosberry</title>
+    <meta name="description"
+        content="Prihajajo novi članki o medkulturnih izzivih in praksah. Medtem si lahko preberete obstoječe prispevke in se povežete z nami.">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
+    <link rel="stylesheet" href="/css/style.css">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+<header class="main-header">
+    <nav class="nav-container">
+        <div class="logo">
+            <a href="/">
+                <picture>
+                    <source
+                        srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
+                        sizes="(max-width: 768px) 100px, 180px" type="image/webp">
+                    <img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
+                        fetchpriority="high">
+                </picture>
+            </a>
+        </div>
+        <div class="nav-links">
+            <a href="/" >Začetna</a>
+            
+            <!-- 1. Poučevanje jezikov (prej Ponudba) -->
+            <a href="/ponudba/" >Učenje jezikov</a>
+            
+            <!-- 2. Medkulturno povezovanje (prej Skupaj za vključevanje) -->
+            <!-- Opomba: Povezava vodi na medkulturno posredovanje s podmenijem -->
+            <div class="dropdown">
+                <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropbtn" >Medkulturno povezovanje</a>
+                <div class="dropdown-content">
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropdown-main-link">Pregled strani</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Načini posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Vrste posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#sodelujem">S kom sodelujem</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek sodelovanja in cena</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#zakaj">Zakaj izbrati Prosberry</a>
+                </div>
+            </div>
+            
+            <!-- 3. Delavnice za vključevanje (Nova glavna kategorija s podmenijem) -->
+            <div class="dropdown">
+                <a href="/delavnice/" class="dropbtn" >Delavnice za vključevanje</a>
+                <div class="dropdown-content">
+                    <a href="/delavnice/" class="dropdown-main-link">Pregled delavnic</a>
+                    <div class="dropdown-submenu">
+                        <a href="#">Šola</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Vrtec</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Zaposleni</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
+                        </div>
+                    </div>
+                </div>
+            </div>
+            
+            <a href="/kdo-sem/" >Kdo sem</a>
+            <a href="/cene-in-reference/" >Cene in reference</a>
+            <a href="/pogosta-vprasanja/" >Vprašanja</a>
+            <a href="/blog/" class="active">Blog</a>
+            <a href="/kontakt/" >Kontakt</a>
+        </div>
+        <div class="mobile-menu-btn">
+            <span></span>
+            <span></span>
+            <span></span>
+        </div>
+    </nav>
+</header>
+    <main>
+        <section class="contact-hero blog-hero">
+            <div class="contact-hero-content" data-aos="fade-up">
+                <span class="contact-hero-kicker">16. november 2025</span>
+                <h1>Prihaja kmalu</h1>
+            </div>
+            <div class="contact-hero-shape shape-a"></div>
+            <div class="contact-hero-shape shape-b"></div>
+            <div class="contact-hero-shape shape-c"></div>
+            <div class="contact-hero-shape shape-d"></div>
+        </section>
+
+        <section class="blog-content">
+            <div class="blog-layout-wrapper">
+                <div class="blog-main-column">
+                    <article class="blog-article-content" data-aos="fade-up">
+                        <div class="article-intro-two-column"
+                            style="display:flex; flex-wrap:wrap; gap:1rem; align-items:center; margin-bottom:2.5rem;">
+                            <p style="flex:1 1 360px; margin:0; line-height:1.7; font-size:1.1rem; text-align:justify;">
+                                Prihajajo novi članki o medkulturnih temah, na katerih delamo v ozadju. Medtem ko dokončujemo
+                                vsebine, si lahko preberete že objavljene prispevke in najdete navdih ali praktične ideje za delo
+                                s skupinami. Novi naslovi bodo kmalu razkriti – spremljajte nas na tej strani ali preko kontaktnega
+                                obrazca.
+                            </p>
+                            <div style="flex:1 1 280px; text-align:right;">
+                                <img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/1.png"
+                                    alt="Prihaja kmalu" loading="lazy"
+                                    style="max-width:130%; height:auto; display:inline-block;">
+                            </div>
+                        </div>
+
+                        <div class="article-body-text">
+                            <h2>Ostanite na tekočem</h2>
+                            <p>Ko bomo pripravljeni, boste tu našli nove prispevke o dojemanju časa, raznolikosti v učnih skupinah
+                                ali vpeljevanju strukturiranih praks v multikulturnih okoljih. Zdaj pa vas vabimo, da preberete
+                                prej objavljene članke:</p>
+                            <ul>
+                                <li><a href="/blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html">Medkulturnost: prostor za rast v razredih in skupinah vrtca</a></li>
+                                <li><a href="/blog/clanki/2025-11-18-dojemanje-casa-tocnosti-discipline.html">Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</a></li>
+                            </ul>
+                            <p>Če si želite svežega vpogleda, izberite enega od zgornjih člankov ali pokličite, da skupaj najdemo podporne poti.</p>
+                        </div>
+                    </article>
+                </div>
+
+                <aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
+                    <div class="sidebar-card">
+                        <h3>Povezane teme</h3>
+                        <div class="sidebar-links">
+                            <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
+                                priseljenci</a>
+                            <a href="/blog/">Vsi članki</a>
+                        </div>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Potrebujete pomoč?</h3>
+                        <p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
+                        <a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+<section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        
+    </main>
+
+
+
+
+
+
+<section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+
+<footer>
+    <div class="footer-content">
+        <div class="footer-logo">
+            <h3>PROSBERRY</h3>
+        </div>
+        <div class="footer-links">
+            <p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
+        </div>
+        <div class="footer-contact">
+            <p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
+            <p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
+        </div>
+    </div>
+</footer>
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>

blog/clanki/2025-11-16-prihaja-kmalu.html

@@ -0,0 +1,244 @@
+<!-- {
+  "title": "Prihaja kmalu",
+  "date": "2025-11-16",
+  "image": "/assets/images/blog/2025-11-16-prihaja-kmalu/header.png",
+  "summary": "Prihajali bodo novi članki o medkulturnih temah; vmes si lahko preberete že objavljeno vsebino."
+} -->
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Prihaja kmalu | Prosberry</title>
+    <meta name="description"
+        content="Prihajajo novi članki o medkulturnih izzivih in praksah. Medtem si lahko preberete obstoječe prispevke in se povežete z nami.">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
+    <link rel="stylesheet" href="/css/style.css">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+<header class="main-header">
+    <nav class="nav-container">
+        <div class="logo">
+            <a href="/">
+                <picture>
+                    <source
+                        srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
+                        sizes="(max-width: 768px) 100px, 180px" type="image/webp">
+                    <img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
+                        fetchpriority="high">
+                </picture>
+            </a>
+        </div>
+        <div class="nav-links">
+            <a href="/" >Začetna</a>
+            
+            <!-- 1. Poučevanje jezikov (prej Ponudba) -->
+            <a href="/ponudba/" >Učenje jezikov</a>
+            
+            <!-- 2. Medkulturno povezovanje (prej Skupaj za vključevanje) -->
+            <!-- Opomba: Povezava vodi na medkulturno posredovanje s podmenijem -->
+            <div class="dropdown">
+                <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropbtn" >Medkulturno povezovanje</a>
+                <div class="dropdown-content">
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropdown-main-link">Pregled strani</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Načini posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Vrste posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#sodelujem">S kom sodelujem</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek sodelovanja in cena</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#zakaj">Zakaj izbrati Prosberry</a>
+                </div>
+            </div>
+            
+            <!-- 3. Delavnice za vključevanje (Nova glavna kategorija s podmenijem) -->
+            <div class="dropdown">
+                <a href="/delavnice/" class="dropbtn" >Delavnice za vključevanje</a>
+                <div class="dropdown-content">
+                    <a href="/delavnice/" class="dropdown-main-link">Pregled delavnic</a>
+                    <div class="dropdown-submenu">
+                        <a href="#">Šola</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Vrtec</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Zaposleni</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
+                        </div>
+                    </div>
+                </div>
+            </div>
+            
+            <a href="/kdo-sem/" >Kdo sem</a>
+            <a href="/cene-in-reference/" >Cene in reference</a>
+            <a href="/pogosta-vprasanja/" >Vprašanja</a>
+            <a href="/blog/" class="active">Blog</a>
+            <a href="/kontakt/" >Kontakt</a>
+        </div>
+        <div class="mobile-menu-btn">
+            <span></span>
+            <span></span>
+            <span></span>
+        </div>
+    </nav>
+</header>
+    <main>
+        <section class="contact-hero blog-hero">
+            <div class="contact-hero-content" data-aos="fade-up">
+                <span class="contact-hero-kicker">16. november 2025</span>
+                <h1>Prihaja kmalu</h1>
+            </div>
+            <div class="contact-hero-shape shape-a"></div>
+            <div class="contact-hero-shape shape-b"></div>
+            <div class="contact-hero-shape shape-c"></div>
+            <div class="contact-hero-shape shape-d"></div>
+        </section>
+
+        <section class="blog-content">
+            <div class="blog-layout-wrapper">
+                <div class="blog-main-column">
+                    <article class="blog-article-content" data-aos="fade-up">
+                        <div class="article-intro-two-column"
+                            style="display:flex; flex-wrap:wrap; gap:1rem; align-items:center; margin-bottom:2.5rem;">
+                            <p style="flex:1 1 360px; margin:0; line-height:1.7; font-size:1.1rem; text-align:justify;">
+                                Prihajajo novi članki o medkulturnih temah, na katerih delamo v ozadju. Medtem ko dokončujemo
+                                vsebine, si lahko preberete že objavljene prispevke in najdete navdih ali praktične ideje za delo
+                                s skupinami. Novi naslovi bodo kmalu razkriti – spremljajte nas na tej strani ali preko kontaktnega
+                                obrazca.
+                            </p>
+                            <div style="flex:1 1 280px; text-align:right;">
+                                <img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/1.png"
+                                    alt="Prihaja kmalu" loading="lazy"
+                                    style="max-width:130%; height:auto; display:inline-block;">
+                            </div>
+                        </div>
+
+                        <div class="article-body-text">
+                            <h2>Ostanite na tekočem</h2>
+                            <p>Ko bomo pripravljeni, boste tu našli nove prispevke o dojemanju časa, raznolikosti v učnih skupinah
+                                ali vpeljevanju strukturiranih praks v multikulturnih okoljih. Zdaj pa vas vabimo, da preberete
+                                prej objavljene članke:</p>
+                            <ul>
+                                <li><a href="/blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html">Medkulturnost: prostor za rast v razredih in skupinah vrtca</a></li>
+                                <li><a href="/blog/clanki/2025-11-18-dojemanje-casa-tocnosti-discipline.html">Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</a></li>
+                            </ul>
+                            <p>Če si želite svežega vpogleda, izberite enega od zgornjih člankov ali pokličite, da skupaj najdemo podporne poti.</p>
+                        </div>
+                    </article>
+                </div>
+
+                <aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
+                    <div class="sidebar-card">
+                        <h3>Povezane teme</h3>
+                        <div class="sidebar-links">
+                            <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
+                                priseljenci</a>
+                            <a href="/blog/">Vsi članki</a>
+                        </div>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Potrebujete pomoč?</h3>
+                        <p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
+                        <a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+<section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        
+    </main>
+
+
+
+
+
+
+<section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+
+<footer>
+    <div class="footer-content">
+        <div class="footer-logo">
+            <h3>PROSBERRY</h3>
+        </div>
+        <div class="footer-links">
+            <p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
+        </div>
+        <div class="footer-contact">
+            <p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
+            <p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
+        </div>
+    </div>
+</footer>
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>

blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html

@@ -0,0 +1,352 @@
+<!-- {
+  "title": "Medkulturnost: prostor za rast v razredih in skupinah vrtca",
+  "date": "2025-11-17",
+  "image": "/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/header.png",
+  "summary": "V razredih in skupinah vrtca si ustvarimo varen prostor, kjer se otroci iz različnih kultur počutijo vključene."
+} -->
+<!DOCTYPE html>
+<html lang="sl">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Medkulturnost: prostor za rast v razredih in skupinah vrtca | Prosberry</title>
+    <meta name="description"
+        content="Kako ustvariti varen prostor za učno povezovanje v razredih in skupinah vrtca, kjer so otroci iz različnih kulturnih okolij.">
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link rel="stylesheet"
+        href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
+    <link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
+    <link rel="stylesheet" href="/css/style.css">
+    <link rel="stylesheet" href="/css/animations.css">
+    <link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
+    <link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
+    <link rel="shortcut icon" href="/assets/favicon/favicon.ico">
+    <link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
+    <link rel="manifest" href="/assets/favicon/site.webmanifest">
+</head>
+
+<body>
+<header class="main-header">
+    <nav class="nav-container">
+        <div class="logo">
+            <a href="/">
+                <picture>
+                    <source
+                        srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
+                        sizes="(max-width: 768px) 100px, 180px" type="image/webp">
+                    <img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
+                        fetchpriority="high">
+                </picture>
+            </a>
+        </div>
+        <div class="nav-links">
+            <a href="/" >Začetna</a>
+            
+            <!-- 1. Poučevanje jezikov (prej Ponudba) -->
+            <a href="/ponudba/" >Učenje jezikov</a>
+            
+            <!-- 2. Medkulturno povezovanje (prej Skupaj za vključevanje) -->
+            <!-- Opomba: Povezava vodi na medkulturno posredovanje s podmenijem -->
+            <div class="dropdown">
+                <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropbtn" >Medkulturno povezovanje</a>
+                <div class="dropdown-content">
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="dropdown-main-link">Pregled strani</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Načini posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Vrste posredovanja</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#sodelujem">S kom sodelujem</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek sodelovanja in cena</a>
+                    <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#zakaj">Zakaj izbrati Prosberry</a>
+                </div>
+            </div>
+            
+            <!-- 3. Delavnice za vključevanje (Nova glavna kategorija s podmenijem) -->
+            <div class="dropdown">
+                <a href="/delavnice/" class="dropbtn" >Delavnice za vključevanje</a>
+                <div class="dropdown-content">
+                    <a href="/delavnice/" class="dropdown-main-link">Pregled delavnic</a>
+                    <div class="dropdown-submenu">
+                        <a href="#">Šola</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Vrtec</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
+                        </div>
+                    </div>
+                    <div class="dropdown-submenu">
+                        <a href="#">Zaposleni</a>
+                        <div class="dropdown-submenu-content">
+                            <a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
+                        </div>
+                    </div>
+                </div>
+            </div>
+            
+            <a href="/kdo-sem/" >Kdo sem</a>
+            <a href="/cene-in-reference/" >Cene in reference</a>
+            <a href="/pogosta-vprasanja/" >Vprašanja</a>
+            <a href="/blog/" class="active">Blog</a>
+            <a href="/kontakt/" >Kontakt</a>
+        </div>
+        <div class="mobile-menu-btn">
+            <span></span>
+            <span></span>
+            <span></span>
+        </div>
+    </nav>
+</header>
+    <main>
+        <section class="contact-hero blog-hero">
+            <div class="contact-hero-content" data-aos="fade-up">
+                <span class="contact-hero-kicker">17. november 2025</span>
+                <h1>Medkulturnost: prostor za rast v razredih in skupinah vrtca</h1>
+
+            </div>
+            <div class="contact-hero-shape shape-a"></div>
+            <div class="contact-hero-shape shape-b"></div>
+            <div class="contact-hero-shape shape-c"></div>
+            <div class="contact-hero-shape shape-d"></div>
+        </section>
+
+        <section class="blog-content">
+            <div class="blog-layout-wrapper">
+                <div class="blog-main-column">
+                    <article class="blog-article-content" data-aos="fade-up">
+
+
+                        <div class="article-body-text">
+                            <div class="article-inline-image float-left">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/1.png"
+                                    alt="Medkulturnost prostor za rast" loading="lazy">
+                            </div>
+
+                            <p>V mnogih slovenskih šolah in vrtcih so danes v razredih in skupinah tudi otroci iz
+                                različnih kulturnih okolij. Takšna raznolikost prinaša svoje izzive, a hkrati ogromno
+                                priložnosti za rast, empatijo in nove poglede. Ta stik med različnimi kulturami – to,
+                                čemur pravimo medkulturnost – pomeni, da se učimo razumeti, spoštovati in ceniti različne
+                                običaje, jezike in načine izražanja, hkrati pa ohranjamo svojo identiteto. V praksi to
+                                pomeni ustvariti prijazno in spodbudno vzdušje, kjer se vsak otrok počuti varno in
+                                vključeno. Kako lahko v razredih in skupinah vrtca zagotovimo, da se vsak otrok počuti
+                                udobno?</p>
+
+                            <h2>Kaj pomenijo medkulturne razlike v razredu in vrtcu?</h2>
+
+                            <div class="article-inline-image float-right article-image-wide">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/2.png"
+                                    alt="Medkulturne razlike" loading="lazy" style="width:100%; height:auto;">
+                            </div>
+
+                            <p>Medkulturne razlike se ne kažejo le v jeziku, praznovanjih ali videzu otrok, temveč
+                                predvsem v načinu razmišljanja, izražanja in vedenja – v stvareh, ki so pogosto
+                                nevidne,
+                                dokler nanje ne opozorimo.</p>
+                            <p>Vsak otrok prihaja iz okolja, kjer so bile določene vrednote in navade učene, cenjene in
+                                razumljene nekoliko drugače. To vpliva na to, kako se vključuje v razred ali skupino,
+                                sodeluje in doživlja šolo ali vrtec kot varen prostor za napredovanje in razvoj.</p>
+                            <p><strong>Pomembno:</strong> To niso pravila, temveč opazovanja. Otroci iz iste države se
+                                lahko med seboj zelo razlikujejo – vsak prinese svojo zgodbo, družinske vrednote in
+                                izkušnje. Te razlike so priložnost za razumevanje in odprtost, ne razlog za sodbo ali
+                                primerjavo.</p>
+
+                            <h2>Kako se otroci izražajo: besede, tišina in pogledi</h2>
+
+                            <div class="article-inline-image float-left article-image-wide">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/3.png"
+                                    alt="Kako se otroci izražajo" loading="lazy" style="width:100%; height:auto;">
+                            </div>
+
+                            <p>V razredu ali skupini se otroci ne izražajo samo z besedami – govorica telesa, očesni
+                                stik in tišina prav tako povedo veliko o tem, kako se počutijo, razumejo učne vsebine in
+                                sodelujejo z drugimi. Razumevanje teh razlik je ključ do uspešne medkulturne
+                                komunikacije, saj različni načini izražanja pogosto izhajajo iz kulturnega ozadja otrok.
+                            </p>
+
+                            <ul>
+                                <li><strong>Komunikacija in odnos do avtoritete:</strong> Nekateri otroci so neposredni in
+                                    povedo stvari naravnost, drugi pa uporabljajo bolj taktičen ali previden način
+                                    izražanja, da ohranijo harmonijo. Enako velja za odnos do učiteljev – v nekaterih
+                                    kulturah je avtoriteta formalna in nedotakljiva, drugje pa bolj partnerska in
+                                    pogajalska. Če tega ne prepoznamo, lahko napačno razumemo otrokove motive ali namene.</li>
+                                <li><strong>Tišina in aktivno sodelovanje:</strong> Nekateri otroci bodo takoj delili svoje
+                                    mnenje, drugi pa raje poslušajo in premislijo, preden spregovorijo. Ti trenutki tišine
+                                    niso znak nezainteresiranosti, temveč drugačen način učenja in participacije, ki ga je
+                                    pomembno razumeti v kontekstu njihove kulturne izkušnje.</li>
+                                <li><strong>Očesni stik in neverbalna komunikacija:</strong> Neposreden očesni stik je v
+                                    nekaterih kulturah znak pozornosti in iskrenosti, v drugih pa lahko pomeni predrznost
+                                    ali nespoštovanje. Geste, mimika in fizična bližina se prav tako razlikujejo – nasmeh je
+                                    lahko znak prijaznosti ali način, kako otrok skrije neprijetna čustva. Če ne poznamo
+                                    kulturnega ozadja, lahko napačno interpretiramo, zakaj se otrok vede na določen način.</li>
+                            </ul>
+                            <div class="article-inline-image float-right article-image-wide">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/4.png"
+                                    alt="Nasvet" loading="lazy" style="width:100%; height:auto;">
+                            </div>
+                            <p>➡️<strong class="tip-label">Nasvet:</strong> Ne sklepajte avtomatično, da otrok ne želi sodelovati ali ni
+                                pozoren. Opazujte, poslušajte in prilagajajte interpretacijo kulturnemu kontekstu. Uporabite
+                                igre, delo v parih ali manjše skupine, da omogočite postopno vključevanje in udobno
+                                interakcijo.</p>
+
+                            <h2>Primeri iz prakse</h2>
+                            <ol>
+                                <li><strong>Učenka iz Ukrajine ne sodeluje pri ustnih odgovorih.</strong> Učitelj lahko
+                                    pomisli, da se noče vključiti, a v resnici še ni samozavestna v slovenščini ali se boji
+                                    neposrednega nastopa v tujem jeziku.
+                                    <p>➡️<strong class="tip-label">Nasvet:</strong> Ponudite možnost pisnega odgovarjanja ali dela v paru.
+                                        Spodbujajte postopno vključevanje brez pritiska.</p>
+                                </li>
+                                <li><strong>Starši otrok iz Albanije se ne udeležijo roditeljskega sestanka.</strong> Ni
+                                    nujno, da jih ne zanima – morda se zaradi omejenega znanja jezika počutijo nelagodno pri
+                                    javnem izražanju svojih mnenj.
+                                    <p>➡️<strong class="tip-label">Nasvet:</strong> Povabilo pošljite v preprostem jeziku in ponudite možnost
+                                        prvega individualnega srečanja, da zgradite zaupanje.</p>
+                                </li>
+                                <li><strong>Otrok iz Sirije se izogiba očesnemu stiku.</strong> V nekaterih kulturah je
+                                    neposreden očesni stik lahko razumljen kot predrznost ali nespoštovanje, zato se ga
+                                    otrok izogiba.
+                                    <p>➡️<strong class="tip-label">Nasvet:</strong> Pristopite z razumevanjem in uporabite igre ali naloge, ki
+                                        omogočajo sodelovanje brez pritiska na neposreden očesni stik.</p>
+                                </li>
+                            </ol>
+
+                            <h2>5 praktičnih nasvetov</h2>
+
+                            <div class="article-inline-image float-right">
+                                <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/5.png"
+                                    alt="Praktični nasveti" loading="lazy">
+                            </div>
+
+                            <ol>
+                                <li><strong>Vprašajte, ne predvidevajte.</strong> Vsaka družina ima svojo zgodbo –
+                                    pristopite z radovednostjo, ne s sodbo.</li>
+                                <li><strong>Učite o raznolikosti.</strong> Pogovorite se o različnih jezikih, praznikih in
+                                    običajih – otroci bodo to doživeli kot bogastvo, ne kot razliko.</li>
+                                <li><strong>Ustvarite varno okolje.</strong> Naj učenci vedo, da je v redu, če delajo napake
+                                    v jeziku. Vzdušje sprejemanja spodbuja učenje.</li>
+                                <li><strong>Sodelujte s starši.</strong> Tudi kratka sporočila o napredku otroka gradijo
+                                    zaupanje.</li>
+                                <li><strong>Povežite se s strokovnjaki.</strong> Delavnice medkulturnega posredovanja ali
+                                    svetovanja lahko učiteljem in staršem pomagajo bolje razumeti kulturne razlike v
+                                    praksi.</li>
+                            </ol>
+
+                            <h2>Zaključek</h2>
+                            <div class="article-conclusion-block">
+                                <div class="article-inline-image article-image-wide conclusion-image">
+                                    <img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/6.png"
+                                        alt="Zaključek" loading="lazy" style="width:100%; height:auto;">
+                                </div>
+                                <div class="article-conclusion-text">
+                                    <p>Medkulturnost v razredu ni ovira, ampak priložnost, da skupaj ustvarimo okolje,
+                                        kjer se vsak otrok počuti slišan, spoštovan in sprejet. Z nekaj razumevanja,
+                                        potrpežljivosti in medsebojnega sodelovanja lahko razred postane resnično bogata
+                                        skupnost. Delite svoje izkušnje in vprašanja v kontaktnem obrazcu – skupaj lahko
+                                        gradimo močnejše in bolj vključujoče šolske in vrtčevske skupnosti.</p>
+                                </div>
+                            </div>
+                        </div>
+                    </article>
+                </div>
+
+                <aside class="blog-sidebar">
+                    <div class="sidebar-card">
+                        <h3>Povezane teme</h3>
+                        <div class="sidebar-links">
+                            <a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
+                            <a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
+                                priseljenci</a>
+                            <a href="/blog/">Vsi članki</a>
+                        </div>
+                    </div>
+                    <div class="sidebar-card">
+                        <h3>Potrebujete pomoč?</h3>
+                        <p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
+                        <a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
+                    </div>
+                </aside>
+            </div>
+        </section>
+
+        <section class="references-section" data-aos="fade-up">
+            <div class="references-container">
+                <div class="split-ref-layout">
+                    <div class="ref-left-wrapper">
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+                        <h2 class="references-kicker-custom">Mnenja, ki dajejo vpogled...</h2>
+                        <div class="ref-left-spacer" aria-hidden="true"></div>
+
+                        <div class="ref-group-left">
+                            <article class="reference-card">
+                                <p style="text-align:justify;">V luči mojega osebnega pozna&shy;vanja kolegice Amre Kurešepi sem prepri&shy;čan, da lastnosti, ki jih je izkazo&shy;vala že med študijem, to je zavze&shy;tost, resnost, odgo&shy;vornost, samo&shy;stojnost in ustvar&shy;jalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
+                                <div style="margin-top:auto; display:flex; flex-direction:column; gap:0.2rem;">
+                                    <p class="reference-author" style="margin-bottom:0;">red. prof. dr. Janez Skela</p>
+                                    <div class="reference-cta" style="white-space:nowrap; margin-top:0;">
+                                        <span>Preberi celo referenco</span>
+                                        <span class="reference-arrow">→</span>
+                                        <a class="reference-button" href="/cene-in-reference/#reference-janez">Prikaži</a>
+                                    </div>
+                                </div>
+                            </article>
+
+                            <article class="reference-card">
+                                <p style="text-align:justify;">Amra, ful ti hvala za vse res. Tako sem vesela, da nimam odpora do učenja angleš&shy;čine. Res čutim, da sem na pravi poti in želim od tega tečaja odnesti max. Me je pa treba priganjati in ti početje to zelo prijazno in profe&shy;sio&shy;nalno, za kar sem ti neskončno hvaležna. Tokrat prvič nimam strahu in sramu, da bom povedala ali naredila kaj narobe.</p>
+                                <p class="reference-author" style="text-align:left;">Mojca Triller, predstavnica klicnega centra</p>
+                            </article>
+                        </div>
+                    </div>
+
+                    <article class="reference-card">
+                        <p style="text-align:justify;">Z današnjo tehno&shy;logijo si s preva&shy;jalnikom sicer lahko prevedemo osnovne infor&shy;macije, za bolj kočljive teme pa je pogovor v živo nena&shy;domest&shy;ljiv. Kadar gre za teme, ki so za starše bolj čustvene (kot so otrokove težave v šoli ali učne težave, med&shy;vrstniško vklju&shy;čevanje, čustvene in vedenjske težave...) je še toliko bolj pomembno, da je sporočilo pravilno posre&shy;dovano in infor&shy;macije niso izgubljene v prevodu. Amra se je izkazala kot odlična pre&shy;vajalka prav v teh situacijah, saj je sama tudi učiteljica na osnovni šoli, pozna tako slovenski kot albanski šolski sistem ter tekoče govori oba jezika.</p>
+                        <p class="reference-author" style="text-align:left;">Barbara Vodopivec, svetovalna delavka v OŠ Livada, Ljubljana</p>
+                        <div class="reference-cta">
+                            <span>Preberi celo referenco</span>
+                            <span class="reference-arrow">→</span>
+                            <a class="reference-button" href="/cene-in-reference/#reference-barbara">Prikaži</a>
+                        </div>
+                    </article>
+                </div>
+            </div>
+        </section>
+        
+    </main>
+
+
+
+
+
+
+<section class="final-cta">
+<div class="final-cta-content" data-aos="fade-up">
+<h2>Imate vprašanje ali razmišljate o sodelovanju?</h2>
+<p style="font-size: 1.1rem; margin-bottom: 2rem; color: #444;">Z veseljem se pogovorimo!</p>
+<div class="final-cta-buttons">
+<a href="tel:+38630312855" class="cta-button contact-link">Pokličite me: +386 30 312 855</a>
+</div>
+<p style="margin-top: 2rem; font-size: 1.05rem;">Ali pišite preko <a href="/kontakt/" style="color: var(--primary-color); font-weight: 600; text-decoration: underline;">kontaktnega obrazca</a>.</p>
+</div>
+</section>
+
+<footer>
+    <div class="footer-content">
+        <div class="footer-logo">
+            <h3>PROSBERRY</h3>
+        </div>
+        <div class="footer-links">
+            <p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
+        </div>
+        <div class="footer-contact">
+            <p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
+            <p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
+        </div>
+    </div>
+</footer>
+    <script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
+    <script src="/js/main.js" defer></script>
+</body>
+
+</html>