Results for “john-locke”

Navigate legal strategy with contracts, compliance, IP protection, and corporate governance.

Write reliable Go code avoiding goroutine leaks, interface traps, and common concurrency bugs.

Ranks weekly token unlocks by Absorption Ratio (unlock value / 7d avg volume) instead of supply percentage, with per-event cliff vs linear classification, recipient category, and a one-line market read.

Expert in creating opening lines, thumbnails, and hooks that stop the scroll. Covers curiosity gaps, pattern interrupts, emotional triggers, and platform-specific hooks. Knows how to earn attention in the first 3 seconds without resorting to clickbait. Use when "hook, opening line, scroll stopper, headline, first line, attention grab, thumbnail, clickable, " mentioned.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

Logic (akao-logic)

Freeze

Freeze

Root cause analysis skill — diagnose bugs systematically before fixing. Iron Law: no fix without a confirmed hypothesis. Uses scope lock, 3-strike escalation, and structured debug reports.

Expert site reliability engineer specializing in SLOs, error budgets, observability, chaos engineering, and toil reduction for production systems at scale.

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

Use when creating hooks for Claude Code plugins. Covers hook events, configuration, exit codes, and stdin/stdout contracts. Hooks execute in response to events to validate operations and enforce policies.

Call Apex methods imperatively from Lightning Web Components for button clicks, lifecycle hooks, and conditional logic, covering import syntax, cacheable vs non-cacheable methods, async/await patterns, error handling, loading states, and parallel calls with Promise.all.