Problem-solving strategies for predicate logic in mathematical logic

Problem-solving strategies for proof theory in mathematical logic

Problem-solving strategies for propositional logic in mathematical logic

Problem-solving strategies for integration theory in measure theory

Problem-solving strategies for sigma algebras in measure theory

Problem-solving strategies for numerical integration in numerical methods

Problem-solving strategies for root finding in numerical methods

Problem-solving strategies for boundary value problems in odes pdes

Problem-solving strategies for second order odes in odes pdes

Problem-solving strategies for constrained optimization in optimization

Problem-solving with Rudin's Real and Complex Analysis textbook

Problem-solving strategies for open sets in topology

Research-to-implement pipeline chaining 5 MCP tools with graceful degradation

MCP Script Rules

Migration workflow - research → analyze → plan → implement → review

Modular Code Organization

Search library documentation and code examples via Nia

OPC Architecture Understanding

Planning agent that creates implementation plans and handoffs from conversation context

Formal theorem proving with research, testing, and verification phases

Check reference SDK implementations using btca ask

Release preparation workflow - security audit → E2E tests → review → changelog → docs

Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase

Research agent for external documentation, best practices, and library APIs via MCP tools

External research workflow for docs, web, APIs - NOT codebase exploration

Document codebase as-is with thoughts directory for historical context

Resume work from handoff document with context analysis and validation

Comprehensive code review workflow - parallel specialized reviews → synthesis

Search Tool Hierarchy

Meta-skill for creating and managing Claude Code skills

Skill Development Rules

Create and use Claude Code slash commands - quick prompts, bash execution, file references

TDD workflow for migrations - orchestrate agents, zero main context growth

Test-driven development workflow with philosophy guide - plan → write tests → implement → validate

Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.

Friendly onboarding when users ask about capabilities

Wiring Verification

Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.

Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.

Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.

Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.

Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.

Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.

Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.

Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.