Explorar skills

Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do

Avoid common mistakes and debug issues in PydanticAI agents. Use when encountering errors, unexpected behavior, or when reviewing agent implementations.

Advanced React Flow patterns for complex use cases. Use when implementing sub-flows, custom connection lines, programmatic layouts, drag-and-drop, undo/redo, or complex state synchronization.

Use when you have a finalized `beagle-analysis:brainstorm-beagle` spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: \"write a plan\", \"plan this spec\", \"turn the spec into a plan\", \"now plan the implementation\", \"/write-plan\". Reads the spec, designs the file structure, decomposes work into 2-5 minute TD

The technology design process from needs assessment through iteration, covering empathy mapping, design briefs, concept development, prototyping, user testing, and iterative refinement. Integrates design thinking methodology (Stanford d.school) with engineering design process (ITEEA) and Don Norman's human-centered design principles. Use when designing technology solutions, evaluating existing des

Converts vague ideas into concrete, testable specifications with acceptance criteria. No implementation begins without a spec.

Build in verifiable increments. Never implement more than can be tested right now. Ship partial working systems over complete broken ones.

Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.

Safe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct.

Red-green-refactor cycle with meaningful coverage. Tests are written before implementation. Coverage is a side effect of good tests, not the goal.

Use when encountering any bug, test failure, unexpected behavior, or error message — before proposing any fixes. Also use when you see tracebacks, exceptions, "not working" complaints, build failures, performance problems, or integration issues. If you're tempted to "just try changing X and see if it works", this skill applies. Systematic root cause investigation always comes before fix attempts.

Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze ste