Results for “proguard”

Prevents destructive operations on production systems and restricts file edits to a specific directory when running agents autonomously.

Forces AI agents to investigate before editing or running destructive commands, improving code quality by requiring concrete facts like importers, data schemas, and user instructions.

Blocks Edit/Write/Bash actions until the agent presents concrete facts about imports, data schemas, and the user's instruction, improving output quality.

Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.

Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.

Full safety mode: destructive command warnings + directory-scoped edits. (gstack)

Guides AI agents to apply advanced mathematical and probabilistic techniques (Bloom filters, HyperLogLog, FFT, etc.) for large-scale data problems where classical algorithms are optimal but math offers better asymptotic bounds.

Full safety mode: destructive command warnings + directory-scoped edits. (gstack)

Use this skill to prevent destructive operations when working on production systems or running agents autonomously.

Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.

JS Proxy Pattern

Full safety mode: destructive command warnings + directory-scoped edits. (gstack)

Runs before every git commit on heleni-memory. Checks: no credentials in tracked files, no oversized files, valid SKILL.md frontmatter for any new/modified skill. Triggers: "commit", "before push", "validate repo", or auto-runs as a git pre-commit hook.

Use when implementing c functionality with production-grade patterns and safeguards.

Detects drift between declared reality (docs, manifests, inventories, ADRs) and actual reality (filesystem, git state, dependencies, hooks) on session start, reporting findings with severity and evidence.

Use when implementing hr functionality with production-grade patterns and safeguards.

Use to design and measure proactive outbound support that prevents inbound contacts without creating new ones. Trigger for "proactive support", "prevent tickets with outbound", outage notifications, shipment alerts, eligibility and suppression rules, measuring prevented contacts, or proactive messaging opt-out.

GOF Proxy Pattern

Use when implementing python functionality with production-grade patterns and safeguards.

Post-execution skill crystallization and learning engine updates for WinDAGs. Runs after successful execution to update Thompson sampling parameters, track method quality, detect monster-barring, log near-miss events, and signal Kuhnian crises. Activate on "curator", "learning update", "skill crystallization", "Thompson sampling", "monster-barring", "near-miss", "Kuhnian crisis", "post-execution learning". NOT for pre-execution risk scanning (use windags-premortem), retrospective analysis (use windags-looking-back), or DAG construction (use windags-architect).

Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)

Imported skill store from langchain

Proactive self-monitoring of infrastructure, services, and health. Tracks disk/memory/load, service health, cron job status, recent errors. Auto-fixes safe issues. Triggers on: health check, heartbeat, monitor status, service status, infrastructure check.

Use when implementing julia functionality with production-grade patterns and safeguards.

Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use when developers want to optimize their app's size, remove redundant or overly broad keep rules, or troubleshoot Proguard configurations.