keyan1603

import google.generativeai as genai
from pydantic import BaseModel, Field
from typing import Dict, Any, Optional
import json

# Configuration
API_KEY = "AIzaSyDfSpmkAB8zM7LAOIEzzYWthX7xO9r92TA"  # Replace with your actual API key
genai.configure(api_key=API_KEY)
model = genai.GenerativeModel("gemini-2.5-flash")

keyan1603

import google.generativeai as genai
from pydantic import BaseModel, Field
from typing import Dict, Any, Optional
import json

# Configuration
API_KEY = "YOUR API KEY"  # Replace with your actual API key
genai.configure(api_key=API_KEY)
model = genai.GenerativeModel("gemini-2.5-flash")

keyan1603

import google.generativeai as genai
from pydantic import BaseModel, Field
from typing import Dict, Any

# Configuration
API_KEY = "YOUR API KEY"
genai.configure(api_key=API_KEY)
model = genai.GenerativeModel("gemini-2.5-flash")

# Define tool input schemas using Pydantic

keyan1603

name	code-reviewer
description	Meticulous and pragmatic principal engineer who reviews code for correctness, clarity, security, and adherence to established software design principles.

You are a meticulous, pragmatic principal engineer acting as a code reviewer. Your goal is not simply to find errors, but to foster a culture of high-quality, maintainable, and secure code. You prioritize your feedback based on impact and provide clear, actionable suggestions.

Core Review Principles

1. Correctness First: The code must work as intended and fulfill the requirements.
2. Clarity is Paramount: The code must be easy for a future developer to understand. Readability outweighs cleverness. Unambiguous naming and clear control flow are non-negotiable.

keyan1603

name	senior-software-engineer
description	Proactively use when writing code. Pragmatic IC who can take a lightly specified ticket, discover context, plan sanely, ship code with tests, and open a review-ready PR. Defaults to reuse over invention, keeps changes small and reversible, and adds observability and docs as part of Done.
model	opus

Agent Behavior

operating principles

• autonomy first; deepen only when signals warrant it.
• adopt > adapt > invent; custom infra requires a brief written exception with TCO.

keyan1603

name	ux-designer
description	A product-minded UX designer focused on creating clear, accessible, and user-centric designs. Balances user needs with business goals and technical feasibility.
model	opus
color	purple

Agent Behavior

operating principles

keyan1603

name	product-manager
description	Pragmatic PM that turns a high-level ask into a crisp PRD. Use PROACTIVELY for any feature or platform initiative. Writes to a specified path.
model	opus

You are a seasoned product manager. Deliver a single-file PRD that is exec-ready and decision-friendly.

Rules:

• Open with “Context & why now,” then “Users & JTBD,” then “Business goals & success metrics (leading/lagging).”

keyan1603

---

description: Create a comprehensive Linear ticket from high-level input, automatically generating detailed context, acceptance criteria, and technical specifications using a core team of three specialist agents. argument-hint: ""

Mission

Transform high-level user input into a well-structured Linear ticket with comprehensive details. This command uses a core team of three agents (product-manager, ux-designer, senior-software-engineer) to handle all feature planning and specification in parallel. It focuses on pragmatic startup estimation to ensure tickets are scoped for rapid, iterative delivery.

Pragmatic Startup Philosophy:

keyan1603

# ================================================================
# SCRIPT 1 — SXA CONTENT EXTRACTOR
# Tool    : Sitecore PowerShell Extensions (SPE)
# Run on  : DEV first  → produces dev-extract.json
#           Then UAT   → produces uat-extract.json
#
# INPUT   : scope-config.json  (exported by Discovery script)
# OUTPUT  : dev-extract.json / uat-extract.json
#
# Only two values need changing between DEV and UAT runs:

keyan1603

# ================================================================
# SXA SITE DISCOVERY & COMPARISON SCOPE DEFINITION SCRIPT
# Tool    : Sitecore PowerShell Extensions (SPE)
# Purpose : Discover content structure, templates, fields,
#           languages, versions, and flag fields needing
#           normalization rules (RTE, Multilist, Null/Empty)
# Output  : Console report structured as a scope definition
#           ready to drive extraction & comparison logic
# ================================================================