ajbm-dev

Plugin ajbm-dev from marketplace ajbm in ajbmachon/ajbm-skills. Commands read from the repo's manifest — 1 month ago.

Skills (15)

• SkillDistiller

  USE WHEN distill, extract skill, capture patterns, teach from conversation, learn from session, skill from conversation. Analyzes conversations to extract user guidance patterns — corrections, questions, quality gates, analysis modes — and collaboratively distills them into permanent, replayable ski

• be-creative

  USE WHEN brainstorm, generate options, break out of default thinking, need diverse alternatives, explore creative angles, the first answer feels too obvious, name something, come up with hooks, find unconventional approaches. Applies Verbalized Sampling (Zhang et al., 2024) — generate multiple low-p

• content-analysis

  USE WHEN extract wisdom, analyze video, analyze podcast, analyze article, extract insights, key takeaways, what did I miss, extract from YouTube, content analysis, insight report. Content-adaptive wisdom extraction — detects what domains exist in the content and builds custom sections (not static ID

• pai-skill-transfer

  USE WHEN transferring a PAI skill to a standard Claude Code plugin, porting skills between environments, strip PAI specifics, adapt PAI skill for marketplace, extract skill from PAI. Guides the transformation of PAI-embedded skills into standalone plugin-compatible skills — strip PAI-specific scaffo

• prompt-craft

  USE WHEN improve prompt, write prompt, craft prompt, analyze prompt, prompt engineering, subagent prompts. Analyze, craft, and improve prompts using 19 research-backed techniques. Modes - Analyze (critique existing), Craft (build from scratch), Teach (explain techniques), Quick Fix (fast improvement

• setup-linter

  USE WHEN setup automatic linting, add linter hook, configure code formatting on completion, enable lint on save. Auto-detects project type (JS/Python/Rust/Go/Deno/Biome), installs linter if missing, creates config with sensible defaults, wires a Stop hook in .claude/settings.json.

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

• test-driven-development

  Use when implementing any feature or bugfix before implementation changes. Enforces test-first behavior: write a failing test, verify failure, implement minimal code, and prove green.

• testing-best-practices

  Use when writing, reviewing, or reporting tests. Enforces trustworthy testing through the Testing Trophy strategy, 15 evidence-based principles, disciplined mocking, AI oracle prevention, anti-pattern detection, and honest execution reporting. Applies to unit, integration, and e2e test work.

• thinking

  Multi-mode analytical thinking — first principles decomposition, iterative depth analysis, multi-agent council debates, adversarial red teaming, and scientific hypothesis testing. USE WHEN first principles, decompose, deconstruct, challenge assumptions, iterative depth, multi-angle, deep exploration

• council

  Multi-agent debate with visible transcripts where specialized agents respond to each other. USE WHEN council, debate, perspectives, weigh options, deliberate, multiple viewpoints, collaborative critique. Collaborative-adversarial — use Red Team for purely adversarial attack.

• first-principles

  Decompose to axioms, challenge inherited assumptions, reconstruct from verified truths. USE WHEN first principles, fundamental, root cause, decompose, deconstruct, challenge assumptions, rebuild from scratch, question everything.

• iterative-depth

  Structured multi-angle exploration — 2-8 scientific lens passes over the same problem to surface requirements single-pass analysis misses. USE WHEN iterative depth, deep exploration, multi-angle analysis, multiple perspectives, examine from angles, surface hidden requirements, lens analysis, deeper

• red-team

  Adversarial analysis using parallel agents to find fatal flaws in arguments. Produces steelman plus counter-argument. USE WHEN red team, attack idea, counterarguments, critique, stress test, poke holes, devil's advocate, find weaknesses, break this, parallel analysis, adversarial validation.

• science

  Hypothesis-test-analyze cycles for systematic problem-solving — the meta-pattern underlying all the other thinking modes. USE WHEN think about, figure out, try approaches, experiment with, iterate on, improve, optimize, define goal, generate hypotheses, design experiment, measure results, analyze re

Subagents (2)

• clean-code-reviewer

  Use this agent when you need to review code for adherence to Robert C. Martin's Clean Code principles. Trigger this agent:\n\n- After implementing a new feature or module\n- Before committing significant code changes\n- As part of orchestrated code documentation with subagents\n- During code review

• docs-research-specialist

  Use this agent when you need to look up current software documentation, API syntax, library usage patterns, or best practices that may be beyond your training data. This agent should be invoked proactively whenever working with libraries, frameworks, or APIs where accuracy and currency are critical

Similar plugins