LumenHelixLab

Versioning, changelogs, releases, migration notes, compatibility, deprecations, and adapter sync.

Use when routing across the full 187SKILLS suite or the NATASHA multi-agent integration stack (THREAD, COMPRESS, TENSION, SPARK, CORD, SCOUT, LAB, FUSE).

Use for EVM-first smart-contract assurance, DeFi economic risk analysis, severity/confidence separation, and responsible disclosure (no live keys or exploits).

Use for quantum algorithm selection, circuit design, optimization, resource estimation, and claim-disciplined audits (no unsupported advantage claims).

Use when generating a new repository, deploying to GitHub, creating an installer site, or routing the 187SKILLS suite.

Use when adding delight, micro-interactions, onboarding, community, or retention to a 187WEB project.

Use when routing across the full 187SKILLS suite or the NATASHA multi-agent integration stack (THREAD, COMPRESS, TENSION, SPARK, CORD, SCOUT, LAB, FUSE).

Use when compiling the 187SKILLS manifest, selecting a prompt, or routing a Layer-4 viral/elegant prompt.

Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.

Execute work efficiently while maintaining quality and finishing features

Build AgentDock Coach and portfolio chat UIs with assistant-ui. Use when upgrading the advisor panel, adding generative UI for launch commands, or scaffolding chat in agentdock/ui. Triggers: "coach UI", "chat panel", "assistant-ui", "Hey Coach".

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. In interactive mode it applies safe, verified fixes and commits them when the working tree is clean (it never pushes); in mode:agent it reports only and the caller applies. Use when reviewing code changes before creating a PR.

Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.