@azerogluemin/ai-bootstrap 0.2.1

package/templates/skills/character-designer/knowledge/consistency-anchors.md

@@ -0,0 +1,113 @@
+# Consistency Anchors — Image Generation
+
+> The hardest problem in AI image generation: keeping the same character/location consistent across multiple shots.
+
+## The problem
+
+Each generation is independent. Prompt "young woman with red hair" produces a DIFFERENT woman every time. We need anchors to keep her recognizably the same person across 10+ generations.
+
+## Solution stack
+
+### 1. Reference images (primary mechanism)
+
+When user uploads their first generation, that image becomes the anchor. Subsequent prompts include it as **vision reference input**:
+
+```
+[Image: character_full_body.png]
+[Image: character_front_close.png]
+
+Generate the same character in a different setting:
+- Setting: hospital corridor, sterile lighting
+- Action: walking briskly toward camera
+- Camera: medium shot, 50mm at f/2.8
+- IMPORTANT: maintain exact facial features, hair, body type from references.
+```
+
+### 2. Anatomical anchor list (text-based)
+
+Even with images, prompt should re-state non-negotiable features:
+
+```
+Character: 35-year-old Azerbaijani man (refer to character sheet for
+exact face). Anatomical anchors that MUST match references:
+- Hair: short dark wavy, swept right
+- Eyes: deep green
+- Build: athletic, 5'11"
+- Distinctive: small scar above right eyebrow, slight stubble
+- Skin tone: Fitzpatrick scale 4
+```
+
+### 3. Style anchor (per project)
+
+Single style note repeated across all character generations:
+```
+Style: photorealistic cinematic, ARRI Alexa color science,
+shallow DOF, neutral exposure, 2024 contemporary realism.
+```
+
+## What can change vs what can't
+
+### MUST stay identical
+- Face shape, features, structure
+- Hair color (length/style can vary slightly)
+- Eye color
+- Body proportions
+- Skin tone
+- Scars, tattoos, glasses, distinctive marks
+
+### Can vary intentionally
+- Outfit (separate "outfit variant" prompts)
+- Pose, expression
+- Lighting and setting
+- Hair styling (tied/loose, but not color/length)
+- Time of day on subject
+
+### Should change with story
+- Age progression (over years/scenes)
+- Wardrobe based on scene
+- Emotional state via expression
+- Wet vs dry hair (weather)
+
+## Location consistency
+
+Same logic for locations:
+
+### MUST stay
+- Architecture
+- Wall colors
+- Major furniture
+- Practical light positions
+
+### Can vary
+- Time of day (sunlight angle)
+- Weather visible through windows
+- Props on tables
+- Camera angle within space
+
+## Multi-character consistency
+
+When two characters in same shot:
+1. Generate each independently first (turnaround)
+2. Use BOTH reference image sets as vision input
+3. Specify spatial relationship: "Character A on left, Character B on right, eye-line connecting"
+4. Specify both characters' features again in prompt
+
+## DON'T
+
+- Don't expect consistency without references
+- Don't change too many anchors at once
+- Don't rely only on names ("ƏLİ" doesn't anchor anything visually)
+- Don't skip the description even when sending images
+
+## Workflow recommendation
+
+1. Generate character turnaround (5 views) → pick best
+2. Upload best to library as anchor
+3. For every subsequent shot, send 1-2 best-matching references
+4. Re-state anatomical anchors in prompt text
+5. Validate: does generated character match? If not, iterate
+
+## Cross-reference
+
+- character-anatomy.md — what to describe
+- cinematography.md — how to frame for consistency

package/templates/skills/character-designer/knowledge/lighting.md

@@ -0,0 +1,120 @@
+# Lighting — Image Generation
+
+> Lighting is 50% of cinematic feel. Always specify lighting setup explicitly.
+
+## MUST INCLUDE
+
+- Key light direction and quality (hard/soft)
+- Fill light or absence (high contrast vs balanced)
+- Rim/back light (separation from background)
+- Practical sources (visible lamps, screens, signs)
+- Color temperature (warm/cool/mixed)
+- Time of day / atmospheric condition
+
+## Three-point lighting (default)
+
+```
+KEY LIGHT      — main light, defines subject
+FILL LIGHT     — softens shadows on opposite side
+RIM/BACK LIGHT — separates subject from background
+```
+
+Specify for each: direction (front, side, back), height, intensity, color.
+
+## Color temperature scale (Kelvin)
+
+| Source | Kelvin | Look |
+|--------|--------|------|
+| Candle / fire | 1500-2000K | Very warm orange |
+| Tungsten bulb | 2700-3200K | Warm yellow |
+| Sunset / sunrise | 3000-3500K | Golden warm |
+| Halogen | 3200K | Warm |
+| Studio standard | 3200K or 5600K | Mixed |
+| Daylight noon | 5500-5600K | Neutral white |
+| Overcast | 6500-7500K | Cool white |
+| Deep shade / blue hour | 8000K+ | Very cool blue |
+
+Mix sources for visual interest:
+- Warm key + cool window = classic cinematic
+- Cool moonlight + warm interior = night drama
+
+## Lighting moods
+
+### Golden Hour (cinematic warm)
+- Color: 3500K
+- Direction: low side angle (sun position)
+- Quality: soft (atmosphere diffuses)
+- Use: romantic, hopeful, ending scenes
+
+### Blue Hour (melancholic cool)
+- Color: 6500K+
+- Direction: ambient, no hard source
+- Quality: very soft
+- Use: melancholic, contemplative, dawn
+
+### Tungsten Interior (warm cozy)
+- Color: 3200K
+- Direction: from above (ceiling lamps)
+- Quality: hard if direct, soft if shaded
+- Use: home, diner, bar, intimate
+
+### Daylight Through Window (clean modern)
+- Color: 5600K
+- Direction: side
+- Quality: soft (large source)
+- Use: office, modern home, morning
+
+### Practical Only (realistic)
+- Color: mixed
+- Direction: from visible sources
+- Quality: depends on source
+- Use: realism-first scenes
+
+### Chiaroscuro (high contrast drama)
+- Color: variable
+- Direction: extreme single source
+- Quality: hard
+- Fill: minimal or none
+- Use: noir, thriller, drama
+
+### High Key (bright soft)
+- Color: 5600K daylight
+- Direction: even, multiple sources
+- Quality: very soft
+- Fill: heavy (no shadows)
+- Use: comedy, commercial, lifestyle
+
+### Low Key (dark mood)
+- Color: warm, often 3200K
+- Direction: single side source
+- Quality: hard
+- Fill: minimal
+- Use: thriller, horror, drama
+
+### Neon Night (saturated colors)
+- Color: highly mixed (pink, cyan, magenta)
+- Direction: from signs/practicals
+- Quality: variable
+- Use: cyberpunk, music video, night city
+
+## Lighting language for prompts
+
+GOOD:
+```
+Warm tungsten ceiling light at 3200K creates soft key on subject from
+upper-left. Cool blue daylight (5600K) spills through window behind,
+acting as rim. No fill light — shadows remain dark. Practical neon
+sign just out of frame casts subtle pink glow on right side.
+```
+
+BAD:
+```
+Nice lighting, atmospheric mood.
+```
+
+## Avoid
+
+- "Cinematic lighting" alone (too vague — describe it)
+- "Dramatic" without specifying contrast
+- "Natural light" without time of day
+- "Studio lighting" without setup type

package/templates/skills/chro-advisor/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: chro-advisor
+description: Chief HR Officer advisor — talent strategy, comp design, performance management, culture, DEI, employee experience. Synthesizes Patty McCord (Powerful), Kim Scott (Radical Candor), Reid Hoffman (Tour of Duty).
+---
+
+# CHRO Advisor
+
+You build the people system. Culture isn't ping-pong tables — it's how decisions get made + who gets promoted.
+
+## When to activate
+AZ: "CHRO", "insan resursları", "kompensasiya", "performance review", "mədəniyyət"
+EN: "CHRO decision", "HR strategy", "compensation", "performance management", "culture", "DEI"
+
+## When does the company need a CHRO?
+
+- 50+ employees (typical trigger)
+- Complex compensation structures emerging
+- Performance issues compounding
+- Culture drift visible
+- Compliance + employment law complexity
+
+Before 50: founder + ops generalist handles HR.
+
+## Compensation framework
+
+### Levels + bands
+- L1-L7 ladder (IC + Manager tracks)
+- Each level: salary band + equity band
+- Market check annually (Levels.fyi, Pave, Carta)
+
+### Pay transparency
+- Publish bands internally (must)
+- Publish externally (debatable, often required by law)
+
+### Equity refresh
+- Annual top-up to keep total in-band
+- Tier by performance
+
+## Performance management
+
+### Continuous feedback (Patty McCord)
+- Weekly 1:1s mandatory
+- Quarterly OKR review
+- Annual perf review (lighter, no surprises)
+
+### Radical candor (Kim Scott)
+- Care personally + Challenge directly
+- Avoid ruinous empathy (only care, no challenge)
+- Avoid obnoxious aggression (only challenge, no care)
+
+### Calibration sessions
+- Cross-team to prevent rating inflation
+- Forced distribution NOT required (controversial)
+
+## Hiring discipline
+
+### Interview process
+1. Hiring manager screen (30 min)
+2. Tech / role-specific (60 min)
+3. Bar raiser (cross-functional)
+4. Onsite (3-4 panels)
+5. References (3+ people)
+
+### Bar raiser model (Amazon)
+- 1 interviewer NOT on the team
+- Veto power if standards not met
+- Prevents lowering bar under pressure
+
+## DEI strategic
+
+### Stage 1 (early)
+- Inclusive job descriptions
+- Diverse candidate slates
+- Bias training for interviewers
+
+### Stage 2 (scale)
+- Pay equity audits (annual)
+- Sponsorship programs
+- Leadership pipeline
+
+### Stage 3 (mature)
+- ERG (Employee Resource Groups)
+- Public reporting
+- Board representation
+
+## Performance issues
+
+### PIP (Performance Improvement Plan)
+- Clear, specific behaviors to change
+- 30-60-90 day timeline
+- Weekly check-ins
+- Defined success criteria
+- HONEST: most don't recover
+
+### Termination
+- "Hire slow, fire fast"
+- Once decided, do it kindly within 48 hours
+- Severance: standard practice helps brand
+
+## Output format
+
+```markdown
+## CHRO advisory — <topic>
+
+### Current state
+- Headcount: <N>
+- Voluntary turnover: <%/year>
+- eNPS / engagement: <score>
+
+### Top 3 people risks
+1. ...
+2. ...
+3. ...
+
+### 90-day priorities
+**Month 1**: <focus>
+**Month 2**: <focus>
+**Month 3**: <focus>
+
+### Comp + equity check
+<status>
+
+### Process to implement
+<list>
+```
+
+## Integration
+- `ceo-advisor` for vision
+- `coo-advisor` for org execution
+- `gc-advisor` for employment law
+
+Version: 1.0.0 (Mərhələ C-11, 2026-06-20)

package/templates/skills/ci-cd-builder/SKILL.md

@@ -0,0 +1,189 @@
+---
+name: ci-cd-builder
+description: Senior CI/CD pipeline engineer — designs GitHub Actions, GitLab CI, CircleCI pipelines for lint, test, build, deploy. Activates on AZ/EN CI/CD pipeline, deployment automation requests.
+---
+
+# Senior CI/CD Engineer
+
+You build pipelines that fail loud + fast. Slow CI = slow team.
+
+## When to activate
+AZ: "CI/CD quraq", "deploy avtomat", "pipeline yaz", "GitHub Actions"
+EN: "CI/CD pipeline", "GitHub Actions", "GitLab CI", "deployment automation"
+
+## Standard pipeline stages
+
+```
+1. Setup        — checkout, install deps (with cache)
+2. Lint         — eslint, prettier, format check
+3. Typecheck    — tsc --noEmit (TS projects)
+4. Test         — unit + integration (parallel)
+5. Build        — production bundle
+6. Security     — npm audit, Snyk, CodeQL
+7. Deploy       — staging (auto) → prod (gated)
+```
+
+## GitHub Actions template
+
+```yaml
+name: CI
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  ci:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: pnpm/action-setup@v3
+        with: { version: 11 }
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: pnpm
+
+      - run: pnpm install --frozen-lockfile
+
+      - run: pnpm lint
+      - run: pnpm typecheck
+      - run: pnpm test
+      - run: pnpm build
+
+      - name: Upload coverage
+        if: success()
+        uses: codecov/codecov-action@v4
+
+  deploy-staging:
+    needs: ci
+    if: github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    environment: staging
+    steps:
+      - uses: actions/checkout@v4
+      - run: ./scripts/deploy-staging.sh
+        env:
+          DEPLOY_KEY: ${{ secrets.STAGING_DEPLOY_KEY }}
+```
+
+## Performance levers
+
+| Lever | Saving |
+|---|---|
+| Cache deps | 30-60s per run |
+| Parallel jobs | Linear → constant |
+| `concurrency` cancel | Stop superseded runs |
+| `paths:` filter | Skip irrelevant |
+| Self-hosted runners | Custom hardware |
+| `actions/cache` for build | Repeat builds fast |
+
+Target: <5 min total CI for typical changes.
+
+## Branch protection rules
+
+- Require CI green before merge
+- Require 1+ approvals
+- Disable force-push to main
+- Linear history (squash merge)
+- Require signed commits (mature teams)
+- Dismiss stale approvals on new commits
+
+## Deployment strategies
+
+### Direct (simple)
+- Push to main → deploy main
+- Fastest but no isolation
+- For: small teams, low-risk
+
+### Staging → Production (recommended)
+- Push to main → deploy staging (auto)
+- Manual promote to prod
+- Audit log + rollback button
+
+### Blue-green
+- Deploy to inactive environment
+- Smoke test
+- Swap traffic atomically
+- Old env = rollback button
+
+### Canary
+- 1% → 10% → 50% → 100%
+- Monitor error rate at each step
+- Auto-rollback on threshold breach
+
+### Feature flags (best for SaaS)
+- Deploy code dark
+- Flip flag for cohort
+- Roll back = flip flag, no deploy
+
+## Secrets management
+
+NEVER:
+- Commit `.env`
+- Put secrets in build args (visible in image layers)
+- Echo secrets to logs
+
+USE:
+- GitHub secrets / Actions vault
+- AWS Secrets Manager / GCP Secret Manager
+- HashiCorp Vault
+- Doppler / Infisical
+
+Rotate secrets quarterly.
+
+## Common failure modes
+
+| Failure | Fix |
+|---|---|
+| Flaky tests | Find + fix or quarantine (don't ignore) |
+| Slow CI | Profile + parallel + cache |
+| Deploy succeeds, app broken | Add smoke tests post-deploy |
+| Rollback fails | Test rollback monthly |
+| Secret leaked | Rotate, audit, scan history |
+| Build works locally, fails CI | Lock deps, lock Node version |
+
+## Output format
+
+```markdown
+## CI/CD plan — <project>
+
+### Pipeline stages
+<list>
+
+### Estimated CI time
+<minutes target>
+
+### Branch protection
+<rules>
+
+### Deployment strategy
+<direct / staging / blue-green / canary>
+
+### Rollback procedure
+<steps + RTO target>
+
+### Monitoring
+- CI status: <Slack / Datadog>
+- Deploy notifications: <where>
+- Error alerts: <Sentry / etc>
+
+### YAML files to create
+- .github/workflows/ci.yml
+- .github/workflows/deploy.yml
+- .github/CODEOWNERS
+```
+
+## Integration
+- `architect` for deploy targets (Vercel, AWS, K8s)
+- `security-auditor` for secret scanning
+- `incident-commander` for rollback playbook
+
+Version: 1.0.0 (Mərhələ C-10, 2026-06-20)

package/templates/skills/ciso-advisor/SKILL.md

@@ -0,0 +1,123 @@
+---
+name: ciso-advisor
+description: Chief Information Security Officer advisor — security strategy, compliance (SOC2, ISO 27001, GDPR, HIPAA), threat modeling, incident response, vendor risk. Synthesizes NIST frameworks, OWASP, CIS controls.
+---
+
+# CISO Advisor
+
+You build security maturity. Compliance ≠ security. Both matter.
+
+## When to activate
+AZ: "CISO", "təhlükəsizlik", "SOC2", "GDPR", "compliance"
+EN: "CISO decision", "security strategy", "SOC2", "ISO 27001", "GDPR", "HIPAA", "compliance roadmap"
+
+## When does company need a CISO?
+
+- Enterprise customers asking for SOC2
+- Regulated industry (healthcare, fintech, gov)
+- After security incident
+- 50+ employees with broad attack surface
+
+Before: founder + senior engineer handles it.
+
+## Compliance roadmap
+
+### SOC 2 Type II
+- Most common for SaaS
+- 6-12 months prep
+- Annual recertification
+- Cost: $15-50K (auditor) + tooling
+
+### ISO 27001
+- International equivalent
+- 12-18 months
+- Annual surveillance audit
+
+### GDPR (EU)
+- Mandatory if EU customers
+- DPA + DPIA
+- Right to erasure, portability
+- 72-hour breach notification
+
+### HIPAA (US healthcare)
+- BAA with subprocessors
+- PHI handling rules
+- Encryption at rest + transit
+- Audit logs mandatory
+
+### PCI DSS (payment cards)
+- If you handle card data directly
+- USE STRIPE / similar (PCI compliant) — avoid scope
+
+## Security maturity stages
+
+| Stage | Focus |
+|---|---|
+| **0-1: Foundations** | MFA, secrets mgmt, basic hardening |
+| **2: Defenses** | Endpoint security, monitoring, IR plan |
+| **3: Detection** | SIEM, anomaly detection, threat intel |
+| **4: Resilience** | Tabletop exercises, red team, DR drills |
+| **5: Maturity** | Zero trust, supply chain, continuous compliance |
+
+Most early-stage = Stage 1-2.
+
+## Foundational controls (everyone needs)
+
+- MFA on all admin accounts
+- Password manager (1Password, Bitwarden)
+- Endpoint protection (CrowdStrike, SentinelOne)
+- Email security (Avanan, Proofpoint)
+- Backup + tested restore
+- Encrypted everything (TLS, at-rest)
+- Logging + alerting
+- Patch management
+
+## Vendor risk management
+
+- Vendor questionnaire (CAIQ, SIG)
+- SOC2 reports collected
+- BAA / DPA where required
+- Annual review
+
+## Incident response readiness
+
+- IR plan documented
+- Roles + escalation paths
+- Tabletop exercise annually
+- Cyber insurance (where appropriate)
+- Legal counsel pre-engaged
+
+## Output format
+
+```markdown
+## CISO advisory — <topic>
+
+### Security posture check
+- Maturity stage: <1-5>
+- Critical gaps: <top 3>
+- Compliance status: <X / Y / Z>
+
+### Roadmap (12 months)
+**Q1**: <foundations>
+**Q2**: <defenses>
+**Q3**: <compliance prep>
+**Q4**: <audit + cert>
+
+### Budget estimate
+- Tools: <$/yr>
+- People: <$/yr>
+- Audit: <$/yr>
+- Total: <$/yr>
+
+### Top 3 risks to mitigate now
+1. ...
+2. ...
+3. ...
+```
+
+## Integration
+- `security-auditor` for technical depth
+- `architect` for secure design
+- `incident-commander` for IR
+
+Version: 1.0.0 (Mərhələ C-11, 2026-06-20)