cokit-cli 1.2.7 → 1.4.0

package/templates/repo/.github/skills/databases/stacks/sqlite.md

@@ -1,244 +0,0 @@
-# SQLite Rules
-
-Guidelines for designing schemas specific to SQLite.
-
----
-
-## Data Types
-
-SQLite has **dynamic typing**, with only 5 storage classes:
-
-| Storage Class | Use case | Notes |
-|---------------|----------|-------|
-| `INTEGER` | PK, FK, counts, booleans | |
-| `REAL` | Floats, decimals | |
-| `TEXT` | Strings, dates, JSON, enums | |
-| `BLOB` | Binary data | |
-| `NULL` | Null values | |
-
-### Type affinity
-SQLite does not strictly enforce types. Type declaration is just a "hint":
-```sql
--- All of these will be stored
-CREATE TABLE test (price REAL);
-INSERT INTO test VALUES (100);      -- Stored as INTEGER
-INSERT INTO test VALUES (99.99);    -- Stored as REAL
-INSERT INTO test VALUES ('free');   -- Stored as TEXT (!)
-```
-
-### Date/Time
-SQLite **does not have** DATE/TIME type. Store as TEXT with ISO format:
-```sql
-created_at TEXT DEFAULT (datetime('now'))
--- Format: YYYY-MM-DD HH:MM:SS
-```
-
----
-
-## Metadata Tables (REQUIRED)
-
-SQLite **does not support comments** on tables and columns. Need to create metadata tables:
-
-### Create metadata tables
-
-```sql
-CREATE TABLE IF NOT EXISTS metadata_tables (
-    table_name TEXT PRIMARY KEY,
-    description TEXT NOT NULL,
-    created_at TEXT DEFAULT (datetime('now')),
-    updated_at TEXT DEFAULT (datetime('now'))
-);
-
-CREATE TABLE IF NOT EXISTS metadata_columns (
-    table_name TEXT NOT NULL,
-    column_name TEXT NOT NULL,
-    description TEXT NOT NULL,
-    data_type TEXT,
-    is_nullable INTEGER DEFAULT 1,  -- 0=NOT NULL, 1=NULL
-    default_value TEXT,
-    created_at TEXT DEFAULT (datetime('now')),
-    PRIMARY KEY (table_name, column_name),
-    FOREIGN KEY (table_name) REFERENCES metadata_tables(table_name) ON DELETE CASCADE
-);
-
-CREATE INDEX idx_metadata_columns_table ON metadata_columns(table_name);
-```
-
-### Insert metadata after creating table
-
-```sql
--- Table metadata
-INSERT INTO metadata_tables (table_name, description)
-VALUES ('orders', 'Table storing customer order information');
-
--- Column metadata
-INSERT INTO metadata_columns (table_name, column_name, description, data_type, is_nullable)
-VALUES
-    ('orders', 'id', 'Primary key, auto increment', 'INTEGER', 0),
-    ('orders', 'order_number', 'Unique order code', 'TEXT', 0),
-    ('orders', 'user_id', 'FK to users.id', 'INTEGER', 0),
-    ('orders', 'status', 'pending|confirmed|shipped|cancelled', 'TEXT', 0),
-    ('orders', 'total_amount', 'Total value', 'REAL', 0);
-```
-
-### Query metadata
-
-```sql
--- View schema with descriptions
-SELECT
-    t.table_name,
-    t.description AS table_description,
-    c.column_name,
-    c.description AS column_description,
-    c.data_type
-FROM metadata_tables t
-LEFT JOIN metadata_columns c ON t.table_name = c.table_name
-ORDER BY t.table_name, c.column_name;
-```
-
----
-
-## Auto Increment
-
-```sql
--- Option 1: INTEGER PRIMARY KEY (recommended)
--- SQLite auto-increments INTEGER PRIMARY KEY automatically
-CREATE TABLE users (
-    id INTEGER PRIMARY KEY,
-    name TEXT
-);
-
--- Option 2: AUTOINCREMENT keyword
--- Ensures deleted IDs are not reused (slower)
-CREATE TABLE users (
-    id INTEGER PRIMARY KEY AUTOINCREMENT,
-    name TEXT
-);
-```
-
----
-
-## Foreign Keys
-
-**IMPORTANT**: FK is disabled by default in SQLite!
-
-```sql
--- Enable FK for each connection
-PRAGMA foreign_keys = ON;
-
--- Create table with FK
-CREATE TABLE order_items (
-    id INTEGER PRIMARY KEY,
-    order_id INTEGER NOT NULL,
-    product_id INTEGER NOT NULL,
-    FOREIGN KEY (order_id) REFERENCES orders(id) ON DELETE CASCADE,
-    FOREIGN KEY (product_id) REFERENCES products(id) ON DELETE RESTRICT
-);
-
--- Create index for FK
-CREATE INDEX idx_order_items_order ON order_items(order_id);
-CREATE INDEX idx_order_items_product ON order_items(product_id);
-```
-
----
-
-## ENUM substitute
-
-SQLite does not have ENUM. Use CHECK constraint:
-
-```sql
-CREATE TABLE orders (
-    status TEXT NOT NULL DEFAULT 'pending'
-        CHECK (status IN ('pending', 'confirmed', 'shipped', 'cancelled'))
-);
-```
-
----
-
-## Index Types
-
-SQLite only supports B-Tree indexes:
-
-```sql
--- Standard index
-CREATE INDEX idx_orders_status ON orders(status);
-
--- Composite index
-CREATE INDEX idx_orders_user_status ON orders(user_id, status);
-
--- Unique index
-CREATE UNIQUE INDEX idx_orders_number ON orders(order_number);
-
--- Partial index (SQLite 3.8.0+)
-CREATE INDEX idx_orders_active ON orders(user_id)
-    WHERE deleted_at IS NULL;
-```
-
----
-
-## Limitations
-
-| Feature | Status | Workaround |
-|---------|--------|------------|
-| `ALTER COLUMN` | ❌ Not supported | Recreate table |
-| `DROP COLUMN` | ✅ SQLite 3.35+ | Recreate table (older) |
-| Comments | ❌ Not supported | Metadata tables |
-| ENUM | ❌ Not supported | CHECK constraint |
-| Stored procedures | ❌ Not supported | App logic |
-| Concurrent writes | ⚠️ Limited | Single writer |
-
----
-
-## Example DDL
-
-```sql
--- Enable foreign keys
-PRAGMA foreign_keys = ON;
-
--- Create table
-CREATE TABLE orders (
-    id INTEGER PRIMARY KEY AUTOINCREMENT,
-    order_number TEXT NOT NULL,
-    user_id INTEGER NOT NULL,
-    status TEXT NOT NULL DEFAULT 'pending'
-        CHECK (status IN ('pending', 'confirmed', 'shipped', 'cancelled')),
-    subtotal REAL NOT NULL DEFAULT 0,
-    discount_amount REAL NOT NULL DEFAULT 0,
-    total_amount REAL NOT NULL DEFAULT 0,
-    created_at TEXT NOT NULL DEFAULT (datetime('now')),
-    updated_at TEXT NOT NULL DEFAULT (datetime('now')),
-    deleted_at TEXT,
-
-    FOREIGN KEY (user_id) REFERENCES users(id) ON DELETE RESTRICT
-);
-
--- Indexes
-CREATE UNIQUE INDEX idx_orders_number ON orders(order_number);
-CREATE INDEX idx_orders_user ON orders(user_id);
-CREATE INDEX idx_orders_status ON orders(status);
-CREATE INDEX idx_orders_updated ON orders(updated_at);
-
--- Metadata
-INSERT INTO metadata_tables (table_name, description)
-VALUES ('orders', 'Table storing order information');
-
-INSERT INTO metadata_columns (table_name, column_name, description, data_type, is_nullable)
-VALUES
-    ('orders', 'id', 'Primary key', 'INTEGER', 0),
-    ('orders', 'order_number', 'Unique order code', 'TEXT', 0),
-    ('orders', 'user_id', 'FK to users.id', 'INTEGER', 0),
-    ('orders', 'status', 'pending|confirmed|shipped|cancelled', 'TEXT', 0),
-    ('orders', 'total_amount', 'Total payment', 'REAL', 0);
-```
-
----
-
-## Checklist
-
-- [ ] `PRAGMA foreign_keys = ON` at start of each connection
-- [ ] Metadata tables created
-- [ ] INSERT metadata after each CREATE TABLE
-- [ ] Use `TEXT` for dates (ISO format: YYYY-MM-DD HH:MM:SS)
-- [ ] CHECK constraint instead of ENUM
-- [ ] Index for FK columns
-- [ ] Update metadata when ALTER/DROP table

package/templates/repo/.github/skills/debug/SKILL.md

@@ -1,178 +0,0 @@
----
-name: debug
-description: Debug systematically with root cause analysis before fixes. Covers bugs, test failures, log analysis, CI/CD failures, database diagnostics, system investigation, performance issues, call stack tracing, multi-layer validation.
----
-
-# Debugging & System Investigation
-
-Comprehensive debugging framework combining systematic investigation, root cause tracing, defense-in-depth validation, verification protocols, and system-level diagnostics.
-
-## Core Principle
-
-**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST**
-
-Random fixes waste time and create new bugs. Find the root cause, fix at source, validate at every layer, verify before claiming success.
-
-## When to Use
-
-**Code-level:** Test failures, bugs, unexpected behavior, build failures, integration problems, before claiming work complete
-
-**System-level:** CI/CD pipeline failures, log analysis, database diagnostics, performance bottlenecks, infrastructure issues
-
-**Especially when:** Under time pressure, "quick fix" seems obvious, tried multiple fixes, don't fully understand issue, about to claim success
-
-## Techniques
-
-### 1. Systematic Debugging (`references/systematic-debugging.md`)
-
-Four-phase framework:
-- Phase 1: Root Cause Investigation (read errors, reproduce, check changes, gather evidence)
-- Phase 2: Pattern Analysis (find working examples, compare, identify differences)
-- Phase 3: Hypothesis and Testing (form theory, test minimally, verify)
-- Phase 4: Implementation (create test, fix once, verify)
-
-Complete each phase before proceeding. No fixes without Phase 1.
-
-**Load when:** Any bug/issue requiring investigation and fix
-
-### 2. Root Cause Tracing (`references/root-cause-tracing.md`)
-
-Trace bugs backward through call stack to find original trigger. Fix at source, not at symptom.
-
-**Includes:** `scripts/find-polluter.sh` for bisecting test pollution
-
-**Load when:** Error deep in call stack, unclear where invalid data originated
-
-### 3. Defense-in-Depth (`references/defense-in-depth.md`)
-
-Validate at every layer data passes through. Four layers: Entry validation → Business logic → Environment guards → Debug instrumentation
-
-**Load when:** After finding root cause, need to add comprehensive validation
-
-### 4. Verification (`references/verification.md`)
-
-Run verification commands and confirm output before claiming success.
-
-**Iron law:** NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
-
-**Load when:** About to claim work complete, fixed, or passing
-
-### 5. Investigation Methodology
-
-For system-level issues (CI/CD, infrastructure, data pipeline):
-
-1. **Scope** - Define what is broken and what is working
-2. **Gather** - Collect logs, metrics, error outputs before touching anything
-3. **Isolate** - Narrow to smallest reproducible case
-4. **Hypothesize** - Form one theory, test it, reject or confirm
-5. **Fix & Validate** - Fix at root, verify at every affected layer
-
-**Load when:** Issue is not code-local — spans services, environments, or pipelines
-
-### 6. Log & CI/CD Analysis
-
-Use `gh` CLI and structured queries to diagnose pipeline failures:
-
-```bash
-# View failed CI run logs
-gh run view <run-id> --log-failed
-
-# List recent runs for a workflow
-gh run list --workflow=<name> --limit 10
-
-# Watch a running workflow
-gh run watch <run-id>
-```
-
-For structured logs: filter by severity, timestamp range, and correlation ID before reading raw output.
-
-**Load when:** CI/CD failure, deployment issue, or log-driven investigation
-
-### 7. Performance Diagnostics
-
-Identify bottlenecks before optimizing:
-- Profile first — measure before guessing
-- Check slow queries with `EXPLAIN ANALYZE` (PostgreSQL) or equivalent
-- Identify N+1 query patterns in ORM usage
-- Check memory allocation patterns for leaks
-- Use `psql` for live database diagnostics
-
-**Load when:** Slowness reported, timeout errors, resource exhaustion
-
-### 8. Reporting Standards
-
-For multi-component investigations, write a structured diagnostic report:
-
-```
-## Diagnostic Report
-- **Issue:** [one-line description]
-- **Root Cause:** [where and why it fails]
-- **Evidence:** [logs, output, reproduction steps]
-- **Fix Applied:** [what was changed]
-- **Verification:** [command run + result]
-- **Remaining Risk:** [any open questions]
-```
-
-Save to `plans/reports/debugger-{date}-{slug}.md`.
-
-**Load when:** Investigation spans multiple components or will be shared with others
-
-### 9. Task Management
-
-For multi-component investigations, track progress with a checklist rather than holding state mentally:
-
-```
-- [ ] Reproduce the issue
-- [ ] Identify root cause
-- [ ] Fix applied
-- [ ] Tests passing
-- [ ] Verification complete
-```
-
-Add this checklist to the active plan or investigation report. Check items off as each step completes.
-
-**Load when:** Investigation touches 3+ components or files
-
-### 10. Frontend Verification
-
-For visual bugs or UI regressions, use browser developer tools (or the `agent-browser` skill) to inspect rendering, network, and console errors directly in the browser.
-
-Use `/ck-scout ext` to search for frontend-specific patterns before diving into devtools.
-
-**Load when:** Visual regression, layout bug, client-side network error, or UI behavior that differs from expected
-
-## Quick Reference
-
-```
-Code bug → systematic-debugging.md (Phase 1-4)
-  Error deep in stack? → root-cause-tracing.md (trace backward)
-  Found root cause? → defense-in-depth.md (add layers)
-  About to claim success? → verification.md (verify first)
-
-System issue → Investigation Methodology (5 steps)
-  CI/CD failure? → Log & CI/CD Analysis (gh CLI)
-  Slow/timeout? → Performance Diagnostics
-  Multi-component? → Task Management checklist + Reporting Standards
-  Visual/UI bug? → Frontend Verification (agent-browser / browser devtools)
-```
-
-## Tools Integration
-
-| Tool | Use Case |
-|------|----------|
-| `execute` | Run test commands, build scripts, verification steps |
-| `gh` CLI | CI/CD log analysis, PR checks, workflow runs |
-| `psql` | Live database diagnostics and slow query analysis |
-| `agent-browser` skill | Frontend visual verification and network inspection |
-| `/ck-scout` | Search codebase for related patterns before investigating |
-
-## Red Flags
-
-Stop and follow process if thinking:
-- "Quick fix for now, investigate later"
-- "Just try changing X and see if it works"
-- "It's probably X, let me fix that"
-- "Should work now" / "Seems fixed"
-- "Tests pass, we're done"
-
-**All mean:** Return to systematic process.

package/templates/repo/.github/skills/devops/SKILL.md

@@ -1,102 +0,0 @@
----
-name: devops
-description: Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Azure (App Service, AKS), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.
----
-
-# DevOps Skill
-
-Deploy and manage cloud infrastructure across Cloudflare, Docker, Google Cloud, and Kubernetes.
-
-## When to Use
-
-- Deploy serverless apps to Cloudflare Workers/Pages
-- Containerize apps with Docker, Docker Compose
-- Manage GCP with gcloud CLI (Cloud Run, GKE, Cloud SQL)
-- Kubernetes cluster management (kubectl, Helm)
-- GitOps workflows (Argo CD, Flux)
-- CI/CD pipelines, multi-region deployments
-- Security audits, RBAC, network policies
-
-## Platform Selection
-
-| Need | Choose |
-|------|--------|
-| Sub-50ms latency globally | Cloudflare Workers |
-| Large file storage (zero egress) | Cloudflare R2 |
-| SQL database (global reads) | Cloudflare D1 |
-| Containerized workloads | Docker + Cloud Run/GKE/Azure Container Apps |
-| Enterprise Kubernetes | GKE / AKS |
-| Managed relational DB | Cloud SQL / Azure SQL |
-| .NET workloads | Azure App Service / Container Apps |
-| Static site + API | Cloudflare Pages |
-| Container orchestration | Kubernetes |
-| Package management for K8s | Helm |
-
-## Quick Start
-
-```bash
-# Cloudflare Worker
-wrangler init my-worker && cd my-worker && wrangler deploy
-
-# Docker
-docker build -t myapp . && docker run -p 3000:3000 myapp
-
-# GCP Cloud Run
-gcloud run deploy my-service --image gcr.io/project/image --region us-central1
-
-# Azure App Service (.NET)
-az webapp up --name myapp --resource-group mygroup --runtime "DOTNET:8.0"
-
-# Azure Container Apps
-az containerapp up --name myapp --resource-group mygroup --image myregistry.azurecr.io/myapp:latest
-
-# Kubernetes
-kubectl apply -f manifests/ && kubectl get pods
-```
-
-## Reference Navigation
-
-### Cloudflare Platform
-- `cloudflare-platform.md` - Edge computing overview
-- `cloudflare-workers-basics.md` - Handler types, patterns
-- `cloudflare-workers-advanced.md` - Performance, optimization
-- `cloudflare-workers-apis.md` - Runtime APIs, bindings
-- `cloudflare-r2-storage.md` - Object storage, S3 compatibility
-- `cloudflare-d1-kv.md` - D1 SQLite, KV store
-- `browser-rendering.md` - Puppeteer automation
-
-### Docker
-- `docker-basics.md` - Dockerfile, images, containers
-- `docker-compose.md` - Multi-container apps
-
-### Google Cloud
-- `gcloud-platform.md` - gcloud CLI, authentication
-- `gcloud-services.md` - Compute Engine, GKE, Cloud Run
-
-### Kubernetes
-- `kubernetes-basics.md` - Core concepts, architecture, workloads
-- `kubernetes-kubectl.md` - Essential commands, debugging workflow
-- `kubernetes-helm.md` / `kubernetes-helm-advanced.md` - Helm charts, templates
-- `kubernetes-security.md` / `kubernetes-security-advanced.md` - RBAC, secrets
-- `kubernetes-workflows.md` / `kubernetes-workflows-advanced.md` - GitOps, CI/CD
-- `kubernetes-troubleshooting.md` / `kubernetes-troubleshooting-advanced.md` - Debug
-
-### Scripts
-- `scripts/cloudflare-deploy.py` - Automate Worker deployments
-- `scripts/docker-optimize.py` - Analyze Dockerfiles
-
-## Best Practices
-
-**Security:** Non-root containers, RBAC, secrets in env vars, image scanning
-**Performance:** Multi-stage builds, edge caching, resource limits
-**Cost:** R2 for large egress, caching, right-size resources
-**Development:** Docker Compose local dev, wrangler dev, version control IaC
-
-## Resources
-
-- Cloudflare: https://developers.cloudflare.com
-- Docker: https://docs.docker.com
-- GCP: https://cloud.google.com/docs
-- Azure: https://learn.microsoft.com/azure/
-- Kubernetes: https://kubernetes.io/docs
-- Helm: https://helm.sh/docs

package/templates/repo/.github/skills/docs-seeker/SKILL.md

@@ -1,96 +0,0 @@
----
-name: docs-seeker
-description: Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
----
-
-# Documentation Discovery via Scripts
-
-## Overview
-
-**Script-first** documentation discovery using llms.txt standard.
-
-Execute scripts to handle entire workflow - no manual URL construction needed.
-
-## Primary Workflow
-
-**ALWAYS execute scripts in this order:**
-
-```bash
-# 1. DETECT query type (topic-specific vs general)
-node scripts/detect-topic.js "<user query>"
-
-# 2. FETCH documentation using script output
-node scripts/fetch-docs.js "<user query>"
-
-# 3. ANALYZE results (if multiple URLs returned)
-cat llms.txt | node scripts/analyze-llms-txt.js -
-```
-
-Scripts handle URL construction, fallback chains, and error handling automatically.
-
-## Scripts
-
-**`detect-topic.js`** - Classify query type
-- Identifies topic-specific vs general queries
-- Extracts library name + topic keyword
-- Returns JSON: `{topic, library, isTopicSpecific}`
-- Zero-token execution
-
-**`fetch-docs.js`** - Retrieve documentation
-- Constructs context7.com URLs automatically
-- Handles fallback: topic → general → error
-- Outputs llms.txt content or error message
-- Zero-token execution
-
-**`analyze-llms-txt.js`** - Process llms.txt
-- Categorizes URLs (critical/important/supplementary)
-- Recommends agent distribution (1 agent, 3 agents, 7 agents, phased)
-- Returns JSON with strategy
-- Zero-token execution
-
-## Workflow References
-
-**[Topic-Specific Search](./workflows/topic-search.md)** - Fastest path (10-15s)
-
-**[General Library Search](./workflows/library-search.md)** - Comprehensive coverage (30-60s)
-
-**[Repository Analysis](./workflows/repo-analysis.md)** - Fallback strategy
-
-## References
-
-**[context7-patterns.md](./references/context7-patterns.md)** - URL patterns, known repositories
-
-**[errors.md](./references/errors.md)** - Error handling, fallback strategies
-
-**[advanced.md](./references/advanced.md)** - Edge cases, versioning, multi-language
-
-## Execution Principles
-
-1. **Scripts first** - Execute scripts instead of manual URL construction
-2. **Zero-token overhead** - Scripts run without context loading
-3. **Automatic fallback** - Scripts handle topic → general → error chains
-4. **Progressive disclosure** - Load workflows/references only when needed
-5. **Agent distribution** - Scripts recommend parallel agent strategy
-
-## Quick Start
-
-**Topic query:** "How do I use date picker in shadcn?"
-```bash
-node scripts/detect-topic.js "<query>"  # → {topic, library, isTopicSpecific}
-node scripts/fetch-docs.js "<query>"    # → 2-3 URLs
-# Read URLs with WebFetch
-```
-
-**General query:** "Documentation for Next.js"
-```bash
-node scripts/detect-topic.js "<query>"         # → {isTopicSpecific: false}
-node scripts/fetch-docs.js "<query>"           # → 8+ URLs
-cat llms.txt | node scripts/analyze-llms-txt.js -  # → {totalUrls, distribution}
-# Deploy agents per recommendation
-```
-
-## Environment
-
-Scripts load `.env`: `process.env` > `$HOME/.copilot/skills/docs-seeker/.env` > `$HOME/.copilot/skills/.env` > `$HOME/.copilot/.env`
-
-See `.env.example` for configuration options.

package/templates/repo/.github/skills/docs-seeker/references/context7-patterns.md

@@ -1,64 +0,0 @@
-# context7.com URL Patterns
-
-## Topic-Specific URLs (Priority #1)
-
-**Pattern:** `https://context7.com/{path}/llms.txt?topic={keyword}`
-
-**When to use:** User asks about specific feature/component
-
-**Examples:**
-```
-shadcn/ui date picker
-→ https://context7.com/shadcn-ui/ui/llms.txt?topic=date
-
-Next.js caching
-→ https://context7.com/vercel/next.js/llms.txt?topic=cache
-
-FFmpeg compression
-→ https://context7.com/websites/ffmpeg_doxygen_8_0/llms.txt?topic=compress
-```
-
-**Benefits:** Returns ONLY relevant docs, 10x faster, minimal tokens
-
-## General Library URLs (Priority #2)
-
-**GitHub repos:** `https://context7.com/{org}/{repo}/llms.txt`
-
-**Websites:** `https://context7.com/websites/{normalized-path}/llms.txt`
-
-## Known Repository Mappings
-
-```
-next.js → vercel/next.js
-nextjs → vercel/next.js
-astro → withastro/astro
-remix → remix-run/remix
-shadcn → shadcn-ui/ui
-shadcn/ui → shadcn-ui/ui
-```
-
-## Official Site Fallbacks
-
-Use ONLY if context7.com unavailable:
-```
-Astro: https://docs.astro.build/llms.txt
-Next.js: https://nextjs.org/llms.txt
-Remix: https://remix.run/llms.txt
-SvelteKit: https://kit.svelte.dev/llms.txt
-```
-
-## Topic Keyword Normalization
-
-**Rules:**
-- Lowercase
-- Remove special chars
-- Use first word for multi-word topics
-- Max 20 chars
-
-**Examples:**
-```
-"date picker" → "date"
-"OAuth" → "oauth"
-"Server-Side" → "server"
-"caching strategies" → "caching"
-```