bee

Skills

21 in the Claude listing

• Ai ergonomicsThis skill should be used when evaluating how well code supports LLM-assisted development.
• Ai workflowThis skill should be used when explaining why Bee follows spec-first TDD workflows, or when teaching mode is on.
• Architecture patternsThis skill should be used when evaluating architecture options, checking dependency direction, or deciding between onion, MVC, and simple patterns.
• Bee stateThis skill should be used when updating workflow state in bee-state.local.md.
• Boundary generationThis skill should be used after discovery completes on a greenfield project when the discovery document contains a Module Structure section.
• brainstormingThis skill should be used when the user wants to brainstorm, explore ideas, think through options, says 'let's brainstorm', 'what are our options', 'how might we', 'what if we', 'help me think through
• Browser testingThis skill should be used when running browser-based verification.
• Clean codeThis skill should be used when writing, reviewing, or refactoring code.
• Code reviewThis skill should be used when performing code reviews, analyzing git hotspots, or detecting coupling.
• Collaboration loopThis skill should be used when processing @bee annotations in documents or managing [ ] Reviewed gates.
• debuggingThis skill should be used when diagnosing failures, fixing bugs, or investigating why tests don't pass.
• Design fundamentalsThis skill should be used when making UI/UX decisions, designing layouts, choosing colors and typography, writing UI specs, or reviewing visual components.
• Grill meInterview the user relentlessly about a plan, design, or idea until reaching shared understanding.
• Grill me with contextInterview the user about a plan or design with full codebase context.
• Lsp analysisThis skill should be used when performing precise dependency analysis with LSP tools.
• Model tiersThis skill should be used when an orchestrator needs to choose or resolve a model for a delegated agent — i.e.
• Requirement architectRewrites software requirements to lead to better code design and architecture.
• Resolve m conflictsThis skill should be used when resolving git merge conflicts.
• Spec writingThis skill should be used when writing specs, acceptance criteria, or slicing features into vertical slices.
• Tdd practicesThis skill should be used when writing a TDD plan, reviewing test quality, choosing between unit and integration tests, or applying red-green-refactor.
• Try it yourselfThis skill should be used after all slices are verified and before review.