lagz0ne
- 7 skills
- 0 followers
- 22 hours ago last updated
- ▌ Matched Abstraction · lagz0neUse when design, planning, implementation, or delegation risks mixing abstraction layers or skipping from high-level intent to detail too quickly; triggers include architecture decisions, design artifacts, testing strategy, implementation plans, task handoffs, layered docs, orchestration, decomposition, verification strategy, artifact-set refinement, derive/match review surfaces, and strategy-to-execution drift.
- ▌ Triage Three · lagz0ne bundleThis skill should be used when the user asks for adversarial code review, security audit, bug triage, architecture review, or any deep analysis that benefits from multiple perspectives challenging each other. Trigger phrases include: 'triage this', 'find bugs in', 'security audit', 'review this code', 'adversarial review', 'find vulnerabilities', 'audit this for', 'review this PR for correctness'. Uses three adversarial roles (Pusher finds, Challenger questions, Arbiter decides) with style presets (measured, wide-funnel, paranoid, baseline, max-tension).
- ▌ Autoresearch · lagz0ne bundleExperiment loop discipline for autoresearch sessions — decision rules, git workflow, JSONL logging, benchmark metrics, anti-patterns
- ▌ Null Hypothesis · lagz0ne bundleKeep claims about complex or failure-prone software honest by testing the direct opposite, preserving earlier behavior, and reporting measured limits. Use when correctness, performance, reliability, concurrency, or safety claims could pass by luck or weak evidence; avoid for straightforward low-risk edits.
- ▌ Reverse Tornado Okr · lagz0ne bundlePlan or run a measured goal loop with anti-goal guardrails. Planning mode drafts metrics, discovery, and work structure without changing the workspace. When the user asks to run, delegate, automate, or resume the loop, execution mode may run bundled local helper scripts, write durable `.okra` records, spawn subagents, and optionally route writer work through an already-installed Codex or Claude CLI. Use for OKRs, metric-led improvement, bounded research, or progress that must preserve budget, quality, safety, trust, or another measured constraint. All actions remain inside the user's request and runtime permissions; the skill does not install tools, add credentials, grant authority, or contact external services on its own.
- ▌ Codex · lagz0neDelegate well-scoped coding, analysis, and review tasks to the OpenAI Codex CLI (gpt-5.5) as a cross-model collaborator. Use for implementation chunks you want a second model to write or cross-check, independent second-opinion review of a design or diff, and applying Codex-authored changes. Triggers: "ask codex", "have codex implement/review X", "second opinion from codex", "cross-check with codex".
- ▌ C3 · lagz0ne bundleTriggers on /c3 or architecture questions in projects with .c3/ directory. Phrases: "adopt C3", "onboard", "where is X", "audit architecture", "check docs", "add component", "implement feature", "what breaks if I change X", "add ref", "coding standard", "edit the canvas", "add prd/user-story". Ops: onboard, query, audit, change, ref, rule, canvas, sweep. The CANVAS is your architecture's own vocabulary; onboarded facts FREEZE; work advances by change-units. Classifies intent, loads the reference, runs the CLI.